Skip to main content

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

Levels grinding

Experience points (XP) hunting means getting a certain amount of experience points to progress to the next level and is a one of the core game aspects of many games.

It is so popular in games the fact is I saw it in more than 100 games. And rightfully it is, as it's a master-piece of what many people love. But what is the underlying mechanism? While it may be lots of fun for many players, the whole point is just doing the same kind of tasks to level up.

Personally, I don't find that too interesting. I mean clearly it is there for a reason, but why would anyone call it fun, if we look directly at the underlying mechanism?

Is it fun then because of  being a superior level? There is a level cap in most games, but what about ones who use infinite level cap? Well I think this a good step beyond capped-skill leveling, but clearly we can go further than so by going a step ahead?

My idea is basically to make something which requires doing special tasks, such as getting more XP by doing epic quests.

The whole point of this post was to show you classic level grinding doesn't have to be included in any game, even in a role-playing game(RPG). If there is really a better leveling system possible, clearly we can make a better one! This won't save the world, but you should consider it before trying to make another MMORPG(massive-multiplayer online role-playing game) which lifespan relies on classic leveling.

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.