Jump to content
  • Advertisement
  • 08/05/13 07:25 PM

    Crafting a 2D RPG

    Game Design and Theory

    In this article we are going to go over a nearly-complete Game Design for an RPG game. We are going to take a look at how the game world is going to be structured, how the player is going to operate, what kind of enemies we are going to have, a deeper look into the skill tree and much more. I plan this article to be lengthy because I would like to cover as much material as possible. So here it is, let's get started.

    The RPG

    So I'm not going to go in-depth here on all of the features. They will be discussed further down the article. However, I am going to make an overview of what we are going to design. To start things off, I want to say that we will be taking a look at a simple example of a 2D-Style RPG. We are going to keep it on a beginner level in nearly all terms. So, the 2D-style RPG will feature an old school King's Quest kind of camera. And yes, I know it's not particularly famous in the role playing genre, however I'm a believer that people should experiment when designing their own games, especially in the indies. So long story short - that's how I felt the viewpoint should be for the purpose of this game.
    Camera 01.png
    Now onward with the player. The player is the most important unit in a game, especially in a RPG. At the beginning of the game, the player will get to choose his character's gender, have the option to switch between two sprites per gender to customize the look and from there - pick a class. The available classes are going to be Warlord (Warrior), Tempest(Warrior/Caster), Elementalist (Caster) and Forest Hunter (Archer). Upon choosing a class, the player is going to be put inside the game world. From there, the player can level up, gear up etc., and thus improve the character. And as far as controlling our player's movement and using specific objects (yes, we are going to talk about this too), we are going to keep things simple - point and click, point and click, point and click. Each character class is going to have its own unique skill tree. Though we are not going to overload this rather simple game with higher-end mechanics, we are going to implement a couple of different use cases for each class' skills. The Game World, as you may have already guessed, is going to be based in a fantasy medieval world. For the bigger part, the world is going to be structured around three large cities, several smaller ones and other areas, such as forests, graveyards etc., and to make things more interesting and not go too linear with the gameplay, all of these regions are going to be available to the player from the very beginning, with an exception for one particular region but we will talk about that later. But back to the topic - the player is going to have one starting zone and from there it's going to be all about exploring the world and going from region to region on a free note basis. You can pick up quests from each region at any desirable time, however there are going to be main quests that are going to get highlighted. But again, we'll talk about that when the time is right. The combat is an essential part of an RPG as well. In the current design for this RPG, I wanted to go for a turn-based combat system. Since we are reverting to old school methods, I thought that it would be an interesting feature to be able to build your attack on a turn. The skills and attacks are going to be selected from a menu and executed on that turn. The first one that gets a go at attacking is the attacker. However, as we are going to see with the enemies, this might not always be the player.
    Combat 01.png
    The narrative is also something that we are going to work with. And not just the narrative itself but the entire story telling process. Firstly though, we need to keep in mind a couple of things - there are players that want to dive deep into the story and the lore and there are those that just want to get the objective and move on. Now, normally you can't make everyone happy, however for this particular case, there is a resolution that suits both types of players. We are going to discuss this further down the article. Another thing to note about the story telling is that we are not going to implement the entire thing in narrative. We will work around this by telling stories through the gameplay. Again, in the Narrative section we will take a closer look at how we can achieve this. In terms of an item base we will have a big variety to choose from. We will have three basic item classes and they are going to be based on quality. The items are going to be of normal type, rare type and artifacts. The normal gear can be bought from shops throughout the game and as loot from lesser enemies. The rare items are going to be loot exclusive and are going to be dropped by more powerful enemies. And finally - the artifacts. They are going to be connected to the story. That would mean that you can get this gear by completing quests - both main and optional. The artifacts will be related to the story and will be the most powerful item quality. In order to maintain balance, however, these items will be way harder to find. This will be discussed in detail in the Items section. The Quests are also going to be an interesting component to the gameplay. For this design we will have two main quest directions - main quests and optional quests. Both are going to contribute to the story and the optional quests are going to help the player out a lot in terms of gear, leveling and skills. However, only the main quests are going to be mandatory to beat the game. So, this was the overview of the RPG. Now let's get down into details and explain further on the listed components and expand with new ones.

    The Player

    The Player will enter this game in the shoes of an unnamed main protagonist. The player has to be able to engage in all of the core mechanics of the game and thus - make the experience full. This would imply that the player needs to be able to do the following things:
    • Navigate freely throughout the game world.
    • Interact with certain objects.
    • Initiate in the game's story by engaging in dialogues and mainly quests.
    • Evolve accordingly with the game's story and progress.
    • Have the option to do certain things before others - that is, have options in front of him.
    • Has to be as much a part of the story as any other component of the game.
    Now, let's see how we can accomplish that. First we'll start with the navigation. As we are going to see in the Game World section further down, about 80% of the regions are going to be unlocked for us to explore and take part in quests, fights with enemies etc., and by crafting such an open world, we get the freedom of choosing a different path each time around, without actually creating story dependencies. As we will see further down the line, the main motive in the game will not require the following of one routine path, rather multiple linear quest lines with no particular starting point. Another interesting notion are the controls and the point of view of the player. We will be able to move around the world and interact with it on the point and click principle. This is going to allow us to have a more quest/adventure-like feeling to our game, however the core mechanics are still those of an RPG. As far as the point of view goes, while exploring the world, we will have our camera fixated on the visible region that we are in, instead of the player. This is mainly for simplicity reasons in developing the navigation to different parts of the game world. As I've mentioned a lot in previous chapters, this is a design for beginners, so in my mind it would be better to focus more on the pure RPG elements instead of focusing on the point of view and camera angle (though this is a really important feature in itself). Another plus to this is the fact that such a game with a point and click movement and region fixated camera, is really easy to port to a mobile device and yet not compromise controls and still be easy to catch on to. In the upcoming sections we will expand on the player logic and how he handles himself in the game world.

    The Game World

    The Game World is one of the most important things to develop here. The fictional world that gives life to our fantasy has to be thought out in such a way, that it makes the player dive into it. Now, firstly, let's take a look at what we have as a design for the current game.
    World Map 01.png
    So, this is what we have. To cut things into pieces, we have three main cities and several smaller ones. As you may have guessed, these cities are going to be the place where we will explore for quests and where we will be able to purchase items. We will go into detail how this is going to be structured further down in this section. Now, aside from these cities and towns, you can see a big red area. This will be the place that is going to give us access to the last parts of the game - some pre-final battles and a last boss battle. How this works, we'll talk later on. Something I especially want to look into here are the regions. If you take a closer look, they are split into themes. Each big city has it's own area and that area has it's own theme to correspond to. For city A the theme is going to be "Forest", for city B the theme is going to be "Mountains" and for city C - "Water". This is evident by the way these regions are structured - with A we have a logistic pathway that is surrounded by trees. For B our path is clearly surrounded by mountains and with C - sea side and rivers/lakes. All of the elements that have a path leading to them are going to be explorable and most certainly are going to be a part of a quest. If there is a road to it - you can go there. Now back to the themes - if you take a good look at the world, you can see that we have taken into consideration the altitude. Why? Well, the most important reason is to make the player's journey feel more like one. If you straight up hop from the mountain to the sea coast that just feels too fast-paced. With a smoother transition mountain - forest - sea you give the player a chance to feel more like he is on a quest and on a journey, rather then just going from one place to another. The themes are not here just to make the world look nice though. We are going to have different enemies in the different regions. Each foe is going to be in a corresponding blend with the current theme. That's to say that for example, in the woods we would get attacked by a feral wolf or by a pack of bandits that have the proper attire. In the mountains we would be attacked by some Big Foot type creature (we will get to the enemies later) or by bandits in winter coats. And at the sea coast we would get attacked by a sea monster or by pirates. As we will see later with the Character Classes, the themes are also going to have a big effect on the character's biography as well. Another thing to note in the world design are the paths and the logistics. In order to promote the exploration factor, we should be able to go from any one area to any other. It might not be through a direct path, however there needs to be a connection. And on that note, if you look at the entire structure of the map, it is built like a graph. This particular map is not picture perfect in terms of the core graph design that is often implemented into building such a thing. That's for two reasons - firstly, at the moment I don't have the resource (especially in terms of time) to build it in the absolutely by-the-book way and secondly, I want to keep things as intuitive as possible. However, when performing this kind of design for a game that is going to go in production and out on the market, you should do your work on the graph structure. Without going too much into detail, you can check more out on the graph theory here. Now - onward to the cities and how they should be structured in this design. Let's take a look at the following picture.
    City Big 01.png
    In this picture we have an example of how we would build City A from the world map. As you can quickly see, I've mapped out only the buildings in the city. Stuff like the Town Square, fountains and other public places are not put into this. They are up to the artist, as they will more likely craft the atmosphere. However, we need to take a look at the functionality in the city, so here is a list of the buildings and what they are there for:
    • City Hall - This is an important building for a lot of reasons. Most of your NPCs with high authority are going to be nested here. The story line intersects with these authorities, whether it's the Mayor, the city guard's Captain or whatever. A lot of the quests will lead you up to this building.
    • Temple - This is the religious center of the city. As you will later on see, in the fictional religion of the game world, this would be the place to go and seek spiritual advice. The Temple is also going to serve the purpose of a healing center, a hospital if you will. Not in a literal way though.
    • The Weapons Shop - Here you will be able to buy/sell items. Mainly weapons. This shop is a useful point for the Warlord, the Forest Hunter and the Tempest.
    • The Armor Shop - Here you will be able to buy/sell items. Mainly armor. This shop is a useful point for the Warlord and the Tempest.
    • The Clothes Shop - Here you will be able to buy/sell items. Mainly leather armor and robes. This shop is a useful point for the Elementalist and the Forest Hunter.
    • The Mage Guild - This place is pretty much the biggest interest point for the Elementalist. From here you are going to be able to buy staffs, wands, books etc. (the items we will cover later on).
    • The Supply Shop - Here you will be able to buy/sell items. Supplies like food, bandages, potions and others.
    • The Prison - In this place you are going to be able to take up "bounty hunter" quests. These are going to be discussed later on.
    • The Library - This is going to be a point of interest only for the players that want to dive deep into the story of the game. As this design promotes exploration, the library is going to do just that - give you the ability to explore facts and myths about the game world. You are going to be able to read books on enemies you might encounter, on the origin of the player classes and many others.
    • Every other building on the picture, the Courtyard included, is there to be able to meet you with quest givers. People from the population of the city. That's not to say that you can't design the vendor at a certain shop to give you a quest, however the approach with having ordinary citizens reveal their not so ordinary stories through quests, is something that can be really enjoyable. The other buildings can vary. I've depicted them as houses, however the artist can choose for them to be something else.
    Now that we have the big city broken down, what do we do with the smaller cities? Well, here is the thing - we need to scale this down. To start off, instead of the large City Hall, we would have a much smaller Town Hall. The figures of authority are going to be less. Adding to that, we are not going to have separate prisons and courtyards. We are going to blend this into one institution. Be it somewhat of a Sheriff's office or a detention center. And as far as the shops go, we are going to start to combine things. We are going to have a Blacksmith instead of an Armor Shop and a Weapons Shop. The Mage Guild will scale down and we will have a Druid Gathering or something along these lines. The Supply Shop is going to be scaled down as well and will be combined with the Clothes shop in a Local Market where we are just going to have two separate vendors for supplies and for clothes. The Temple is going to be much smaller and it's going to be the source of the book readings as well. This means no library. So now we've covered the world, the regions, the cities and towns. Time to move on to the next topic.

    Basic Story

    Now in order for our world to have some logic into it, we need to mark out at least the overall story. No details, just the most fundamental things. They influence the gameplay, so basically we need to have them. So without going into names, details and other things along these lines, here is what it's all about. The game world was crafted by three godlike entities - one for each of the themes. A forest god, a mountain god and a water god. These three entities were tyrants and despots. They saw creation as a means to have something to destroy. As years pass and their torment over the beings of this world progresses and this pointed out to a defining moment in history. One of their own creations - a demigod hero, created for the purpose of forcefully spreading their will, is now too attached to the earthly creatures and opposes the entities. After an excruciating battle, the hero manages to seal them in an alternate isolated realm. He would have to offer himself as a sacrifice for three seals - one for each of the entities. By giving his own life, he manages to lock up the evils away from the realm of humans. The three seals were scattered throughout the world into the strangest of places and thus - the tyrants were no more. After the three entities were locked away, humanity progressed like never before. The people managed to find left over artifacts, scrolls and many other things that belonged to the tyrants and their minions. And even though the minions were still in this realm and not with their masters, they were no match for the humans. They became outcasts - terrorizing and attacking from a distance and not engaging in open warfare. This state allowed the humans to evolve beyond anything they've imagined possible - they tamed magic, they became exceptional warriors, they started to bend their own world to their will. In the wake of these events, a new religion came to be - one that would worship the hero that locked away the evils so long ago. And in the way of that religion, an order would be formed - The Order of the Tempests. They settled near the gateway to the other realm that was sealed so long ago and protect its entirety with their lives. Even more years pass. The hero, the evil entities and their cosmic battle now looks to be more of a religious story then an actual event. The only ones that still see and treat it as something real are the Tempests, however with time, they started becoming more and more of an outcast heretic order. However, some disturbing events are starting to unravel. The minions of the godlike entities, treated like insane heretics by the current population, are growing in numbers. They are starting to go through with more and more open attacks. It is at this point that our main protagonist receives a dark vision. The likeness of the ancient hero appears to him/her and tells a story of an upcoming storm that you have to stop. A story in which the evil entities have to be killed once for all or humanity will be devoured by them. And thus - after deepening the visions, our player is convinced that this is something that's real and has to to, so he/she sets on a quest to find the three seals, enter the tyrants' realm and put an end to them once and for all. So, now that we've looked at the story, let's go to something else in that regard - the questing and the narrative.

    Storytelling, Questing and Narrative

    Now, in order to get a better grasp of how we are going to handle things with the storytelling, we will start off with the quests. Questing is going to be the essence of the game. We don't want a grindfest, mostly due to the core mechanics of the game. What we want is for the player to get the goods and rewards he deserves by doing something significant, at least to some extent. So, now we will have two lines of quests - main and optional. The main quests are going to serve as your progress meter - the more of these you complete, the further you will go. However, doing main quests only should not make your experience the best one out there. Yes, sure, you should be able to play through the game but not easily. The main quests should play the role of the mechanism that moves the story forward while optional quests should be there to grant the player experience and thus - levels, to enforce the story and last but not least - to help the player gear up with good items. That way, you will make the player experience more full and in turn - promote exploration. This is at the core of the current mechanics so this is something that we should strive for. Now onwards at how we are going to tell the story. This is something that we have to be very careful about. There are players that love story and dialogue and there are those that want to get straight to the point. Both types of players are right in their wishes and it is not impossible to attract both in one game. So to start off, one of the most important things in this regard are the dialogue interactions. On initiation, the dialogue should be short, concise, make a good but short summary of what's it all about and if it's information regarding a quest - you should be able to receive it in as few sentences as possible. However, with this being said, this should not be the dialogue in it's entirety. This is the feature that's meant for the players that want to go out and do things instead of talking. But let's extend on the dialogue - after everything is said and done, you should have more dialogue options. One is to stop the dialogue by saying "Thanks, bye now." but the others should have the function of extracting more and more information on your current topic. These other options should not contain data that is mandatory to complete the quest - that should be in the first, short version of the dialogue. The dialogue should enforce additional story, not mission objectives. So, the dialogue structure is out of the way. However our storytelling should not be restricted in just the narrative of dialogue. The gameplay and environment should be able to help out. How? Well, let's give a couple of examples. Let's say that you have a quest in a town and the objective is to hunt down a dangerous criminal. You have not taken the quest yet. As you go through the town, there should be one or two "WANTED" posters. On "use" action, you should be able to read more information on the wanted person. Also, this can be enforced by having the local people talk about the criminal. That way when you go and take the quest, you know what you are dealing with and that's done with no cut scenes and no additional dialogue. Another example of this would be the ability to read parts of the story in a big city's library. Let's say you want more information on an enemy type that you've encountered in the region. By going to the library you can read something on that enemy's origin and other helpful stuff along these lines. Another thing to note are the cut scenes. Even though we are talking about a 2D game, this can still be an issue. Cut scenes are awesome when implemented correctly and a real joy killer in other cases. So for our design we should have as few cut scenes as possible. They should be reserved only for the most important parts of the game and should not be too long. In them, we should just get the main point across. Nothing more and nothing less.

    Player Classes, Leveling and Skill trees

    Now, in the beginning we've talked about the four classes that we are going to have - the Warlord, the Tempest, the Forest Hunter and the Elementalist. Now we are going to go more into detail of how they work, what their skills are going to look like and what the skill tree system is going to be. Just to clarify though - we are not going to go into details in terms of skills. Just outline them. Otherwise this article is going to get way too big. So now on to the classes. Warlord - this is the warrior class in the game. Brutal and ruthless, the Warlord craves combat and glory in an open battle. Can equip heavy armor and leather armor. Can use swords, maces, axes, spears, daggers and knives, hammers, shields. The skills of this class should be orientated to melee combat and close-quarter fighting. The skillsets that the Warlord can implement are those of a two-arm weapon specialist, dual wield weapon specialist and sword and shield specialist. This would mean that the first type is a slower, more damage dealing kind of build, the second is a faster fighter that deals less pure damage but more critical hits and lastly the last build is that of a character that places defense and attack on the same level. That is - he does not have the biggest damage output, however he can survive. Now, some of you might ask - what does faster and slower mean in a turn-based RPG? Well, it means that if you play a slow character, there is a bigger chance that your opponent can attack you twice before you can attack back. A faster is the opposite - you get a bigger chance of attacking twice. In case you level up correctly, you can get that attack number to three before the opponent can lash back. The normal pace is the norm - turn per turn. Tempest - the tempest is part warrior part caster. Can equip heavy armor and leather armor. Can use one handed swords, maces, hammers and shields. The skills are orientated to melee combat and close quarter fighting. The Tempest in his essence is not a real caster. The skills at his disposal are primarily buffs that increase either the attack, defense, speed or other attribute. Aside from that, the combat abilities are paced to an offensive warrior with a weapon and shield. This class should really be diverse and the way of play should be felt the strongest at your combat strategies. Elementalist - this is the caster class in the game. The Elementalist uses magic to bend the elements to his will. Can equip robes and clothes. Can use staffs, wands, daggers and books. In the gameplay of the Elementalist, the book is the off-hand weapon, like the shield in the examples above. Aside from that, the staffs can be two-handed and one-handed. The wands and daggers are naturally one handed. As a skill set, here we have three main builds - a fire mage that uses the power of the flames, a lightning wielder that bends the lightning to his will and a water mage that uses immense water attacks to drown his enemies. Forest Hunter - this is the archer in the game. The Forest Hunter's purpose is to keep the balance of nature intact. That some times, and that's quite often, requires a lot of killing. Being more of a cleanser to those who would threaten the forest, this range fighter has no problems in doing whatever is needed. Can equip leather armor. Can use bows, crossbows, daggers, knives, claws. As a build, the Forest Hunter can go on and kill opponents from a distance, thus giving two attacks to the player one after the other, he can also attack up close with increased critical hits and last but not least, he can use stealth as an increased defense mechanism, thus making him hard to hit. Each class has their own starting region. For the Warlord that would be the cold and brutal reality of the mountain terrain of City B; for the Forest Hunter, the woods of City A are the perfect place to fulfill their desire to balance out nature; for the Elementalist the perfect home are the shores of City C where they would gather knowledge from many known and unknown wizards and mages that travel from coast to coast; and the Tempest would find refuge in the town that's positioned right next to the sealed gate (the big red circle on the world map), leading to the exiled ancient evils. Now onto the leveling system. Naturally as with all games of this genre, we will level up through gaining experience. The attributes of a character (strength, agility, magic, health, mana, stamina) are going to be automatically incremented on a pre-defined basis. Per say the Warlord is going to gain more strength per level then the Elementalist. Now, as far as the level cap goes, in my estimation a total of 30 levels is going to be more then enough for this small setup. Now, on the topic of the attributes, we should take a look at just these simple schematics - strength increases damage; agility increases the chance that the enemy misses an attack; magic increases magic damage; health, mana and stamina are pretty clear. The one thing that needs to be noted here is this - the resource that the Elementalist and Tempest use for their skills is mana, and the resource for the Warlord and Forest Hunrer is stamina. So now that we've got the leveling and attributes covered, let's take a look at how we are going to spend skills. You will gain one point to spend per level. You will have a skill tree split into three branches, each of them being a character specialization as shown above. Now, the first skill of each branch is going to be unlocked at the beginning, the others are going to have a requirement of points invested into the branch. So, with the first skill being unlocked, you would need 3 points allocated into the branch and more specifically into the first skill in order to unlock the second skill and be able to allocate points into it. The third skill will need 8 points allocated into the branch, the fourth will need 16 and the final and fifth - 25. As the point number allocated per skill grows, so does the skill's efficiency. Now, let's take a look at how a skill can be used in a combat scenario - remember the combat picture from above? Well, the Shield Bash could be considered a skill in that instance. From the UI menu you would pick a possible "Skill" option and use the one that you would want.


    Now to take a brief overview of the items. I've pretty much explained the items' grades and quality up to here, so I'm not going to repeat myself mostly because this article is starting to grow a lot. So, let's see how the rare items and the artifacts are going to affect our character. To start off, let's look at the rare items - they will have higher damage then your normal ones. Aside from that, they will grant you attribute bonuses. For example, a rare sword could give +3 to your strength. There could be all sorts of combinations in terms of upgrading your attributes. However, we need to add a bit of balance to this, so here is a rule for the current design - a rare item should not be able to add bonus points to more then two attributes. The artifacts are a different thing all together. Remember how in terms of the story they are left behind by the three godlike entities and their most powerful minions? Well, we have to reinforce that logic. These items have to really give the player the feeling that they have something special in their possession. So, straight to the point - the artifacts are going to be able to give bonus points up to four attributes. They are also going to be able to give up to 3 points to a specific skill. If the player has not allocated points to that skill, he will still be able to use it but as if just one point was allocated. In some special cases where the item has close correlation to the story, it can possess a special skill on its own and allow the player to use it. Aside from these item statistics, I'm not going to venture more into this, since again, this article is going to become too big. However, I want to note that the key to developing good items and good item systems is to test, test and test again. Do this until you have a good balance and a good experience.

    Enemies and Random Encounters

    The enemies are a key feature in a game where exploration is in the center stage. If you want to have a good exploration feeling, you must have diversity in your opponents. As we've talked about earlier, the enemies are going to be theme-based. In order to make a good roster of enemies per theme, we should do a little grouping that looks something like this:
    • Recurring enemies - these are the lowest in power terms in the hierarchy. Only their attire changes on a regional basis.
    • Region specific - these are enemies you will see in the entire region but are exclusive for it.
    • Area specific - these enemies appear only in specific areas in the region. For example in the cemetery or in a specific forest.
    • Bosses - they are unique. We will only have several of these throughout the game.
    Some enemies should also possess specific skill sets. For example an Area specific enemy from City C, let's say a Hydra, should be able to cast some kind of water spells. This is not valid for all enemies tough. Another thing that I really wanted to discuss is the Random Encounters. So this is how they are going to work - say you are walking down some path that you are exploring and boom - you suddenly get attacked by an enemy. This adds an element of surprise and gives for more excitement. Also, in some areas, it will make you rethink your visits to that place unprepared. The mechanic behind the random encounters is going to be percent-based. Say you want to make an area of a region support this feature. For that specific place you should add a percent that the attack will happen. So this obviously has many virtues in terms of excitement, leveling, looting etc., but what if you are more into the story and the pure exploration instead of the combat element? Well, this is a feature that is easily placed and easily removed. Removing the Random Encounter can be customized per player experience. It can be done in several ways. For example by disabling them on difficulty selection. Or better yet - something you can do is enable/disable them through the Options menu. That way you can have the idea of doing random encounters if you want to, and not do them if you don't feel like it.

    The Final Encounter

    This is a very interesting point. However, I'm not going to discuss it in the current article since we are going into overload mode. I'm going to write a separate article on the encounter where we are going to talk about boss fights in a more broad spectrum and then I'll link the two materials together.


    Crafting a game experience is something that has to come from your own vision of what you want to see. In this design, I wanted to see a revert to the old school turn-based gameplay, quest-like atmosphere and broad exploration. I may have missed out on something but I hope I've encompassed enough in the current article.

    Article Update Log

    2 Jun 2013: Initial release

      Report Article

    User Feedback

    Nice! It's the basics but covered in a way that makes sense to a beginner.

    Share this comment

    Link to comment
    Share on other sites

    Great article, covers most important topics and it's really begginer (a.k.a. "me") friendly. It was pleasure to read this text.

    Share this comment

    Link to comment
    Share on other sites

    "I'm a believer that people should experiment when designing their own games, especially in the indies"




    You can say that again.  Very appropriate level of abstraction for beginners.

    Share this comment

    Link to comment
    Share on other sites

    It's a nice article, and it goes over his ideas for a game, but it's so high level.  I was hoping to see a design a bit lower with generalization of how these ideas would come to life.  Will an editor be used for the maps?  How will items, monsters, cities, etc. be stored and placed in the game?


    Anyway, this article is the 1st step for creating an RPG, but I'm curious how you plan on going to next step.

    Share this comment

    Link to comment
    Share on other sites

    Thank you all for the feedback. I'm glad that this turned out to be helpful to someone.

    @BeerNutts You know, I actually thought of going into deeper levels with this and as far as to go to basic level design for the regions and to map out the transitions form area to area and other stuff like that. Some basic UI for the character screen may be. However I ended up scrapping that idea because there are a lot of developers that just need to get a basic grip of how to build on the basics of designing their first game experience. A lot of guys just want to go into coding the thing and they end up building a zombie FPS or whatever and really when you are using a game engine (Unity, UDK etc.), doing such a game isn't really expanding any skill level, if you already have basic scripting skills. When you have at least some form of game mechanics that isn't fully supported and built into the game engine (example - path finding in Unity v.4+) you need to expand your knowledge both in development and in creative.

    However I do plan to expand this article and finish the final boss encounter. Maybe I'll do it in different parts, I'm not sure yet. I'll work on it in the upcoming days for sure though.

    Share this comment

    Link to comment
    Share on other sites


    Removing the Random Encounter can be customized per player experience. It can be done in several ways. For example by disabling them on difficulty selection. Or better yet – something you can do is enable/disable them through the Options menu. That way you can have the idea of doing random encounters if you want to, and not do them if you don't feel like it.


    Random encounters usually play a very important role in leveling. If the option to disable them is provided to the players, most of them will disable the encounters without realizing their importance in leveling. This will drastically increase difficulty of the game and the players will get really frustrated.

    One way I can think of to avoid this, is by placing 'minimum level constraints' on quests (at least the main quests) so that the player will take leveling and hence,random encounters more seriously.


    The article is really great and well structured. It made me aware of all the basic aspects of rpg designing. Bookmarked this. 

    Share this comment

    Link to comment
    Share on other sites
    There are a couple of a bit more advanced concepts that are a bit harder to implement balance wise in this article. The map design and areas part of the article is fine, but a beginner should not implement skill trees or have so many classes and stats because it is very hard to balance. A beginner should implement only one class that has only the 2 most basic stats: attack & defense. Those 2 basic stats can be used to extrapolate other stats, hp, xp etc. example:
    playerHP = (playerATT + playerDEF) * 5;
    playerXP += (enemyATT + enemyDEF) * 3;
    The less base stat's you have, the easier it is to balance later on. Remember this at all times!
    Also the damage formula is much simpler with less parameters that go into it. example:
    damageToPlayer = randomMax( enemyATT / playerDEF * 10 );
    damageToEnemy = randomMax( playerATT / enemyDEF * 10 );
    You can also add some dummy stats that don't affect anything, like Luck. You specify that Luck affects drop rate, but you don't make it affect drop rate. Now the player thinks it does but can never know for sure unless he reverse engineers the exe. What I want to say is that there are a lot of ways to make the game appear very complex, but internally you keep it as simple as possible to allow yourself easier maintenance. That is the number one lesson for beginners, coming from someone who published 2 small but successful games.

    Share this comment

    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!