Issue information

Issue ID
#4931
Status
Invalid
Severity
None
Started
Hercules Elf Bot
May 25, 2011 12:02
Last Post
Hercules Elf Bot
Mar 19, 2012 19:25
Confirmation
N/A

Hercules Elf Bot - May 25, 2011 12:02

Originally posted by [b]Kamikai[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=4931

i've the parameters like this on my battle_conf:

CODE
max_parameter: 99

max_baby_parameter: 80

max_third_parameter: 120

max_baby_third_paramater: 108

use_statpoint_table: no

use_renewal_statpoints: no


and whenever i set a stat higher than 100 and reset it, the reset command steals 5 status points for each 1 point above 100, say for example:
* an trans-3rd class lv 110 with no status point spent, has 1582 stpt
* then i set 1 attribute to 100 and then reset it (either npc/script or @streset), no problem, i got the 1582 stpt back
but...
* an trans-3rd class lv 110 with no status point spent, has 1582 stpt
* then i set 1 attribute to 101 and then reset it (either npc/script or @streset), i got only 1577 stpts back...5pts were stolen >_<'


how should i fix this? the problem is not only using the script command, but the atcommand as well...so i'm sure its core-related calculation, i just have no clue on how to fix this bug


EDIT: i just figured something else, normally when you're expending your stpts, i.e: from 1 until 11 attribute points you spend 2 stpoints for each attribute, from 11 until 21, 3 stpoints for each attribute, and so on...but when we talk about 90+...well, you spend 10 spts for each atribute from 81 until 91, and from 91 to 100 its 11 for each attribute, but from 100 until 105 its 16, then from 105 to 110 it's 20, so...each 5 lvs(when above 100) the cost for attributes inscreases in 4pts, but....i dont know how it works on the reset command though...

This post has been edited by Kamikai: May 25 2011, 05:23 AM

Hercules Elf Bot - Dec 8, 2011 16:41

Originally posted by [b]Ind[/b]
this does not belong to trunk, because "max_baby_third_paramater" is not a parameter here.