Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #002211

  • 0 - None Assigned

  • Duplicate

Issue Confirmations

  • Yes (0)No (0)
Photo

skill tree saving cleanup

Posted by Hercules Bot on 11 September 2008 - 08:44 AM

Originally posted by theultramage
http://www.eathena.w...er&showbug=2211

I need to get rid of this:
CODE
    //FIXME: is this neccessary? [ultramage]
    for(i=0;i<MAX_SKILL;i++)
        if ((p->skill[i].lv != 0) && (p->skill[i].id == 0))
            p->skill[i].id = i; // Fix skill tree
this thing is in the sql charserver saving code. It apparently re-enables skills that were 'hidden' by the mapserver (hidden but not forgotten). The trick here is that skill[i].id == i, therefore recovery is possible.

I traced this change to r700 and r764. But why is this sort of adjustment even done on the charserver? Also, I am unable to find the equivalent in the TXT charserver code.

Perhaps this thing has been superceded by some followup fix and left forgotten? I'd suggest adding a debug message in there, and doing a few tests to see if the code indeed makes a difference when it's there.

Originally posted by Ind
duplicate of [bug=3380]