To sum everything up: I try to be very thorough with my planning and testing. As a developer, it is impossible to 100% put yourself in a player’s shoes, so it’s best to just get actual players to do it for you. Don’t make the common mistake of spending months making a game only to realize that you’ve accidentally been making the game for yourself rather than the average player. Testing frequently with diverse groups of players is important as you’ll figure out if your game needs to be changed earlier rather than right before release. Test often, collect feedback (not just from your own friends), tweak and create more things, repeat. Moreover, rapid development and testing are extremely helpful, as feedback is very precious when it comes to making a game. For me, if I ever feel like I’m in a phase of aimlessness while developing (where I struggle to think of things to do or how to execute them), it helps a lot to switch my brain to “manager mode”, where I make a list of specific tasks for myself based on what I know has to be done. Many games fall apart because developers don’t understand how to be their own managers/bosses. Try to keep polish towards the end of the game-making process. Generally, you’ll want to focus on creating and perfecting the core of your game prior to creating multiple levels or other game systems. It’s very important to map out each step of the development process, and then map out those individual steps to be specific once you get to them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |