I remembered this thread and decided to look into it again because I've fixed most of the bugs in the port. Turns out there *was* an actual reason for it! It transmits the value without a sign bit, so if you try to go under 0 tickets, it overflows backwards. The solution was to make hitting 0 tickets losing and locking spawning at 1 ticket, but obviously that doesn't seem right, so the solution to *that* was to subtract one ticket from the display. Or you know, make it signed so it can be -1. That works too. Anyways, should be fixed.
I forgot about this one. It'll take some extra testing because it might have an issue or two near the very end of ticket usage, but we'll find out, I guess.
Unless you've yet to put it on the public release, it still doesn't work that way - my map has x-1 tickets displayed.