Difference between revisions of "User:Xudojnik"

From The Battle for Wesnoth Wiki
m (this doesn't belong in Category:WML_Reference, nor does it need the sidebar of Template:WML_Tags)
 
(71 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
I know Wesnoth from version 1.1.2a. This is really perspective game not only as strategy, but as RPG too. Large world, filled by history, epic battles, heroes and factions, is perfect for creating RPG. It's not so hard because Wesnoth have simple language, what support wide variety of events, easy way to define dialogs, items, forum and Wiki, where always can be found answer for any question.
 
I know Wesnoth from version 1.1.2a. This is really perspective game not only as strategy, but as RPG too. Large world, filled by history, epic battles, heroes and factions, is perfect for creating RPG. It's not so hard because Wesnoth have simple language, what support wide variety of events, easy way to define dialogs, items, forum and Wiki, where always can be found answer for any question.
−
 
−
There are function, what are completed or close to it:
 
−
#Weapon vendor.
 
−
#Potion vendor.
 
−
#Home(place, where hero can change his weapons, take rest).
 
−
#Stable, where hero can buy horse.
 
−
#Mounting/dismounting on that horse. Two types of weapon: for mounted hero and foot.
 
−
#Talking to NPC's.
 
−
#NPC's shedule in one string.
 
−
#Spellcasting system (general-purpose examples of spells, what can be copied and changed later).
 
−
#Quest log now wait for content.
 
−
#Beneficial spell effects needs only more spells.
 
−
#Improved inventory, Spellbook.
 
−
 
−
There are in the future:
 
−
#Dog (taming, training, feeding).
 
−
#Levelling and customising character.
 
−
 
−
 
−
----
 
−
At the end of my work, I get unimaginable amount of lags, long and boring loading time and HUGE savegames. And I leave it. Now I wait for stable version of BfW 1.9. The only reason is implemented persistent variables. I will wrote here some basic terms of this project.
 
  
 
===WesMMO===
 
===WesMMO===
 
To play it (now only in theory):
 
To play it (now only in theory):
−
#Design new character.
 
 
#*Download WesMMO era.
 
#*Download WesMMO era.
−
#*Download beginner's map, designed for WesMMO.
+
#*Download any map, designed for WesMMO.
−
#*Create game in lobby.
 
−
#*Create an "account" and character on it.
 
−
#*Win beginner's scenario.
 
−
#Get fun.
 
−
#*Download some other playable map, designed for WesMMO.
 
 
#*Create game in lobby.
 
#*Create game in lobby.
−
#*Map will automatically use your account. Now choose any existed character and play.
+
#*WesMMO era will automatically use your account.
−
 
+
#*Now choose any three units from your account or create new and play.
−
:''I planned to invent spell-system in this MMO, but not yet decide about mana and cooldowns.''
+
#*Persistent data will be stored at the end of each turn
  
−
Character is a "team" of three units. Each unit have own stats, small inventory'' and spellbook''.
+
Character is a "team" of three units. Each unit have own stats and small inventory
−
;Stats should be simple:
+
;Stats:
−
:Stamina - increases your hitpoints by 2 (3?) per point.
+
:Stamina - increases your hitpoints. ''Each point of stamina should increase survivalalibity of unit for an average amount of damage, given by 1 strength or agility, multiplied by 6.
−
:Strength - increases your melee damage.
+
:Strength - increases your melee damage and armor contribution from items.
 
:Speed - increases your movement points.
 
:Speed - increases your movement points.
−
:Agility - increase your defense on each type of terrain by 1 per point and ranged damage.
+
:Agility - increase your ranged damage and defense on each type of terrain.
−
:''Intellect of Spell Power (or both)- increase magical potence of unit''
+
::100 * A / (A + 30) 60% Defence at 45 agility
 +
::100 * A / (A + 20) 60% Defence at 30 agility
 +
::100 * A / (A + 10) 60% Defence at 15 agility
 +
:Intellect - increase magical potence of unit in some ways
  
−
;Inventory contains:
+
;Inventory:
−
:Healing Potion - number of them.
+
:Melee Weapon - affects melee combat: multiplies damage from strength and number of strikes.
−
:''Mana Potions - number of them.''
+
:Ranged Weapon - affects ranged combat: multiplies damage from agility and number of strikes.
−
:Melee Weapon - affects melee combat: strength_multiplier and number_of_strikes and possibly defenses.
+
:Amulet - affects base stats, magical resistances and magical potency of unit
−
:Ranged Weapon - affects ranged combat: damage_from_agility_multiplier and number_of_strikes.
 
−
:''Amulet - affects base stats, magical resistances and magical potency of unit''
 
 
:Body Armor - affects base stats, all resistances and defenses.
 
:Body Armor - affects base stats, all resistances and defenses.
−
:Boots - affects base stats and have movement_multipier.
+
:Boots - affects base stats and multiplies speed of unit.
−
:Helm - affects melee resistances ''and magical potency of unit''.
+
:Helm - affects melee resistances and magical potence of unit.
 +
 
 +
Each item have it's own stats.
 +
 
 +
;Spell system:
 +
:Each class have some predefined spells. ''In most cases they are not simple "damage unit X for Y hp". That's why they are the greatest headache for me.''
 +
:Each unit can use it's spell once per turn.
 +
:There are no limit of uses through whole scenario.
 +
 
 
Each item has it own's id. This ID is the key to macro what will apply effect of item stats to unit structure. Data about it will be stored inside WesMMO era. That allows me to implement 'inventory slots'. Players will carry unused items in them.
 
Each item has it own's id. This ID is the key to macro what will apply effect of item stats to unit structure. Data about it will be stored inside WesMMO era. That allows me to implement 'inventory slots'. Players will carry unused items in them.
  
−
''Spellbook will contains information about direct spells and units's auras.''
 
  
−
;How does this work
 
−
There should be macro to refresh visible stats of hero (hp, damage e.t.c.) It should be called when unit change it's base stats.
 
  
−
In perfect way, I should create some sort of database (TD).
+
Ideas:
 +
#situation: players A,B,C,D starts the game. player B leaves game before it ends. spectator E (player A) takes control of units B. players A,E,C,D ends the game and information about their units is stored to persistent. player E gets units of player B.
 +
#suggestion: Best items should kill much time before player get them, but players should get something each time they play this game. Ways to reach this objective:
 +
#*1) Add "random stats" to items. Then item drops, RNG choose stats on them between predefined sets. 1/4 of randem stat set (RaSS) should be awesome and 1/4 should be real crap.
 +
#*2) Add "crafted items". Players should collect some resourses and get to place where they can craft this item.
 +
#Itemisation(1). WesMMO will be published by patches. In each patch I will add some new items and functions to players. Items added in new patch should be better than items added in previous patch. But difference should not be enormous.
 +
#levelling(1). I would not change standart mechanic of XP colection of BfW. Each player have 3 unit, what allows them to prapare and perform last-hit for any unit. Levelling shouldn't make items of this patch worster.
 +
#Levelling(2). Data, stored in unit.class[], should contain multipliers of stats. Later this will be used to recalculate stats of unit.
 +
#Itemisation(2). There are three items: A(require 1-3 of X), B(require 2-5 of X), C(require 4-8 of X). While player have 3 X, he can't share A and B to others if he get them and can not use C. But when he collect 4 X, he can share A, can't share B and can use C.
 +
#Crafted items++. If craft of new items will require resourses from old patch, old maps will become outdated only if I will want this.
 +
#Itemisation(3). Items should have requirments by level.
 +
#Levelling(3). There should be a level cap in each patch.
 +
#Itemisation(4). Items can have no requirements by level, but stats on item can be influensed by level.
 +
#Itemisation(5). Add "mantle". It will have +int, +stam and magical resistances. Body no longer affect magical resistences and stam.
 +
#Development(1). Add various "count" functions to collect statistical data about each option in dialogs. This data should be stored in special namespace. Then this will be done, I should add to feedback thread request to put file with this data to the forum.
 +
#UI(1). Frankensteining. Each equipped item will have it's own overlay on unit. During the fights overlays aren't shown. Thats why I should create attack and defend animations what will look like cloud with "Ouch" messages jumped out of it.
 +
#UI(2). Fast backpack browser
 +
+-----------------------------+
 +
|  Backpack browser
 +
| +-------------------------+ |
 +
| | Back
 +
| +-------------------------+ |
 +
| +-------------------------+ |
 +
| | Next 10(5?)
 +
| +-------------------------+ |
 +
| +-------------------------+ |
 +
| | Previous 10(5?)
 +
| +-------------------------+ |
 +
| +-------------------------+ |
 +
| | item_slot) item_name id | |
 +
| +-------------------------+ |
 +
| +-------------------------+ |
 +
| | 2) Cracked Bow <id>
 +
| +-------------------------+ |
 +
+-----------------------------+
 +
 
 +
#UI(3). Resourse browser
  
−
''It consist of tree parts. First parts should contain booleans to check "does item useful?". And second should contain one big macro, what will create variables for "useful items". There will be as much of this DB's as slots for items.''
+
===WesMMO. Theorycraft===
 +
;Main questions:
 +
:1) I have some 'slots' of equipped items. Why player should fill all this slots?
 +
:2) I have some 'stats' on items. Why player should concentrate on some stats and ignore other?
 +
:3) There are some 'classes' of characters. How to make real difference between any two classes?
 +
:4) How to make class system where anticlasses will exists.
  
−
Comment: At the beginning, load whole Database of items to see how it eats PC's memory.
+
;Base statements:
 +
:Player control 3 units.
 +
:Units have around 5 equipment 'slots' and few stats.
 +
:Any damage dealing should be based on stadart battle system.
 +
:There are around 5-10 different classes.
 +
:Each class have at least 2 good, 2 worst and 2 average attack types and defenses.
 +
:Item can not affect 2 good or 2 worst stats for any class at once.
 +
:Bonuses from items should not break class balance.
 +
:Items are not able to affect all stats.
 +
:All characters have same movement cost and base defence at any type of terrain.
 +
:Any character is able to wear any item he gets.
  
−
struct body{
+
;Stat system
−
  int stamina;
+
Handling good/average/worst stats for any class.
−
  int strength;
+
Each class will have set of modifiers, what will affect resistances. It can be equal to 1 (good), 2 (average), 4 (worst).
−
  int agility;
+
  ''main formula of effect diminishing'':
−
  int pierce;
+
  y = x / (a * x + 20) * 100%, where
−
  int blade;
+
  x - value from gear,
−
  int blow;
+
  a - class modifier.
−
  int arcane;
+
According to this formula, there are 3 tier of armor exists:
−
  int fire;
+
1 tier: gear give 1-20 value (5-50;5-33;5-20)
−
  int cold;
+
2 tier: gear give 20-40 value (50-66;33-40;20-22)
−
}
+
3 tier: gear give 40-80 value (66-80;40-45;22-23)
−
+
The following stats are good for any class:
−
struct boots{
+
:hitpoint amount. ''Even mages with ranged combat should stand face-to-face to it's current opponent. Noone can one-shot any other class with full hp. Thats why mage surely will get some amount of damage from counterattack.
−
  int speed;
+
:movepoints amount. ''Difference in 1 point of movement make one unit unreachable by other.
−
  int speed_multiplier;
 
−
  int stamina;
 
−
  int strength;
 
−
  int agility;
 
−
}
 
−
 
−
struct head{
 
−
  int pierce;
 
−
  int blade;
 
−
  int blow;
 
−
}
 
−
 
−
struct melee{
 
−
  int strength_multiplier;
 
−
  int speed;
 
−
  int defense;
 
−
}
 
−
 
−
struct defense{
 
−
  int castle;
 
−
  int cave;
 
−
  int deep_water;
 
−
  int flat;
 
−
  int forest;
 
−
  int frozen;
 
−
  int fungus;
 
−
  int hills;
 
−
  int reef;
 
−
  int sand;
 
−
  int shallow_water;
 
−
  int swamp_water;
 
−
}
 
−
 
−
struct resistance{
 
−
  int arcane;
 
−
  int blade;
 
−
  int cold;
 
−
  int fire;
 
−
  int impact;
 
−
  int pierce;
 
−
}
 
−
 
−
struct class{
 
−
  int stamina;
 
−
  int strength;
 
−
  int speed;
 
−
  int agility;
 
−
  struct defense;
 
−
  strect resistance;
 
−
}
 
−
 
−
struct buffed{
 
−
  int stamina;
 
−
  int strength;
 
−
  int agility;
 
−
  int speed;
 
−
  int pierce;
 
−
  int blade;
 
−
  int blow;
 
−
  int arcane;
 
−
  int fire;
 
−
  int cold;
 
−
  int hitpoints_multiplier; //NOTE: There is no stamina_multiplier.
 
−
  int strength_multiplier;
 
−
  int agility_multiplier;
 
−
  int speed_multiplier;
 
−
  }
 
−
   
 
−
  struct free_slot{
 
−
  int item_id;
 
−
  string item_type;
 
−
  }
 
−
 
−
struct inv{
 
−
  int body_item_id;
 
−
  int boots_item_id;
 
−
  int head_item_id;
 
−
  int melee_item_id;
 
−
  int ranged_item_id;
 
−
  int healing_potions;
 
−
  struct free_slot[6];
 
−
  struct body;
 
−
  struct boots;
 
−
  struct head;
 
−
  struct melee;
 
−
  struct ranged;
 
−
}
 
−
 
−
struct attack{
 
−
  int damage;
 
−
  int number;
 
−
  int type;
 
−
  int range;
 
−
}
 
−
 
−
struct unit{
 
−
  struct inv;
 
−
  struct buffed;
 
−
  struct class;
 
−
  //standart WML values:
 
−
  int max_experience;
 
−
  int max_hitpoints;
 
−
  int max_moves;
 
−
  struct defense;
 
−
  struct resistance;
 
−
  struct attack[2]; // 0 - melee, 1 - ranged
 
−
}
 
−
struct "inv" will be stored as persistent variable. Other structures will be forgotten, because there will be functions to calculate their content.  
 
  
−
unit Player;
+
There are 5 equippable slots:
−
StoreUnit( Player );
+
:1 - affects magical combat
−
//This function counts output values, what player will see on the right panel.
+
:2 - affects defences
−
void UpdateStats( unit * Player )
+
:3 - affects melee combat
−
{
+
:4 - affects ranged combat
−
  Player.damage = ( Player.class.strength + Player.inv.body.strength + Player.inv.boots.strength + Player.buffed.strength ) *  Player.inv.melee.strength_multiplier * Player.buffed.damage_multiplier;
+
:5 - affects movement
−
 
−
  Player.hitpoints = ( Player.class.stamina + Player.inv.body.stamina + Player.inv.boots.stamina + Player.buffed.stamina ) * Player.buffed.hitpoints_multiplier;
 
−
 
−
  Player.max_moves = ( Player.class.speed + Player.inv.boots.speed + Player.buffed.speed ) * Player.inv.boots.speed_multiplier * Player.buffed.speed_multiplier;
 
−
 
−
  Player.
 
−
}
 
−
UnstoreUnit();
 
  
−
void TakeOffItem( int itemid, string itemtype, unit * Player )
+
If item affects combat, it always says how many strikes you have and how much damage you will deal with this item. This should also be influenced by class, in some way, to make sure, what character A can not be owerpowered just because enemy have wrong and this class - right weapon.
−
{
 
−
}
 
  
−
void PickUpItem( int itemid, string itemtype, unit * Player )
+
How can I make difference for class A between weapon a and b?
−
{
+
:1) Class multiplier. ''Multipliers for damage is not a good idea.
−
}
+
:2) Gear hacking. ''This way is rather hard, but possible.
 +
:3) Weapon blocking. ''Easy as pie.
  
−
void CancelStats(string itemtype, unit * Player)
+
Damage and number of strikes completely influenced by weapon. That means, what weapons of same tier, will have same damage output.
−
{
+
:Blade-based melee weapons are fast. Ex: 2-6
−
  switch(itemtype)
+
:Blow-based melee weapons have average characterictics. 3-4 or 4-3
−
  {
+
:Only arcane melee weapon allowed. it's speed and damage is not good itself, but it is not influenced by common physical resistances.
−
  case "body" :
+
:Pierce weapons are usually ranged and rather fast. 3-4 or 2-6.
−
  {
+
:Fire magic is one-shottable. 12-1 and cannot miss, of course.
−
    Player.inv.body.stamina = 0;
+
:Cold magic is a pain. 1-12.
−
    Player.inv.body.strength = 0;
 
−
    Player.inv.body.agility = 0;
 
−
    Player.inv.body.pierce = 0;
 
−
    Player.inv.body.blade = 0;
 
−
    Player.inv.body.blow = 0;
 
−
    Player.inv.body.arcane = 0;
 
−
    Player.inv.body.fire = 0;
 
−
    Player.inv.body.cold = 0;
 
−
    Player.inv.body_item_id = 0;
 
−
  } break;
 
−
 
−
  case "boots" :
 
−
  {
 
−
    Player.inv.boots.speed_multiplier = 0;
 
−
    Player.inv.boots.stamina = 0;
 
−
    Player.inv.boots.strength = 0;
 
−
    Player.inv.boots.agility = 0;
 
−
    Player.inv.boots_item_id = 0;
 
−
  } break;
 
−
 
−
  case "head" :
 
−
  {
 
−
    Player.inv.head.pierce = 0;
 
−
    Player.inv.head.blade = 0;
 
−
    Player.inv.head.blow = 0;
 
−
    Player.inv.head_item_id = 0;
 
−
  } break;
 
−
 
−
  case "melee" :
 
−
  {
 
−
    Player.inv.melee.strength_multiplier = 0;
 
−
    Player.inv.melee.speed = 0;
 
−
    Player.inv.melee.defense = 0;
 
−
    Player.inv.melee_item_id = 0;
 
−
  } break;
 
−
 
−
  case "ranged" :
 
−
  {
 
−
    Player.inv.ranged.agility_multiplier = 0;
 
−
    Player.inv.ranged.speed = 0;
 
−
    Player.inv.ranged.defense = 0;
 
−
    Player.inv.ranged_item_id = 0;
 
−
  } break;
 
−
 
−
  default :
 
−
  {
 
−
    ErrorMessage();
 
−
  }
 
−
  }
 
−
}
 
  
−
void GiveStats( int new_item_id, string itemtype, unit * Player )
+
There are 2 group of stats:
−
{
+
:''Active''
−
  switch(itemtype)
+
:''Passive''
−
  {
+
There are two ''active'' stat: hitpoint and damage, and two ''passive'': dodge chance and absorbition.
−
  case "body" :  
+
And total list of stats will look like this:
−
  {
+
+--------------------+---+
−
    Player.inv.body.stamina = TD.body[new_item_id].stamina;
+
| stat              |PPL|
−
    Player.inv.body.strength = TD.body[new_item_id].strength;
+
+--------------------+---+
−
    Player.inv.body.agility = TD.body[new_item_id].agility;
+
| hitpoints          |60 |
−
    Player.inv.body.pierce = TD.body[new_item_id].pierce;
+
+-------+------------+---+
−
    Player.inv.body.blade = TD.body[new_item_id].blade;
+
| blade |            |  |
−
    Player.inv.body.blow = TD.body[new_item_id].blow;
+
| blow |            |  |
−
    Player.inv.body.arcane = TD.body[new_item_id].arcane;
+
| pierce|absorbitions| 5 |
−
    Player.inv.body.fire = TD.body[new_item_id].fire;
+
| arcane|            |  |
−
    Player.inv.body.cold = TD.body[new_item_id].cold;
+
| fire |            |  |
−
    Player.inv.body.item_id = new_item_id;
+
| cold |            |  |
−
  } break;
+
  +-------+------------+---+
−
   
+
  | blade |            |  |
−
  case "boots" :
+
| blow |            |  |
−
  {
+
| pierce|  power   |10 |
−
    Player.inv.boots.speed_multiplier = TD.boots[new_item_id].speed_multiplier;
+
  | arcane|            |  |
−
    Player.inv.boots.stamina = TD.boots[new_item_id].stamina;
+
| fire  |            |  |
−
    Player.inv.boots.strength = TD.boots[new_item_id].strength;
+
| cold  |            |  |
−
    Player.inv.boots.agility = TD.boots[new_item_id].agility;
+
+-------+------------+---+
−
    Player.inv.boots.item_id = new_item_id;
+
| avoidance          | 4 |
−
  } break;
+
+-------+------------+---+
−
   
+
Absorbitions have limits in 12 levels.
−
  case "head" :
+
Let's imagine, what absorbition capped at 75% value. According to ''main formula of effect diminishing'', character with a=1 will achieve 75% mitigation at x=60. And 60 / 5 = 12.
−
  {
 
−
    Player.inv.head.pierce = TD.head[new_item_id].pierce;
 
−
    Player.inv.head.blade = TD.head[new_item_id].blade;
 
−
    Player.inv.head.blow = TD.head[new_item_id].blow;
 
−
    Player.inv.head.item_id = new_item_id;
 
−
   } break;
 
−
   
 
−
  case "melee" :
 
−
  {
 
−
    Player.inv.melee.strength_multiplier = TD.melee[new_item_id].strength_multiplier;
 
−
    Player.inv.melee.speed = TD.melee[new_item_id].speed;
 
−
    Player.inv.melee.defense = TD.melee[new_item_id].defense;
 
−
    Player.inv.melee.item_id = new_item_id;
 
−
  } break;
 
−
 
−
  case "ranged" :
 
−
  {
 
−
    Player.inv.ranged.agility_multiplier = TD.ranged[new_item_id].agility_multiplier;
 
−
    Player.inv.ranged.speed = TD.ranged[new_item_id].speed;
 
−
    Player.inv.ranged.defense = TD.ranged[new_item_id].defense;
 
−
    Player.inv.ranged.item_id = new_item_id;
 
−
  } break;
 
−
 
−
  default :
 
−
  {
 
−
    ErrorMessage();
 
−
  }
 
−
  }
 
−
}
 
  
−
TODO:
+
Look to this table:
−
<br>Add missed formulas to UpdateStats();.
+
x value difference value difference value difference
−
<br>Update PickUpItem();.
+
0 0 0 0
−
<br>Update TakeOffItem();.
+
5 16,66666667 16,66666667 12,5 12,5 20 20
−
<br>Implement free slots.
+
10 25 8,333333333 16,66666667 4,166666667 33,33333333 13,33333333
−
<br>Make things clear about spells.
+
15 30 5 18,75 2,083333333 42,85714286 9,523809524
−
<br>Make things clear about AMLA.
+
20 33,33333333 3,333333333 20 1,25 50 7,142857143
−
<br>Make things clear about trade.
+
25 35,71428571 2,380952381 20,83333333 0,833333333 55,55555556 5,555555556
−
<br>Implement loot tables from bosses and mobs.
+
30 37,5 1,785714286 21,42857143 0,595238095 60 4,444444444
−
<br>Implement "Group Loot".
+
35 38,88888889 1,388888889 21,875 0,446428571 63,63636364 3,636363636
 +
40 40 1,111111111 22,22222222 0,347222222 66,66666667 3,03030303
 +
45 40,90909091 0,909090909 22,5 0,277777778 69,23076923 2,564102564
 +
50 41,66666667 0,757575758 22,72727273 0,227272727 71,42857143 2,197802198
 +
55 42,30769231 0,641025641 22,91666667 0,189393939 73,33333333 1,904761905
 +
60 42,85714286 0,549450549 23,07692308 0,16025641 75 1,666666667
 +
2'nd column shows mitigation value at a = 2, 4'th at a = 4 and 6'th at a = 1. If you calculate average value of all difference columns and turn float value to int, you get 4. This is Avoidance PPL.
 +
There are also ''Soft cap'' and ''hard cap'' of mitigation. Soft cap means what further collecting of this stat is useful, but player can spend training points into something more valuable. Hard cap means what further improvement is not recommended (by me of course).
 +
:for a = 1. SC = 30. HC = 60
 +
:for a = 2. SC = 20. HC = 40.
 +
:for a = 4. SC = 10. HC = 20.
 +
Avoidance should give static value, because it is not depend from character class. And it should be capped too. According to wesnoth phylosophy, defence should not be higner than 60. 60 / 4 = 15 levels of stat.

Latest revision as of 20:57, 4 March 2018

I know Wesnoth from version 1.1.2a. This is really perspective game not only as strategy, but as RPG too. Large world, filled by history, epic battles, heroes and factions, is perfect for creating RPG. It's not so hard because Wesnoth have simple language, what support wide variety of events, easy way to define dialogs, items, forum and Wiki, where always can be found answer for any question.

WesMMO

To play it (now only in theory):

    • Download WesMMO era.
    • Download any map, designed for WesMMO.
    • Create game in lobby.
    • WesMMO era will automatically use your account.
    • Now choose any three units from your account or create new and play.
    • Persistent data will be stored at the end of each turn

Character is a "team" of three units. Each unit have own stats and small inventory

Stats
Stamina - increases your hitpoints. Each point of stamina should increase survivalalibity of unit for an average amount of damage, given by 1 strength or agility, multiplied by 6.
Strength - increases your melee damage and armor contribution from items.
Speed - increases your movement points.
Agility - increase your ranged damage and defense on each type of terrain.
100 * A / (A + 30) 60% Defence at 45 agility
100 * A / (A + 20) 60% Defence at 30 agility
100 * A / (A + 10) 60% Defence at 15 agility
Intellect - increase magical potence of unit in some ways
Inventory
Melee Weapon - affects melee combat: multiplies damage from strength and number of strikes.
Ranged Weapon - affects ranged combat: multiplies damage from agility and number of strikes.
Amulet - affects base stats, magical resistances and magical potency of unit
Body Armor - affects base stats, all resistances and defenses.
Boots - affects base stats and multiplies speed of unit.
Helm - affects melee resistances and magical potence of unit.

Each item have it's own stats.

Spell system
Each class have some predefined spells. In most cases they are not simple "damage unit X for Y hp". That's why they are the greatest headache for me.
Each unit can use it's spell once per turn.
There are no limit of uses through whole scenario.

Each item has it own's id. This ID is the key to macro what will apply effect of item stats to unit structure. Data about it will be stored inside WesMMO era. That allows me to implement 'inventory slots'. Players will carry unused items in them.


Ideas:

  1. situation: players A,B,C,D starts the game. player B leaves game before it ends. spectator E (player A) takes control of units B. players A,E,C,D ends the game and information about their units is stored to persistent. player E gets units of player B.
  2. suggestion: Best items should kill much time before player get them, but players should get something each time they play this game. Ways to reach this objective:
    • 1) Add "random stats" to items. Then item drops, RNG choose stats on them between predefined sets. 1/4 of randem stat set (RaSS) should be awesome and 1/4 should be real crap.
    • 2) Add "crafted items". Players should collect some resourses and get to place where they can craft this item.
  3. Itemisation(1). WesMMO will be published by patches. In each patch I will add some new items and functions to players. Items added in new patch should be better than items added in previous patch. But difference should not be enormous.
  4. levelling(1). I would not change standart mechanic of XP colection of BfW. Each player have 3 unit, what allows them to prapare and perform last-hit for any unit. Levelling shouldn't make items of this patch worster.
  5. Levelling(2). Data, stored in unit.class[], should contain multipliers of stats. Later this will be used to recalculate stats of unit.
  6. Itemisation(2). There are three items: A(require 1-3 of X), B(require 2-5 of X), C(require 4-8 of X). While player have 3 X, he can't share A and B to others if he get them and can not use C. But when he collect 4 X, he can share A, can't share B and can use C.
  7. Crafted items++. If craft of new items will require resourses from old patch, old maps will become outdated only if I will want this.
  8. Itemisation(3). Items should have requirments by level.
  9. Levelling(3). There should be a level cap in each patch.
  10. Itemisation(4). Items can have no requirements by level, but stats on item can be influensed by level.
  11. Itemisation(5). Add "mantle". It will have +int, +stam and magical resistances. Body no longer affect magical resistences and stam.
  12. Development(1). Add various "count" functions to collect statistical data about each option in dialogs. This data should be stored in special namespace. Then this will be done, I should add to feedback thread request to put file with this data to the forum.
  13. UI(1). Frankensteining. Each equipped item will have it's own overlay on unit. During the fights overlays aren't shown. Thats why I should create attack and defend animations what will look like cloud with "Ouch" messages jumped out of it.
  14. UI(2). Fast backpack browser
+-----------------------------+
|  Backpack browser
| +-------------------------+ |
| | Back
| +-------------------------+ |
| +-------------------------+ |
| | Next 10(5?)
| +-------------------------+ |
| +-------------------------+ |
| | Previous 10(5?)
| +-------------------------+ |
| +-------------------------+ |
| | item_slot) item_name id | |
| +-------------------------+ |
| +-------------------------+ |
| | 2) Cracked Bow <id>
| +-------------------------+ |
+-----------------------------+
  1. UI(3). Resourse browser

WesMMO. Theorycraft

Main questions
1) I have some 'slots' of equipped items. Why player should fill all this slots?
2) I have some 'stats' on items. Why player should concentrate on some stats and ignore other?
3) There are some 'classes' of characters. How to make real difference between any two classes?
4) How to make class system where anticlasses will exists.
Base statements
Player control 3 units.
Units have around 5 equipment 'slots' and few stats.
Any damage dealing should be based on stadart battle system.
There are around 5-10 different classes.
Each class have at least 2 good, 2 worst and 2 average attack types and defenses.
Item can not affect 2 good or 2 worst stats for any class at once.
Bonuses from items should not break class balance.
Items are not able to affect all stats.
All characters have same movement cost and base defence at any type of terrain.
Any character is able to wear any item he gets.
Stat system

Handling good/average/worst stats for any class. Each class will have set of modifiers, what will affect resistances. It can be equal to 1 (good), 2 (average), 4 (worst). 

main formula of effect diminishing:
y = x / (a * x + 20) * 100%, where
x - value from gear,
a - class modifier.

According to this formula, there are 3 tier of armor exists: 1 tier: gear give 1-20 value (5-50;5-33;5-20) 2 tier: gear give 20-40 value (50-66;33-40;20-22) 3 tier: gear give 40-80 value (66-80;40-45;22-23) The following stats are good for any class:

hitpoint amount. Even mages with ranged combat should stand face-to-face to it's current opponent. Noone can one-shot any other class with full hp. Thats why mage surely will get some amount of damage from counterattack.
movepoints amount. Difference in 1 point of movement make one unit unreachable by other.

There are 5 equippable slots:

1 - affects magical combat
2 - affects defences
3 - affects melee combat
4 - affects ranged combat
5 - affects movement

If item affects combat, it always says how many strikes you have and how much damage you will deal with this item. This should also be influenced by class, in some way, to make sure, what character A can not be owerpowered just because enemy have wrong and this class - right weapon.

How can I make difference for class A between weapon a and b?

1) Class multiplier. Multipliers for damage is not a good idea.
2) Gear hacking. This way is rather hard, but possible.
3) Weapon blocking. Easy as pie.

Damage and number of strikes completely influenced by weapon. That means, what weapons of same tier, will have same damage output.

Blade-based melee weapons are fast. Ex: 2-6
Blow-based melee weapons have average characterictics. 3-4 or 4-3
Only arcane melee weapon allowed. it's speed and damage is not good itself, but it is not influenced by common physical resistances.
Pierce weapons are usually ranged and rather fast. 3-4 or 2-6.
Fire magic is one-shottable. 12-1 and cannot miss, of course.
Cold magic is a pain. 1-12.

There are 2 group of stats:

Active
Passive

There are two active stat: hitpoint and damage, and two passive: dodge chance and absorbition. And total list of stats will look like this: 

+--------------------+---+
| stat               |PPL|
+--------------------+---+
| hitpoints          |60 |
+-------+------------+---+
| blade |            |   |
| blow  |            |   |
| pierce|absorbitions| 5 |
| arcane|            |   |
| fire  |            |   |
| cold  |            |   |
+-------+------------+---+
| blade |            |   |
| blow  |            |   |
| pierce|   power    |10 |
| arcane|            |   |
| fire  |            |   |
| cold  |            |   |
+-------+------------+---+
| avoidance          | 4 |
+-------+------------+---+

Absorbitions have limits in 12 levels. Let's imagine, what absorbition capped at 75% value. According to main formula of effect diminishing, character with a=1 will achieve 75% mitigation at x=60. And 60 / 5 = 12.

Look to this table: 

x	value		difference	value		difference	value		difference
0	0				0				0	
5	16,66666667	16,66666667	12,5		12,5		20		20
10	25		8,333333333	16,66666667	4,166666667	33,33333333	13,33333333
15	30		5		18,75		2,083333333	42,85714286	9,523809524
20	33,33333333	3,333333333	20		1,25		50		7,142857143
25	35,71428571	2,380952381	20,83333333	0,833333333	55,55555556	5,555555556
30	37,5		1,785714286	21,42857143	0,595238095	60		4,444444444
35	38,88888889	1,388888889	21,875		0,446428571	63,63636364	3,636363636
40	40		1,111111111	22,22222222	0,347222222	66,66666667	3,03030303
45	40,90909091	0,909090909	22,5		0,277777778	69,23076923	2,564102564
50	41,66666667	0,757575758	22,72727273	0,227272727	71,42857143	2,197802198
55	42,30769231	0,641025641	22,91666667	0,189393939	73,33333333	1,904761905
60	42,85714286	0,549450549	23,07692308	0,16025641	75		1,666666667

2'nd column shows mitigation value at a = 2, 4'th at a = 4 and 6'th at a = 1. If you calculate average value of all difference columns and turn float value to int, you get 4. This is Avoidance PPL. There are also Soft cap and hard cap of mitigation. Soft cap means what further collecting of this stat is useful, but player can spend training points into something more valuable. Hard cap means what further improvement is not recommended (by me of course).

for a = 1. SC = 30. HC = 60
for a = 2. SC = 20. HC = 40.
for a = 4. SC = 10. HC = 20.

Avoidance should give static value, because it is not depend from character class. And it should be capped too. According to wesnoth phylosophy, defence should not be higner than 60. 60 / 4 = 15 levels of stat.

Retrieved from "https://wiki.wesnoth.org/index.php?title=User:Xudojnik&oldid=59238"
This page was last edited on 4 March 2018, at 20:57.