What my partner and I do is that we have a set of default codes and sprites that are going to be in the game no matter what. So when the topic is announced, I make all the defaults while he comes up with a game idea. Once we have our idea I start putting code together while he gives constant feedback on whether something is too fast, too slow, too big, etc. Once we're done he redesigns the sprites and troubleshoots.Game On is my team's worst event, and the people doing it are confused on two things. One is that they don't understand why the event allows two people and how to capitalize on that (they say one person codes and the other person sits there looking pretty). The other is how to practice and improve at this event. If someone could answer these it would be much appreciated.
Users browsing this forum: No registered users and 1 guest