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

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() {   ...

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

Programmer's Role in Game Development -part 1: Better Code Organization This will be a bit different blog post compared to the previous. It will be a sub-series of the role of programmer in the game development. The first part of the sub-series will explain how a game programmer is more effective alone or in a team. Code organization is in my experience essential, as the amount of code quickly increases, especially if the game has many features. It includes: knowledge of the programming language, APIs, dev kits and make sure you know the techniques with which will you finish the project  list of steps to get there a clear to read and understand GDD a clear task list don't rush to learn everything about everything related to your project-set to make a project which you can actually handle(=have learnt 98%-100% about it) There you go, one step closer to understanding how to make a classic game.