GAME MECHANICS AND PACING

Tips on how to not waste your player's time.

So, you’re making a game. You build the maps tile by tile. You name the characters. You write the epic story. You program the weapons and armor. You make the badass battle animations. You choreograph the awesome cutscene where the MC beheads a villain with an envelope opener. You balance your awesome battles. You give the characters stats. You always create your encounters to be a challenge.

“The game is perfect!” you say. And in your mind, it is. It does everything that you think an RPG should do.

But maybe it’s not as perfect as you think it is. Maybe people don’t enjoy the combat. Maybe they find the battles tedious or boring.

“They’re just wimps!” you tell yourself. “The game is challenging! They just don’t like things that are hard!”

Chances are, however, that this isn’t it either. Chances are that your combat, and possibly your entire game, is badly paced.

I am here to tell you why this happens and how you can prevent it.

Go with the flow.

I’m a fan of story-telling techniques through the use of game mechanics. By integrating your mechanics with you narrative, it makes the player feel closer to the story. These aren’t just things happening to a character on a screen. The player is IN the scene and these things are happening to them.

This isn’t something you can impose selectively, however. It happens whether you want it to or not. And all kinds of factors can influence how the player is approaching or interacting with a scene. This means that factors you might never even think about while you are developing your game are influencing absolutely everything about how your player is absorbing information about your narrative.

You need to think about everything that conveys information to the player, and the manner in which they are acquiring it. Some of these can be obvious things, such as font size and style, text speed, the walking speed of the player’s avatar, the game’s palette and other graphical choices. But those are only surface elements. Other things, from dungeon length, to the length and difficulty of encounters, can interrupt your game’s narrative if you aren’t careful.

What I’m talking about here is a game’s flow, and if you don’t know what that is, flow is how the game’s narrative fits together. Think about how someone tells a story. If someone is good at telling a story, they will present all the relevant information you need only when you need it, and probably doesn’t weigh their story down with irrelevant tangents or pointless information. Someone who is bad at telling a story might be incoherent, might forget to mention things, or tie scenes together in an illogical manner. That’s bad flow. Don’t do that.

The flow of a game’s narrative must make sense and be logical. Some of this is obvious, such as scenes logically following from each other. There is actually a style of writing known as modular storytelling that doesn’t follow a coherent narrative, but often consists of self-contained vignettes that may or may not fit together in a larger perspective. But you need to have some pretty serious stylistic justification to get away with that sort of thing. If your narrative is choppy and disjointed, it’s probably just going to confuse and irritate your player.

“But Solitayre, I thought we were here to talk about game mechanics! Story is stupid!”

No, you’re stupid. Also, I’m getting to that.

Adventurus Interruptus

I know your type. You’re one of those gameplay people, aren’t you? You probably think every single enemy in the whole game must be handcrafted through statistics and abilities to provide the a challenging yet reasonable battle for your heroes to face. That’s great. Really. There are absolutely lots of places in a game where you want challenging, well-crafted opponents for your heroes to fight. But there are some places you might not WANT to do that.

Did you know battles are a part of your game’s story? They are! Sure, we can assume that every giant rat and flying spaghetti monster we slay outside the starting village while squirreling away the cash to buy that super sweet LONG SWORD aren’t very important to the game’s narrative. Creatures like that are just game abstractions, they’re there for the player to fight, use his SWEET MOVES on, get stronger. We can assume no major revelations or life-altering epiphanies will happen in the midst of a battle with two dire bunnies and a ninja who lives in a medieval fantasy setting for some reason.

But you can’t treat all enemies like that. Some enemies are part of your plot. And if implemented badly, they can damage your plot, and damage your game. Let’s look at an example.

Evil Baron Nefarious has kidnapped the hero’s childhood love interest, Damsela, and is forcing her to marry him! That bastard! Our Hero, Heroy, decides he needs to go kick the Baron’s ass and save his love interest from this horrible fate. He and his comrades kick in the door to the Church shouting “I do!” even thought the priest didn’t ask if anyone objected yet. They feel kind of silly, but that doesn’t matter. Baron Nefarious sends his guardsmen to stop Heroy from ruining his wedding! The guardsmen come in three separate waves and Heroy will have to fight them all before facing the baron himself, who has been honing a secret EVIL TECHNIQUE especially to kill that pesky Hero with.

So, which of these two scenarios is more compelling in this situation?

A. Heroy engages a battle with the guards. Each guard is a challenging opponent who will take many hits to defeat. These battles go back and forth for upwards of ten rounds as Heroy slowly whittles down each guard, probably being forced to heal several times over the course of the battle. He will repeat this encounter two more times as he fights all three waves, before facing Baron Nefarious who is a very challenging boss who might kill Heroy with his secret technique and force him to reload his game and replay this entire sequence again.

B. Heroy mows down each of these guards in one or two hits. Heroy absolutely plows through them. Each battle is over quickly allowing Heroy to rapidly advance towards rescuing his love. The guardsmen are powerless to stop him. Baron Nefarious challenges Heroy to a duel, but he and his secret technique aren’t actually that much of a threat and Heroy bests him easily to rescue his beloved.


Scenario B is probably more narratively compelling even though the enemies in this situation are complete wusses. Why? Because the actual act of fighting battles is not the point of this scene. The point of this scene is Heroy rescues Damsela like a badass. If Heroy had to spend five minutes with each wave of guards, that would disrupt the scene’s flow. Who cares how strong these guards actually are? Heroy is pissed and they are in his way. Dispatching them in one hit gets the point across. Heroy is kicking the guards’ asses. That’s what needs to happen here. Having each guard be a trial defeats the point of that. Having each guard take forever to kill would distract the player from what’s going on in the larger context. If Heroy actually loses any of these battles, the moment is ruined and the scene will lack any of the same impact when they sigh and reload the game.

What about the Baron? Surely he must be a worthy opponent! Well, sure, but you can convey that narratively too. Because you see, you probably don’t actually want the player to lose in a sequence like this. This is the middle of a cutscene/action sequence, and if the player dies here, he has to do the whole thing again. You don’t want that. Putting a super hard boss at the end of a scripted sequence is usually bad design (I’m looking at you, Xenogears.)

So how can we make the Baron a badass without actually making the player lose to him? The Baron has an aforementioned SECRET TECHNIQUE OF EVIL. If this move actually had a serious chance of killing the player here, that would be bad. The player shouldn’t lose in situations like this unless they’re being stupid. So what can we do?

1. Baron Nefarious telegraphs his attack. “I’M ABOUT TO HIT YOU WITH MY SUPER EVIL TECHNIQUE!” (Translation: “Defend, stupid!”). The player knows the attack is coming and can take proper precautions.

2. The super evil technique is non-lethal. Maybe it drops Heroy’s HP to 1.

Both of these situations are good, because they create tension and the illusion of danger without actually putting the player in danger. In the first situation, the player will guard. In the second, he will heal himself. If they don’t do those things, they deserve to lose!

Using these techniques, we can have game mechanics enhance the game’s narrative instead of interrupting your game’s flow.

“But Solitayre! Enemies should always be well-crafted encounters designed to challenge your player. Why even play your dumb stupid dumb game otherwise?”

You again. You’re the problem. Yes, you. Go sit in the corner.


Variety is the spice of life.

There are lots of reasons to have weak, throwaway enemies. Not ALL enemies should be like this, probably. But having some variety in the level of difficulty in your enemies is a good thing. And again, one of the reasons is pacing.

The player might not want to have to undergo a hellish trial worthy of being chronicled by Alighieri every time they go into a battle. Sometimes they just want to drop one of their strongest area spells on an enemy group and watch them all drop dead. Or maybe they don’t want to spend five minutes jackhammering the attack key while waiting for the battle to be over. Sometimes they want to be Rambo and just blow everything away. It is okay to let them do this sometimes.

There is a psychological effect behind this, too. If every single enemy in the game advances at the same rate of strength as the player, the player won’t notice much difference in encounters from one area to the next. The player won’t feel like they’re making progress. This can be frustrating. Varying up your encounters can not only break up monotony but give a greater sense of progress as the player occasionally runs into an enemy they can annihilate easily instead of all enemies being of equivalent strength and challenge. There are lots of ways to spread out and pace your encounters. Each area might have a pack of really weak enemies that can be dispatched without effort. There might be groups of enemies designed to be a moderate challenge. There might be a single enemy who is quite powerful. Clever designers can mix and match these creatures to create more interesting encounters.

There is plenty to be gained from varying the difficulty of your encounters, both for the sanity of your players, and for story purposes. Let’s go back to Heroy for a minute. Let’s say Heroy was raised in a remote mountain village where he acquired a reputation for being a badass. This reputation was enough that the king wanted to hire Heroy for some task that starts the plot.

Heroy sets out for the castle, fighting monsters on the way. If these monsters are designed to give Heroy a hard time, I’m going to wonder what it is that makes Heroy so badass. Why is he strong enough get the king’s attention? He’s having trouble fighting rats! If Heroy dispatches the enemies around his starting home village with ease, it makes him seem much more competent. He has already mastered this area’s wildlife and it will feel justified as he moves out into the world and challenges greater threats. There is plenty of time for you to ramp up your difficulty. Don’t feel like you have to balance every encounter be a hassle just because. Do you have a reason for why you want to make everything so hard?

So, where DO you put the hard stuff? The dungeons are the places to put your challenging, thoughtful encounters. And not the first tutorial dungeon, either. That place should be easy, to give the player a sense of mastery for clearing it. If they walk out of the tutorial dungeon beaten to all hell, they’ll feel like they don’t know what they’re doing.

Once the player has played enough of the game to get a sense of how to play, what techniques work, what items are useful, once they’ve had a chance to get their equipment in order, to figure out their party’s strengths and weaknesses, that is when you can start populating your dungeons with your fiendish encounters. The player will walk into a dungeon expecting enemies and bosses, so you can feel free to bring the noise. The player will appreciate that you gave them the opportunity to figure things out before manhandling them, and they’ll approach these new challenges with confidence. Don’t manhandle your player right out of the gate. Nothing is more likely to make someone give up on your gate then a game over in the first twenty minutes.

Don’t waste my time.

This is the golden rule. This is the maxim. You should really, definitely think about this part. Yes, even you.

Don’t waste your player’s time. Twenty years of grind-heavy, repetitive RPGs and MMOs have made it acceptable for games to waste your time. I don’t want to waste my time. Your game shouldn’t make me waste my time.

Every time you make any decision in your game, whether it’s adding a battle or a puzzle or making the player backtrack or anything like that, ask yourself this: Is this adding something to the game or am I just wasting the player’s time? If the answer is the latter, you should probably adjust the sequence. Your game, and its pacing and flow, will be better as a result.

But that’s not all! All kinds of stupid ideas designed only to waste the player’s time have been floating around the game development hivemind in the guise of “stylistic choices.” Here’s a list of some of them and why they’re terrible and you’re terrible if you use them. (And you are.)

1. Slow text speed.

I honestly can’t fathom why anyone ever thought this was a good idea. Somewhere along the line, it even became acceptable artificially insert pauses into your dialogue to draw it out.

Some of us can read fast. You are punishing us for being able to read fast. If you want to break up your dialogue, be willing to go the extra mile and break it up with something besides vacant pauses. Even little things like having the characters move around while talking can make a huge difference!

2. Slow walk speed.

This is a big one. People love to throw around slow walking speeds as some kind of legitimate gameplay mechanism as though it can enhance the game’s setting, mood, tone, or atmosphere. “They need to be walking slow here, so they can appreciate all the work I put into building these maps!” No, if I feel like I want to appreciate your rigorous tileset/light map endeavors, I am free to take my own time through the map if I wish. You forcing me to do so is putting your priorities over the player’s. You could get away with a really slow walking speed if the maps are small and well-constructed enough that I won’t notice (some games have done this!) but if I ever have huge amounts of empty space to traverse you can bet this is the first thing people will notice and complain about.

“But Solitayre, slow walk speed is a legitimate tool that I should be allowed to use for certain purposes! You’re dumb and stupid!”

You’re right. When used properly, slow walk speed CAN be used as a narrative tool. But probably not for the reasons you think it is. The primary use for slow walk speed would be for the purposes of building tension during a certain scene. The heroine is alone in a dark room, and there’s a killer! Slow walk speed would be an excellent choice to increase suspense in this situation. But using it always, on every map, all the time, is not only annoying, it makes the legitimate usages of this technique ineffective.

3. Pointless backtracking.

This is another common way to pad play time, by making the player traverse the same few locales over and over again. If you’re going to make the player backtrack, at least add something novel for the player to do en-route. Are there any new events along the way? Have the player’s abilities allowed for opening new passages or revealing new treasures? Are there any shortcuts that can be opened now? Backtracking is an opportunity for you to toy with the player’s expectations! Just forcing the player to pointlessly replay sections of your game is just boring.

4. Random chance.

This convention has been around pretty much as long as role-playing games have. It’s often an easy way to pad play time. MMOs are full of this. Collect 20 “whatevers” to complete this quest. This item is only dropped by the “whatever man” which has only a 1/20 chance of appearing in a certain area. Also, the “whatever man” only has a 30% chance of dropping the “whatever!” Voila, you’ve instantly wasted three hours of the player’s time. Each time they find one of those vaunted “whatevers” they feel like they’re making progress! But they’re not. You’ve just tricked them into thinking they have. You monster.

This happens in single player games too. Any time you have an xty percent chance to succeed at a given task, whether making a potion, disabling a trap, or opening a lock, you’re really just saying “There’s a chance that doing this was a waste of your time.” This is especially true if failing a task forces them to fight a battle or complete some other task for failing what was essentially a dice roll.

“But SOLITAYRE!”

You again? What now?

“Random chance has been a staple of RPGs for twenty years. It’s dumb and weird that you would think this is bad!”

People used to think slavery was a good idea. Then they realized it was terrible and wrong, and stopped doing it. People are capable of realizing that an idea they thought had merit is actually stupid, and moving past it. This is called “progress.” Saying that something should remain the same because it has always been that way is basically the worst way you could ever frame an argument, because you aren’t appealing to logic or reason. You’re just appealing to the status quo.

I’m not saying that if you like random chance, you support slavery, but I’m not sure how you can sleep at night.


You cannot get there from here.

Ever been wandering around in a game not really knowing what you’re supposed to be doing? There are two things that might have happened here.

1. The designer did a bad job of telling you where you were supposed to go.
2. The designer thought making you wander around and figure out what to do on your own was a good idea.

But it’s not!

It’s your job to tell the player where to go to get to the next part of your epic plot! If the player makes an honest effort but can’t figure it out, that’s not their fault, it’s yours. Let your player know where they’re supposed to go or what they’re supposed to do, or who they have to kill/talk to/both. Any time the player is wandering around bored and not knowing what they’re supposed to do is bad, and you should do everything reasonable to minimize this.

Honestly, I see a lot of developers who seem to expect the onus of understanding their game to be on the player, and any problems they have are because they didn’t understand the author’s intentions. But it isn’t the player’s job to decipher your ideas. It’s your job to make your intentions and ideas clear to the player. If they can’t figure it out, they’re probably not going to like your game, and you won’t have anyone to blame but yourself!

There are lots of reasons someone may or may not like your game. But chances are you are going to think it is your mechanics or your writing that will make or break your game. Pacing might be something that never even crosses your mind. I hope that now, you realize what an important and essential tool this is in your game design arsenal.

Go forth and wield this tool for justice.

Posts

Pages: first 123 next last
Craze
When you look long into an abyss, the abyss also looks into you.
12568
This is a terrific article, if a bit hyperbolic at times. Errybody read this.
It's not Baron, it's Commander Nefarious. Along with Captain ImABadGuy and Admiral BoneToPick

The guard and Baron flow you mentioned is pretty much taking how movies go when Arnie shoots up an entire company of soldiers. You don't spend time on the mooks, Arnie guns them down and only until you get to General Dastardly. It's the climax, the audience wants Arnie to shoot him up because they hate GD's guts. Ending it like a mook ruins the experience and everything that was building up to it and the audience is expecting a serious fight. The conclusion is thrilling because of the emotional connection the audience has with the climax, because it tested their ability and skill to play the game and they succeeded is not as much of a significant factor. The big difference (besides time frames, any fight will take longer than Arnie gunning a dozen mooks) is interactivity.

I'd personally prefer avoiding gimmick bosses for anything beyond tutorial bosses. I agree that hitting a wall will kill the scene deader than roadkill but the fight should include the player and let them decide their fate. Gimmick bosses nine times out of ten end up in two ways: 1) The game tells the player what to do making their presence irrelevant 2) Take fucking forever in a slog of boredom. What about at the end of the game when Baron Nefarious is the final boss? A gimmick final boss would piss me right off as everything that I was building my party for just went up in smoke, gone to a previous fight back when my decisions mattered. If RPGs took an innovation back from 1992 restarting wouldn't be such a huge problem either. When lil'me lost against the Dark King (shut up I was like six) I got to restart on the spot. The kickass music never stopped, no momentum was lost, and I kicked his teeth in next round. RPGs need to learn how to keep momentum going because it is a very precious resource that's hard to create, easy to lose, and impossible to replicate.

Bonus fun is the boss you're probably referencing in Xenogears is also a gimmick boss that can't kill you if you figure out the gimmick (Miang?). To be fair it isn't hinted at very well.

And if you're going to call games out on wasting time you really should bring up big ones that just reek of padding. Nothing breaks the flow of the plot like everything grinding to a halt to do a fetch quest. Or going to ancient ruins to turn off a barrier of no progression. Or finding yourself on the wrong side of a week looking wooden door. Or on the gameplay side how about a wall in the difficulty curve? More than one game had that dungeon or boss that would make you taste the curb until you power up enough. One of the nice things in FF games is grinding isn't often necessary. You can beat FF9 without finishing an optional battle and FF4 only needs one good grinding segment (admittedly it's a hell of a segment if you only do it once).


Lastly, I whipped this up for a previous thread or something but never used it. It shows my intended difficulty curve of peaks (bosses 'n shit), drops (just beat a boss fuck yeah gonna cruise over some goons and show off and relax), and raises (oh hey next dungeon). It's pretty much "I agree with the Variety is the Spice of Life" section in graph form! Magnitude is very much not to scale.



author=Craze
... if a bit hyperbolic at times.
That's the obnoxious strawmen in there that makes the article feel more amateurish.
kentona
▲▲▼▼◄►◄►(B) (A)
19528
But Solitayre, without any randomness, it creates an unrealistic rigidity to the game universe! The incompetent thief will never accidentally stumble upon the correct combination for the lock he was picking, the unskilled ranger will never get off a lucky shot that pierces the dragon's eye, killing it instantly. It makes the game less friendly to players you are a hair underprepared for a certain task.

EDIT:
I also don't like the implication that a failure or loss implies that it was a waste of time. So does that mean that "we should never let the player fail?" Serious question. Or that we can never let the player succeed if he gets "lucky"? Or, since the element of chance is eliminated, does that mean you have to make all of your numbers highly visible? Take for example the Thief with the steal skill - my steal rating is 40, but the golbin's hoarding skill is 60, in the rigid universe you propose I could never steal from that goblin. Are you going to reveal that in-game for me so I can make an inform decision to steal or not?

A "chance to win X" is a very useful motivational tool when creating games for humans! To discount that out of hand seem rather naive. (If it wasn't we wouldn't have casinos and lotteries!). Without an element of chance, it seems that all major interactions would be reduced to a binary result set - either you can or you can't. (This is based on the standard assumption that skill in RPGs is represented by character skill, and not player skill. ie- things are reduced to numberz)

In a nutshell, you are way off base on the use, purpose and implementation of random chance in RPGs.
author=Solitayre
You monster.
Between this and the quote in your profile, I now imagine this article being read by GLADOS.

Anyway, I 95% support this article.
The only thing I don't agree on is the fact that Barion Nefarious not being strong actually works against the pacing of the scene. I mean, heroes don't prove they're badasses by only bullying mooks; they have to defeat other badasses.
So, you can give the player his power trip by making him curbstomp the mooks, then he can become a real badass by defeating the actually dangerous boss.
(And you put a checkpoint just before that, because it's true that boss battles immediately after cutscenes are bad)

The only ways I can see Baron Nefarious being weak as a good move would be if he were a really minor villain and/or if the protagonist/player already had to overcome the main difficulties of the quest and the "wedding" scene is just falling action.

An example of the latter: Baron Nefarious threw the protagonist into the Pit of Progressively Stronger Random Encounters, but he emerged victorious from the horde of monsters and he became strong enough to curbstomp the villaing against who he couldn't do anything before. In this case, the real "difficulty" is the Pit, and kicking Nefarious' ass is just a way to give some sweet regenge to both the protagonist and the character.

But Baron Nefarious isn't a joke villain and if you build up the "wedding" scene as the last showdown with him, then it being easy will just be disappointing.

Also, if you want the fight not to be dangerous, I think making Nefarious a gimmick boss would actually not ba a good idea: usually, during normal battles it takes a series of errors to lose; if you screw up on one turn, you have the opportunity to make up on the next one. In your examples, on the other hand, if the player makes ONE mistake (even just pushing the wrong button at the wrong time) during the turn immediately before/after the Gimmick Boss Attack, he has no hope of surviving.

Rather, if you want to make the battle easy, make it easy.
Baron Nefarious just cowers when it's his turn, or maybe attacks with a wimpy animation for 1 point of damage; maybe he tries calling other easily dispatched mooks (which after a while won't even come, after having seen what the protagonist has done to their comrades).
Make him shed all the "dangerous villain" act he put up when he had an army of mooks who protected him. Make him cry and whine everythime the protagonist attacks him. Make him try to bribe the protagonist with laughable offers.
If the battle is not supposed to be a equal fight but just a chance for the player/protagonist to vent his rage against the guy who made him suffer, go all the way with it.

Anyway, the rest of the article points out a lot of "less-obivious-than-they-seem" common mistakes. I like it very much.

(I hate when random chance is used too much myself, but Kentona makes some good points.
I'd say random chance has its places in RPGs, but it's very annoying when it's used outside of these places.)
I feel some of the points in this article aim toward a very specific mould of RPG.

author=Soli
Random chance.


Random chance really depends on how 'visible' the chance is. Morrowind was very frustrating because it played like an action rpg but every hit had a dice roll involved even if you were up against someone bashing them in the head over and over. Random chance would probably not work well in RM battles either because wasting a turn is not fun. But luck can work if add a positive element to each outcome (critical hits/enchanting weapons with procs). If you suck at brewing potions you'll only have 40% chance to make the weakest potion, however if you make it so that even if you failed, the skill level increases (slower anyway), then luck isn't so bad. I think luck can be tamed but it really depends on the game and how well you fit the player's skill in there. Kentona, while an old man from the dinosaur age, does have a point that luck can be really addicting.

The designer thought making you wander around and figure out what to do on your own was a good idea.


Uh there are games out there that focus on doing that. Not many RM games intend to do that, but exploration can be very neat sometimes instead of holding the player's hand. I was playing Dark Souls recently, and the game has no map or quest log thing, but it is designed with a lot of landmarks and different looking structures so that everything doesn't look the same. It's very rewarding figuring stuff on your own. Other non RPG games like Super Metroid or La Mulana rely on this stuff too.

I think everything else is spot on though.
Craze
When you look long into an abyss, the abyss also looks into you.
12568
Darken
Uh there are games out there that focus on doing that. Not many RM games intend to do that, but exploration can be very neat sometimes instead of holding the player's hand. I was playing Dark Souls recently, and the game has no map or quest log thing, but it is designed with a lot of landmarks and different looking structures so that everything doesn't look the same. It's very rewarding figuring stuff on your own. Other non RPG games like Super Metroid or La Mulana rely on this stuff too.


Having "landmarks and different-looking structures" helps prove Soli's point. It was a conscious decision to lead you on in that direction.
kentona
▲▲▼▼◄►◄►(B) (A)
19528
Someone's got to stick around and make sure you kids stay in line.
author=Craze
Having "landmarks and different-looking structures" helps prove Soli's point. It was a conscious decision to lead you on in that direction.

That just prevents you from backtracking accidentally to prevent time wasted. But it doesn't lead you to a direction, you're still wandering around, there's still discovery. I feel Soli is part of the camp where everything needs a quest marker location/log thing and an NPC going "HEY YOU NEED TO GO HERE, HEY YOU STUPID, GO EXACTLY NORTH AND WEST, DO YOU WANT ME TO REPEAT THAT?" TUTORIAL TIP: TALKING TO NPCS WILL HELP YOU GO WHERE YOU NEED TO GO. That's not bad, but you don't HAVE to do that, some games are enjoyed through not knowing whats ahead.
author=Darken
I feel Soli is part of the camp where everything needs a quest marker location/log thing and an NPC going "HEY YOU NEED TO GO HERE, HEY YOU STUPID, GO EXACTLY NORTH AND WEST, DO YOU WANT ME TO REPEAT THAT?" TUTORIAL TIP: TALKING TO NPCS WILL HELP YOU GO WHERE YOU NEED TO GO.

You are strawmanning him a bit.
Sure, the player doesn't need an NPC saying "You must go east for 327 steps to reach the Cave of Flaming Ducks", but an NPC saying "You could go east for about three hundred steps, if you need some flaming ducks" is always a good thing.

And, as Craze said, developers do use landmarks as a subtle way to guide the player around; they're not just there to prevent accidental backtracking. It's like a even milder version of the NPC I mentioned before.
(A visible pyramid in a wasteland is like an NPC saying "Hey! If you come here, there will be interesting things!")
Regarding direction:
Using these tips in subtle ways to direct the player is the job of the designer. I don't know how often people like to argue good advice because they can come up with a counter-example in a special situation.

Digesting good ideas and implementing them into your game if appropriate is YOUR job!

Regarding Random Chance:
Random chance in things like lockpicking and other activities can often lead to players doing something like saving before a lockpick, and retrying until they succeed.

I think random chance is best replaced by a method that gives the player the choice, like a pool of 'lockpick' or 'skill' points they can spend in a period of time - the more you 'upgrade' a skill the less points it uses, then they can weigh what they want to do instead of depending on random luck (and maybe just saving their game first and reloading until they get the result they want - a tactic I VERY OFTEN use.)

@Kentona:
Allow me to address your concerns regarding Random Chance:
http://www.penny-arcade.com/comic/2007/01/29

(Random chance can have it's place, but once you actually understand how computers do 'random' you realize it's actually a load of bull and why it's a terrible idea.)
Craze
When you look long into an abyss, the abyss also looks into you.
12568
You made several excellent points here.

I will like to add that when lining up inherently 'disjointed' vignettes, you can fake coherency and flow with some techniques.

One method is cut one scene short on a fade-to-black and then 'finish' the flow of dialogue in the next, totally unrelated, scene.

For example:

"Why am I even here? This is such a waste of my..."


"Time! Alright, pencils down. Pass your exams to the front of the room."
"Aw man, I did terrible on that one."
"I know, if I fail this class, my mom's gonna..."


"Kill me, you bastard! How dare you walk away!"
"Mercy is the mark of a great man. And besides... I've proven my point."
"You're going to regret letting me live. Someday, I'll make you..."


"Pay up. 100 in cash."
"WHAT?! That's such a rip off."
"If you don't like my price, you can always..."


"Leave. Get out of my house and leave me alone."
"I'm just trying to help."
"You're not helping. You're just bothering me!"


Obviously, there's no context here, and it really is totally random. However, this can soften the irritation of confusion, while the gamer still has too little information to grasp your "big picture."



Another technique could be to have two well developed perspectives appear together. Well developed as in, you've seen them before and already know what they're supposed to be doing. Say, two parties: one group secretly starting a rebellion, the other group hunting down a famous thief. Both groups are in the SAME town.

Instead of flipping from one scene to another, you could combine the scenes in one "shot." You have the rebel group walking through town, before entering their secret hideout. Instead of cutting to inside the hideout with them, the shot remains outside, where the second party walks onto the screen. They'll comment on how that thief MUST be here in this town.

Totally unrelated parties to the gamer right now. Little do they know that the thief is one of those rebels you already know. How you transition from perspective to perspective is important.



Writing techniques can be important in keeping the audience. Say you have 10 different seemingly unrelated perspectives. Of course, they WILL become related, or are already related, but the gamer would not know that. Until more background or developments on theses different parties surface, the gamer would continue to remain in dark about the relationships.

It's not as disaster unless the gamer is confused within the scope of a single perspective. Then, there's trouble.

pyrodoom
I am Pyrdoom, Hedgehog of Fire and the Time Controller.
1245
author=Solitaiyre
You cannot get there from here.

Ever been wandering around in a game not really knowing what you’re supposed to be doing? There are two things that might have happened here.

1. The designer did a bad job of telling you where you were supposed to go.
2. The designer thought making you wander around and figure out what to do on your own was a good idea.

But it’s not!

It’s your job to tell the player where to go to get to the next part of your epic plot! If the player makes an honest effort but can’t figure it out, that’s not their fault, it’s yours. Let your player know where they’re supposed to go or what they’re supposed to do, or who they have to kill/talk to/both. Any time the player is wandering around bored and not knowing what they’re supposed to do is bad, and you should do everything reasonable to minimize this.

Honestly, I see a lot of developers who seem to expect the onus of understanding their game to be on the player, and any problems they have are because they didn’t understand the author’s intentions. But it isn’t the player’s job to decipher your ideas. It’s your job to make your intentions and ideas clear to the player. If they can’t figure it out, they’re probably not going to like your game, and you won’t have anyone to blame but yourself

But Solitayre! Sometimes it's GOOD to use this, and what if the author gives you hints and hints to what to do, and the player STILL complains? It's even shown in GREAT games like Yume Nikki and the Legend of Zelda!
Solitayre
Circumstance penalty for being the bard.
17912
kentona
Random chance!

My argument is that random chance should never be used as a barrier to progress. See my thoughts regarding the use of chance for criticals.

http://rpgmaker.net/articles/497/


author=Cozzer
But Baron Nefarious isn't a joke villain and if you build up the "wedding" scene as the last showdown with him, then it being easy will just be disappointing.

Baron Nefarious probably isn't the final boss in the scene as described above. The point of this scene is that Nefarious is a challenge, but not hard enough to actually kill the player and ruin the scene.

author=Darken
I feel Soli is part of the camp where everything needs a quest marker location/log thing and an NPC going "HEY YOU NEED TO GO HERE, HEY YOU STUPID, GO EXACTLY NORTH AND WEST, DO YOU WANT ME TO REPEAT THAT?" TUTORIAL TIP: TALKING TO NPCS WILL HELP YOU GO WHERE YOU NEED TO GO. That's not bad, but you don't HAVE to do that, some games are enjoyed through not knowing whats ahead.

I sure don't remember saying this!

pyrodoom
But Solitayre! Sometimes it's GOOD to use this, and what if the author gives you hints and hints to what to do, and the player STILL complains? It's even shown in GREAT games like Yume Nikki and the Legend of Zelda!

Legend of Zelda does have ways of telling you where to go. Hints like "Go up, up, up the mountain ahead" is a clue where the next dungeon is. Once you have the raft, you will try using all the docks. One takes you to a dungeon. That's telling you where to go. All the dungeons have distinctive architecture that tells you "Hey, this is one of the dungeons you need to clear!" You can't walk past one without realizing it's important. The exception is Level 8 which is hidden under a completely random and arbitrary bush which isn't so much as hinted at anywhere. That one is pretty dumb. Can even the Recorder show you where that one is? I don't remember.
kentona
▲▲▼▼◄►◄►(B) (A)
19528
I don't understand the comic.
pyrodoom
I am Pyrdoom, Hedgehog of Fire and the Time Controller.
1245
author=Solitayre
kentona
Random chance!
My argument is that random chance should never be used as a barrier to progress. See my thoughts regarding the use of chance for criticals.

http://rpgmaker.net/articles/497/


author=Cozzer
But Baron Nefarious isn't a joke villain and if you build up the "wedding" scene as the last showdown with him, then it being easy will just be disappointing.


Baron Nefarious probably isn't the final boss in the scene as described above. The point of this scene is that Nefarious is a challenge, but not hard enough to actually kill the player and ruin the scene.

author=Darken
I feel Soli is part of the camp where everything needs a quest marker location/log thing and an NPC going "HEY YOU NEED TO GO HERE, HEY YOU STUPID, GO EXACTLY NORTH AND WEST, DO YOU WANT ME TO REPEAT THAT?" TUTORIAL TIP: TALKING TO NPCS WILL HELP YOU GO WHERE YOU NEED TO GO. That's not bad, but you don't HAVE to do that, some games are enjoyed through not knowing whats ahead.


I sure don't remember saying this!

pyrodoom
But Solitayre! Sometimes it's GOOD to use this, and what if the author gives you hints and hints to what to do, and the player STILL complains? It's even shown in GREAT games like Yume Nikki and the Legend of Zelda!


Legend of Zelda does have ways of telling you where to go. Hints like "Go up, up, up the mountain ahead" is a clue where the next dungeon is. Once you have the raft, you will try using all the docks. One takes you to a dungeon. That's telling you where to go. All the dungeons have distinctive architecture that tells you "Hey, this is one of the dungeons you need to clear!" You can't walk past one without realizing it's important. The exception is Level 8 which is hidden under a completely random and arbitrary bush which isn't so much as hinted at anywhere. That one is pretty dumb. Can even the Recorder show you where that one is? I don't remember.

And what about Yume Nikki...in fact, it's even greater with another thing, people actually liked it at times! And even the fact that it goes against another thing you said, about random chance, players of Yume Nikki loved how you never knew what was going to happen! Sure...alot of those players shit their pants because of it, but they still loved it.
Solitayre
Circumstance penalty for being the bard.
17912
I've never played Yume Nikki so I can't comment.
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
4927
Ah, the thing about the guards and the Baron is actually good stuff. I definitely agree that having all four battles hard causes a major problem, and having just the Baron be hard still causes a more minor problem. I'm not sure, though, that the more minor problem of the player losing and having to redo the scene and easy guards is worse than the new problem you've created: the fight against the Baron is anticlimactic and doesn't feel like a major achievement on the player's part.

For my part, I am completely ignoring your advice for this aspect of battle pacing. But that's because I know exactly why you want it done the way you do, and I agree with you, but I have a different way of solving the problems you mentioned. My way is to use FF13 style game overs, so that when you die, you get sent back to right before the battle. Not right before the series of battles; right before the exact battle you died in. Because I essentially agree with everything you said, I don't want the player to have to redo the boring crap, but I also want my climactic gameplay moments to coincide with my climactic story moments.

Of course, this kind of custom game over doesn't work well in many types of RPGs, and I'm not proposing it as a strictly superior method. I know exactly why I'm breaking your rule and how I'm going to clean up my mess; your rule is still a good one.
author=Solitayre
Baron Nefarious probably isn't the final boss in the scene as described above. The point of this scene is that Nefarious is a challenge, but not hard enough to actually kill the player and ruin the scene.
Still, you seemed to set up that scene as some kind of climax; not for the whole story, but for a storyarc.

And I think making a "plot" climax coincide with a "gameplay" anticlimax would greatly hurt player immersion, as LockeZ said.

(I never quite got the difference between Yume Nikki and a bunch of .png files tied to a random number generator. But that's probably just me.)
Pages: first 123 next last