Skip to main content

Level design basics, part 14

Accuracy in levels

It takes a lot of accuracy to beat all the level's objectives. The
primary ones, not bonus. And it takes a lot of skill to be accurate
when firing. So it is very important to make accuracy based

objectives. The bonus objectives are really hard to get. Harder to
reach objectives are fun when based on weapon accuracy. Talking is
basically a good support for team work. So making ventrillo or team

speak support. Objectives are actually very small amounts of data,
but can take a huge place on the hard disk drive and on random
access memory. Memory banks business has a lot of problems with

small, but extensive ammount of data. To build a level, it will take
a very solid draft first. Unreal tournament 2004 has a very
challenging single player and multiplayer. I think that forest levels

can be awesome to play if done correctly and they provide accuracy
challenge. A good example be a small rectangular geographic level
with most objectives being at small altitude. Especially if there are

monster protecting it. A good example of such level design would be
a combat arena with 4 very hard places to climb on. Means it takes a
lot of weapon accuracy to even have a chance at bonus objectives.

Team speak can contribute to the accuracy and if there is enough
loyal team work. The hard to reach objectives at locked non standard
mission doors and higher altitude take a mastery of effort to take.

Wild forests are scary, but fun to play. There is enemy danger and
animal monster type danger every where, which is why it is fun, as it
is challenging. Challenge makes a level fun, which makes the game

fun. And challenges in life are fun too. Avoiding challenges is smart
if you are not ambitious and don't want to appear arrogant, but
avoiding challenges in life, just like in levels isn't much fun.

To apply accuracy in levels, use challenging monsters and opposition,
carefully pick challenging attack spawn points; for example in unreal
tournament 2004, skaars are really much fun to fight against.

Comments

Popular posts from this blog

object oriented programming

Object oriented programming is a sound and bold approach to c++ and internet wiring application and video games. It reduces a lot of code messes, made by global and half global functions. One of the more advanced object programming techniques are private access, poly morph and object message inheritance. It is set by c++ bjarne stroustrup and iso isometric standard convention comitee to use classes instead of structs and structures for making objects. Which means you most definitely should , but not must or have to. class Monster {     std::string memory_attributes{}; public:     void treck();     void track();     void trace(); }; The treck() function makes the monster roam and do human like jogging and trimming. track() means the monster goes ai path tracking and trace() means it tries to find other monsters in the area. class Weapon {     std::string memory_attributes{}; public:    void use(); }; void Weapon::use() {   ...

C++ and OOP in a different manner

Keep in mind this article is meant strictly for C++ game devs and not for application programmers or game devs of scripting/other languages. I have my own technique when it comes to OOP in C++. The game I'm deving right now(or we are making) is a simple windows console project. It's up to you to decide whether you'll use this technique. First let me tell you in which cases you might need this technique: if you're ready for a new look on OOP if you need a new toolset for your coding practice if you like to learn(which I clearly hope for) So, the technique then. Decide which you prefer more: classes or structures. This helps you understand what kind of objects you want in a game.