Yes this is a known bug thanks to latest update. We are still gathering details on it so it can be fixed. Someone has found a workaround, somewhere. I'll make sure info gets posted here.

It's caused by the previous game update.

Did you try joining Redstone or Beta? That bug is fixed on there. (for the most part)

Sorry about that. I was not aware of the issue until this thread.

As a workaround from the server side, if running SourceMod, try setting:

I'll take a look to see why the client would be spamming so many commands at once while commanding, and increasing the default until a proper fix is available.

Redstone is immune to this issue. It runs a higher tick-rate so players have lower pings. The i7-4770 proccessor runs at 100% performance (with an 80 tick) when the player count is 32.

The higher tick-rate allow more commands, so players don't get disconnected. Redstone fixed this issue before it could be reported to the game developer. It's an amazing server!

Many people join the Redstone steam group, to receive in-game rewards on the server!
https://steamhost.cn/steamcommunity_com/groups/RedstoneND

Originally posted by ᵡᴳḽᴰ::Vertex:

The higher tick-rate allow more commands, so players don't get disconnected.

That's not how it works.

Originally posted by psychonic:

Originally posted by ᵡᴳḽᴰ::Vertex:

The higher tick-rate allow more commands, so players don't get disconnected.

That's not how it works.

We tested disconnects on both 60 tick and 80 tick servers. The result was less disconnects.

This is a negative relationship from a chain reaction of events. A higher tick-rate indirectly causes players not to disconnect. It's like putting Band-Aid on a cut, so your finger stops leaking blood.

Originally posted by ᵡᴳḽᴰ::Vertex:

Redstone is immune to this issue. It runs a higher tick-rate so players have lower pings. The i7-4770 proccessor runs at 100% performance (with an 80 tick) when the player count is 32.

Wait a minute, weren't you saying changing the default tickrate is a bad thing to do? Psychonic even confirmed there are issues with it (mainly physics). https://steamhost.cn/steamcommunity_com/app/17710/discussions/0/3559414588262395798/

Originally posted by Rusher_go:

Originally posted by ᵡᴳḽᴰ::Vertex:

Redstone is immune to this issue. It runs a higher tick-rate so players have lower pings. The i7-4770 proccessor runs at 100% performance (with an 80 tick) when the player count is 32.

Wait a minute, weren't you saying changing the default tickrate is a bad thing to do? Psychonic even confirmed there are issues with it (mainly physics). https://steamhost.cn/steamcommunity_com/app/17710/discussions/0/3559414588262395798/

Psychonic released a game update and fixed these issues. Redstone tested and reported these issues to the game developer. And now the Nuclear Dawn community is better off!

Originally posted by ᵡᴳḽᴰ::Vertex:

Originally posted by Rusher_go:

Wait a minute, weren't you saying changing the default tickrate is a bad thing to do? Psychonic even confirmed there are issues with it (mainly physics). https://steamhost.cn/steamcommunity_com/app/17710/discussions/0/3559414588262395798/

Psychonic released a game update and fixed these issues. Redstone tested and reported these issues to the game developer. And now the Nuclear Dawn community is better off!

The issue wasn't fixed due to you personally reporting in one of your posts ♥♥♥♥-talking other servers (which also included some misinformation, like suggesting that tickrate was locked). The problems were already known, and the timing was coincidental.

The issue was fixed because it was a simple copy/paste after the same fix was released for Counter-Strike: Source a week or two prior to it in ND. (https://steamhost.cn/news/42271/)

Redstone stopped players from disconnecting before the game developer fixed the issue. And did not adjust the tick-rate, until the physics issues were fixed. This is not fake news.

When problems arise with the game, we will continue to report them and our solutions. It's difficult to provide 100% accurate information becuase the game code is closed source.

Originally posted by ᵡᴳḽᴰ::Vertex:

...stopped players from disconnecting before the game developer fixed the issue.

Originally posted by ᵡᴳḽᴰ::Vertex:

we will continue to report them.

You've contradicted yourself. The original poster was the first report of the issue visible to devs.

If you had wanted to help, you shouldn't have been part of the reason that anti-DoS features like that were needing to be added to the game.

Redstone does NOT use it's server hosting to launch DoS attacks against other servers. It is not our fault the game developer caused players to disconnect with an anti-DoS feature.

This is fake news. Words on the community hub do not launch DoS attacks. People do.

Righhht.... So, this has been addeessed as far as im concerned. i didnt feel like logging back into to childish banter on both sides. all i wanted was to be able to play a game, i dont care what side of the argument is correct, there was no need for an argument to begin with. I am fine with this thread being locked to prevent more comment.

It's fixed on Redstone. But I didn't see an update for the other servers.

Just leaving that here, for somebody special to reflect upon: ;-)
https://imgflip.com/i/2g8cjp