API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 9th, 2018
953
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 56.14 KB | None | 0 0
raw download clone embed print report
  1. #include "global.h"
  2.  
  3. #define FILE_PREFIX "itemstatcost"
  4. #define NAME_PREFIX "is"
  5.  
  6. /*
  7. Stat - An Id pointer used in other *.txt files (Properties.txt, Skills.txt, States.txt and also within ItemStatCost.txt) to refer to this stat, this field must be unique, otherwise you're looking into a world of glitches and bugs.
  8.  
  9. Id - This field isn't compiled into the bin files, and thus only serves as reference for the internal numeric Id. The internal idea is identical to the # of the record in the array (that is, the first stat would be 0, the second 1 and so on).
  10.  
  11. Send Other - A boolean that controls whenever the value of this stat is sent to other players, this is only semi functional because most of this is hardcoded to specific stats only, leave it set only for the stats that are being sent in vanilla (Strength
  12. , Dexterity etc) because the game needs to keep clients up to date on these values to function properly (otherwise you'll just glitch up the game).
  13.  
  14. Signed - A boolean that controls whenever the stat is signed (can be both positive and negative) or unsigned (can only be positive), this doesn't really seam to make any difference because whenever a stat is really signed or unsigned depends on how the
  15. code is designed to use it, and not on this column, for example Life, Mana, Stamina (etc) can all become negative when they exceed 8388607 * 256 no matter what you set this too, I suspect this simply has to do with the way the game reads stat packets
  16. because these packets generally only transmit stats in WORD size and it would need to know if they are signed or unsigned for a semi-proper conversion (...)
  17.  
  18. Send Bits - How many bits of data the game will attempt to fit into a stat update packet for the value of the stat if the stat is sent to clients, again this is not really utilized too a very great extent because most of this is hardcoded, in general
  19. for signed stats, it is best to set this to 1 more then Save Bits (so say, if save bits is 31 then set this to 32), for unsigned stats it shouldn't matter. Stats with Save Bits of 32 are never treated as signed, always unsigned, and you can't really set
  20. Send Bits to above 32 bits anyway (for very obvious reasons).
  21.  
  22. Send Param - How many bits of data the game will attempt to fit into a stat update packet for the parameter of the stat if the stat is sent to clients, it is best to set this to 1 more then Save Param Bits unless it is set to 32 bits (in which case it
  23. is unsigned), otherwise the param is always signed. This is used to transmit things like the skill granted by oskills (etc), however the same applies here as applied to the previous column, this is almost entirely hardcoded.
  24.  
  25. UpdateAnimRate - This boolean tells the game to call the speed handler and properly adjust the speed of a unit when a stat with this boolean set to true is altered on the unit (via a skill for example), this is for example the case when an aura is
  26. applied, so that the speed of the unit changes immediately and not after the current cycle (either attack, walk to a cell etc) ends... As usual, this is rather hardcoded so you'd need to expand the code if you add custom speed stats like these!
  27.  
  28. Saved - This boolean controls whenever the value of the stat is saved on characters inside the *.d2s file after you leave the game, be aware that statNo 511 is used to signify the "End-Of-Stat-Section" and cannot be used, there are reports that only
  29. stats 0 to 255 are saveable and other reports that all 510 stats are saveable, I haven't tested this myself so I cannot validate either claim ATM... Looking at the *.d2s reading and writing code I however could not find any artificially imposed
  30. limitation (other then the aforementioned fact stat 511 cannot be used for anything).
  31.  
  32. CSvSigned - If the previous column is set to true, this boolean controls whenever the stat is saved in signed or unsigned format, this makes no real difference, other then the fact the way it is written and read from the *.d2s is different (this has
  33. more revelance when you have the source code at hand and don't want to get tons of warning messages about signed / unsigned mismatch I guess)...
  34.  
  35. CSvBits - How many bits of data are allocated to the value of this stat within the *.d2s file stat section when the stat is saved (only used if the Saved boolean is true), for unsigned stats you can go all the way to 32 bits (allowing for a range of 0
  36. to 4294967295), for signed stats you can go only to 31 bits (allowing for a range of -2147483648 to 2147483647), it makes no real difference as stated for the previous column, keep it like in vanilla for the existing stats though, it works so no need to
  37. fix it. Setting this field to 32 bits for a signed stat has the same effect as setting CSvSigned to false.
  38.  
  39. CSvParam - How many bits of data are allocated to the parameter of this stat within the *.d2s file stat section when the stat is saved (only used if the Saved boolean is true), the parameter is always signed, unless you set this to 32 bits, in which
  40. case it becomes unsigned. The same applies here as for the previous column...
  41.  
  42. fCallback - This boolean controls whenever the stat-assignment callback function is called by the game if the value of this stat changes, this is used to assign / remove item events, skills, auras, states and more to the character / monster... For new
  43. special effects you have to expand the callback function... It will work fine for new stats that trigger item events however!
  44.  
  45. fMin - This boolean controls whenever the game will attempt to keep the stat in range calling a special function (and at times doing this inline, such as when the stats are altered by an aura), this prevents stats like strength, dexterity, energy,
  46. vitality (etc) from dropping below zero...
  47.  
  48. MinAccr - This field (a DWORD btw) controls the minimum value that the stat is capped to, this seams (I haven't verified this) to work hand-in-hand with fMin, however the times I've seen the code access that flag inline I haven't seen it utilize this
  49. column, but rather use hardcoded minimum values!
  50.  
  51. Encode - This field tells the game whenever to encode the stat (and in this case in what way to encode it) when it is saved to conserve space, this is used for complex stats with more then just a parameter and a value such as 'chance to cast on event',
  52. which have to store the chance, sLvl and the skill to cast, the arithmetics of this are rather complex and aren't within the scope of this fileguide, you can read about them in several old forum posts however... For new stats, follow the theme vanilla
  53. is using and use this only if you try to duplicate a stat that is encoded in vanilla!
  54.  
  55. Add and Multiply - These two fields control the additional price added to an item's cost (be aware that certain stats like armorclass on armors (etc) are treated more then once as there are hardcoded cases for them!), the bonus equals: cost * (1 + value
  56. * multiply / 1024)) + add (...)
  57.  
  58. Divide - This field is not used by the code anymore, the game uses a inline function for all this price judgling, and it never accesses divide, rather it uses a hardcoded division by 1024!
  59.  
  60. ValShift - This field tells the game how the stat is going to be read from and written to items, it does not control whenever the stat is generally used in higher precision, this is entirely hardcoded! Basically this field is only there to save space in
  61. the *.d2s file, so that instead of having to save +256 life it will simply save +1 life when this stat is present on an item!
  62.  
  63. 1.09-Save Bits and 1.09-Save Add - These fields are used only for items imported from v1.07 - v1.09, they replace Save Bits and Save Add so that you can convert the items to the old stat format to the new one, character stats didn't use ItemStatCost.txt
  64. prior to v1.10 so this doesn't apply to those stats... If you want to prevent people from cheating by creating a v1.09 character and then entering your mod with hacked items (that will get automatically converted by the game), simply blank out all these
  65. columns and they'll get a nice "bad stats" or "bad inventory" error in their face icon_wink.gif
  66.  
  67. Save Bits and Save Add - These fields control how many bits of data are allocated to the value of this stat within the *.d2s file item stat section ONLY, they have almost no realtime application at all, stats granted by skills and monster stats (etc)
  68. are not in any way or form bound to this! The only realtime application this has is when an item is getting compressed / decompressed (which happens every time you pick it up or do anything with it) any way, with this misconception taken off the shelf,
  69. lets look at how they work. Save Bits controls how many bits of data are allocated to the stat value (see discussion under CSvBits for more info about unsigned / signed implications on what values you can use in this field), the actual maximum value of
  70. the stat is therefore equal to 2^SaveBits-1, now Save Add comes into play, this controls how large the negative range of the stat can be, for example a Save Add equal to 100 would allow you to use -100 for this stat on an item, this also means the
  71. maximum value possible for the stat decreases by 100, thus the final range possible for a stat is -SaveAdd to 2^SaveBits-(SaveAdd+1).
  72.  
  73. Save Param Bits - This field controls how many bits of data are allocated to the parameter of this stat when it is saved on items, the same applies here as to the previous column and to CSvParam so refer to the description of these columns, Save Add
  74. does not effect the maximum or minimum value of the stat's parameter however... It is best to set this to 17 for all stats that use any form of Id for their parameter (either a skill or a monster etc), because most Id ranges are capped to 65,535, and
  75. these parameters always being signed unless they are set to store 32 bits means this will allow you to use all Ids without any fear of glitches or bugs!
  76.  
  77. KeepZero - This boolean supposedly controls whenever to prevent the stat from going negative, probably working hand-in-hand with some of the fMin implementations, at best the effect is however only client-side, as we all know stats like mana and stamina
  78. can roll over when they exceed 8388607 * 256!
  79.  
  80. Op, Op Param, Op Base and Op Stat1 to Op Stat3 - These fields control special forms of stat assignment used for example for stats that add a bonus depending on cLvl (etc), I'll explain each of the op methods in detail below (there are in total 13 op
  81. formulae, but not all are used by the game)... Leaving this field blank or setting it to 0 will use the default op, that just adds the stat to the unit directly... In the below formulae, opstat refers to the stats set in the three Op Stat columns,
  82. statvalue refers to the value of the stat itself (the stat that has the op stuff assigned to it), basevalue refers to the stat set in the Op Base column and param refers to the value set in the Op Param column!
  83.  
  84. 1 - adds opstat.base * statvalue / 100 to the opstat.
  85.  
  86. 2 - adds (statvalue * basevalue) / (2 ^ param) to the opstat, this does not work properly with any stat other then level because of the way this is updated, it is only refreshed when you re-equip the item, your character is saved or you level up,
  87. similar to passive skills, just because it looks like it works in the item description does not mean it does, the game just recalculates the information in the description every frame, while the values remain unchanged serverside.
  88.  
  89. 3 - this is a percentage based version of op #2, look at op #2 for information about the formula behind it, just remember the stat is increased by a percentage rather then by adding an integer.
  90.  
  91. 4 - this works the same way op #2 works, however the stat bonus is added to the item and not to the player (so that +defense per level properly adds the defense to the armor and not to the character directly!)
  92.  
  93. 5 - this works like op #4 but is percentage based, it is used for percentage based increase of stats that are found on the item itself, and not stats that are found on the character.
  94.  
  95. 6 - like for op #7, however this adds a plain bonus to the stat, and just like #7 it also doesn't work so I won't bother to explain the arithmetic behind it either.
  96.  
  97. 7 - this is used to increase a stat based on the current daytime of the game world by a percentage, there is no need to explain the arithmetics behind it because frankly enough it just doesn't work serverside, it only updates clientside so this op is
  98. essentially useless.
  99.  
  100. 8 - hardcoded to work only with maxmana, this will apply the proper amount of mana to your character based on CharStats.txt for the amount of energy the stat added (doesn't work for non characters)
  101.  
  102. 9 - hardcoded to work only with maxhp and maxstamina, this will apply the proper amount of maxhp and maxstamina to your character based on CharStats.txt for the amount of vitality the stat added (doesn't work for non characters)
  103.  
  104. 10 - doesn't do anything, this has no switch case in the op function.
  105.  
  106. 11 - adds opstat.base * statvalue / 100 similar to 1 and 13, the code just does a few more checks
  107.  
  108. 12 - doesn't do anything, this has no switch case in the op function.
  109.  
  110. 13 - adds opstat.base * statvalue / 100 to the value of opstat, this is useable only on items it will not apply the bonus to other unit types (this is why it is used for +% durability, +% level requirement, +% damage, +% defense [etc]).
  111.  
  112.  
  113. Direct - this boolean controls whenever this stat has a maximum stat associated with it, which among others means that unless you screw up something badly, this stat can never exceed the value of the maximum stat and that any change to this stat is
  114. permanent (a skill that alters mana, hitpoints or stamina is permanent, while a skill that alters maxmana, maxhp and maxstamina is temporary). You do not need to specify a maximum stat for the effect to be permanent, this can be used to get kill
  115. counters to work (look for SVR's old post).
  116.  
  117. MaxStat - the maximum stat associated with this stat, this field only ever has an effect if Direct is set to true, see the discussion under that field. Percentage based increases to the max stat will usually alter this stat too, however this has some
  118. hardcoded aspects to it and is not entirely softcoded.
  119.  
  120. ItemSpecific - this boolean controls whenever this stat is specific to a single item, that is, if you socket a jewel that adds +durability or +quantity into something else, the quantity or durability of both items will not stack when a general call to
  121. GetStat is returned, however whenever this works properly is unknown, I at least haven't tested it and nobody else has either. It should also prevent the stat from being added to the item owners accumulated total of that stat.
  122.  
  123. DamageRelated - this boolean controls whenever the stat will be restricted to a single weapon and not stack with the item owners accumulated total of that stat when he equips the weapon (this is used to prevent barbarians who dual wield from for example
  124. having 50% lifesteal if one weapon has 1% and the other 49% no matter what weapon they swing). To explain this more indepth, when you swing your weapon the game copies all these stats (from the weapon involved) to a temporary statlist that is then
  125. flushed after the attack is completed (this is not 100% what happens, but it should give you an idea).
  126.  
  127. ItemEvent1 and ItemEvent2 - the event (from Events.txt) that will trigger the associated event function be aware that not every event will work with every event function, and some event functions will not work when set as an item event!
  128.  
  129. ItemEventFunc1 and ItemEventFunc2 - the event function associated with the corresponding event set in the previous columns. Below is a list of events and what they do.
  130.  
  131. 1 - shoots a missile at the owner of a missile that has just hit you (Chilling Armor uses this)
  132. 2 - freezes the attacker for a set duration the attacker (Frozen Armor uses this)
  133. 3 - does cold damage to and chills the attacker (Shiver Armor uses this)
  134. 4 - % of damage taken is done to the attacker (Iron Maiden, thorns uses a hardcoded stat)
  135. 5 - % of damage done added to life, bypassing the targets resistance (used by Life Tap)
  136. 6 - attacker takes physical damage of #
  137. 7 - knocks the target back
  138. 8 - induces fear in the target making it run away
  139. 9 - applies Dim Vision to the target (it casts the actual curse on the monster)
  140. 10 - attacker takes lightning damage of #
  141. 11 - attacker takes fire damage of #
  142. 12 - attacker takes cold damage of #
  143. 13 - % damage taken is added to mana
  144. 14 - freezes the target
  145. 15 - causes the target to bleed and lose life (negative life regen)
  146. 16 - crushing blow against the target
  147. 17 - mana after killing a monster
  148. 18 - life after killing a demon
  149. 19 - slows the target
  150. 20 - casts a skill against the defender
  151. 21 - casts a skill against the attacker
  152. 22 - absorbs physical damage taken (used by Bone Armor)
  153. 23 - transfers damage done from the summon to the owner (used by Blood Golem)
  154. 24 - used by Energy Shield to absorb damage and shift it from life to mana
  155. 25 - absorbs elemental damage taken (used by Cyclone Armor)
  156. 26 - transfers damage taken from the summon to the owner (used by Blood Golem)
  157. 27 - used to slow the attacker if he hits a unit that has the slow target stat (used by Clay Golem)
  158. 28 - life after killing a monster
  159. 29 - destroys the corpse of a killed monster (rest in peace effect)
  160. 30 - cast a skill when the event occurs, without a target
  161. 31 - reanimate the target as the specified monster
  162.  
  163.  
  164. DescPriority - the higher this value is the further up in the item description this stat will be listed, if more then one stat share the same priority they are listed in the order they are inside the file, valid values range between 0 and 255.
  165.  
  166. DescFunc - the function used for generating the description for this stat, this works like the descfuncs in SkillDesc.txt pretty much. See below for an explanation of individual functions, these are listed the way they would show up if DescVal is set to
  167. 1. This follows the syntax Char used in the old fileguide, but includes the functions he didn't cover.
  168.  
  169. 1 - +[value] [string1]
  170. 2 - [value]% [string1]
  171. 3 - [value] [string1]
  172. 4 - +[value]% [string1]
  173. 5 - [value*100/128]% [string1]
  174. 6 - +[value] [string1] [string2]
  175. 7 - [value]% [string1] [string2]
  176. 8 - +[value]% [string1] [string2]
  177. 9 - [value] [string1] [string2]
  178. 10 - [value*100/128]% [string1] [string2]
  179. 11 - Repairs 1 Durability In [100 / value] Seconds
  180. 12 - +[value] [string1]
  181. 13 - +[value] to [class] Skill Levels
  182. 14 - +[value] to [skilltab] Skill Levels ([class] Only)
  183. 15 - [chance]% to case [slvl] [skill] on [event]
  184. 16 - Level [sLvl] [skill] Aura When Equipped
  185. 17 - [value] [string1] (Increases near [time])
  186. 18 - [value]% [string1] (Increases near [time])
  187. 19 - this is used by stats that use Blizzard's sprintf implementation (if you don't know what that is, it won't be of interest to you eitherway I guess), look at how prismatic is setup, the string is the format that gets passed to their sprintf spinoff.
  188. 20 - [value * -1]% [string1]
  189. 21 - [value * -1] [string1]
  190. 22 - [value]% [string1] [montype] (warning: this is bugged in vanilla and doesn't work properly, see CE forum)
  191. 23 - [value]% [string1] [monster]
  192. 24 - used for charges, we all know how that desc looks icon_wink.gif
  193. 25 - not used by vanilla, present in the code but I didn't test it yet
  194. 26 - not used by vanilla, present in the code but I didn't test it yet
  195. 27 - +[value] to [skill] ([class] Only)
  196. 28 - +[value] to [skill]
  197.  
  198. DescVal - Controls whenever and if so in what way the stat value is shown, 0 = doesn't show the value of the stat, 1 = shows the value of the stat infront of the description, 2 = shows the value of the stat after the description.
  199.  
  200. DescStrPos - The string used for the description when the stat value is positive.
  201.  
  202. DescStrNeg - The string used for the description when the stat value is negative.
  203.  
  204. DescStr2 - An additional string used by some DescFuncs, usually used as a suffix or for aditional info (such as per character level etc).
  205.  
  206. dGrp - When all stats in this group are present on the same item and they all have the same value, replace their description with the associated group description.
  207.  
  208. dGrpFunc - The same as DescFunc, just for the group description
  209.  
  210. dGrpVal - The same as DescVal, just for the group description
  211.  
  212. dGrpStrPos - The same as DescStrPos, just for the group description
  213.  
  214. dGrpStrNeg - The same as DescStrNeg, just for the group description
  215.  
  216. dGrpStr2 - The same as DescStr2, just for the group description
  217.  
  218. Stuff - Stay far away from this column unless you really know what you're doing and / or work for Blizzard, this column is used during bin-file creation to generate a cache regulating the op-stat stuff and other things, changing it can be futile, it
  219. works like the constants column in MonUMod.txt and has no other relation to ItemStatCost.txt, the first stat in the file simply must have this set or else you may break the entire op stuff.
  220.  
  221. */
  222.  
  223. /*
  224. A.Stat = 属性名。
  225. B.ID = 属性ID。
  226. C.Send Other = 很可能用来决定在联机游戏时，此属性是否发送给其他人,只针对那些对图象要求较高的属性(faster attack/cast/gethit rate)。由于某些原因,敏捷(dexterity)和力量(strength)也同时被发送。留意一下txt文件即知。
  227. D.Signed = 该属性值是否为有符号数。也就是说该属性是否能为负值(negative)。
  228. E.Sendbits = 在客户端和服务器之间传送此值时所用的位长。
  229. F.Send Param = 与客户端和服务器有关的参数。
  230. G.UpdateAnimateRate = ???。可能情况：取布尔值，告诉客户端更新角色动画的速率。
  231. H.Saved = 角色存档时该属性是否同时被保存。物品上的属性随物品一起保存。
  232. I.CSvSigned = 在角色存档是否采用有符号数来保存该属性。1=是,0=否。
  233. J.CSvBits = 存储位长,在角色存档中采取多少位保存。能够保存的最大值为''2^CSvBits-1''。
  234. K.CSvParam = 存储参数,与保存某些属性的参数有关。
  235. L.fCallback = ???
  236. M.fMin = ???
  237. N.MinAccr = ???
  238. O.Encode = 与编码方式有关。
  239. P/Q/R.Add/Multiply/Divide = 计算物品价格时的参数值。(其他txt文件同)
  240. S.ValShift = 决定值以多大的精度变化?。’1‘表示有2^1=2阶精度,’2‘则有2^2=4阶精度,’8‘具有2^8=256阶精度,比如生命点就按1/256的精度进行计算。
  241. T/U.1.09-Save Bits/1.09-Save Add = 在1.09版中的存储位长/相对1.09的增加值。可能与角色转换有关,即1.09的存档导入1.10。
  242. V/W.Save Bits/Save Add = 用来处理物品上数值的保存。同时也决定了该属性可能的最小和最大值。其中,‘’Save Bits‘’决定了属性值的存储位长,‘’Save Add‘’决定了最小值,且和''Save Bits'一起决定最大值。
  243. 结果为:stat最小值 = - [Save Add];
  244. stat最大值 = 2^[Save Bits] - [Save Add] - 1;
  245. 比如:"Save Add'' = 32,"Save Bits = 8"
  246. 则有:最小值 = - 32;
  247. 最大值 = 2^8 - 32 -1 = 256 - 33 = 223
  248. X.SaveParamBits = 决定参数以多少位(bits)保存(???)。
  249. Y.keepzero = 布尔值，控制该属性能否出现负值(或者理解为有消极效果)。1=不能。
  250. Z.op = 操作数ID。用来计算该属性产生的效果。
  251. 已知的ID及其效果:
  252. 1 : op 状态按 [statvalue] 百分比增加（op stats are increased by [statvalue] percent）
  253. 2 : op 状态按 [statvalue] * [op base] / 2^[op param]增加（op stats are increased by [statvalue] * [op base] / 2^[op param]）
  254. 3 : 未使用，效果未知（not used, effect unknown）
  255. 4 : 似乎是和2的效果相同（seems to have the same effect as 2）
  256. 5 : op 状态按 [statvalue] * [op base] / 2^[op param]百分比增加（op stats are increased by [statvalue] * [op base] / 2^[op param] percent）
  257. 6 : op 状态按时间增加（op stats are increased by time）
  258. 7 : op 状态按时间和百分比增加（op stats are increased by time and percent）
  259. 8 : 用来计算法力值基于能量值的增加（used to calculate the mana based on energy）
  260. 9 : 用来计算生命力和体力值基于活力值的增加（used to calculate the hitpoints and stamina based on vitality）
  261. AA.op param = 见’op‘。
  262. AB.op base = 见’op‘。
  263. AC/AD/AE.op stat1-op stat3 = 控制状态,见’op‘。
  264. AF.direct = 如果该属性能加成到其他属性上,此处设置为1。比如当装备上一个+30mana的物品时,你的最大mana值也会同时增加。
  265. AG.maxstat = 当‘’direct=1‘’时,该属性能加成到的最大属性。
  266. AH.itemspecific = 该属性是否为某类(个)物品独有(且只能影响此类/个物品),比如耐久度,孔数等。比如你可以在这里设置使你的第二件武器不会增加第一件武器的攻击速度。
  267. AI.damagerelated = 该属性是否与‘’伤害‘’(damage)有关。1=是。(效果未知)
  268. AJ.itemevent1 = 当事件(event)发生时,触发‘’intemeventfuc1‘’(见下)。
  269. AK.itemeventfunc1 = 作用在‘’itemevent1‘’上的函数。使用的函数如下:
  270. 6:attacker takes damage of [statvalue] // 攻击者获得伤害
  271. 7:knockback // 弹回
  272. 8:howl effect // bar的吼叫效果
  273. 9:stupidity effect // 致盲效果
  274. 10:attacker takes lightning damage of [statvalue] // 攻击者获得闪电伤害
  275. 14:freeze effect // 冰冻效果
  276. 15: openwounds effect // 撕裂伤口效果
  277. 16:crushing blow // 一击致命(或者’粉碎性打击‘?!)
  278. 17:get mana (after kill) // 每杀死一个怪物得到魔法值
  279. 18:get life (after demon kill)
  280. 19:slow effect // 迟缓效果
  281. 20:skill is released // 技能释放,触发事件:被围攻&杀死怪物等
  282. 21:skill is released //类似20?!
  283. 28:get life (after kill) // 每杀死一个怪物得到生命值
  284. 29:slain monster rests in peace // 杀死怪物回复平静
  285. 30:skill is released // 释放技能,触发事件:被杀死&升级
  286. 31:reanimate slain monster // 杀死怪物后被鼓舞
  287. AL.itemevent2 = 当事件(event)发生时,执行‘’intemeventfuc2‘’
  288. AM.itemeventfunc2 = 作用在‘’itemevent2‘’上的函数。
  289. AN.descpriority =控制该属性在物品上显示的优先级。值越高,在物品上出现得越早。(尚不能确定)
  290. AO.descfunc = 控制属性显示方式的函数。以下是其中的一些:
  291. 1 : + [数值] [字符串]（+[value] [string]）
  292. 2 : [数值]% [字符串]（[value]% [string]）
  293. 3 : [数值] [字符串]（[value] [string]）
  294. 4 : + [数值]% [字符串]（+[value]% [string]）
  295. 5 : [数值/1.28]% [字符串]，野蛮人的吼叫技能使用（[value/1.28]% [string] // used for howl）
  296. 6 : + [数值] [字符串] (基于角色等级)（+[value] [string] (based on character level)）
  297. 7 : [数值]% [字符串] (基于角色等级)（[value]% [string] (based on character level)）
  298. 8 : + [数值]% [字符串] (基于角色等级)（+[value]% [string] (based on character level)）
  299. 9 : [数值] [字符串] (基于角色等级)（[value] [string] (based on character level)）
  300. 10 : [数值/1.28]% [字符串] (基于角色等级)（[value/1.28]% [string] (based on character level)）
  301. 11 : 每 [100/数值] 秒自动修复1点耐久度（Repairs 1 durability in [100/value] seconds）
  302. 12 : + [数值] [字符串]，致盲和冰冻使用（+[value] [string] // used for stupidity, freeze）
  303. 13 : + [数值] 到 [角色] 技能等级（+[value] to [class] skill levels）
  304. 14 : + [数值] 到 [角色技能页] (仅限[角色])（+[value] to [skilltab] skills ([class] only)）
  305. 16 : 装备时显现等级 %d %s 灵气（Level %d %s Aura When Equipped）
  306. AP.descval =
  307. 0:不显示值。
  308. 1:值先显示,即显示顺序为‘’值+字符串‘’。比如“+5 to strength‘’(加5到力量)。
  309. 2:字符串先显示,然后才是值,即‘’字符串+值‘’。比如‘’strenght +5‘’(力量加5)。
  310. AQ.descstrpos = 值为正时使用的描述性字符串。
  311. AR.descstrneg = 值为负时使用的描述性字符串。
  312. AS.descstr2 = 第二个显示字符(与’‘attributes/per level’‘有关--随等级增长属性,如’‘item-resist-cold-perlevel,ID=230’‘)。
  313. AT.dgrp = 显示组。同一显示组中的相同属性将一起显示。
  314. 说明:该txt源文件中一共只有两组,每组含四个属性。
  315. 组一:’‘dgrp=1’‘,包括’‘strength(力量,ID=0)’‘,’‘energy(精力,ID=1)’‘,’‘dexterity(敏捷,ID=2)'',''vitality(生命,ID=3)''。
  316. 组二:''dgrp=2'',包括’‘fireresist(抗火,ID=39)'',''lightresist(抗闪电,ID=41)'',''coldresist(抗寒,ID=43)'',''poisonresist(抗毒,ID=45)''。
  317. AU.dgrpfunc = 与‘’descfunc‘‘同,控制显示组(display groups)的显示方式。
  318. AV.dgrpval = 与‘’descval‘’同,针对显示组。
  319. AW.dgrpstrpos = 与’‘descstrpos’‘同,针对显示组。
  320. AX.dgrpstrneg = 与’‘descstrneg’‘同,针对显示组。
  321. AY.dgrpstr2 = 与’‘descstr2’‘同,针对显示组。
  322. AZ.stuff = ???
  323. BA.*eol = 行结束符’0‘。
  324.  
  325. 注: op参数和显示方式参考了Sloovy的帖子,在此表示感谢！
  326. */
  327.  
  328. /*
  329. 文件名解析：
  330. Item：道具，在这里表示装备。
  331. Stat：状态，在这里表示属性。
  332. Cost：开销，在这里表示某些相关信息。
  333. 所以此文件就是描述所有可能在装备出现的属性的相关信息。1.10版本以后此文件中又加入了人物属性的一些信息。
  334. 此文件中的每一行表示一条属性。
  335.  
  336.  
  337. 回复
  338.  
  339. 2楼
  340. 2011-09-20 23:48
  341.  
  342. 举报 |
  343.  
  344. zqtjingzi
  345. 小吧主
  346. 12
  347.  
  348. 每列的含义如下：
  349.  
  350.  
  351. 回复
  352.  
  353. 3楼
  354. 2011-09-20 23:48
  355.  
  356. 举报 |
  357.  
  358. 虫师林若
  359. 天堂信徒
  360. 11
  361.  
  362. 留名
  363.  
  364.  
  365. 回复
  366.  
  367. 4楼
  368. 2011-09-20 23:49
  369.  
  370. 举报 |
  371.  
  372. zqtjingzi
  373. 小吧主
  374. 12
  375.  
  376. Stat：属性名。所以其它文件中都使用此列的名字来指明某条属性。
  377.  
  378. ID：属性编号。实际上没有用到。
  379.  
  380. Send Other：控制是否将此属性发送给其它人，但大多数时候都由硬代码写明。
  381.  
  382. Signed：此属性值是否为有符号数，但经本人测试并无效果，是由硬代码写明的。据说在联网传输时会用到此列。
  383.  
  384. Sendbits：联网传输此属性时所用的位长，但大多数时候都由硬代码写明。如果此属性值为有符号数，则此列的值最好为Save Bits + 1，且不要超过32。
  385.  
  386. Send Param：联网传输此属性的参数时所用的位长，但大多数时候都由硬代码写明。由于Param总为有符号数，所以此列的值最好为Save Param Bits + 1且不要超过32。
  387.  
  388. UpdateAnimateRate：当此属性变化时是否独立于检测循环外更新（可能会更快的获得效果），但大多数时候都由硬代码写明。
  389.  
  390. Saved：此属性的值是否存入.d2s文件中，基本只用于人物属性。
  391.  
  392. CSvSigned：若此属性存入.d2s文件中，是否使用有符号数存储。大多数时候由硬代码写明。
  393.  
  394. CSvBits：若此属性存入.d2s文件中，存储的位数是多少。
  395.  
  396. CSvParam：若此属性存入.d2s文件中，此属性参数的存储位数是多少。
  397.  
  398. fCallback：当此属性变化时，是否调用反馈函数以达到此属性的效果（如增加某一技能，会修改人物技能列表）。
  399.  
  400. fMin：此属性的值是否被限定在一定范围内。
  401.  
  402. MinAccr：若此属性的值受限，那么其最小值是多少。实际上此列不起作用，由硬代码写明。
  403.  
  404. Encode：当此属性的参数较为复杂时（如打击触发技能），使用何种编码方式存储属性参数。
  405.  
  406. Add：价格增加因子a。
  407.  
  408. Multiply：价格增加因子b。
  409.  
  410. Divide：价格计算底数，全为1024，实际上都不起作用，硬代码中写明是1024。
  411.  
  412. 此属性对物品价格的影响应为 cost * (1 + value * multiply / 1024) + add。
  413.  
  414. ValShift：此属性值的精度。公式为1/2^n，n为此列的值。
  415.  
  416. 1.09-Save Bits：在1.07-1.09版中的存储位长。
  417.  
  418. 1.09-Save Add：在1.07-1.09版中的存储偏移量。
  419.  
  420. Save Bits：存储位长。硬代码中已写明，且游戏开始时会检测，若修改则会导致游戏出错。
  421. Save Add：存储偏移量。
  422.  
  423. 此属性可能存在的值受以上两列限制，最小值为-1 * SaveAdd，最大值为 2^SaveBits - SaveAdd - 1。
  424.  
  425. SaveParamBits：Param参数的存储位长。
  426.  
  427. keepzero：此属性是否能出现负值。但实际上并没有作用。
  428.  
  429.  
  430.  
  431.  
  432. 回复
  433.  
  434. 5楼
  435. 2011-09-20 23:49
  436.  
  437. 举报 |
  438.  
  439. zqtjingzi
  440. 小吧主
  441. 12
  442.  
  443. op：此属性值的计算公式，后面会列出op的取值**及对应的计算公式。
  444.  
  445. op param：计算公式中的参数。
  446.  
  447. op base：计算公式中的参数。
  448.  
  449. op stat1：此属性所影响的属性1。
  450.  
  451. op stat2：此属性所影响的属性2。
  452.  
  453. op stat3：此属性所影响的属性3。
  454.  
  455. direct：此属性是否有关联的最大值属性。
  456.  
  457. maxstat：此属性所关联的最大值属性，仅当direct=1时有作用。
  458.  
  459. itemspecific：此属性是否只作用于单一物品，手套上增加耐久度的属性不会改变鞋子的耐久度。
  460.  
  461. damagerelated：此属性是否只作用于单一武器，如第二件武器上的火焰伤害不会加到第一件武器上。
  462.  
  463. itemevent1：触发此属性函数1的事件，与Events.txt关联。如CB需要先击中怪物才能触发。
  464.  
  465. itemeventfunc1：事件1发生时触发的函数。函数的取值**和作用在后面集中说明。
  466.  
  467. itemevent2：触发此属性函数2的事件，与Events.txt关联。
  468.  
  469. itemeventfunc2：事件2发生时触发的函数。
  470.  
  471. descpriority：物品属性显示时的优先级，此列的值越高则此属性在装备的属性列表中越靠上，取值范围为0-255。
  472.  
  473. descfunc：文字描述此属性的方式，取值**和对应描述方式后面集中说明。
  474.  
  475. descval：如何显示此属性的值。0表示不显示值；1表示先显示值，如+5力量；2表示后显示值，如力量+5。
  476.  
  477. descstrpos：属性值为正数时的描述语句。
  478.  
  479. descstrneg：属性值为负数时的描述语句。
  480.  
  481. descstr2：描述方式中的语句2。
  482.  
  483. dgrp：此属性所属的描述组别。相同组别的属性若属性值相等会统一显示，如+1力量、+1敏捷、+1精力、+1体力会变成+1所有属性。抗性也一样。目前只有这两种组中坚力量。
  484.  
  485. dgrpfunc：含义同descfunc，用在组显示中。
  486.  
  487. dgrpval：含义同descval，用在组显示中。
  488.  
  489. dgrpstrpos：含义同descstrpos，用在组显示中。
  490.  
  491. dgrpstrneg：含义同descstrneg，用在组显示中。
  492.  
  493. dgrpstr2：含义同descstr2，用在组显示中。
  494.  
  495. stuff：如果你不是暴雪的工作人员的话请不要动这一列。bin文件生成时有用。
  496.  
  497. *eol：行尾标志，必须为0。
  498.  
  499.  
  500. 回复
  501.  
  502. 6楼
  503. 2011-09-20 23:49
  504.  
  505. 举报 |
  506.  
  507. zqtjingzi
  508. 小吧主
  509. 12
  510.  
  511. 说明1：op的取值范围及计算方式：
  512. 设op param = p，op base = b，原属性值为v，最终属性值为s。
  513. op = 1 —— s = b * v / 100
  514. op = 2 —— s = b * v / 2^p
  515. op = 3 —— s = b * v / 2^p 用于按百分比增加的属性。
  516. op = 4 —— s = b * v / 2^p 用于作用于装备的属性。
  517. op = 4 —— s = b * v / 2^p 用于按百分比增加且作用于装备的属性。
  518. op = 6 —— 用于随时间变化的属性，已经没用了。
  519. op = 7 —— 用于随时间变化且按百分比增加的属性，已经没用了。
  520. op = 8 —— 只用于精力属性，会根据CharStats.txt中的属性对不同的角色加不同的最大魔法值。
  521. op = 9 —— 只用于体力属性，会根据CharStats.txt中的属性对不同的角色加不同的最大生命值和最大耐力值。
  522. op = 11—— s = b * v / 100 比1多了一些相关的检查。
  523. op = 13—— s = b * v / 100 用于仅作用于一件装备的属性。
  524.  
  525.  
  526. 回复
  527.  
  528. 7楼
  529. 2011-09-20 23:49
  530.  
  531. 举报 |
  532.  
  533. zqtjingzi
  534. 小吧主
  535. 12
  536.  
  537. 说明2：ItemEventFunc的取值范围及函数作用：
  538. func = 1 —— 当有远程攻击命中你时发射一个导弹，如寒冰装甲。
  539. func = 2 —— 冻结近身攻击你的人。
  540. func = 3 —— 对近身攻击你的人造成一定的冰冷伤害。
  541. func = 4 —— 按比例反弹近身攻击对你造成的伤害。
  542. func = 5 —— 按比例将对敌人的伤害转化为生命。
  543. func = 6 —— 攻击者受到伤害。
  544. func = 7 —— 击退。
  545. func = 8 —— 恐惧。
  546. func = 9 —— 致盲。
  547. func = 10—— 攻击者受到闪电伤害。
  548. func = 11—— 攻击者受到火焰伤害。
  549. func = 12—— 攻击者受到冰冷伤害。
  550. func = 13—— 将受损的生命转化为法力。
  551. func = 14—— 冻结目标。
  552. func = 15—— 撕开伤口。
  553. func = 16—— 压碎性打击。
  554. func = 17—— 杀死怪物获得法力。
  555. func = 18—— 杀死恶魔时获得生命。
  556. func = 19—— 减速。
  557. func = 20—— 对属性拥有者的攻击对象施放法术。
  558. func = 21—— 对攻击属性拥有者的对象施放法术。
  559. func = 22—— 吸收物理伤害。
  560. func = 23—— 将召唤物造成的伤害转到角色身上。
  561. func = 24—— 用法力抵消伤害。
  562. func = 25—— 吸收元素伤害。
  563. func = 26—— 将召唤物受到的伤害转到角色身上。
  564. func = 27—— 对伤害到此属性拥有者的或此属性拥有者伤害到的减速。
  565. func = 28—— 杀死怪物时获得生命。
  566. func = 29—— 杀死怪物恢复平静。
  567. func = 30—— 在某一事件发生时施放技能，不用选择施放对象。
  568. func = 31—— 复活目标成为某一指定目标。
  569.  
  570.  
  571. 回复
  572.  
  573. 8楼
  574. 2011-09-20 23:50
  575.  
  576. 举报 |
  577.  
  578. zqtjingzi
  579. 小吧主
  580. 12
  581.  
  582. 说明3：descfunc的取值范围及属性描述方式：
  583. value为属性的值，string1为此属性本身对应的字符串，string2为descstr2中对应的字符串。
  584. func = 1 —— +[value] [string1]
  585. func = 2 —— [value]% [string1]
  586. func = 3 —— [value] [string1]
  587. func = 4 —— +[value]% [string1]
  588. func = 5 —— [value*100/128]% [string1]
  589. func = 6 —— +[value] [string1] [string2]
  590. func = 7 —— [value]% [string1] [string2]
  591. func = 8 —— +[value]% [string1] [string2]
  592. func = 9 —— [value] [string1] [string2]
  593. func = 10—— [value*100/128]% [string1] [string2]
  594. func = 11—— 回复装备耐久度 1 于 [100/value] 秒内
  595. func = 12—— +[value] [string1]
  596. func = 13—— +[value] [某一职业] 技能等级
  597. func = 14—— +[value] [某一系] 系技能
  598. func = 15—— [当某一事件发生时有] [chance]% 机会施展等级 [技能等级] [技能名]
  599. func = 16—— 赋予等级 [value] [灵气名] 灵气
  600. func = 17—— [value] [string1] "(Increases near" [time] ")"
  601. func = 18—— [value]% [string1] "(Increases near" [time] ")"
  602. func = 20—— [value * -1]% [string1]
  603. func = 21—— [value * -1] [string1]
  604. func = 22—— [value]% [string1] [montype]
  605. func = 23—— [value]% [string1] [monster]
  606. func = 24—— 等级 [技能等级] ([剩余聚气数/总聚气数] 聚气 )
  607. func = 27—— +[value] [技能名] (限[某一职业]使用)
  608. func = 28—— +[value] [技能名]
  609.  
  610.  
  611. 回复
  612.  
  613. 9楼
  614. 2011-09-20 23:50
  615.  
  616. 举报 |
  617.  
  618. zqtjingzi
  619. 小吧主
  620. 12
  621.  
  622. 特殊说明：此文件大量参考了某前辈的帖子，忘了叫什么了，先致歉再致敬
  623.  
  624.  
  625. 回复
  626.  
  627. 10楼
  628. 2011-09-20 23:50
  629.  
  630. 举报 |
  631.  
  632. zqtjingzi
  633. 小吧主
  634. 12
  635.  
  636. 完毕。
  637. 如果有错误请指出。
  638. 祝各位游戏愉快。
  639.  
  640. 7楼有个小错误。
  641. 有两行op = 4，第一个没错，第二个op = 4应该是op = 5。
  642. 应该很容易看出来吧，不过还是提醒一下的好。
  643. */
  644.  
  645. typedef struct
  646. {
  647. unsigned int vID;
  648.  
  649. #if 1
  650. unsigned char vCombinedBits1;
  651. unsigned char vCombinedBits2;
  652. #else
  653. unsigned char iPadding1_1 : 3;
  654. unsigned char vdirect : 1;
  655.  
  656. unsigned char vitemspecific : 1;
  657. unsigned char vdamagerelated : 1;
  658. unsigned char vSigned : 1;
  659. unsigned char vSendmyspOther : 1;
  660.  
  661. unsigned char iPading1 : 1;
  662. unsigned char iPading1_1 : 1;
  663. unsigned char vCSvSigned : 1;
  664. unsigned char vSaved : 1;
  665.  
  666. unsigned char vfCallback : 1;
  667. unsigned char vfMin : 1;
  668. unsigned char vUpdateAnimRate : 1;
  669. unsigned char iPadding1_2 : 1;
  670. #endif
  671.  
  672. unsigned char iPadding1[2];
  673.  
  674. unsigned char vSendmyspBits;
  675. unsigned char vSendmyspParammyspBits;
  676. unsigned char vCSvBits;
  677. unsigned char vCSvParam;
  678.  
  679. unsigned int vDivide;
  680. int vMultiply;
  681. unsigned int vAdd;
  682.  
  683. unsigned char vValShift;
  684. unsigned char vSavemyspBits;
  685. unsigned char v1mypoint09mysubSavemyspBits;
  686. unsigned char bUnKnown;
  687.  
  688. int vSavemyspAdd;
  689.  
  690. int v1mypoint09mysubSavemyspAdd;
  691.  
  692. unsigned int vSavemyspParammyspBits;
  693.  
  694. unsigned int iPadding10;
  695. unsigned int vMinAccr;
  696.  
  697. unsigned char vEncode;
  698. unsigned char bUnKnown2;
  699. unsigned short vmaxstat; //引用自身
  700.  
  701. unsigned short vdescpriority;
  702. unsigned char vdescfunc;
  703. unsigned char vdescval;
  704.  
  705. unsigned short vdescstrpos; //strings
  706. unsigned short vdescstrneg; //strings
  707.  
  708. unsigned short vdescstr2; //strings
  709. unsigned short vdgrp;
  710.  
  711. unsigned char vdgrpfunc;
  712. unsigned char vdgrpval;
  713. unsigned short vdgrpstrpos; //strings
  714.  
  715. unsigned short vdgrpstrneg; //strings
  716. unsigned short vdgrpstr2; //strings
  717.  
  718. unsigned short vitemevent1; //events
  719. unsigned short vitemevent2; //events
  720.  
  721. unsigned short vitemeventfunc1;
  722. unsigned short vitemeventfunc2;
  723.  
  724. unsigned int vkeepzero;
  725.  
  726. unsigned char vop;
  727. unsigned char vopmyspparam;
  728. unsigned short vopmyspbase; //引用自身
  729.  
  730. unsigned short vopmyspstat1; //引用自身
  731. unsigned short vopmyspstat2; //引用自身
  732.  
  733. unsigned short vopmyspstat3; //引用自身
  734. unsigned short iPadding23;
  735.  
  736. unsigned int iPadding24;
  737. unsigned int iPadding25;
  738. unsigned int iPadding26;
  739. unsigned int iPadding27;
  740. unsigned int iPadding28;
  741. unsigned int iPadding29;
  742.  
  743. unsigned int iPadding30;
  744. unsigned int iPadding31;
  745. unsigned int iPadding32;
  746. unsigned int iPadding33;
  747. unsigned int iPadding34;
  748. unsigned int iPadding35;
  749. unsigned int iPadding36;
  750. unsigned int iPadding37;
  751. unsigned int iPadding38;
  752. unsigned int iPadding39;
  753.  
  754. unsigned int iPadding40;
  755. unsigned int iPadding41;
  756. unsigned int iPadding42;
  757. unsigned int iPadding43;
  758. unsigned int iPadding44;
  759. unsigned int iPadding45;
  760. unsigned int iPadding46;
  761. unsigned int iPadding47;
  762. unsigned int iPadding48;
  763. unsigned int iPadding49;
  764.  
  765. unsigned int iPadding50;
  766. unsigned int iPadding51;
  767. unsigned int iPadding52;
  768. unsigned int iPadding53;
  769. unsigned int iPadding54;
  770. unsigned int iPadding55;
  771. unsigned int iPadding56;
  772. unsigned int iPadding57;
  773. unsigned int iPadding58;
  774. unsigned int iPadding59;
  775.  
  776. unsigned int iPadding60;
  777. unsigned int iPadding61;
  778. unsigned int iPadding62;
  779. unsigned int iPadding63;
  780. unsigned int iPadding64;
  781. unsigned int iPadding65;
  782. unsigned int iPadding66;
  783. unsigned int iPadding67;
  784. unsigned int iPadding68;
  785. unsigned int iPadding69;
  786.  
  787. unsigned int iPadding70;
  788. unsigned int iPadding71;
  789. unsigned int iPadding72;
  790. unsigned int iPadding73;
  791. unsigned int iPadding74;
  792. unsigned int iPadding75;
  793. unsigned int iPadding76;
  794. unsigned int iPadding77;
  795. unsigned int iPadding78;
  796. unsigned int iPadding79;
  797.  
  798. unsigned int vstuff;
  799. } ST_LINE_INFO;
  800.  
  801. typedef struct
  802. {
  803. char vStat[64];
  804. } ST_ITEM_STATES;
  805.  
  806. static char *m_apcInternalProcess[] =
  807. {
  808. "Stat",
  809. "*eol",
  810. NULL,
  811. };
  812.  
  813. static unsigned int m_iItemStatesCount = 0;
  814. static ST_ITEM_STATES *m_astItemStates = NULL;
  815.  
  816. MODULE_SETLINES_FUNC(FILE_PREFIX, m_astItemStates, ST_ITEM_STATES);
  817.  
  818. static int ItemStatCost_FieldProc_Pre(void *pvLineInfo, char *acKey, unsigned int iLineNo, char *pcTemplate, char *acOutput)
  819. {
  820. ST_LINE_INFO *pstLineInfo = pvLineInfo;
  821.  
  822. if ( !strcmp(acKey, "Stat") )
  823. {
  824. #ifdef USE_TEMPLATE
  825. if ( 0 != pcTemplate[0] )
  826. {
  827. strcpy(acOutput, pcTemplate);
  828. }
  829. else
  830. #endif
  831. {
  832. sprintf(acOutput, "%s%u", NAME_PREFIX, pstLineInfo->vID);
  833. }
  834.  
  835. strncpy(m_astItemStates[m_iItemStatesCount].vStat, acOutput, sizeof(m_astItemStates[m_iItemStatesCount].vStat));
  836. String_Trim(m_astItemStates[m_iItemStatesCount].vStat);
  837. m_iItemStatesCount++;
  838. return 1;
  839. }
  840. else if ( !strcmp(acKey, "*eol") )
  841. {
  842. acOutput[0] = '0';
  843. acOutput[1] = 0;
  844.  
  845. return 1;
  846. }
  847.  
  848. return 0;
  849. }
  850.  
  851. static int ItemStatCost_FieldProc(void *pvLineInfo, char *acKey, unsigned int iLineNo, char *pcTemplate, char *acOutput)
  852. {
  853. ST_LINE_INFO *pstLineInfo = pvLineInfo;
  854.  
  855. if ( !strcmp(acKey, "Stat") )
  856. {
  857. #ifdef USE_TEMPLATE
  858. if ( 0 != pcTemplate[0] )
  859. {
  860. strcpy(acOutput, pcTemplate);
  861. }
  862. else
  863. #endif
  864. {
  865. sprintf(acOutput, "%s%u", NAME_PREFIX, pstLineInfo->vID);
  866. }
  867.  
  868. return 1;
  869. }
  870.  
  871. return 0;
  872. }
  873.  
  874. static int ItemStatCost_ConvertValue(void *pvLineInfo, char *acKey, char *pcTemplate, char *acOutput)
  875. {
  876. ST_LINE_INFO *pstLineInfo = pvLineInfo;
  877. char *pcResult;
  878. int result = 0;
  879.  
  880. if ( !strcmp(acKey, "maxstat") )
  881. {
  882. pcResult = ItemStatCost_GetStateName(pstLineInfo->vmaxstat);
  883. if ( pcResult )
  884. {
  885. strcpy(acOutput, pcResult);
  886. }
  887. else
  888. {
  889. acOutput[0] = 0;
  890. }
  891. result = 1;
  892. }
  893. else if ( !strcmp(acKey, "descstrpos") )
  894. {
  895. pcResult = String_FindString(pstLineInfo->vdescstrpos, "dummy");
  896. if ( pcResult )
  897. {
  898. strcpy(acOutput, pcResult);
  899. }
  900. else
  901. {
  902. acOutput[0] = 0;
  903. }
  904. result = 1;
  905. }
  906. else if ( !strcmp(acKey, "descstrneg") )
  907. {
  908. pcResult = String_FindString(pstLineInfo->vdescstrneg, "dummy");
  909. if ( pcResult )
  910. {
  911. strcpy(acOutput, pcResult);
  912. }
  913. else
  914. {
  915. acOutput[0] = 0;
  916. }
  917. result = 1;
  918. }
  919. else if ( !strcmp(acKey, "descstr2") )
  920. {
  921. pcResult = String_FindString(pstLineInfo->vdescstr2, "dummy");
  922. if ( pcResult )
  923. {
  924. strcpy(acOutput, pcResult);
  925. }
  926. else
  927. {
  928. acOutput[0] = 0;
  929. }
  930. result = 1;
  931. }
  932. else if ( !strcmp(acKey, "dgrpstrpos") )
  933. {
  934. pcResult = String_FindString(pstLineInfo->vdgrpstrpos, "dummy");
  935. if ( pcResult )
  936. {
  937. strcpy(acOutput, pcResult);
  938. }
  939. else
  940. {
  941. acOutput[0] = 0;
  942. }
  943. result = 1;
  944. }
  945. else if ( !strcmp(acKey, "dgrpstrneg") )
  946. {
  947. pcResult = String_FindString(pstLineInfo->vdgrpstrneg, "dummy");
  948. if ( pcResult )
  949. {
  950. strcpy(acOutput, pcResult);
  951. }
  952. else
  953. {
  954. acOutput[0] = 0;
  955. }
  956. result = 1;
  957. }
  958. else if ( !strcmp(acKey, "dgrpstr2") )
  959. {
  960. pcResult = String_FindString(pstLineInfo->vdgrpstr2, "dummy");
  961. if ( pcResult )
  962. {
  963. strcpy(acOutput, pcResult);
  964. }
  965. else
  966. {
  967. acOutput[0] = 0;
  968. }
  969. result = 1;
  970. }
  971. else if ( !strcmp(acKey, "itemevent1") )
  972. {
  973. pcResult = Events_GetEventName(pstLineInfo->vitemevent1);
  974. if ( pcResult )
  975. {
  976. strcpy(acOutput, pcResult);
  977. }
  978. else
  979. {
  980. acOutput[0] = 0;
  981. }
  982. result = 1;
  983. }
  984. else if ( !strcmp(acKey, "itemevent2") )
  985. {
  986. pcResult = Events_GetEventName(pstLineInfo->vitemevent2);
  987. if ( pcResult )
  988. {
  989. strcpy(acOutput, pcResult);
  990. }
  991. else
  992. {
  993. acOutput[0] = 0;
  994. }
  995. result = 1;
  996. }
  997. else if ( !strcmp(acKey, "op stat1") )
  998. {
  999. pcResult = ItemStatCost_GetStateName(pstLineInfo->vopmyspstat1);
  1000. if ( pcResult )
  1001. {
  1002. strcpy(acOutput, pcResult);
  1003. }
  1004. else
  1005. {
  1006. acOutput[0] = 0;
  1007. }
  1008. result = 1;
  1009. }
  1010. else if ( !strcmp(acKey, "op stat2") )
  1011. {
  1012. pcResult = ItemStatCost_GetStateName(pstLineInfo->vopmyspstat2);
  1013. if ( pcResult )
  1014. {
  1015. strcpy(acOutput, pcResult);
  1016. }
  1017. else
  1018. {
  1019. acOutput[0] = 0;
  1020. }
  1021. result = 1;
  1022. }
  1023. else if ( !strcmp(acKey, "op stat3") )
  1024. {
  1025. pcResult = ItemStatCost_GetStateName(pstLineInfo->vopmyspstat3);
  1026. if ( pcResult )
  1027. {
  1028. strcpy(acOutput, pcResult);
  1029. }
  1030. else
  1031. {
  1032. acOutput[0] = 0;
  1033. }
  1034. result = 1;
  1035. }
  1036. else if ( !strcmp(acKey, "op base") )
  1037. {
  1038. pcResult = ItemStatCost_GetStateName(pstLineInfo->vopmyspbase);
  1039. if ( pcResult )
  1040. {
  1041. strcpy(acOutput, pcResult);
  1042. }
  1043. else
  1044. {
  1045. acOutput[0] = 0;
  1046. }
  1047. result = 1;
  1048. }
  1049.  
  1050. return result;
  1051. }
  1052.  
  1053. static int ItemStatCost_BitProc(void *pvLineInfo, char *acKey, char *acOutput)
  1054. {
  1055. ST_LINE_INFO *pstLineInfo = pvLineInfo;
  1056. int result = 0;
  1057.  
  1058. if ( !strcmp(acKey, "CSvSigned") )
  1059. {
  1060. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits2 & (1 << 5)) != 0);
  1061. result = 1;
  1062. }
  1063. else if ( !strcmp(acKey, "Saved") )
  1064. {
  1065. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits2 & (1 << 4)) != 0);
  1066. result = 1;
  1067. }
  1068. else if ( !strcmp(acKey, "fCallback") )
  1069. {
  1070. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits2 & (1 << 3)) != 0);
  1071. result = 1;
  1072. }
  1073. else if ( !strcmp(acKey, "fMin") )
  1074. {
  1075. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits2 & (1 << 2)) != 0);
  1076. result = 1;
  1077. }
  1078. else if ( !strcmp(acKey, "UpdateAnimRate") )
  1079. {
  1080. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits2 & (1 << 1)) != 0);
  1081. result = 1;
  1082. }
  1083. else if ( !strcmp(acKey, "direct") )
  1084. {
  1085. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits1 & (1 << 4)) != 0);
  1086. result = 1;
  1087. }
  1088. else if ( !strcmp(acKey, "itemspecific") )
  1089. {
  1090. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits1 & (1 << 3)) != 0);
  1091. result = 1;
  1092. }
  1093. else if ( !strcmp(acKey, "damagerelated") )
  1094. {
  1095. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits1 & (1 << 2)) != 0);
  1096. result = 1;
  1097. }
  1098. else if ( !strcmp(acKey, "Signed") )
  1099. {
  1100. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits1 & (1 << 1)) != 0);
  1101. result = 1;
  1102. }
  1103. else if ( !strcmp(acKey, "Send Other") )
  1104. {
  1105. sprintf(acOutput, "%d", (pstLineInfo->vCombinedBits1 & 1) != 0);
  1106. result = 1;
  1107. }
  1108.  
  1109. return result;
  1110. }
  1111.  
  1112. static char *ItemStatCost_GetKey(void *pvLineInfo, char *pcKey, unsigned int *iKeyLen)
  1113. {
  1114. ST_LINE_INFO *pstLineInfo = pvLineInfo;
  1115.  
  1116. sprintf(pcKey, "%u", pstLineInfo->vID);
  1117. *iKeyLen = (unsigned int)strlen(pcKey);
  1118.  
  1119. return pcKey;
  1120. }
  1121.  
  1122. int process_itemstatcost(char *acTemplatePath, char *acBinPath, char *acTxtPath, ENUM_MODULE_PHASE enPhase)
  1123. {
  1124. ST_LINE_INFO *pstLineInfo = (ST_LINE_INFO *)m_acLineInfoBuf;
  1125.  
  1126. ST_VALUE_MAP *pstValueMap = (ST_VALUE_MAP *)m_acValueMapBuf;
  1127.  
  1128. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, ID, UINT);
  1129.  
  1130. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, CSvSigned, CombinedBits2, BIT);
  1131. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, Saved, CombinedBits2, BIT);
  1132.  
  1133. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, fCallback, CombinedBits2, BIT);
  1134. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, fMin, CombinedBits2, BIT);
  1135. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, UpdateAnimRate, CombinedBits2, BIT);
  1136. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, direct, CombinedBits1, BIT);
  1137.  
  1138. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, itemspecific, CombinedBits1, BIT);
  1139. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, damagerelated, CombinedBits1, BIT);
  1140. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, Signed, CombinedBits1, BIT);
  1141. VALUE_MAP_DEFINE_2(pstValueMap, pstLineInfo, SendmyspOther, CombinedBits1, BIT);
  1142.  
  1143. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, SendmyspBits, UCHAR);
  1144. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, SendmyspParammyspBits, UCHAR);
  1145. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, CSvBits, UCHAR);
  1146. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, CSvParam, UCHAR);
  1147.  
  1148. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, Divide, UINT);
  1149. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, Multiply, INT);
  1150. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, Add, UINT);
  1151.  
  1152. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, ValShift, UCHAR);
  1153. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, SavemyspBits, UCHAR);
  1154. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, 1mypoint09mysubSavemyspBits, UCHAR);
  1155.  
  1156. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, SavemyspAdd, INT);
  1157.  
  1158. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, 1mypoint09mysubSavemyspAdd, INT);
  1159.  
  1160. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, SavemyspParammyspBits, UINT);
  1161.  
  1162. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, MinAccr, UINT);
  1163.  
  1164. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, Encode, UCHAR);
  1165. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, maxstat, USHORT);
  1166.  
  1167. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descpriority, USHORT);
  1168. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descfunc, UCHAR);
  1169. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descval, UCHAR);
  1170.  
  1171. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descstrpos, USHORT);
  1172. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descstrneg, USHORT);
  1173.  
  1174. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, descstr2, USHORT);
  1175. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrp, USHORT);
  1176.  
  1177. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrpfunc, UCHAR);
  1178. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrpval, UCHAR);
  1179. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrpstrpos, USHORT);
  1180.  
  1181. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrpstrneg, USHORT);
  1182. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, dgrpstr2, USHORT);
  1183.  
  1184. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, itemevent1, USHORT);
  1185. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, itemevent2, USHORT);
  1186.  
  1187. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, itemeventfunc1, USHORT);
  1188. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, itemeventfunc2, USHORT);
  1189.  
  1190. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, keepzero, UINT);
  1191.  
  1192. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, op, UCHAR);
  1193. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, opmyspparam, UCHAR);
  1194. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, opmyspbase, USHORT);
  1195.  
  1196. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, opmyspstat1, USHORT);
  1197. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, opmyspstat2, USHORT);
  1198.  
  1199. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, opmyspstat3, USHORT);
  1200. VALUE_MAP_DEFINE(pstValueMap, pstLineInfo, stuff, UINT);
  1201.  
  1202. switch ( enPhase )
  1203. {
  1204. case EN_MODULE_SELF_DEPEND:
  1205. m_iItemStatesCount = 0;
  1206.  
  1207. //m_stCallback.pfnGetKey = ItemStatCost_GetKey;
  1208. m_stCallback.pfnFieldProc = ItemStatCost_FieldProc_Pre;
  1209. m_stCallback.pfnSetLines = SETLINES_FUNC_NAME(FILE_PREFIX);
  1210. m_stCallback.pfnFinished = FINISHED_FUNC_NAME(FILE_PREFIX);
  1211. m_stCallback.ppcKeyInternalProcess = m_apcInternalProcess;
  1212.  
  1213. return process_file(acTemplatePath, acBinPath, acTxtPath, FILE_PREFIX, pstLineInfo, sizeof(*pstLineInfo),
  1214. pstValueMap, Global_GetValueMapCount(), &m_stCallback);
  1215. break;
  1216.  
  1217. case EN_MODULE_OTHER_DEPEND:
  1218. MODULE_DEPEND_CALL(itemstatcost, acTemplatePath, acBinPath, acTxtPath);
  1219. MODULE_DEPEND_CALL(string, acTemplatePath, acBinPath, acTxtPath);
  1220. MODULE_DEPEND_CALL(events, acTemplatePath, acBinPath, acTxtPath);
  1221. break;
  1222.  
  1223. case EN_MODULE_RESERVED_1:
  1224. case EN_MODULE_RESERVED_2:
  1225. break;
  1226.  
  1227. case EN_MODULE_INIT:
  1228. //m_stCallback.pfnGetKey = ItemStatCost_GetKey;
  1229. m_stCallback.pfnConvertValue = ItemStatCost_ConvertValue;
  1230. m_stCallback.pfnFieldProc = ItemStatCost_FieldProc;
  1231. m_stCallback.pfnBitProc = ItemStatCost_BitProc;
  1232. m_stCallback.ppcKeyInternalProcess = m_apcInternalProcess;
  1233.  
  1234. return process_file(acTemplatePath, acBinPath, acTxtPath, FILE_PREFIX, pstLineInfo, sizeof(*pstLineInfo),
  1235. pstValueMap, Global_GetValueMapCount(), &m_stCallback);
  1236. break;
  1237.  
  1238. default:
  1239. break;
  1240. }
  1241.  
  1242. return 1;
  1243. }
  1244.  
  1245. char *ItemStatCost_GetStateName(unsigned int id)
  1246. {
  1247. if ( id >= m_iItemStatesCount )
  1248. {
  1249. return NULL;
  1250. }
  1251.  
  1252. return m_astItemStates[id].vStat;
  1253. }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!