[Crossfire-wiki] [Crossfire DokuWiki] page changed: user:saru:balance

[no-reply_wiki at metalforge.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2014/10/08 19:56
User        : saru
Edit Summary: 

@@ -204,8 +204,9 @@
  ==Map specific==
  Map specific items are items that have been modified inside a map to grant new features (both positive and negative) to greatly enhance the speed and diversity of map making. These items present the biggest challenge in balance as they are more difficult to track. Some of these items should probably be 'god granted'. These items only vary by how map makers design them (no random variation)
    - specific map based items
    - specific monster drop
+ 
  
  
  ====Generic monster & random treasure loot====
  Currently the game offers a specific set of items with various likelihoods for each to drop based on the treasurelist of that monster (or chest etc). This approach does allow for interesting diversity in what items players may encounter for some examples but also means that:
@@ -215,13 +216,16 @@
  To add to this, the requirement to list every possible item that a particular treasurelist may drop is very time consuming and would be extremely difficult to update. Secondly it doesn't work at all for modified creatures so map makers must instead either create whole new archetypes (and the associated even longer treasurelist)
  
  While each of these problems could be addressed individually, I want to propose a more general approach to fixing this effect that should be more tune-able, more easily.
  
- I propose that generic treasurelists for classes/groups/types of items should probably be maintained (such as what currently exists in treasurelist for chests). Items that are not generic should be flagged to avoid being accidently included in these treasure lists via something like an 'is_artifact' flag. Then the most basic generic treasure list would probably be each item type. With a generic treasurelists, instead of listing each possible item for a monster treasure list, we can now simply list axes, maces, shields, body armour, food, body parts and money. We can set each generic treasurelist for the orc to have different probabilities (e.g. 5% chance to drop (95% chance not to drop) each type of equipment, a 10% chance to drop food, and a 50% chance to drop body parts). This should make it far easier for developers to add new generic items to the game without requiring extensive time additional to creating generic items in adding these items into each monster's treasurelists.
+ === Generic treasurelists ===
+ A generic treasurelists for classes/groups/types of items should probably be maintained (such as what currently exists in treasurelist for chests). Items that are not generic should be flagged to avoid being accidentally included in these treasure lists via something like an 'is_artifact' flag. The most basic/important generic treasure list would probably be each item type. With a generic treasurelists, instead of listing each possible item for a monster treasure list, we can now simply create these treasurelists on compile based on type such as axes, maces, shields, body armour, food, body parts and money. Each generic treasurelist can be customized inside a specific item dropping object. Orcs might have a 5% chance to drop (95% chance not to drop) each type of equipment, a 10% chance to drop food, and a 50% chance to drop body parts). By automating the inclusion of new generic items, it should be far easier for developers to add new generic items to the game without requiring extensive time additional to creating generic items in adding these items into each monster's treasurelists.
  
+ === Item Level ===
  The potential downside to this is that without knowing which items within a generic treasurelist are more or less valuable, generic treasure would be far more consistent in what dropped (boring) and players would be exposed to a wider quality of items from smaller variety of monsters making powerful items less valuable. To overcome this, I propose that we start using the level attribute of equipment to denote what the target audience (player level) should be. If we use the item archetypes to provide a target level, crossfire can then use the ratio between the item level and the level of the drop mechanism (monster, chest etc) to determine a sensible probability for the player to receive that item. This probability can be based off of a distribution (normal or poisson) with the standard deviation used to set how much variation from the monster level there is (And +luck could influence the standard deviation). We might consider adding an upper bound value such that items higher than monster level + upperbound are disregarded to avoid players getting too lucky.
  
- If we add a process to calculate the drop table during compile by creating treasurelists per item type based on item level from 1 - 110. For example, for armour we might see something like:
+ === Combining a generic treasurelist with item level ===
+ If we add a process to calculate the drop table during compile by creating generic treasurelists per item type and distributing each item within a generic treasurelist based item level from 1 - 110. For example, for armour we might see something like:
  
  ^Name ^ Item Level ^ range of values which drop this item ^ Probability ^
  |robe | 1 | 1< = robe <3 | 100% |
  |armour	| 4 | 4< = armour <6 | 50% |
@@ -232,11 +236,9 @@
  |full scale mail | 8 | 8< = full scale mail<10 | 100% |
  |plate mail | 10 | 10< = plate mail<15 | 100% |
  |hauberk | 15 | 15< = hauberk <110 | 100% |
  
- This must be run for all treasurelists of generic items.
- 
- We can now roll a dice and calculate a roll for an item.
+ We can now use a loaded (normal distribution) dice roll to calculate the probability for a specific item dropping.
  
  ===Example===
  A player kills a level 6 orc. The first item roll for treasure determines that the orc has successfully dropped an axe type item from the generic axe treasurelist. The new system would then roll to determine which type of axe from within the treasurelist it drops. The axe treasurelist might have 3 axes in it; a stone axe might be level 5, an axe might be level 8 and a Battle Axe might be level 15.  Using a normal distribution, the mean is the level of the object dropping the item, in this case a level 6 orc. The standard deviation (SD) is the variability of item drops. So for a SD of 4 the likelihoods would be:
  


IP-Address  : 59.167.121.117
Old Revision: http://wiki.metalforge.net/doku.php/user:saru:balance?rev=1412815788
New Revision: http://wiki.metalforge.net/doku.php/user:saru:balance

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/