Exhausted execution time is glitched

In my game loop script, this line bugs in certain servers:

game.StarterPlayer.StarterCharacter:Destroy()

The StarterCharacter IS there, but I believe it’s something else. I might have a backdoor on my game from a web hook I used. I did disable HTTP requests, but it still happens.

How does it bug? And if the script exhausts then it means you aren’t putting any “waiting” in the loop, right? You know that deleting the model from StarterPlayer won’t do anything to players until they respawn, right?

1 Like

That line of code wouldn’t even cause an exhaustion error unless it was wrapped inside of an unyielding loop.

It just landed on a task.wait() for exaustion -__-