Add a limitation for admins to not be able to /tp another player to them.

For instance if you want an admin to only serve as a spectator and nothing else, there is no reason you would need that person to be able to tp another player to them. In this scenario, they have permanent vanish, and cannot interact with any items/containers or do damage using limited-admin. They would only ever need to tp to another player covertly. The feature of teleporting another player to them can be abused. 

I'm suggesting to add an option in the config to disallow /tp'ing a player to a target,

or an oxide permission that restricts that functionality. something like o.grant group trialadmin nteleportation.disallowsending

i can add this, but it would also need to block /tp nivex 0 0 0 as they could easily exploit it by using this method instead.

Merged post

https://pastebin.com/u4Tieeug


save as NTeleportation.cs

• Fixed rock check inside caves (WIP)
• Fixed locations being set on zipline towers at Outpost
• Fixed some issues where homes would be removed in error
• Added Ukrainian localization per @DIGGER
• Added void OnHomeAdded(BasePlayer player, Vector3 homePos, string homeName) (player may be null when teleport.importhomes command is used and player is dead and offline)
• Added void OnHomeRemoved(BasePlayer player, Vector3 homePos, string homeName)
• Added permission nteleportation.ignoreglobalcooldown
• Added permission nteleportation.disallowtptome to prevent the user from teleporting players to the user
• Added `Hours Before Useable After Wipe` (0) to bandit, outpost, tpr, sethome, etc
• Added `Settings => TPB => Countdown` (0)
• Added `Settings => TPB => Countdowns` (0)
• Added `Settings => TPB => Available After X Seconds` (0)
• Removed `TPB Available After X Seconds`
• Updated teleport method to use the latest native changes
• hitchtrough.deployed prefabs placed in custom maps at the Outpost will now serve as static markers for custom teleport locations. these prefabs will be destroyed on server startup by this plugin. this is useful for maps which have an Outpost, but do not have Bandit camp

nivex

i can add this, but it would also need to block /tp nivex 0 0 0 as they could easily exploit it by using this method instead.

Merged post

https://pastebin.com/u4Tieeug

save as NTeleportation.cs

• Fixed rock check inside caves (WIP)
• Fixed locations being set on zipline towers at Outpost
• Fixed some issues where homes would be removed in error
• Added Ukrainian localization per @DIGGER
• Added void OnHomeAdded(BasePlayer player, Vector3 homePos, string homeName) (player may be null when teleport.importhomes command is used and player is dead and offline)
• Added void OnHomeRemoved(BasePlayer player, Vector3 homePos, string homeName)
• Added permission nteleportation.ignoreglobalcooldown
• Added permission nteleportation.disallowtptome to prevent the user from teleporting players to the user
• Added `Hours Before Useable After Wipe` (0) to bandit, outpost, tpr, sethome, etc
• Added `Settings => TPB => Countdown` (0)
• Added `Settings => TPB => Countdowns` (0)
• Added `Settings => TPB => Available After X Seconds` (0)
• Removed `TPB Available After X Seconds`
• Updated teleport method to use the latest native changes
• hitchtrough.deployed prefabs placed in custom maps at the Outpost will now serve as static markers for custom teleport locations. these prefabs will be destroyed on server startup by this plugin. this is useful for maps which have an Outpost, but do not have Bandit camp

How can i stop the error message "you cant teleport into another entity" when i am trying to /sethome inside a cave where i have had a /sethome for the last 4 wipes (same map) and before i used the updated patch file above. I have already /sethomes in 2 other caves so that is not the problem.

i would need the map and coords to where you are trying to sethome

nivex

i would need the map and coords to where you are trying to sethome

Thanks but it seems it was some kind of a glitch and has not happened before, I have been using the same map for the last 4 wipes and it was the first time it would not let me set the home there even though my team mate had already done it,
Everything else is working well, have a good "New year"

ah ok well when it happens again let me know that info and ill see what i can do