DCProtect

FireStorm78 submitted a new resource:

DC Protect - Prevents looting of players for a specified time after disconnecting or server start.

Read more about this resource...

 

FireStorm78 updated DC Protect with a new update entry:

1.0.2

 

What if they just DC from the server manualy while they are about to lose their loots etc?

 

The plugin would also NEED to read-out the disconnect reason to identify the disconnect-method on the client-side.
But that does not fully prevent abuse in those cases where people use a client-side network disconnect.
Therefore such a solution can never be fully abuse-protected

 

You can do machine learning BUT I don't think its worth it for such a small plugin.

 

It is a good plugin for "honorable" players but it is Rust...

 

Thanks for the feedback. This was written for a server I help maintain which is mostly PVE with a purge day once a week. We used to use PreventLooting but people were sleeping out in the open. We don't like protecting people from stupid since it is pvE so this plugin was born. It's not perfect but hopefully people can find use of it.

Like Fujikura said we could use the disconnect reason to be more specific but that doesn't stop people from yanking the proverbial network cable to accomplish the same thing.

But even if people try to abuse this to protect loots people just have to wait for the player to come back online or the timer to expire and shoot them in the head to get the loots. Either way they are going to die from the attack. It delays the looting not preventing it. So just set the delay to what makes sense for your server.

 

Is there anyway to retrofit this into making player unlootable after a teleport (spawn-in)? We have a public area people use with NTeleport's /town feature, and it'd be great to have people teleporting in not able to be looted until X amount of seconds so people dont camp the spawn and steal their stuff before they wake up. Currently I use ZoneManager, but with it being a nopvp and nodestroy area, people abuse it and sleep in the spawn bubble so they can't be killed or looted.

 

It's a good idea for a future enhancement. The way we handle it on our server is to have the TP point above the ground. Then players can't loot them and they drop in. We don't have fall damage so it doesn't matter how high the TP point is.

 

hello, @ FireStorm78 is it possible maybe add as config true/false protect players from damage for this time. we have sometimes players they are in diverent monuments and we use BotSpawn so they get sometimes DC and was killed by NPC so we want prevent this with this plugin if it possible.

 

Sure. Good idea. I'll work on that in a couple days. Just in the middle of a server migration.

 

FireStorm78 updated DC Protect with a new update entry:

1.0.3

 

Currently seeing the following if also using TruePVE:

Calling hook OnEntityTakeDamage resulted in a conflict between the following plugins: TruePVE - False (Boolean), DCProtect (True (Boolean))

Looking for a solution. I assumed the result of the hook would be a logical AND from multiple plugins.

 

FireStorm78 updated DC Protect with a new update entry:

1.0.4

 

Players getting killed by rockets while protected.

 

Works fine for me. Are you using TruePVE? Have you updated to the latest version with the fix?

 

yeah im using TruePVE in a mix with pvp nights. pve days. have latest version

 

Can you send me your TruePVE config and I'll see if I can reproduce. I can't reproduce on my server. Thanks.

 

I have testet with axe myself in pvp mode. That worked correct. got message and all - no damage no loot. I will so a rocket test later tonight before send you config pm. I cant kill them with rockets. So plugin works. Dont know how they got killed. Well, thanks for great plugin!

 

Thanks for the appreciation! A quick note to add on the added functionality however...It gives a small advantage to less than honorable players during PvP. If a player wants to avoid death they can DC and be protected. Raiders can wait for the timer to end to kill the player, BUT if they player is quick enough on the reconnect they can obtain temporary GOD like mode.

This is why setting the delay to as little as reasonably possible is key. The default 5 minutes may be too long for your server. It was based on the average time to restart a computer, load rust and connect to the server with no assets cached. If a player simply disconnects and reconnects inside the game the time to reconnect is much lower.

Set DC_DelayInSeconds to the average time it takes to reconnect that won't give too much of an advantage during a raid if abused. Also make it a rule of the server that abusing the DC Protection will result in a ban. Since there are logs you can see this behavior quite easily.

Note to self: Add timestamps to warning messages to assist in this. Also potentially move warning messages to a proper oxide log rather than spamming console.