You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I think it would be useful to skip checking whether a nickname or serial is already in use in DEBUG mode. The issue is that during testing or debugging crashes, when MTA crashes, the player is still considered to be on the server. Sometimes the player count shows 0, sometimes 1, but in reality, the server is empty. It's very frustrating to have to kick a ghost player on a local server after every crash just to be able to join. Until now, it was somewhat bearable because it didn't always happen, but after adding serial checks, it has become extremely annoying
Describe the solution you'd like
I'd like to work on crashes faster without having to kick the ghost player after every crash
Describe alternatives you've considered
No response
Additional context
No response
Security Policy
I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I think it would be useful to skip checking whether a nickname or serial is already in use in DEBUG mode. The issue is that during testing or debugging crashes, when MTA crashes, the player is still considered to be on the server. Sometimes the player count shows 0, sometimes 1, but in reality, the server is empty. It's very frustrating to have to kick a ghost player on a local server after every crash just to be able to join. Until now, it was somewhat bearable because it didn't always happen, but after adding serial checks, it has become extremely annoying
Describe the solution you'd like
I'd like to work on crashes faster without having to kick the ghost player after every crash
Describe alternatives you've considered
No response
Additional context
No response
Security Policy
The text was updated successfully, but these errors were encountered: