Designing Game Elements: Game State (Part 5)

Designing Game Elements: Game State

Everything in the game together, including the current player resources and everything else that makes up a snapshot of the game state at a single point in time. 

Since the game is meant to have an MMORPG feel, a database must be used in order to track important details of the final game state whenever ending a session. The database is then used in the following session to continue from where the game was left off.

The following is a list of the Game State Variables that need to be saved:

Player Character Names along with the respective player names must be saved in order for each player to be able to continue playing their characters in future sessions.

Equipment / Items which are equipped by each player must be saved in the database in order not to lose player progression. When players regain their equipment and items in the following session, they will be able to work out their total stats (Max Health / Power).

Gold which the players have been saving up also must be saved, for the same reason as with equipment and items.

Current Zone refers to the highest level zone which is currently accessible by players but is not yet completed. This must be saved in the database in order to keep track of how many zones the players have completed so far. In the following session, the current and all lower level zone decks are made accessible to players but only the boss card of the current zone is added since all previous bosses had been defeated by this point.

Conclusion

At this point, until the game rules are updated, using just these variables will be enough to catch up to previous session's game state.

Designing Game Elements: Resources and Management (Part 4)

Designing Game Elements: Resources and Management

This refers to everything that is under control of a single player. What kinds of resources do the players control? How are these resources manipulated during play?

Resources controlled by the player:

Health Pool is the amount of damage the player can take before dying. This resource can be improved through Equipment / Items.

Damage Taken is the amount of damage the character has taken. This is more of a drain which must be managed. Its purpose is to add danger of defeat while the player progresses. Damage taken must be reset before it becomes greater than the player's health pool.

Power is the amount of damage done when the player attacks. This resource can be improved through Equipment / Items.

Equipment / Items are purchased from the market for gold, but they give bonuses and effects to whom has them equipped.

Gold is earned by defeating enemies and is used at the market to buy Equipment / Items.

Enemies can be encountered while exploring, they are a threat to players because players must take damage in order to defeat them and gain gold.

Designing Game Elements: Rules (Part 3)

Designing Game Elements: Rules

The rules of play refers to three things:

setup (things you do once at the beginning of the game).

progression of play (what happens during the game).

resolution (what conditions cause the game to end, and how is an outcome determined based on the game state).

My goal here is to use the basic rules of the game 'Munchkin', but twisting them to fit the MMORPG
atmosphere I wish to achieve.

In munchkin combat was resolved with a simple comparism of power levels. The team with the highest power level wins the encounter. This is very quick and simple, however I wish to add character customization and longer combat encounters in order to give the game more of an MMORPG feel.

Setup

The database is opened or loaded (using a notebook or spreadsheet).

New players get:

• Name added to the database.

All players are informed of their character's current state (which zones they may access, damage taken and gold).

All players are given the items they owned in their previous sessions (if any).

Players are advised to keep track of their stats in order to help them when they're making decisions (using a paper or notebook).

The 'market' deck is shuffled and placed face down.

All 'zone' decks accessible in the current game state are shuffled and placed face down.

Only the highest level 'zone' deck will contain its boss card.

The turn order is decided and players start taking turns.

Progression of Play

During their turn, the player can choose one of the following actions:


- Teleport to a town and rest

Damage taken by the player is set to 0.

Player may leave the game session while in town.

(Note: Right now when a player teleports to town, they don't lose any progress towards finding the boss. This works against the element of risk and reward and will need to be updated).

- Search the town market

Player draws 3 cards from the 'market' deck and may spend gold to purchase any of them (as long as they can afford it).

Cards that are not purchased are returned to the market deck which is then shuffled.

Player can place the purchased card face up in front of them to show that it is equipped.

Player may only equip 1 item of each type, if the player has more, they must choose which one to equip. The other card is returned to the market deck which is then shuffled.

The bonuses and effects of equipped items and spells take effect during encounters.

Player may only choose this action while in town.

Player may leave the game session while in town.

- Explore a zone

Player chooses a zone deck and draws a card from it. The card can either be an encounter with a regular enemy or with the zone's boss.

If the player is already in a zone, they may only explore the zone they are in.

Whenever a player chooses to explore, other players in the same zone or in town may join the encounter, as long as the explorer accepts their help.

After assisting in an encounter, players must pass their next turn.

*** Handling Regular Encounters ***

Each player in the encounter attacks.

- Attack deals damage equal to the player's power.

When all players have taken their actions, (even if the enemy has taken lethal damage), players taking part in the fight will decide who between them will take the enemy's attack.

After all damage is dealt, check if any players or enemies have taken damage equal or greater to their health pool, these characters are defeated.

Defeated players lose their gold, and are returned to town with their damage removed.

If all players are defeated, the encounter is lost.

If the enemy is not defeated after the first cycle, the same steps are repeated until the players or the enemy is defeated.

When the enemy is defeated the encounter is complete. The gold reward is divided between all participants (rounded up).

The enemy cards are reshuffled into their deck when encounters end.

*** Handling Boss Encounters ***

If players encounter the zone boss, they can take the same actions as with a regular encounter, however any of the players may also choose to teleport to town instead. If all players teleport away, the boss card is then reshuffled back into the zone deck.

If a boss is defeated, all players in the game (including ones currently not playing) gain access to the next level and the boss card is permanently removed from the game.

Resolution

If the final boss is defeated by anyone, the victory condition is achieved for everyone.

Designing Game Elements: Objectives (Part 2)

Designing Game Elements: Objectives

What is the objective of the game? What are the players trying to do?

Following upon the planned theme of Sword Art Online, the common objective of all players is to escape from the game world by defeating its final boss. While the main goal is straight forward, players will first have to complete a number of objectives in order to be able to attempt the final objective.

Breakdown of Objectives in Sequence

Players need to constantly improve their power in order to be successful in completing the following objectives.

• As the game starts, players need to first find the boss room of the first level, allowing them to face the first boss.

• The next objective is to defeat the boss of that level, granting them access to the next level.

• As new levels are unlocked, players will repeat the process for each level, until they defeat the boss of the final level, at which point all players achieve the win condition.

Designing Game Elements: Players (Part 1)

Designing Game Elements: Players

This game element refers to the minimum and maximum player limits as well as the teams they will be in.

When choosing the number of players it is important to consider what I can do to make the game resemble an MMORPG as much as possible, while also keeping in mind the limitations of the game being handled by a 'game master' rather than a server.

Number of Players Required

I want to have the player limit to be high enough to allow as many players to play the game as possible. Many players might find the game uninteresting and not keep playing, especially if the game is long enough to last more than one session. It is important to have moments where multiple players are playing at the same time, otherwise it will not allow me to test whether players are being brought together.

For the sake of being able to test more frequently I will set the starting requirement to only 3 players, and allow for more players to drop in as the game as it progresses. It would be preferable if I am able to recruit more play testers to begin with.

I will not set an upper limit to the number of players able to join, I will simply need to keep track of each player. This should not be difficult as long as i'm using a system to help keep track of variables attached to each player.

Teams

As mentioned in an earlier post, I want players to be on the same team working towards the same goal. This means all players can help each other and do not need to compete with each other in order to reach their goal. This does not mean that competition between players is completely removed, players that enjoy competition will be glad to show off how skilled they are at the game or how helpful they have been towards other players.

Naturally in order to have conflict, there must be another team: The game itself.

Simultaneous Player Limit

In the event that a high number of players will want to take part during a hosted session, I will need to put a limit on how many players can be playing simultaneously. The reason for this is because the pacing of the game will be slowed for each player when all their actions are being handled by a single 'game master'. Players are likely to get bored if they have to wait for long periods of time between choices and actions.

Since players are on the same team, they will be able to help each other and make the game easier than if they were alone. The bigger the range of players that can play simultaneously, the harder it will be to balance the game's difficulty. The following are three examples showing how players are expected to react based on the number of simultaneous players that the game is balanced around.

---

Example 1: Boss encounter is balanced to be a challenge for 1 player.

1 player will find the boss fight challenging, and may team up with more players to make it easier.

2 players might find the boss fight easy.

3 or more players will find the boss was too easy.

Result: The game can only allow up to 2 simultaneous players, but everything can be done by anyone.

---

Example 2: Boss encounter is balanced to be a challenge for 3 simultaneous  players.

1 - 2 players will find the boss fight too difficult, and must team up with more players.

3 players will find the boss fight challenging, and may team up with more players to make it easier.

4-5 players might find the boss fight easy.

6 or more players will find the boss was too easy.

Result: The game can allow up to 5 simultaneous players, but will require 3 people to simultaneously help each for boss fights.

---

Example 3: Boss encounter is balanced to be a challenge for 10 simultaneous players.

1 - 9 players will find the boss fight too difficult, and must team up with more players.

10 players will find the boss fight challenging, and may team up with more players to make it easier.

11-15 or more players might find the boss fight easy.

more players would find the boss was too easy, but it is very unlikely to have so many simultaneous players available.

Result: The game can allow up to 15 simultaneous players, but will require 10 people to simultaneously help each for boss fights.

---

Based on these expected outcomes, I will set the maximum simultaneous player limit per session to five. This way the game can be balanced around having 3 to 5 simultaneous players helping each other when progressing through boss phases.

Summary

Requires: 3+ Players

Teams: Players vs Game

Simultaneous Limit: 5 Simultaneous Players

Designing Game Elements

Game Elements to Consider

Having chosen the theme and the mechanics that I want to build upon, I must now consider and decide on the different game elements to use in the game.

In the website Game Design Concepts, Sebastian Sohn, mentions what kind of things need to  be created in order to make a game. The following is a list of game-parts that I will be considering.

Players, Objectives, Rules, Resources & Management, Game State, Information, Sequencing, Player Interaction and Theme.

Players

Summary: This game element refers to the minimum and maximum player limits as well as the teams they will be in.

Objectives

Summary: What is the objective of the game? What are the players trying to do?

Rules

Summary:  The rules of play refers to three things: 
setup (things you do once at the beginning of the game).
progression of play (what happens during the game).
resolution (what conditions cause the game to end, and how is an outcome determined based on the game state).

Resources & Management

Summary:  This refers to everything that is under control of a single player. What kinds of resources do the players control? How are these resources manipulated during play?

Game State

Summary: Everything in the game together, including the current player resources and everything else that makes up a snapshot of the game at a single point in time. 

Information

Summary: How much of the game state is visible to each player?

Sequencing

Summary: In what order do players take their actions? How does play flow from one action to another? Is there any time limit?

Player Interaction

Summary: How do players interact with one another? How can they influence one another?

Theme

Summary: The parts of the game that do not directly affect game play at all but are intended to get players emotionally invested and help them make sense of the rules.

The Next Step

In the following posts I will tackle the design of each element in order to finally have a complete game to test, learn and improve.

References / Bibliography

Sebastian Sohn. (2009). Atomic Elements of Games. Available: https://learn.canvas.net/courses/3/pages/level-3-dot-1-atomic-elements-of-games?module_item_id=44529. Last accessed 18th Jan 2015.

Considering Existing Games as a Starting Place

Introduction

As stated in my proposed title, I would like to make a Non-Digital Asynchronous Multiplayer Game, with the purpose of testing methods which would motivate players to play together in an environment similar to an MMORPG.

As mentioned in the feedback from my proposal, it might be very time consuming to start designing such a game from scratch, so it might be a good idea to instead find an existing game that has its own working economy and mod it to fit my requirements.

Deciding on the Starting Place

During our Game Design Degree course, we have been encouraged to pay more attention to non digital games as it is a good method of inspiring and understanding game rules design.

Quite a few games have been inspiring, two of which have interesting characteristics that I should consider using in my game.

1. Munchkin

This game puts several players in the shoes of typical fantasy RPG characters and gives them a simple goal to reach level 10 before the other players. Players want to achieve the goal alone, but can utilize help from other players in order to gain an advantage. On the other hand, players must always be aware that there are no true friends, other players will suddenly turn on you once they no longer need you to reach their goal.

The game is amusing due to the high amount of interaction between players, but what I liked in particular was how the game gave a very similar feeling to progression based RPG games. The reason for this is because players customize their characters' equipment and become more powerful as they get closer to their goal. 

Equipment is represented through the cards players have placed in front of them, each of which granting their own bonus to the player. Random cards are acquired as they progress towards their goal by 'kicking down dungeon doors' which is simply represented by drawing a card.

I think a similar system to this would work nicely for my game: The player has cards displaying their new-found powers and exploration is represented through drawing cards from a deck.

Something interesting I noticed when looking back at this game, is that while players can get very far ahead of others, no matter how weak a player was, they would still feel involved because at times they can still be the deciding factor of whether an encounter by the strongest player would be successful or not.

2. Pandemic

Pandemic was the first non digital game I had experienced where the players are playing entirely on the same team with a common goal and a common enemy: The game itself.

The game has more power than each individual player can handle on their own, thus players are naturally brought together and interact with each other to be as helpful as possible for the sake of their own survival. Same as with munchkin, the 'enemies' of the players (infections and such) are brought into the game through a card draw each turn.

Just as mentioned in a previous post, this technique where power is taken away from players to bring them together is an effective way to enrich the social experience of a game. The issue I can see with this system is that it is balanced around simultaneous play from the start until the end, and would become unbalanced the moment the number of players changed.

In an asynchronous multiplayer game where players can join and leave at any point, I want players to be able to contribute towards their common goal just like in pandemic, however I will need to avoid having a possibility of defeat based on another player's actions while you aren't involved. This means players will need to face challenges based on their own choices.

Theme of the Game

Just as any game, I will have to think of a theme to use for my game in order to help immerse players into the game world and giving them a purpose and motivation to overcome the obstacles and reach the goal.

An animated series called 'Sword Art Online' was rather inspiring from the perspective of a game designer and along with several other friends of mine, I thought it would be nice to be able to play in an MMORPG using its setting.

A summery of its setting is that several players are trapped inside the game world of a fantasy MMORPG called 'Sword Art Online'. Everyone is unable to leave until someone manages to clear the highest level dungeon in the game world - at which point, everyone would be free to leave the game. However players are given very good motivation to want to become stronger as they are told that if anyone was to die in the game world, they would also die in real life.

This setting can work well to give players a common goal like in Pandemic, then using Munchkin's mechanics as the start point for the economy would give the game the fitting RPG feeling I am looking for.

Next Step

Now that I have chosen my starting place, I will next need to go into a bit more depth about several game elements: Players, Objectives, Rules, Resources, Game State, Information, Sequencing, Player Interaction and Theme. I will need to make decisions, building upon the economy of Munchkin, the team play of Pandemic and the setting of Sword Art Online.