I am having a strange issue, my current match handler its writhen in Lua, so far so good, everything works out as expected, but when I increase the tickrate high enough (around 10 while we use it at 2 normally), the server suddenly stops after enough player interactions.
What can the issue be?
My first guess is that the tickrate its higher than what the server can handle (meaning that the server cant run the whole loop faster enough), but since there is no error on the console its hard to actually tell what is happening here.
On the server console I still register incoming messages and no error its presented on it, no warnings or anything at all.
Hello,
first of all, the server shouldn’t stop if the match loop cannot keep up with the tick rate: it should still process falling behind. So there is something else going on but we’d need to see the code, probably starting with the match loop itself. And since the server is registering incoming messages then the server isn’t really stopped - could it be the client that actually stops ?
@mharis
Found the bug. It was related to the empty checks template provided on the documentation.
The # operator in Lua only accounts for numerical keys on tables (the same way ipairs do) so it returns 0 when used with the provided template check on the documentation.
