Jonas Tyroller | Most Annoying Game Dev Mistake That Just Keeps Happening! @JonasTyroller | Uploaded August 2018 | Updated October 2024, 3 hours ago.
This is a video about how to make a game when you already know how to make one.
For me there seems to be a big gap between how I actually develop games and how I think you should go about creating a video game.
That makes my knowledge about game development absolutely utterly useless, because I simply don't seem to use it.
Why is that? And how can you prevent yourself from making this mistake?
So far I have three ideas how to fix this problem:
A) Writing a detailed production plan how I want to go about developing my next game, before I get started with the actual production. Once I get started I'm usually in tunnel vision mode and it's too late. You fall in love with an idea and suddenly playtesting or creating a couple more prototypes seems unnecessary, but not doing that is obviously a big mistake. During development you should strictly follow your plan step by step.
B) Finding some people that hold you accountable for your actions. Share your values with your audience or your friends, so they can tell you when you get off track. This is also why it's a lot easier not to mess your development process up when making games in a team.
C) Take some time to reflect on your actions every now and then. Is your knowledge still in sync with your actions? If not, correct course. Maybe it could be a good idea to write a little checklist for this. Something like: No feature creep, no over-scoping, at least one playtest, tried different solutions for design problems, etc.
Do you struggle with this problem as well when making games or are your actions always in sync with you knowledge?
Which one of those ideas do you think will be most effective or which additional ideas and tips do you have?
I don't want to do these mistakes again, so I count on your feedback. :)
This is a video about how to make a game when you already know how to make one.
For me there seems to be a big gap between how I actually develop games and how I think you should go about creating a video game.
That makes my knowledge about game development absolutely utterly useless, because I simply don't seem to use it.
Why is that? And how can you prevent yourself from making this mistake?
So far I have three ideas how to fix this problem:
A) Writing a detailed production plan how I want to go about developing my next game, before I get started with the actual production. Once I get started I'm usually in tunnel vision mode and it's too late. You fall in love with an idea and suddenly playtesting or creating a couple more prototypes seems unnecessary, but not doing that is obviously a big mistake. During development you should strictly follow your plan step by step.
B) Finding some people that hold you accountable for your actions. Share your values with your audience or your friends, so they can tell you when you get off track. This is also why it's a lot easier not to mess your development process up when making games in a team.
C) Take some time to reflect on your actions every now and then. Is your knowledge still in sync with your actions? If not, correct course. Maybe it could be a good idea to write a little checklist for this. Something like: No feature creep, no over-scoping, at least one playtest, tried different solutions for design problems, etc.
Do you struggle with this problem as well when making games or are your actions always in sync with you knowledge?
Which one of those ideas do you think will be most effective or which additional ideas and tips do you have?
I don't want to do these mistakes again, so I count on your feedback. :)
