Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualOrymus3

Posted 09 November 2012 - 10:36 AM

1) Produce data spreadsheets

This would entail something like putting all of the character data for each experience level into a spreadsheet application along with a sample of enemies, use some simplified equations to calculate average DPT (damage-per-turn) and how much damage we can expect a character party to take, determining how "hard" a battle is based on the amount of hit points likely to be lost before the battle is over.


I think you need to set yourself some guidelines beforehand and use the spreadsheet to verify and adjust accordingly.

For experience, for example, you would like to know:
- How many "fights of my level" do I need to complete for a levelup (followup questions can help identify this)
-- How much attrition do I suffer on average during one of those fights (see damages)
--- How many trips back to town does it entail (is this acceptable (to review damages))

Let's assume the answer is 5, for any given reason. Then, I'm going to take the experience I need for the next levelup and divide it by roughly 5. This is my "pool" which, essentially is a base reference.
Looking at individual encounters of this area (it is important to look at encounters as a whole rather than single monsters that form them) I need to define which I think are "appropriate level". Then, individually, I need to see which ones are slightly on the tough side, and which are slightly on the easy side, and adjust my baseline accordingly to each of these encounters.
Identifying which monster within the encounter is generally the culprit for making the encounter easier or harder will allow to decrease or increase their individual score.

Now the challenge is, how do I define what encounter is "appropriate level". That is actually tricky, but for the most part, it is entirely up to you. In most jRPGs, you have arbitrary increase in difficulty. This serves several purposes but generally allows you to influence the narrative. For example, if there is a steep increase in difficulty, it may be because you're about to enter an important chunk of the story. I won't go into the details of my understanding of this, but basically, a jRPG balancing really required to be fine-tuned with the narrative you intend on following. It is acceptable to have arbitrary difficulty levels here and there.

With that said, your spreadsheet should contain a "likely path" of the player across the game, level by level, fight by fight, and it will let you know roughly what level the player may be when entering a new area. For the most part, this is ok, but like I said, the jRPG difficulty curve is not linear, and this is not a balancing error.

- How uneffective do I want lower level fights to be
This question helps you establish the range between levels. How do you want the XP curve to scale, and as such, how much more experience should one monster give when it is stronger than another monster. If you want grinding to be a viable strategy in your game (which you may want to help casual gamers get up to speed) you'll likely want to make lower level fights relevant in terms of experience. If you're going for the hardcore experience, a tougher monster will probably yield a lot more XP than the tough monster from the previous areas.
That's entirely up to you and the flow/game experience you want to set.


For battle damage:
- How many rounds to I want a "fight of my level" to last?
This is the critical stat that you need to define. Do you want a fast-paced jrpg where everything lasts 1-2 younds if you are at the right level?
Do you want to add more strategic depth at the cost of flow and make fights 3-4 rounds?
Are you more into mid-term tactics and fewer fights such that your average fight will last 5+ rounds?
Once you have that number, you have your base to determine player Attack and monster HP/Def.

- How much attrition do I suffer on average during one of those fights (see damages)
This is the counterpart to the previous question. Here you want to define the relationship between Character HP and monster Attack.
In brief the question could also be "how many fights can I sustain before requiring to recover?". Consumable items and resting at an inn are two different ways to achieve this, but basically, this is the measure of attrition of your game.


The two first questions will help you set two basic coefficients.

- How easily do you want to slice through under-leveled encounters?
Much like experience, you need to determine how shorter fights will be when against weaker foes, and how attrition will be diminished as a result.
Personally, I like to reduce XP gain "a lot" but attrition "a bit". The idea is that the player gets to understand there isn't much gain in fighting these weaklings, but they will still cost his resources.
My recommandation would be to increase the character's attacks so that the fight is much shorter, but not so much the defense so that they still suffer attrition.

These three questions together will set a baseline. You should be able to generate your formulae from these resulting 4 coefficients and end up with a fairly functional system.

- Further Utilities
I haven't touched on that subject, but you will need to handle utilities. By utilities, I mean everything that does not radically fall in the attack-attack scenario.
These include:
*Healers: Monsters with abilities that heal or powerup are harder to gauge. It will be hard to determine how many rounds a fight will last when they are on the battlefield. As a general rule of thumb, you'll want them to be tankers, so that they can last long enough to cope for the fact they won't be dealing damage directly, but will indirectly help out their allies. If you do have such enemies in your game(s), it will be interesting to discuss this further, but I don't want to try and chart everything that is possible.
*Magic attacks/resources: A lot of enemies and characters will probably have access to more efficient attacks that cost resources. Don't forget to factor this when you check for attrition. While MPs aren't life, they still require a refresh once in a while, and this might need a standalone factor in your spreadsheet. Monsters with such options might be considered harder, and should yield more exp. Monsters that are less affected by regular attacks and require magical attacks to defeat them should also be worth more.

If you have more concrete examples of what you're trying to balance exactly, I'll be more than happy to lend a hand.

EDIT: I've built a quick spreadsheet to display this example.
My parameters are:
- Fights per level
- Attrition per fight (% of HP loss)
- XP Leap Multiplier (a value that I gauge to align the numbers: the ratio of everything remains the same)
- Growth Factor HP (The rate at which HP increases, so as to make previous enemies less of an attrition threat)
- Growth Factor STR (The rate at which STR increases, so as to make previous enemies faster to kill off)

I've input original arbitrary values and established a list of per encounter level and stats. Now I need to allocated the "per encounter" as described above.
Everything else is tweaking and manual manipulations (and a lot of testing it in-game).

#1Orymus3

Posted 09 November 2012 - 09:20 AM

1) Produce data spreadsheets

This would entail something like putting all of the character data for each experience level into a spreadsheet application along with a sample of enemies, use some simplified equations to calculate average DPT (damage-per-turn) and how much damage we can expect a character party to take, determining how "hard" a battle is based on the amount of hit points likely to be lost before the battle is over.


I think you need to set yourself some guidelines beforehand and use the spreadsheet to verify and adjust accordingly.

For experience, for example, you would like to know:
- How many "fights of my level" do I need to complete for a levelup (followup questions can help identify this)
-- How much attrition do I suffer on average during one of those fights (see damages)
--- How many trips back to town does it entail (is this acceptable (to review damages))

Let's assume the answer is 5, for any given reason. Then, I'm going to take the experience I need for the next levelup and divide it by roughly 5. This is my "pool" which, essentially is a base reference.
Looking at individual encounters of this area (it is important to look at encounters as a whole rather than single monsters that form them) I need to define which I think are "appropriate level". Then, individually, I need to see which ones are slightly on the tough side, and which are slightly on the easy side, and adjust my baseline accordingly to each of these encounters.
Identifying which monster within the encounter is generally the culprit for making the encounter easier or harder will allow to decrease or increase their individual score.

Now the challenge is, how do I define what encounter is "appropriate level". That is actually tricky, but for the most part, it is entirely up to you. In most jRPGs, you have arbitrary increase in difficulty. This serves several purposes but generally allows you to influence the narrative. For example, if there is a steep increase in difficulty, it may be because you're about to enter an important chunk of the story. I won't go into the details of my understanding of this, but basically, a jRPG balancing really required to be fine-tuned with the narrative you intend on following. It is acceptable to have arbitrary difficulty levels here and there.

With that said, your spreadsheet should contain a "likely path" of the player across the game, level by level, fight by fight, and it will let you know roughly what level the player may be when entering a new area. For the most part, this is ok, but like I said, the jRPG difficulty curve is not linear, and this is not a balancing error.

- How uneffective do I want lower level fights to be
This question helps you establish the range between levels. How do you want the XP curve to scale, and as such, how much more experience should one monster give when it is stronger than another monster. If you want grinding to be a viable strategy in your game (which you may want to help casual gamers get up to speed) you'll likely want to make lower level fights relevant in terms of experience. If you're going for the hardcore experience, a tougher monster will probably yield a lot more XP than the tough monster from the previous areas.
That's entirely up to you and the flow/game experience you want to set.


For battle damage:
- How many rounds to I want a "fight of my level" to last?
This is the critical stat that you need to define. Do you want a fast-paced jrpg where everything lasts 1-2 younds if you are at the right level?
Do you want to add more strategic depth at the cost of flow and make fights 3-4 rounds?
Are you more into mid-term tactics and fewer fights such that your average fight will last 5+ rounds?
Once you have that number, you have your base to determine player Attack and monster HP/Def.

- How much attrition do I suffer on average during one of those fights (see damages)
This is the counterpart to the previous question. Here you want to define the relationship between Character HP and monster Attack.
In brief the question could also be "how many fights can I sustain before requiring to recover?". Consumable items and resting at an inn are two different ways to achieve this, but basically, this is the measure of attrition of your game.


The two first questions will help you set two basic coefficients.

- How easily do you want to slice through under-leveled encounters?
Much like experience, you need to determine how shorter fights will be when against weaker foes, and how attrition will be diminished as a result.
Personally, I like to reduce XP gain "a lot" but attrition "a bit". The idea is that the player gets to understand there isn't much gain in fighting these weaklings, but they will still cost his resources.
My recommandation would be to increase the character's attacks so that the fight is much shorter, but not so much the defense so that they still suffer attrition.

These three questions together will set a baseline. You should be able to generate your formulae from these resulting 4 coefficients and end up with a fairly functional system.

- Further Utilities
I haven't touched on that subject, but you will need to handle utilities. By utilities, I mean everything that does not radically fall in the attack-attack scenario.
These include:
*Healers: Monsters with abilities that heal or powerup are harder to gauge. It will be hard to determine how many rounds a fight will last when they are on the battlefield. As a general rule of thumb, you'll want them to be tankers, so that they can last long enough to cope for the fact they won't be dealing damage directly, but will indirectly help out their allies. If you do have such enemies in your game(s), it will be interesting to discuss this further, but I don't want to try and chart everything that is possible.
*Magic attacks/resources: A lot of enemies and characters will probably have access to more efficient attacks that cost resources. Don't forget to factor this when you check for attrition. While MPs aren't life, they still require a refresh once in a while, and this might need a standalone factor in your spreadsheet. Monsters with such options might be considered harder, and should yield more exp. Monsters that are less affected by regular attacks and require magical attacks to defeat them should also be worth more.

If you have more concrete examples of what you're trying to balance exactly, I'll be more than happy to lend a hand.

PARTNERS