A little explanation on this:
Code:
UPDATE dbo.user_character
SET wCon = 2000, nHP = 58000
WHERE (byPCClass = 0) AND (nHP >= 65000) AND (wCon >= 2000);
1: Your script works on AK only, because of (byPCClass = 0).
2: You don't need to set the HP, because it automaticly adjusts itself according to the constitution, so changing it manually can actually bug ut char.
3: In your script, you use more or equal in (wCon >= 2000), and if that is true, you set it to 2000 ,and basicly that matches the wCon >= 2000 again, so it is like a never-ending procedure, thus it causes lag.
So I would use this:
Code:
UPDATE dbo.user_character
SET wCon = 2000
WHERE (wCon > 2000);
Much simpler, and less bugged, I should say... Still, credits to you for the idea to fix the bug ^^