Excalibur reverted back to Lame D'Argent after logging back in

King

Member
Gender
Male
Guildcard
42021999
Not sure if it's an actual bug or it's something I did, but I'm reporting just in case.

I logged in to the game just now, and my Excalbur reverted back to the Lame. I unsealed the weapon yesterday. The kill counter now is currently at 9875. When I unsealed it, it was a little over 10k.

Is there a bug, was there a rollback, or is there something I can do to prevent this from happening again? It's a pain having to unseal certain items.
 
Most likely desync with server, they had mismatching counts and according to the server, you never actually reached 10,000.

It won't happen again most likely.
 
Whenever you're finished getting your kills, it's a good idea to change blocks so your inventory can sync with the server. Kill counts and readers can be wonky sometimes. This probably happened because of that.

Probably.
 
I unsealed the weapon again, logged out, logged back in, and the weapon reverted again, but now the counter is at 9929.

This is annoying. Probably won't be using any other sealed items for this reason. I tried changing blocks, but there was no change to the counter.

EDIT: OK, I think I figured out the issue. There was a mismatch between the value from the /killcount command and the counter in the item reader tool. I'm thinking the problem is the item reader, because once I hit 10k using /killcount, the problem was solved. XII was correct.
 
Last edited:
I'm thinking the problem is the item reader
The item readers read the game memory, if the game itself is not synchronized with the server, there is not much we can do.
The problem is the game itself (which is obvious since you unsealed the thing in game but then it went back to Lame D' ... the reader didn't do that ¯\_ツ_/¯).
 
I unsealed the weapon again, logged out, logged back in, and the weapon reverted again, but now the counter is at 9929.

This is annoying. Probably won't be using any other sealed items for this reason. I tried changing blocks, but there was no change to the counter.

EDIT: OK, I think I figured out the issue. There was a mismatch between the value from the /killcount command and the counter in the item reader tool. I'm thinking the problem is the item reader, because once I hit 10k using /killcount, the problem was solved. XII was correct.

I don't know how you managed to get item reader to have a higher KC, thats some crazy desync going on but yeh always rely on /killcount. If you stand with inventory reader open as your unsealing and spam /killcount now and then (it's what I do as I have kc command shortcutted) you will notice the numbers are slower in item reader than the banner, at least tha't's what happens with me. But if I change blocks/restart client/open+close reader it reverts to the same (afaik).
 
Back
Top