[sebbs]

hey Ace was wondering after looking through the commitments a bit

--d("next skill prio being set:"..tostring(skill.nskillprio))

- SkillMgr.SkillProfile[skill.prio].lastcast = Now()

+ SkillMgr.SkillProfile[tonumber(skill.prio)].lastcast = Now()

just wondering as to why it was changed to convert to number when the original way had it has just default with no conversion at all? Also talking about the 'SkillManager now saves skills to a "skills" table using persistence" commit on Feb 15th

Edit: Or is that just for when your debugging for console purposes?

Edit #2: And it's not that the abilities aren't firing something weird is just stopping moves from being used in there proper order. Like for sebbs 4 star all i have to do is copy rapid synth, delete it and re-add it paste move it back up to where it was and the profile works like it always has. So the bug is a weird one i'll tell you that. try and change one thing like enable disable see if that works.. save between changes

Edit #3: After checking a bit further it seems the problem is most likely within that huge chunk a bit further down that builds old profiles into new ones. I will test this theory by re-building one of sebbs profiles from scratch to see how it hold out with all the buff checking.

Edit #4: Also if it helps any the bot seems to be acting weird with profiles that lets say have '8 Basic Synthesis, great strides, basic touch... the list goes on' to accompany their respected jobs, since each one works with it's own ID but yet all have the same name. I'm saying this cause when i disable the one for the job that i'm on out of the many, it seems that another one will still set it off.
a new table that allows 1 skill to trigger that skill for all classes has been added. I am altering all my profiles now.