If a host sets any variable such as respawnitemtime or startinglives to a number higher than the maximum possible value, say startinglives 100 for example, and then tries to display the value, what he sees is that it is set to MAX.
But when other players join his server, the value on their end...
If one player in splitscreen coop mode gets a game over, then the level music doesn't start again until the other player finishes the level.
I think that this is what the second bug in this topic meant.
If the host or admin in a server types the kick reason as "Consistency failure" when kicking someone, then the person who was kicked can't tell that the host or admin kicked them and instead might think that they c-failed. I'm not sure if this counts as a bug or not.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.