Game Creation > Tutorials

Sai'Kar Breaks Your Hopes and Dreams

(1/4) > >>

SaiKar:
Here's some things to consider if you are planning on releasing a demo / full game.

Your game is probably too hard.

Seriously, it very likely is. Most of us, having spent forever and a day programming our RPGs, design the difficulty around challenging ourselves.

Battles, specifically boss battles, may be too difficult if any of the following apply:
1) Certain, strange party setups are required for victory. Requiring a character that can remove poison present when there hasn't been any poison to remove thus far is just a dick move.
2) Requiring tricky, complicated tactics required to win. If you're going to force the player to use a weak skill that sucks in every other situation but is somehow the key to victory, you have to at least hint at some point about it.
3) You need to have found special weapons/armor that are off the beaten path to stand a chance. Making fire resistant gear available in treasure chests before facing a fire boss is okay. Requiring a totally optional, easy to miss subquest to track down the fire gear when nothing implies that this would what you need to do is not okay.
4) The enemies have certain attacks that, if repeated a couple times due to their random AI, can totally decimate the players' chances of winning. If you must give a boss these types of moves, limit how often their AI can use it (such as making it only trigger every X number of turns, or at a lower % of health with a low priority)
5) You feel that the player really should lose 3 or 4 times before they "really figure out what they have to do." Man, if I lose a boss 3 times or so in an amateur RPG, especially because of reasons like #2 on this list, at that point I'm just going to chalk it up to really bad playtesting and balancing instead of being sneaky. It's far more likely that it's just a badly programmed fight. Real video games have test groups of players play through to make sure the difficulty isn't too impossible. Did YOU put anywhere near that much work into balancing?
6) You're being a dick with save points. Nobody wants to have to run through 5 rooms of random enemies and then watch the same 2-minute cutscene before every boss battle that ends in frustrating failure. If you're going to put in save point pressure, you have to make your fights a lot easier. If you provide save points right before major fights, you can safely make them a little harder, but not such that you start to break rule 5 above.
7) The boss challenges you as a programmer. You know every trick possible. You know all of your characters. You know all the weak points. You know how much HP the boss has. You know what items to buy in preparation for how difficult the fight is. You programmed all this stuff, after all! The player knows no such things. If the boss occasionally beats the programmers, imagine how bad it's going to stomp players!

Your first boss fight should be easy. It should be so freaking easy that a trained monkey could win it. Think about it. The players are totally new to your world. They have limited resources, little control over their party setup, only a few skills to use, not many items, and they're fully sure of all the capabilities of their characters. Too many times I've barely beaten a first boss encounter by having to use every healing item available and still having a few people dead at the end. No. NO. Not good start!

I generally use Chrono Trigger as a gage for difficulty. Though some of the bosses are a bit tricky with timing and tactics, few or no parts of Chrono Trigger are bang-head-on-desk frustrating. The battle with Magus is a great example of a complicated battle that's fun, has an element of danger, rewards tactics and paying attention, and is also unlikely to really frustrate players.

If you absolutely must have the really nasty, hard fights that require bizarre tactics and obscure armor from subquests, the best way to handle them is to make them optional and also warn the players of the danger before they jump in. I don't mind losing to an optional fight - in fact, it makes me want to try it again more than a standard boss would because I know that, if I really can't figure it out, I can still continue with the rest of the game. This can let programmers put in the really hard stuff that challenges them without completely destroying the more casual players.

More abuse to come :3

SaiKar:
Your Plot Isn't Nearly as Memorable as You Think It Is

Most amateur RPGs (and even some of the hokier mainstream ones) start out by throwing a few thousand years of the history of the world at the player. Usually in the form of telling about some ancient war between some countries and some evil force that ends with the evil force being defeated / sealed / banished / something, but lately things have been kinda lousy and there have been troubles and whispers that the evil is coming back. And sometimes it's just text, and sometimes it has still frames of important events while there is text, and sometimes it takes place in the forms of conversations, but it's all pretty much blah.

Now, I'm not here to bash the clichés. I just think this is a really lousy way of introducing the player to your world. You bury them with information that is not immediately interesting to them. Big war, dozen names or so, evil, blah blah when do I get to play? Storyline isn't something you can just club people over the head with. If you want players to get immersed in your storyline, you have to let them discover it by themselves. Small pieces, slowly revealed over time, is tremendously better than these huge megaparagraphs that are better suited for a history lesson classroom.

Think about how Final Fantasy 6 starts. A couple short sentences about a great war and magic disapearing for the world, but it may be coming back. Then you're in command of some kick-*** magitech armor, shooting up civilains. The storyline is there - you're sent from the Empire to find a source of magic, but rather than being told it, you're playing it, and more details of the situation come out as you do.

Final Fantasy 7. You blow up a huge reactor in the middle of a massive, dark city. Barret keeps bitching about ecological impacts of the reactor, so you figure you're some sort of eco-terrorist, but that's all you really have to go on at the very beginning. No history of the world or mention of Sephiroth or JENOVA or any of that crap. Just shooting. The “why”s come a lot later.

What about Chrono Trigger? (get used to this - I love Chrono Trigger) What happens between when you select New Game and when you have control of your character? Almost nothing! Fireworks, a bell ringing, and the hint that Crono is a lazy bastard. No big history lesson. No forced plot hook. You have control of a pretty normal guy on what appears to be a pretty normal day. You can go visit that fair and play a bunch of minigames, or you can wander the town, find another town down south, take a stroll through the woods and head up to the castle, whatever. And talking to people and seeing stuff slowly reveals the nature of the game. A kid at the fair mentions that the fair is in celebration of beating a wizard a few hundred years ago. Is that important? You find out. Not immediately, not all at once, but at a much more natural pace.

The worst part about the "history lesson" type intros is that the writers, having imparted the entire history of the planet and all the names of the heroes and villains of old, assume that the player will remember every detail of this information and never reiterate it but reference the details constantly. This is terrible form. You can get away with that in books because the reader can always flip back. But RPGs are not books – they are stories. There is a reason that storytelling involves repeating the important names and details several times – no matter how cool what you are describing is, the listener is likely to forget the important names or events if overloaded with too much information. If there is something that really is important for your player to remember, you have to keep bringing it up. Make the player a bit sick of hearing about it – at least then they’ll know they’ve heard it before.

YOU know every detail of your plot. You've had a lot of fun coming up with it. There are probably important details in your head that never make into the game at all. Be very careful with assuming that the player will put two and two together or even remember the basics.

zuhane:
This should be an agreement form before submitting a game for the contest. I wholeheartedly agree
with everything I'm reading. Fortunately for me, I haven't hit a single criteria that you've mentioned
so far :P

SaiKar:
For Frick's Sake, Test It!

Our community is small, and the players that play demos of games are even smaller. The last thing you want to do is cheese these people off by making an unplayable game. It seems like every freaking game I download on this site either has a game-breaking bug or a totally ridiculously hard fight (ala "Your game is probably too hard" section above) that turns me off from it for good. Nearly all of these types of things would have been incredibly obvious to the game's creator if they had just played through the demo they were sending me themselves just one time.

When you're testing your game, it can be tempting to run from one plot point to the next, to make sure that they all work. And that's fine, as long as you also test doing exactly the opposite - dallying around stupidly as long as possible. Attempt strongly to get off the beaten path. When you enter a room, immediately try to leave. When a townsfolk tells you to go west, head east. Fight hard fights with inferior gear. Do events out of sequence. Try to walk through trees, over rocks, on water. Press buttons at random in your custom menu and battle systems. The goal is for YOU to break the game so that you know what's broken and can fix it before other people find that it's broken and can't fix it.

If you have the option, have a friend play it. You'll be AMAZED at the types of things that you assume are obvious but are not. I had my father play one of my minigame puzzles a few months ago. He completed the easiest one eventually but took such a long time and tried to do things that, in my mind, made no sense. I realized that I had to make certain visual cues considerably more obvious so that the rules of the game were more clear. Confusion over how to play the game at all is always a bad thing.

And when you've gone through the entire thing, tweaking stuff along the way, guess what. You have to do it again. From the beginning to the end, just to make sure. A full play run without you being able to break anything, and not from a lack of trying, is your best and only defense against a game that nobody will want to play due to bugs.

Natako:

--- Quote from: SaiKar on March 02, 2011, 04:52:33 PM ---Storyline isn't something you can just club people over the head with. If you want players to get immersed in your storyline, you have to let them discover it by themselves. Small pieces, slowly revealed over time, is tremendously better than these huge megaparagraphs that are better suited for a history lesson classroom.

--- End quote ---

This is exactly the reason I give people when they ask me why I didn't like FFXII (this and characterization).

Anyway, great posts and I agree with everything 100%. I'm so glad that I've grown out of the stage where I would put huge chunks of exposition into my games and expect people to remember them. Since my current project is very story-intensive, I always have to be careful not to go overboard. At least I'm not writing history text intros like I used to back when I was a game-making noob.

And yeah...playtesting. I've seen a lot of playtesting errors, even in games that are otherwise very polished. I played an amateur RPG lately where I was able to walk through trees in one place and get to a location I really wasn't supposed to be in. I wasn't even trying to look for mapping errors, but there you go. I also have bad luck with amateur games crashing on me because one object or another wasn't found. More likely than not, it happens when I haven't touched a save point in a while...Murphy's Law and all of that.

The other thing I see a lot is a lack of balance between level difficulty and boss difficulty. This also happens in professional games, but it's especially bad in amateur games. I know that you mentioned bosses that are too hard, but how about bosses that are too easy? I've literally played games where I went through a hair-ripping dungeon and the boss died in under a minute. ...What?

Navigation

[0] Message Index

[#] Next page