[Crossfire-wiki] [Crossfire DokuWiki] page changed: user:cavesomething:possible_stat_values

[no-reply_wiki at metalforge.org]

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

Date        : 2010/05/10 11:53
User        : ryo
Edit Summary: comment on speed

@@ -82,10 +82,12 @@
  
  All of the discussion of times above are in seconds, for the purposes of the combat engine, these are translated into ticks. When an attack is made, the game calculates which tick the attack finishes in, and doesn't take another move until then. The 'partial tick' is stored as a value for when control is given back after the attack. If there is an attacking monster and the player elects not to attack, the attack speed rolls against the player speed to determine how good a hit the creature gets as the player moves away. - This is kind of what the speed system is supposed to do, but this approach is simpler, and prevents commands queuing so much.
  
  I am considering keeping all of the times described above as real-time not game time, and that typically 3 or 4 hits with an axe would be required to defeat a tough opponent, it is quite reasonable then that combat with a single creature might take an entire minute or more.
+ > fine by me, but then we need to drastically reduce the number of monsters on maps :)  --- //Ryo//
+ 
  
  AC and WC work like this (with wc the attacker's wc, ac the defender's ac):
    * if wc == ac, 50% chance to hit
    * if wc > ac, >50% chance to hit, capped to 90% or 95% - you can always miss?
    * if wc < ac, <50% chance to hit, bottom value is 5 or 10% - you can always get lucky
  The change shouldn't be linear, it should give bonuses for way higher wc or ac


IP-Address  : 82.236.87.204
Old Revision: http://wiki.metalforge.net/doku.php/user:cavesomething:possible_stat_values?rev=1273510243
New Revision: http://wiki.metalforge.net/doku.php/user:cavesomething:possible_stat_values

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