Skip to main content

What does a good game consist of? (part 31)

Level tasks

Making fun tasks for the level, is fun developing and makes for
excellent levels. This can be missions, secrets, quests, objectives,
puzzles, side quests, unlocks, story tasks, memory puzzles and most

importantly explore tasks.  Legend of zelda: breath of the wild has a
very large ammount of stuff to beat after you bet the all the story
line quests and levels. It's not necessary, but still hell tons of

fun. All level tasks work something like a bar code, it is hard to
decrypt, unless you have something like a c++ encryption. However,
even levels tasks are built by a game maker or in some cases a

programming language, so we are back to the start of the problem.
Really challenging levels might sound ten times over expensive or
sometimes just plain stupid, but it's a more than welcome reality.

Making camp levels is for example a giant channel, becomes it
requires tons of investment and copy rights support of the us army
army, but with a lot of creativity it is possible to made anyways.

Here is an example level tasks in level design documentation:

the first floor is basic

It is a floor based level design:

First floor = regular rewards
second = regular + unlocks
third = uncommon + unlock + secrets
fourth = boss key

This is a 3 d game. Getting on a higher sounds easy, but it isn't.
This is just a basic pattern example for you to understand, how level
tasks work. Here's another:

main mission = beat the level in 20 min = 20 points
bonus mssion #1 = ?                                = 15 points
bonus mssion #2= ?                                 = 15 points
bonus mssion #3= ?                                 = 15 points

Labels:

Comments

Post a Comment

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() {   ...
Post a Comment
Read more

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.
Post a Comment
Read more