Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

de-leveling with #setlevel doesn't remove skills you shouldn't have #4300

Closed
jdestefx opened this issue May 7, 2024 · 2 comments
Closed

Comments

@jdestefx
Copy link

jdestefx commented May 7, 2024

For example, if you level up to level 50 and max your skills, you will have the skill "Double Attack", but if you then #setlevel back down to level 5, then #set skill_all 1, then #set skill_all_max (to get your skill caps back where they should be), it will APPEAR as though you DON'T have "Double Attack" anymore, but if you go attack some mobs, you WILL double-attack - and the skill will be listed in character_skills.

FWIW I came up with this query to drop skills I shouldn't have:

7 = my char ID
3 = paladin (my char)

delete from character_skills where id=7 and character_skills.skill_id in (select skill_id from skill_caps where class_id = 3 and level = 5 and cap=0);

After running that, I logged out and back in (not sure if this was necessary?) and it appears to have solved the issue.

@jdestefx
Copy link
Author

jdestefx commented May 7, 2024

Another observation:
#level 50
#set skill_all_max
#level 5
#set skill_all 0

select * from character_skills where id = {yourCharID} ---> will show multiple skills that are still max value.

@Kinglykrab
Copy link
Contributor

Fixed by #4423.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants