resistibility data incorrect in server
Posted: Sat Aug 16, 2008 10:52 am
I know this hasn't been ironed out, so this is just to log the defect.
When you set the `spells`.`resistibility` value, it is supposed to be represented in the client as a "Hit Bonus" (thank you Scatman for clarifying that). Currently there are a couple things wrong with setting this value.
1) In the database, the float is `unsigned`, so that has to change or you cannot put 0.25 for 25%, nor negative values... renders the float unfloaty.
2) Setting "25" for 25% currently shows up in the client (oddly) as "Hit Bonus: 2,400% Easier". This is how we found out that the datatype is incorrect.
3) Changing the float to `signed` allowed us to try "0.25" as a value, but it winds up being seen in the server now as "Hit Bonus: 75% Harder".
4) Opposite that, we tried a "-0.25" value and the Hit Bonus does not even appear in the client. Is the server still converting it to an unsigned or round() value maybe?
I'd like to look into this sooner than later, since we are right now going through and fixing spell data - and to have to go back through 4000 entries does not sound appealing to me.
Let me know if there's anything we can do to expedite this fix, if any. Maybe we're using the field incorrectly?
Thanks
When you set the `spells`.`resistibility` value, it is supposed to be represented in the client as a "Hit Bonus" (thank you Scatman for clarifying that). Currently there are a couple things wrong with setting this value.
1) In the database, the float is `unsigned`, so that has to change or you cannot put 0.25 for 25%, nor negative values... renders the float unfloaty.
2) Setting "25" for 25% currently shows up in the client (oddly) as "Hit Bonus: 2,400% Easier". This is how we found out that the datatype is incorrect.
3) Changing the float to `signed` allowed us to try "0.25" as a value, but it winds up being seen in the server now as "Hit Bonus: 75% Harder".
4) Opposite that, we tried a "-0.25" value and the Hit Bonus does not even appear in the client. Is the server still converting it to an unsigned or round() value maybe?
I'd like to look into this sooner than later, since we are right now going through and fixing spell data - and to have to go back through 4000 entries does not sound appealing to me.
Let me know if there's anything we can do to expedite this fix, if any. Maybe we're using the field incorrectly?Thanks