1. ??

    player kick Flooding Protection
     
  2. Playrust.com

    It means that if a certain player uses several ticks at once, which would normally cause spam on a server, he will now be automatically kicked by Rust.
     
  3. what do you mean with ticks?
     
  4. Somewhat weird to explain, but it is similar to having a time-interval tick in which something gets done (that is a tick, but can probably mean other things as well). For example, a plugin such as BuildingOwners uses ticks to keep track owners, and update them every 5-10 minutes or so, or however the system works.

    -Post below explains better haha
     
    Last edited by a moderator: Jun 19, 2016
  5. A tick is just one full iteration where things get done.

    The server flooding protection is supposed to weaken DDoS attacks.
    Say the client is configured to send its position to the server every second.
    The server might have to do a lot of work when it receives position data, so a client could modify his game to send its position a lot more regularly, to spam the server.
    Flooding protection attempts to protect from this by simply ignoring packets sent too quickly.

    Keep in mind that the rate at which the server receives packets from clients is nondeterministic (e.g.: your ping spikes to 1s and back to 30ms - the first packet might take a route that's way longer than that of the second packet, meaning they might arrive shortly after each other).

    Assuming flooding protection is properly done (you never know ;)), a warning like this might be caused by someone trying to DDoS your server via client packet spam or by players that have ping spikes.
     
  6. Right so ive been getting this today and allot not often but a couple of hours and bam gets kicked for "Flooding Protection (1965)" (number changes everytime) i looked at the logs but nothing i do noticed that the server is running on 100% ram which is in my case 6gigs but theres only 3 people on lol

    i dont know if anyone else had this issue but its definitely after the latest update.

    Edit: Didnt know there was a post about it. Guess the search function isnt working correctly? but thanks adming for moving me here.

    And this happened as well Kicked: Flooding Protection (2665) just a different number now
     
    Last edited by a moderator: Jun 19, 2016
  7. Same thing happened today again and after we got kicked ( all of us ) the server went nutz and went into "OutOfMemoryException" and on the console its spitting out things for oxide?

    Code:
    OutOfMemoryException: Out of memory
      at (wrapper managed-to-native) object:__icall_wrapper_mono_array_new_specific (intptr,int)
      at System.Collections.Generic.Queue`1[Oxide.Core.Libraries.Timer+TimerInstance].SetCapacity (Int32 new_size) [0x00000] in <filename unknown>:0
      at System.Collections.Generic.Queue`1[Oxide.Core.Libraries.Timer+TimerInstance].Enqueue (Oxide.Core.Libraries.TimerInstance item) [0x00000] in <filename unknown>:0
      at Oxide.Core.Libraries.Timer+TimeSlot.GetExpired (Double now, System.Collections.Generic.Queue`1 queue) [0x00000] in <filename unknown>:0
      at Oxide.Core.Libraries.Timer.Update (Single delta) [0x00000] in <filename unknown>:0
      at Oxide.Core.OxideMod.OnFrame (Single delta) [0x00000] in <filename unknown>:0
      at Oxide.Ext.Unity.UnityScript.Update () [0x00000] in <filename unknown>:0 
    Screenshot
    [​IMG]

    still have no clue whats going on o_O
     
  8. You said: i looked at the logs but nothing i do noticed that the server is running on 100% ram which is in my case 6gigs but theres only 3 people on lol
    This isn't unlikely, even for smaller servers.
    The errors states the issue pretty clearly: "OutOfMemoryException: Out of memory"
    When all memory is used up as well as the swap partition then the server will crash, which is normal, because if it can't allocate memory then it can't operate properly.
    The server properly starts acting up when it starts allocating to the swap partition because of how slow that is.
     
  9. Strange thing is then it runs fine for about 6 hours and then poof kicks everyone for flooding protection and then the server goes to 100% ram this isnt normal at all o_O ill be testing this tomorrow with no plugins at all and see if it does the same thing.

    Edit: yes i know what out of memory states, i just added it, cause its normal to show the error log when you are having an issue. but that was the only thing the error log was spitting out.
     
  10. I was AFK with 1 other player in the server. Looking at RCON, the other player fired invalid projectiles (incendiary 5.56 rounds) several times, then both he and I were kicked for flooding protection. The PC hosting the server is running at 50% RAM usage (16/32 GB of RAM) and the server had only been up for about 1.5-2 hours.
     
  11. Is there any way to disable this???