News | Forum | People | FAQ | Links | Search | Register | Log in
D. U. I.
Designing User Interfaces. Well, ok, not quite.

I had some free time on my hands, and so decided to play Yoshi s Island because of some of the praise it s been getting here. And while cruising through it, I realized just how many visual clues it has. Arrows and various signs are in abundance, so you re never lost or confused, and most secret areas arent tucked away under some obscure texture, but are in plain view, just waiting for you to figure out how to reach them.

So Im curious, how much importantance do you place on making your level easy to navigate and understand? Do you do anything special, if so what? Or should the player have to figure everything out by themselves? Does having these hints make it too easy?
First | Previous | Next | Last
... 
Matter of choice and personal taste, I would say. 
My Approach... 
For big ticket items, i like to have an obvious cue saying "i am a secret" like a megahealth behind bars, or a quad on a high ledge or something, to tease the player. This challenges people to figure out how to get the item.

For any secret, even a +25 health, i think it's important to have a subtle clue that tells players how to get it -- slightly rotated texture on a shootable door, or one light fixture that is a different color than the others, or whatever. The cue can be MORE subtle in cases where the tease is also present, becuase then people will be trying stuff anyway. (shooting walls, exploring, etc.)

As an alternative to the subtle cue, i like to put the access to secrets in a place that players often don't think to explore. This can be becuase it's obviously not a route, like the pool of water in house of desolution. Or, it can exploit the fact that players don't think about how moving objects change the environment -- the quad under the lift in contract revoked is a good example. You can also exploit the player's limited spatial sense, especially with regard to the vertical dimention.

Or... well, i'd give more examples, but i don't want to give away all the secrets in my unreleased levels :) 
Teh Secret Of Sterces 
Or... well, i'd give more examples, but i don't want to give away all the secrets in my unreleased levels :)

Heh, too true.

While cramming secrets into Contract, I tried to go for variety.
Some of the secrets are intended to have a direct benefit on subsequent combat, the lightning gun hidden in the first map is a good example - the LG is the best weapon to use against shamblers so providing it at that point allowed about 6 shamblers to be defeated more easily if the player found the secret. For that reason, the 'tantalizing visibility' trick was used so the player would at least be aware there was something to find.
For more powerful, potentially devastating benefits like a pentagram, I have no qualms about being an utter bastard, tho I always endevour to make the secret an integral part of its surroundings, like using the chequered platforms or wooden beams.
I guess I assume that any player will try to explore every reachable area of a map even if it's not part of required navigation; especially if it's not part of required navigation. I do that in every FPS I play - I'm a nosy cunt - so I tend to put secrets in corners, dead ends, pools , pits and so on.

In terms of normal navigation, I always try to make the path explicit. Arrows I find are a hokey way of directing the player because they look incongruously generous for an environment that is otherwise trying to kill the player; a last resort only. One of the important things about SP is giving the player room to look around - places to stand, distance to jump - so they can gradually build up an impression of the overall construction of the map. It also helps if the layout is based on consistent elements that the player gets used to.
Lighting is also critical - ffs, don't leave the most important exit in a room in total shadow. That can be really frustrating. Weapons should also be delivered to the player in a way that is unmissable even to a myopic elephant.
Basically, the more important a structure/item/route is to progression, the more prominent a place it should take in the player's perception. 
Another Point 
another rule i try to follow is: never give the player a key until after he sees the door that it will unlock. This is a specific case of a more general principle, that it's good to have places/things that a player sees but can't get to until later, creating anticipation/desire and then later providing closure. It also defeats the purpose of a key to have it unlock a door that you don't get to until you have the key, becuase the door never blocks your progress, then. 
Yup 
same goes for switches really; see moving part -> find switch.
Also, if a switch is remote from its target, there should be something to help the player match up action with consequence: center print message, texture similarity etc. Mostly important in a map with lots of doors or switches. e.g. all the shootable switches in Contract were for secrets only; all the same animating texture, different texture from 'normal' switches.
Consistency, people, consistency... :P 
Yeah 
I liked all the custom Q2 maps that used the destructable-crate texture on non-destructable crates. 
... 
I think metlslime is pretty much bang on.

The are two things I find I say to myself which signify a bad map design. The first is: "so what the hell do I do now?" And the second is: "why the hell did that happen?" Saying hell is an integral part of it. :)

Do what Nintendo does, not what Cyan Worlds does. 
 
I liked all the custom Q2 maps that used the destructable-crate texture on non-destructable crates.

On a somewhat related note: is there ever a point when these design elements become cliche? And if so, how wise is it to try and change it to something new? 
Yes, 
they can become cliché. But the principles behind them are universal, i think. 
Hmm 
cliché? 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.