DoorLimiter

redBDGR submitted a new resource:

DoorLimiter - Only allow a certain number of people to use one door

Read more about this resource...

 

redBDGR updated DoorLimiter with a new update entry:

1.0.1

 

redBDGR updated DoorLimiter with a new update entry:

1.0.2

 

I think this is a fantastic idea, as a lot of servers use team size limits, which you can control with clan size limits, but really this doesn't stop people having another person live inside their base. This allows staff to really lock down on the issue, although I'm curious and will check if it works with SharedDoors?

 

It shouldn't really matter if you have SharedDoors installed, as it does everything when you try to open the door, haven't looked into it too much though. Thanks for sharing your opinion though

 

does this have to be installed at server wipe or will it work if i install it mid-wipe? When does it start tracking someone? When they auth on the codelock? How can you remove someone, say if they quit, and you want to remove them from the door limit?

 

It registers the "owner" or "first user" of the door when they place it, but will not start tracking other users until a codelock is placed on it and the other user has entered the correct code and attempted to open the door. You are fine to install this mid-wipe, but it will only track activity from there on. As for removing people from the list, i still have to work on implementing this but it should be in soon currently the only way is to remove the door (which will wipe the data entry)

 

Ok sounds very promising once the remove/replace issue is addressed. What about just rotating non-owners off the list when someone auth's over the limit? So if the owner places a door and a lock, then his 2 friends auth on it (say you set the limit to 3 people).. then a 4th person auth's, have it rotate off the 2nd person off and then it adds the new 4th person, maybe?

Of course, some control for the "owner of the door" like /doorlimit remove "player name" would also be awesome too.

Just some ideas.

 

Thanks giving your advice / insight. I'll start working on removing players from a door & hopefully push an update sometime tomorrow

 

Ok so.. already got some feedback questions from players: "What about code raids"? If the door is maxxed out, no espionage code raids I guess?

 

Yeah, probably no codelock raids unless i could think of something... i doubt there would be a way to do it though

 

Well it worked fine otherwise.. so far. The code raid issue is killer tho haha. oh well.

 

@redBDGR is it possible to set it where once the max number of people is reached that any new players trying to add get zapped for XX health?

I have clans set to 5 so I would set the max to 5. If a 6th person put in the code (even if it was right) the lock would deny it and zap them for lets say 45hp?

Maybe add a GUI that the codelock owner can remove people from the authed list? Incase of clan kicks or something, with a cooldown timer?

 

Not the biggest fan of doing stuff with GUI, but i might have a go sometime in the future. And as for the damage thing, i'll include some sort of system like this in the near future

 

Is there a way you can allow an admin to choose a door that has this plugin applied to it. And on top of that, allow the admin to assign exactly who has access to this door or not. That would be a fantastic feature for town-based servers, such as my own.

 

Doesn't seem to work with shared doors after troubleshooting. Would this functionality be possible, as most servers are using this.

(Plguin Reference SharedDoors for Rust | Oxide

 

I'll look into it

 

Code:

(22:24:34) | 'DoorLimiter v1.0.2' is using deprecated hook 'CanUseLock', which will stop working on Thursday, 13 April 2017. Please ask the author to update to 'CanUseLockedEntity'

 

redBDGR updated DoorLimiter with a new update entry:

1.0.3

 

Oxide build 2.0.3238

Failed to call hook 'CanUseLockedEntity' on plugin 'DoorLimiter v1.0.3' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.DoorLimiter.CanUseLockedEntity (.BasePlayer player, .BaseLock baselock) [0x00000] in <filename unknown>:0
at Oxide.Plugins.DoorLimiter.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00000] in <filename unknown>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (HookMethod method, System.Object[] args) [0x00000] in <filename unknown>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x00000] in <filename unknown>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00000] in <filename unknown>:0