|
|
|
|
|
by kd5bjo
2513 days ago
|
|
If you have a computer science/programming background, don’t worry too much about the skills you listed— they’re not ultimately that different than what you’ve already learned and you can pick them up as needed. The game design skills are probably what you should be focusing on first: as far as I know, nobody knows how to teach them and the only way to learn is to make (bad) games yourself. Come up with a small idea, make a prototype, and play it. Ask yourself which parts are fun and which parts aren’t; make an adjustment and try again, or start over with a different game idea. As you go through this process, you’ll necessarily need to acquire some technical skills, but they’ll each be in support of a specific outcome. More importantly, you’ll start to understand how your decisions at the design/programming stage affect the players’ experience. |
|
In terms of self-education, I would recommend to play as many games as possible, and play them twice. The first, as a player: develop an emotional connection with the experience. The second, as a designer: look at everything under a magnifying glass and never stop asking "why did they do this the way they did?" Hope that helps, just my 2 cents.