• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

TFS 1.2 4294967295 maglevel bug?

Tbol

Well-Known Member
Joined
Apr 7, 2019
Messages
529
Reaction score
56
Hello,
found a weird issue that happens but its hard to replicate this bug it happens really rare so for some reason i have few characters that are stuck to 129 mag level and when they reach 130 they maglevel goes back too 129, so i though maybe its issue in vocation.xml but then i noticed that everything is fine they created exactly the same how other characters are made and other people with same characters dont have this issue, so its really weird. The only think i noticed is that they have same manaspent in dabatabase which is 4294967295
5e566eaddb0f9e0b5fc5260f4dd4def9.png

Any ideas how to fix it?
 
This is the maximum number of a unsigned 32 bit integer. Meaning it can't get any higher.
Changing the column to a 64 bit integer (bigint) will fix the problem. The max value of this is 18446744073709551615

This SO post is having the same issue

This query should do the trick.
ALTER TABLE table_name
MODIFY manaspent bigint unsigned;
 
This is the maximum number of a unsigned 32 bit integer. Meaning it can't get any higher.
Changing the column to a 64 bit integer (bigint) will fix the problem. The max value of this is 18446744073709551615

This SO post is having the same issue

This query should do the trick.
ALTER TABLE table_name
MODIFY manaspent bigint unsigned;
So you saying too change manespent column type from INT to a BIGNIT?
350cd200e4755adeacbdd74701657cad.png
 
Back
Top