Short game development tips

A list of short tips

September 22nd, 2018 · 2 min read

#Tips #Short

The last couple of months we've been sharing short and sweet game development tips on our Twitter profile. Here's all of them, slightly expanded. Let us know if you've got a great tip yourself!

1. Staying organized

Schedule a couple of hours to clean a project that has gone through a few iterations, in the process there's a huge chance you'll find duplicate files or unconver possible optimizations.

Not using version control for a project? Make sure to never remove files, move them to a folder outside of the project for safety.

Original tweet

2. Playtest soon and often

Nothing beats good quality feedback from players, game designers and other developers. The only way to gain this feedback is to get others to play your game. Look outside of your usual network for more honest feedback, don't take criticism personal but instead use it to improve your game.

Original tweet

3. Join a community

Other developers are your friends! Treat them with respect and you'll find that most will be able to help you out when you're stuck or need feedback on your game. Join a game development Discord or community for instant help.

Original tweet

4. Create a plan

Planning before starting development is a good idea (and you know it) but don't worry if your game design document isn't a 100-page behemoth. Create a simple tasklist, a moodboard or write some notes. Anything helps!

Original tweet

5. Details

Don't get trapped spending hours on details when the rest of the game isn't anywhere near finished. Try creating both the start and end of the game (or level, world, etc.) and make sure the player can play from beginning to end, then start filling in the gaps.

Original tweet

6. Never stop learning

There's tons of resources which offer videos, articles, and tips. We've collected a bunch of great videos for you. Follow news sources to stay on top of the latest game trends!

Original tweet

7. Getting stuck is not a problem

Stuck on a bit of code or part of your game? Take a break and return to it later, see if there's other elements that you can focus on for a while. You'll find that you might be able to finally fix that one bug once you've taken a break from it.

Original tweet

Library Discuss on Discord