Jun-01-2017, 05:07 PM
I'm new to this forum, but I'm hoping this is the correct place to post something like this. I'm currently working on a game that I believe is unique (at least, I haven't been able to find anything similar here or by Googling). I'm not having any specific problems with the game, just hoping for suggestions as far as gameplay mechanics and base code, so feel free to redirect me to another area on the forums if this would be better suited elsewhere.
Here's the background:
I'm teaching several children how to program in Python, ranging from about 4th to 9th Grade. I wanted to introduce file I/O to them, but had to think of a way to do it in a way that would keep the attention of children as young as 11 y.o., so my first thought was a game. But, instead of just a game that uses file I/O to find game stats from a text file or to save data, I wanted to make the file I/O a more central and active role in the game, so I got inspiration from a Digimon game I saw my little sister playing (Digimon Story: Cyber Sleuth, in case you're interested). What I'm basically saying is: Keep in mind that this game is intended for teaching children about file I/O, not to be the next AAA game.
With all that out of the way, here's the basic game idea:
Each player has a short core file, which has the player name, hit points, and the most basic functional code (all this is only about 30 lines without referencing any functions stored in other modules). On a player's turn, they run their core file, which initially summons a single monster to their core directory (the monster data is all stored in a subfolder, but it's against the rules to access the folder while playing). You can only perform one action per turn, so that is your entire first turn. On subsequent turns, you run a single file from your core directory, either your core file or a monster file (also, all the monsters are named after and based on actual Digimon, since this is entirely non-commercial and I have no plans for distributing the game). The monsters, once used, are destroyed, though they could be randomly summoned back by the core file later. Unlike games like MTG and Pokemon, instead of having monsters battle one another or deal direct damage to a controller, they have effects on the core code of another file. For example, Devimon's effect inserts a chunk of code into the other player's core file that causes their hit points to drop by 1 every time the player activates their core file, whereas Demidevimon's effect opens the other player's core file, finds the first function under the "Base Functions" section, and makes the first entire function into a block comment, using ''' notation. The game ends when either a player's hit points hit 0 or a player's core file becomes too corrupted to function. I've made about a dozen monsters for the game, and now I'm having the kids write their own to add to it (I have to approve the monster before they can use them, so they don't have a single monster that just erases an enemy's entire core file in one move or something like that).
That's pretty much the entire concept. I would love any input or ideas for future effects to use in the game. The kids really seem to enjoy it, which is more than I expected for something that's teaching them about file I/O in Python, one of the duller but more useful subjects in programming. If you have an idea, please leave it below, preferably with pseudo-code for how to get any monster effects to work. I'm not a programmer, just a Civil Engineer who uses Python at work, so any code or pseudo code would probably save me a lot of trial-and-error and aggressive Googling. There are a few other rules that make the game run smoother, like each player has a RAM stat that they can increase with monster effects, and certain monsters will only be summoned if they have a high enough RAM, similar to summoning costs in MTG or mana costs for spells in other Fantasy games. Beyond that, I'm also open to gameplay mechanic ideas.
Here's the background:
I'm teaching several children how to program in Python, ranging from about 4th to 9th Grade. I wanted to introduce file I/O to them, but had to think of a way to do it in a way that would keep the attention of children as young as 11 y.o., so my first thought was a game. But, instead of just a game that uses file I/O to find game stats from a text file or to save data, I wanted to make the file I/O a more central and active role in the game, so I got inspiration from a Digimon game I saw my little sister playing (Digimon Story: Cyber Sleuth, in case you're interested). What I'm basically saying is: Keep in mind that this game is intended for teaching children about file I/O, not to be the next AAA game.
With all that out of the way, here's the basic game idea:
Each player has a short core file, which has the player name, hit points, and the most basic functional code (all this is only about 30 lines without referencing any functions stored in other modules). On a player's turn, they run their core file, which initially summons a single monster to their core directory (the monster data is all stored in a subfolder, but it's against the rules to access the folder while playing). You can only perform one action per turn, so that is your entire first turn. On subsequent turns, you run a single file from your core directory, either your core file or a monster file (also, all the monsters are named after and based on actual Digimon, since this is entirely non-commercial and I have no plans for distributing the game). The monsters, once used, are destroyed, though they could be randomly summoned back by the core file later. Unlike games like MTG and Pokemon, instead of having monsters battle one another or deal direct damage to a controller, they have effects on the core code of another file. For example, Devimon's effect inserts a chunk of code into the other player's core file that causes their hit points to drop by 1 every time the player activates their core file, whereas Demidevimon's effect opens the other player's core file, finds the first function under the "Base Functions" section, and makes the first entire function into a block comment, using ''' notation. The game ends when either a player's hit points hit 0 or a player's core file becomes too corrupted to function. I've made about a dozen monsters for the game, and now I'm having the kids write their own to add to it (I have to approve the monster before they can use them, so they don't have a single monster that just erases an enemy's entire core file in one move or something like that).
That's pretty much the entire concept. I would love any input or ideas for future effects to use in the game. The kids really seem to enjoy it, which is more than I expected for something that's teaching them about file I/O in Python, one of the duller but more useful subjects in programming. If you have an idea, please leave it below, preferably with pseudo-code for how to get any monster effects to work. I'm not a programmer, just a Civil Engineer who uses Python at work, so any code or pseudo code would probably save me a lot of trial-and-error and aggressive Googling. There are a few other rules that make the game run smoother, like each player has a RAM stat that they can increase with monster effects, and certain monsters will only be summoned if they have a high enough RAM, similar to summoning costs in MTG or mana costs for spells in other Fantasy games. Beyond that, I'm also open to gameplay mechanic ideas.