ah, ok. See i wasn't even thinking in terms of states. I was just thinking of the actaul game programming. Should we assign each one to everyone, so we dont end up doing the same one? (for the exception of the actual game) If so, whos all in for this part to be assigned?

If someone comments on an issue saying they would like to work on it go ahead and assign them (or state you want to do something and assign yourself). No worries. I just threw it up so that people might go, "hey, I want to work on that," and we would start moving forward.

Basically all you need to do to add a State is add the appropriate import and modify the dictionary in the main module. If you are doing the splash screen you should be able to use the placeholder Title State as a template. Obviously the state module itself goes in the State directory.

im not sure how to do like a pull request to my own repo, lol. It would be good to just show the code, but i would assume it would just update the repo. And i dont want to just push what i have cuz it could just be crap, and wanting the old back, hmm but then again, its mostly just one file that i added. i guess i will just post the code here for now.

i couldnt find where you loaded all the images to? i also assumed at first the directory would be hard coded in that function, otherwise i had to put it splash independently. i loaded them separetly, because i wasnt sure, your function laods all the images and it seemed moot to load all images on every state, so i just put a temp independent load image in.

But now i was expecting the background (hot pink) of those images to be transparent, but they show up hot pink. Obviously i missed something.

oh and uh yeah, i know it looks like a lawn mower hit it, but that is why i didnt want to push it

Edit: In the future it might be necessary to change the resource loading so that the states pass the resources around. It depends how deep our directory structure gets. We don't want to have to start doing things like:

i pushed a basic splash page, havent gotten to fading in. The only problem i had with it, is it needs not only x number of seconds, but it appears to also need input. I am not sure why though. (at this point)

Again, my fault for not providing enough documentation. All States have an attribute self.start_time which is initialized to the current time every time we switch to that state, so no need for a new timer in this case. Also you don't need the self.next_state flag. Since the splash can only go to one other state, set self.next in the init, then just set self.done to True when it needs to be.

should we merge all the splash images into one? It seems kind of overdoing it with multiple images, and text. the only good thing is switching out images, for example, i put the python-forum.org logo in there, but that is not necessarily our logo though.

Yeah you could rearrange those all into one image. We can move them around later if we'd like. I just pushed a minor change to yours. The time out needed to go within the update function. Things in the get_event function will only run IF control has an event to pass down.

Just makes things look professional. Most games have a company logo screen that appears first before the actual title screen of their game. Strictly speaking, no, it isn't necessary; but strictly speaking, most things aren't. I think a quick fade in title screen with (eventually) some sort of accompanying soundeffect/music gives a strong impression (and later if it can be used to hide resource loading time, so much the better).