|Posted by underworldfan [22.214.171.124] on 2006/08/09 14:51:36|
|There are different "types" of gameplay in Q1SP maps.
I have always been interested in what makes "good" or better gameplay, and how exactly to define gameplay.
gameplay seems to be made up of a number factors which can be applied or created in a given map to a certain degree, for example the main 2 might be:
etc (i am sure they are are others? suggestions?).
Difficulty is fairly obvious, but what about predictability?
When you design a map do you think much about how predictable or unpredictable the gameplay will be? or is it unimportant?
I think it is important to have aspects of combat and navigation that are unpredictable. However I think you can make a completely predictable map that still plays solidly and is enjoyable to the player. The authors who can work surprises into their maps without having them feel too gimmicky or out of place are the best authors.
A good example of doing it poorly would be in my 1000-brush Norway SP map from last year. If the player missed an invisible "leap of faith" they were teleported to this "hell room." I'm sure most of the players were just expecting to fall to the bottom of the area and take 5 damage, as there was no visible teleport there.
In retrospect I shouldn't have tried to work in such a gimmicky piece of gameplay but such are the risks you take in trying to make compelling gameplay :)
Depends On What You Mean...
are you talking about predictable to the level designer or predictable to the player?
Predictable to the level designer means levels on a rail -- no route choices, very regulated and scripted gameplay, and lots of measures taken to keep players from breaking the gameplay.
Predictable from a player standpoint means learning how different classes of things behave, and then being able to build strategies around them. In other words, "systems-based" design. Of course level-on-a-rail can be predictable to the player as well.
Things I Find Boring ...
1. Perfect level symmetry where everything is so nice and clean that I can predict what is around every corner.
2. Redundant placement of monsters. Like push a button, see some monsters. Repeat. Open a door, see some monsters. Repeat.
3. End of map climax with hordes and hordes of monsters, focusing on quantity not quality.
Things that are nice to see when they happen.
1. Monsters with walkpaths, effectively randomizing their position or occasionally surprising a player because they "weren't there" and then see the player from behind when they come around a corner.
2. Moderately complicated situations where the type of monster and the environment creates the challenge. Very small area plus Shambler/Hell Knight, area with no cover and Vore, darkness plus some scatter grunts, zombie plus no gib weapon.
3. Rocket Jump/Grenade Jump! Is Once Upon Atrocity solvable without a grenade jump? I've never found the way, if so. (I mean without the secret RL, I wish I never found that on accident).
Also in Trinca's Forgotten Tomb, I found myself surrounded by knights. I only had rockets and decided my only option was to rocket jump over them, as I had no other exit opportunity.
4. Unanticipated/unconventional geometry. Tunnels, confusing hallways!, maze-like structures where it hard to tell where you are (ac.bsp, bnt.bsp, etc.)
5. Water! (ant.bsp)
6. Slime! Why do we see so little of this and so much lava???
7. Unintuitive shortcuts or map navigation. Anyone else *really* like that area on Insomnia where you encounter the difficult, but climbable area or the part of -- is it czg01 -- where you have to make a jump across lava rocks and then later a complicated jump from the top of a box to a ceiling tile (hard!)
8. The monster that scares you. Can be a simple as a dog awkwardly placed.
RE: #2. John, i mean predictable to the player i guess.
Predictability Is Good
What metl said, systems-based.
Predictability is what gives the player 'rules' to play within. Monster behavior in Quake is an example of that. Once you can predict what monsters will do you can exploit their behaviors to be better at the game. In Quake you can, in theory, handle a room full of shamblers and fiends and vores and shit, because you know what they're all going to do.
Once you, the designer, have those rules set up, you can play off them, and do something new and, arguably, "unpredictable" instead of just re-testing the player on the same rules. You want the player to start predicting things, because once you know what he's predicting you can interrupt him, and make his predictions wrong.
The one moment in Doom3 that scared me was actually not a planned scare. I had stopped and backtracked for health and missed an Imp somewhere, and he was just hanging out behind a door on my return. Now, doom had a lot of imps behind doors, and the unfortunate effect was that "doors have pre-placed imps behind them" became one of the rules the player learned. Who else started playing the game by edging up to doors from the side until they brushed the door trigger, specifically to avoid that stupid repeated ambush?
The reason it worked on me that one time is that I knew I had cleared the door already. It was a "safe" door, and thus not covered by the rule.
Monster behavior in Quake is an example of that. Once you can predict what monsters will do you can exploit their behaviors to be better at the game.
Yes, i agree. I find this monster predictability in quake 1 so fascinating because it seems so perfectly balanced, this seems to me one of the primary reasons quake 1 gameplay is so good.
Also, watching speedrunning in quake 1, the way they can predict everything to such a fine degree in an artifical 3D environment is amazing, i think.
Blitz' comments kind of hit home for me. In almost all of my maps I go teleport crazy in an attempt to create unpredictable situations. In a way it works, but it gets old. I think the reason that many mappers use lava - at least the reason why I do - is largely because of the amount of control a mapper can wield with it. Slime is too survivable when you want to keep the player focused... does that make sense?
In SMs I think it's less shameful to have that kind of rails gameplay, especially with teleports, etc. I think a great example of unpredictable gameplay was Ant.bsp. The monsters were placed oh so perfectly (especially the shamblers), and it was never over the top.
The Best Kind Of Surprise...
... is when the player goes "duh! i should have seen that coming." Which ties into what Lunaran says.
And uwf, speedrunning is a mix of prediction, practice and hope :-) You don't see the demos where the ogre stubbornly refused to get out of the way...
I�m working on something atm thats very loose in play style, the player has to wander around alot, but I�m trying to keep play moving forward without them getting lost / bored / frustrated, just because it�s something new to do. Seems like all mappers want to create very strict A to B maps, and whilst this has to be the case it needn�t rule always.
And the only reason to experiment with this is because its rarely done well, but very good when it is.
I only just bought hl2 and find it kind of irritating that there�s no real wandering around sections - you always feel funneled along a path, something that the first hl removed from play, and one of the reasons it was so good.
Linear Vs. Open
I think the main issue with open maps is that there needs to be a close connection between weapon progression and monster progression. In a linear map, this is easy to maintain, becuase you know when players will get a weapon and when they will meet a monster.
In a standalone map, the mapper often gives the players all the weapons in the course of the map. This means the progression is steeper.
In a map that is part of an episode or an entire game, you will progress much more slowly through the weapons. Becuase of this, it's a lot easier to have open, nonlinear layouts becuase you might spend most of the map without getting any new weapons.
Some of the Doom2 maps were very open and this worked quite well.
The map I am making at the moment is partially linear but contains route choices. These basically amount to which route you choose first, or which way around a loop you travel, though I have given the player the choice taking one weapon instead of another also. I'm hoping that this will allow many players to get a different experience from the same map. Perhaps I could even implement difficulty by having an easy/normal/hard route through the level, though I think I'll just stick with the traditional method for now.
in a custom level the player is assumed to have already played the original game, and so knows what weapons exist in the toolset. In the original game you have levels (eg. in q1) where the player has only shotgun / nailgun, no rockets or lightining at all - imagine these being left out of even the first two-three levels of a custom episode; it wouldn't happen because it'd likely piss people who played it off. You can do it ni the original game because everything is new to the plaer, in a custom level its assumed to be at least familiar, if not expected.
IN And PLAYER
I think it's the point that many quake1 mappers forget about. Environment interaction as a gameplay element was well used in many modern (and not so modern) games. It makes another experience to the player than just go-kill-monster-press-a-button-kill-another-monster gameplay. It may be called unpredictable for player in quake imho.
I'd think you want the player's direct effect on the environment to be pretty predictable. It's another element of the player having to recognize the control he has so he can use it.
In fact, it's usually pretty hard to ensure that his actions are predictable. Unpredictable is easy that way. If the player has to hit a button which opens a door he couldn't get through ten minutes prior, the designer better make damn sure the player is going to know the button will do that as soon as he sees it. Making the button a key with a particular color tends to help in that regard. :)
But, buttons aside, if your game involves you using your environment at all (which it better), the player's gotta have a handle on that to use it same as he does with the monster behavior. That'd be an area I'd regard as more sacred, where the designer shouldn't pull unexpected stuff.
There was a fake exit room in the first Doom that had the same door and exit sign as every other exit but was actually a rather heinous ambush. ha ha, clever, but, I wouldn't rely on shit like that too much. It's dirty, and an intentional lie by the designer to take advantage of the trust he's developed in the player by making all the exits look the same. Remember the first time you played Doom what a beacon of happiness and joy seeing that damned exit door was?
Like, imagine if your HUD lied to you about how much health you had. it might be tense at first because you'd always have to regard every situation as if you were inches from death, because you very well could be, but after a couple of moments of that you'd be mad as hell. Fuck you, game, just tell me how much health I have.
If the player has to hit a button which opens a door he couldn't get through ten minutes prior the designer better make damn sure the player is going to know the button will do that as soon as he sees it
Confuse the player with some nice sparkly particle effects and a hoard ambush and he'll lose track of the logic sequence.
Which brings up the question: Level designer -- Illusionist or Engineer?
First, in contrast to the fake exit in doom, I thought the exit at the end of Jawbreaker was a good example of a suprise that wasn't unfair or dirty, but fun.
Second, there was an article I read a while ago about Donkey Kong Country which discussed the fact that you can always trust the bananas in the game:
In order to create this feeling, the game established and religiously followed a few unwritten rules. First, bananas (the common items littered everywhere on every level) are always helpful. If they spell out a letter or an arrow, it�s always a genuine clue, never a trick. If a single banana is placed in some precarious, seemingly impossible to reach spot, it�s always pointing to a secret. If a banana is over a pit, it always signifies that jumping in the pit will not kill you. In effect, the bananas themselves are a character�an entity�trying to help you at all times.
The whole article is a recommended read: http://www.sirlin.net/archive/hiding-secrets-in-platform-games/
let's put bananas in quake levels =)
Now that looks like a cool site. I've got it bookmarked, and hopefully I'll get to read some of it later.
wrote to sirlin a while back. He said, "I like your aerowalk [whatever that is] guide, you should buy my new book!" But, yeah, he's got some good insights into competitive gaming.
I heard the book is better.
My insinuation was that he shamelessly promoted his book to the detriment of a possibly interesting exchange of ideas.
My insinuation was that the book is always better than the movie.
but what if the movie was filmed in joequake?
My insinuation was that the book is always better than the movie.
Godfather -- movie is, well, the Godfather, but the novel is trash. It reads as a pretty intense story, but because the publishers took the rough draft from Puzo and published it as is, it contains lurid and weird material that Puzo never intended to see the light of day. Like a mobster moll with a super sized vagina that only Sonny has a big enough dick to please. Later, she is sent off to Vegas, and gets it stitched to a normal sized Caucazoid female by a doctor who lost his license for performing abortions so he winds up working for the Corleone family.
metlslime: I dunno. Are film directors who use JoeQuake immediately elevated to the level of Hitchcock? Somebody better tell Paul Anderson before he decides to make a sequel to Alien Vs Predator.
headthump: you're entitled to your own insinuation.
I'm Just Saying
the part should be played by Christi Canyon in a Godfather remake, and Ron Jeremy can be Moe Green.
39 of the DK coins are hidden somewhere inside a level. Exactly 1 DK coin is hidden in a bonus room inside a level. A secret within a secret. The game has trained the player to assume that no secrets will be in a bonus room, so what better place to hide something?
If your game has design tools like 'bananas' you can use like that, you're golden.
Discuss: What bananas does Quake have? Other games?
<lunaran> should I put armor shards/+1 health packs in Coriolis Force?
<metlslime> yes. It's fun to pick things up.
<lunaran> it IS fun to pick things up.
Finishing Your Mod
... is a carrot on a stick.
also, you just grepped your logs for "coriolis force" didn't you?
ah, you missed my point. shards/stimpacks serve a similar purpose to coins/bananas in that they are relatively worthless but plentiful, and make a nice sound when you pick them up. They are FUN to pick up, so people go out of their way to collect them anyway.
Perhaps they don't serve the secondary purpose of bananas, which is to provide hints or clues to the player. But they are at least relevant for the first reason.
also, i couldn't find that quote on google, so i just wrote it from memory.
= health packs, easy!
Come on, they are fullbright so you can spot them easy, they are sometimes in places you cant get to imediately, but you know you CAN get there or why would there be a health pack there. They are sometimes in dark areas, so you know its safe to go in there to get it, etc.
They are sometimes in dark areas, so you know its safe to go in there to get it, etc.
If there happens to be a hole in the floor, or a trigger that springs a fiend in the players face, that health banana won't have such a sweet taste.
Actually, I'd argue with myself that it makes the taste of the banana even better when you kill the beast and get a little health boost.
You're a twat, than.
No, YOU are a twat.
you could argue that putting a hidden trap in a very dark area with a health pack as bait is very bad design =)
Unless you are a bastard level designer like, ooh I dunno, me :)
So you can use items like that.
Has anyone ever actually attempted that? Solved the problem of showing the player where to go by luring him with an item? I frankly had never considered that, since often FPS maps just aren't that navigable - you don't need an item to show the way because the way is usually bleeding obvious.
Am I wrong?
i mainly use architecture and lighting to call attention to the important features of a room, such as exits.
however... in Breakthrough I did use bad guys to guide the player, becuase the levels were more open. So you'd have player walking through a forest, and if a group of nazis started shooting at you from the top of a hill, that would naturally lead the player towards where they emerged. It was a pretty common MoH thing.
I bet that could be helpful in quake too, especially in levels with a lot of criss-crossing through the same rooms.
Actually, as a player, I picked that up many years ago. If I'm wandering around in a non-linear level and don't know where to go, I just try to go everywhere until some enemy attacks me, and then see where he came from.
Not quite the same overall appeal as bananas since enemies are usually considered bad. Except for grunts. Grunts are easy to kill and generally give you far more ammo than you expended to dispense with them.
I guess enemies draw the player to the extent that he is healthy/armed enough to fight them. If he's weak, they repel the player of course, but otherwise, they draw the player becuase in quake, the main gameplay is fighting monsters, so people who play quake want to fight monsters.
I think that thing with monsters showing the player where to go may be called monster trail type of gameplay in complex levels.
And about bananas in quake I think that any useful item (not only health) can be easily used as "banana". If an item is placed in any place, that means that this place is reachable for the player. The other type of banana can be a specific for one level thing (sign, special item, unique lighting, model or maybe even special peaceful monster/npc that guides you) that repeates thru the whole level.
Website copyright © 2002-2017 John Fitzgibbons. All posts are copyright their respective authors.