IROG'S PROFILE

Another way to teach the players about a useful skill is to use that skill against them. The player starts without the guard skill. Then, you setup a fight where the enemy uses the guard skill and retaliates strongly on the player, making this fight difficult. An enemy using an efficient skill that the player lacks makes that skill desirable. Shortly after the player gains that skill. You then make sure the player fights the same enemy and that guarding makes the fight easy.

As we test our game ourselves many many times, we become extremely efficient at beating the AI we coded. You are the most hardcore player of your own game. To make your game accessible to others, its initial difficulty should feel to you as "This is too easy".

The indoor lighting looks great but the orientation of the outdoor incoming light is not consistent. All projected light should be parallel.

Here is a quick sketch to illustrate:

You can convert the links in your first post in MP3 using http://www.youtube-mp3.org/us

Multiples downloads tend to confuse players. The only good reason to have multiple downloads is when you created platform specific builds of your game (for example: one download for Windows, one download for Linux). You can keep your development versions on your local drive for debugging purpose. Keeping one or two old stable versions should be fine.

author=XBuster
you can edit the midi track's instruments with your preferred program and MP3s altogether.

What program do use / recommend?

Yes, the Extra Credits (and Extra History) videos are very informative. This week they talk about what we do: make games non commercially. And the narrator high-pitched voice is the result of playing his recoding faster than it was recorded. They probably play a 10 minutes recoding over a 7 minutes video.

You have the same strategy as me about play-testing: hunting down bugs yourself before players experience the game. And at the same time, you need to know if the content you create is enjoyable.

I usually focus my reviews on how game mechanic and game content create good or bad play experiences. As I lack artistic and musical skills my reviews don't dig deep in those areas. If you need more of my feedback, I'll be happy to help when you need it.

Good ideas comes from discussion and experimentation. It's because you built (maybe by accident) the gambler exploit that I thought it was a good idea. To point out good idea you simply ask yourself: is this good or bad for the player?

Story time: I'm a hobbyist programmer and I once incorrectly programed the game quit function. I could not quit the game anymore or the game would quit without a quit request. Pretty bad, isn't it? At that time yes. But I wondered if it would always be so. In the development of H16 (renamed Red Balloon of Happiness thanks to Luiishu535) I reused the two "incorrect quit behaviors" as features because they fit some particular aspect of the game. It is always up to you, the developer, to decide if a particular game behavior contribute to the experience you want to create.