I wanted to make a map that was kind of like an rpg.
It would have 6 different possible classes, and it would be entirely controlled by the keyboard.
There are several different ways I could see how to make this map, but I am not sure which is best.
One of the things that I wanted to do, but might create more challenges was give each class 3 sub classes
for example: warrior-squire-knight
so here are my ideas and the pros and cons how I see them. If you have an idea of another way or pro or con, post it and I will consider it.
What I want to know is which ones people think are best gameplay wise, and then which ones would be most worthwhile (if the best gameplay is hard to make and there is another that is a lot easier, and only slightly worse, that would be this one).
1a. I could just have 1 player that was able to switch between all of the classes using only the 6 main classes
pros: it would be easy to program and fun that you could switch
cons: no fun subclasses, and not multiplayer
1b. All of the same, except it would have the subclasses too.
pros: fun subclasses, pretty easy to program
cons: people would only use their top tier classes and ruin the point of switching*, and not multiplayer
2a. 6 players, with each one having one of the classes and using only the 6 main classes
pros: multiplayer
cons: harder to program, no switching, and really no major benefits over 2.b
2b. All of the same, except it would have the subclasses too.
pros: fun subclasses, multiplayer
cons: harder to program, no switching
3a. 6 players, each one starting with one of the classes, and the players can trade characters for fun
pros: multiplayer, some switching
cons: harder to program, no subclasses, players might not be willing to switch
3b. Same with subclasses
pros: multiplayer, some switching, fun subclasses
cons: harder to program, no subclasses, players might be even less willing to switch
4a. a 6 player version of the first idea
pros: multiplayer, switching
cons: no subclasses, very hard to program
4b. same with subclasses
pros: multiplayer, subclasses
cons: very hard to program, people would only use their top tier classes and ruin the point of switching*
*what I mean is that, each class will probably have a specific point in the game where they upgrade to the next tier subclass, so a player might have 2 classes at the top tier and only use those while they have 4 unused bottom tier classes
It would have 6 different possible classes, and it would be entirely controlled by the keyboard.
There are several different ways I could see how to make this map, but I am not sure which is best.
One of the things that I wanted to do, but might create more challenges was give each class 3 sub classes
for example: warrior-squire-knight
so here are my ideas and the pros and cons how I see them. If you have an idea of another way or pro or con, post it and I will consider it.
What I want to know is which ones people think are best gameplay wise, and then which ones would be most worthwhile (if the best gameplay is hard to make and there is another that is a lot easier, and only slightly worse, that would be this one).
1a. I could just have 1 player that was able to switch between all of the classes using only the 6 main classes
pros: it would be easy to program and fun that you could switch
cons: no fun subclasses, and not multiplayer
1b. All of the same, except it would have the subclasses too.
pros: fun subclasses, pretty easy to program
cons: people would only use their top tier classes and ruin the point of switching*, and not multiplayer
2a. 6 players, with each one having one of the classes and using only the 6 main classes
pros: multiplayer
cons: harder to program, no switching, and really no major benefits over 2.b
2b. All of the same, except it would have the subclasses too.
pros: fun subclasses, multiplayer
cons: harder to program, no switching
3a. 6 players, each one starting with one of the classes, and the players can trade characters for fun
pros: multiplayer, some switching
cons: harder to program, no subclasses, players might not be willing to switch
3b. Same with subclasses
pros: multiplayer, some switching, fun subclasses
cons: harder to program, no subclasses, players might be even less willing to switch
4a. a 6 player version of the first idea
pros: multiplayer, switching
cons: no subclasses, very hard to program
4b. same with subclasses
pros: multiplayer, subclasses
cons: very hard to program, people would only use their top tier classes and ruin the point of switching*
*what I mean is that, each class will probably have a specific point in the game where they upgrade to the next tier subclass, so a player might have 2 classes at the top tier and only use those while they have 4 unused bottom tier classes