[Kyle]

Quote:

Originally Posted by DiverseCardinal I'm not the OP, but his explanation was clear. If someone disconnects while modding a vehicle and then reconnects, the menu for modding will have never formally been closed and thus remain open. Since that menu is open, Kyle's gamemode considers the person to be modding their vehicle; however, that person isn't in the proper interior and so the gamemode believes that the person is cheating. To the OP: Perhaps one hack-y solution would be to treat the OnPlayerDisconnect callback like a destructor would be used in several OOP languages. You could try to close all menus and/or dialogs which were left open by the player, so that (s)he won't be banned upon immediate connection. Another approach would be to consider whether or not the player has spawned yet, and if (s)he hasn't then the script won't ban him (or her).

Tried your first idea before, doesn't fix it.

Also, as for the second, they'll spawn, enter a vehicle, and use the menu to mod it. They don't get banned instantly, it's when they use the menu.