Problem description:
I'm not sure exactly what's wrong with the game right now, but for some reason whenever people relog or even disconnect, it doesn't fully remove their character from the world and leaves a clone behind when they fully logout or relog, and when they come back in the character is still loaded and teleports to their location.
The only resolution is a reboot to fix the person, and it continues even after that, even on a brand new character who hasn't done ANYTHING. Please help. I don't even know what part of the code could be affecting it, but it doesn't seem to be related to ownership or saving from what I can tell so far. Its currently happening to everyone playing the game.
ID:2950737
 Oct 31 2024, 12:34 am (Edited on Oct 31 2024, 12:54 am)
(See the best response by Ter13.)
|
|
Unfortunately, I haven't gotten any runtime errors to my knowledge. I've checked through logout and client/Del() a few times, I haven't seen anything really abnormal in it.
| |
Are you sure you are looking in the right place for your runtime errors? Most anime games on BYOND put their log outputs into a log file, and are unaware even when runtime errors are happening, because the runtime errors are being displayed somewhere the current maintainers aren't aware of.
And nobody can really help you with a problem with your code without taking a look at the relevant code that is causing the problem. | |
I...do not have a log output for my runtime errors, that I know of. I usually just use dream daemon to tell me stuff. How would I go about doing that?
| |
As for the Logout code, its literally just 2 lines, impossible to screw up. The client/Del() proc is more likely to be the issue, but I don't see anything in there as of right now that could cause this to happen I don't think. Its too long to post in here.
| |
I solved the issue, It was literally just because of ancient indentations in the code from when I first inherted it, I modernized them and it basically fixed itself. Thx Ter
| |
<3 I'm glad my fucking off into the ether to get barbecue chips gave you space to fix it.
| |
Check your mob/Logout() code for your various mob types, and your client/Del() code. If there are any runtime errors before you tell the mob to be deleted, but after those functions have started, that will be a cause of this problem, so any runtime errors related to mob/Logout() or client/Del() will be relevant as well.