My 2nd homebrew game demo
Moderator: Moderators
My 2nd homebrew game demo
This time we've gone to a simpler game: Simon. I dubbed this project Siamond due to the way the game board is laid out.
This game was a pretty quick one to make and the demo here is more or less the whole game. I might add some stuff, but the overall game is pretty much here.
Link:
http://www.nintendoage.com/media/_userm ... ond2%2Ezip
This game was a pretty quick one to make and the demo here is more or less the whole game. I might add some stuff, but the overall game is pretty much here.
Link:
http://www.nintendoage.com/media/_userm ... ond2%2Ezip
Very nice. It works on my emulator.
You did a great job. I like this kind of game.
You did a great job. I like this kind of game.
Zepper
RockNES author
RockNES author
Gets a bit frantic once the sequence gets of a decent length (I got to 16). Overall, it's clean. I saw no momentary vertical scrolling issues lots of homebrew games have, when switching screens. Some specific critique:
"At the start of the game, a sequence of colors begins. The player must repeat this sequence perfectly. [...] once a player inputs a wrong part of the sequence, the game is over."
Talking about the player in third-person is inappropriate when the text is meant for the player to read. Talk about the player in the first-person: "You must repeat this sequence perfectly. Once you input a wrong part of the sequence..."
Also, don't change verb tense in mid-sentence: "On every successful repetition, a new, random color will be added to the sequence and the process repeats." Either change "will be" to "is", or change the last word from "repeats" to "repeated", so that you have "will be ... repeated". I prefer the former, since "is" is more assertive than "will be".
In general, your instructions read more like a design document for the game. The following seems much more friendly (and concise) to a player just interested in how to play:
"Your goal is to remember then repeat the sequence of colors shown before you, using the d-pad. Each time you succeed, a new step is added to the sequence. The game ends when you make a mistake."
Technically, would it be possible to queue d-pad input so that the player can input the sequence as fast as he likes, rather than having to wait for the game to highlight that color? This would involve polling the d-pad inside the NMI handler, and keeping track of presses in a small queue. I might post some code that shows how to do this cleanly. It could be frustrating to know you entered it correctly, but the game was too slow to keep up.
"At the start of the game, a sequence of colors begins. The player must repeat this sequence perfectly. [...] once a player inputs a wrong part of the sequence, the game is over."
Talking about the player in third-person is inappropriate when the text is meant for the player to read. Talk about the player in the first-person: "You must repeat this sequence perfectly. Once you input a wrong part of the sequence..."
Also, don't change verb tense in mid-sentence: "On every successful repetition, a new, random color will be added to the sequence and the process repeats." Either change "will be" to "is", or change the last word from "repeats" to "repeated", so that you have "will be ... repeated". I prefer the former, since "is" is more assertive than "will be".
In general, your instructions read more like a design document for the game. The following seems much more friendly (and concise) to a player just interested in how to play:
"Your goal is to remember then repeat the sequence of colors shown before you, using the d-pad. Each time you succeed, a new step is added to the sequence. The game ends when you make a mistake."
Technically, would it be possible to queue d-pad input so that the player can input the sequence as fast as he likes, rather than having to wait for the game to highlight that color? This would involve polling the d-pad inside the NMI handler, and keeping track of presses in a small queue. I might post some code that shows how to do this cleanly. It could be frustrating to know you entered it correctly, but the game was too slow to keep up.
Last edited by blargg on Sun Feb 24, 2008 9:35 pm, edited 1 time in total.
Diss my grammar will you?
Well, I may change how it's written. I basically wrote something in a text file I felt made sense. I really didn't think too many would even bother reading the instruction screen since, unlike my other game Geminim, Simon is probably more widely-known. I just put it there as a formality, heh.
As for the speedy input, I would probably have to modify the code rather significantly to do it that way. Right now it looks at what you input, waits 10 frames to show you what you pressed and play the tone, then lets you press another. I originally had this at 15, but to me that seemed slow. 10 seemed more than fair. I could probably lower it to 7 or even 5 if that still seems high.
Roth: Make it your next EOR power. 8)
Well, I may change how it's written. I basically wrote something in a text file I felt made sense. I really didn't think too many would even bother reading the instruction screen since, unlike my other game Geminim, Simon is probably more widely-known. I just put it there as a formality, heh.
As for the speedy input, I would probably have to modify the code rather significantly to do it that way. Right now it looks at what you input, waits 10 frames to show you what you pressed and play the tone, then lets you press another. I originally had this at 15, but to me that seemed slow. 10 seemed more than fair. I could probably lower it to 7 or even 5 if that still seems high.
Roth: Make it your next EOR power. 8)
Sorry, if I had realized you didn't want critique aimed at improving it, I would have avoided giving that. I am a part-time grammar Nazi, after all.Diss my grammar will you?
Check out the demo code I just posted. It should be really easy to plug that into your game (if you want queueing). Sounds like your current method would register a button held down as multiple presses, which is also bad, as it would prevent use by players who have slow reflexes. With a game like this, you can make it playable by people no matter how slow they are at pressing buttons.As for the speedy input, I would probably have to modify the code rather significantly to do it that way. Right now it looks at what you input, waits 10 frames to show you what you pressed and play the tone, then lets you press another.
- All your base are belong to us.blargg wrote:Sorry, if I had realized you didn't want critique aimed at improving it, I would have avoided giving that. I am a part-time grammar Nazi, after all.Diss my grammar will you?
Zepper
RockNES author
RockNES author
Well, no. One key press won't register as multiple. When you hit a button, a variable gets set. When the action takes place it gets set to something else in a sort of "Held" state. You need to release the key in order for it to be reset to 0 or "unheld".
I have modified the game since this release because right now, you can press up (for example) to hit red in the pattern, release it and then quickly press and hold it again while the red animation is playing and it'll register as being a request for red if you keep it held. With my new improvements, the D-pad will be put in a "held" state until the animation finishes and you're able to input another press.
I was being a little silly with the grammar statement. I know the game text was written quickly.
I have modified the game since this release because right now, you can press up (for example) to hit red in the pattern, release it and then quickly press and hold it again while the red animation is playing and it'll register as being a request for red if you keep it held. With my new improvements, the D-pad will be put in a "held" state until the animation finishes and you're able to input another press.
I was being a little silly with the grammar statement. I know the game text was written quickly.
-
- Posts: 518
- Joined: Thu Jun 29, 2006 7:44 pm
- Location: lolz!
-
- Posts: 214
- Joined: Sun Apr 01, 2007 2:10 pm
How about a happy little "aww, you lost" jingle? Kinda like when you run out of time in Elebits?Sivak wrote:I actually have considered changing the loss sound so it's a little less "scary". I think that high-pitched triangle wave does it, heh.NotTheCommonDose wrote:Great to enhance my memory skills but when I lost, it scared me like a screamer on youtube.
For those interested, I have a newer version:
http://www.nintendoage.com/media/_userm ... ond3%2Ezip
Some better graphics in-game (I think anyway), a more ornate title screen with music, and you have a time limit to enter your move now.
I rewrote some of the instruction screen as per Blargg's suggestions, although I do realize I spelled "Ends" wrong. It's been fixed.
As I post newer demos I continue to update more things, heh.
http://www.nintendoage.com/media/_userm ... ond3%2Ezip
Some better graphics in-game (I think anyway), a more ornate title screen with music, and you have a time limit to enter your move now.
I rewrote some of the instruction screen as per Blargg's suggestions, although I do realize I spelled "Ends" wrong. It's been fixed.
As I post newer demos I continue to update more things, heh.
-
- Posts: 518
- Joined: Thu Jun 29, 2006 7:44 pm
- Location: lolz!