- Configuration File:
- Allows admins to prod an entire building (including deployables)
- Allows admins to change or remove ownership from an entire building (including deployables)
- Allows admins to see cupboard/turret authorization
- Allows admins to change authorization for all nearby cupboards/turrets
- Supports message localization
- Supports both authLevel and permission authentication.
- Provides an API for other plugins to integrate easily
Check ownership of entity you are looking at
Gives you ownership of the entire structure (including deployables)
/own all PlayerName
Gives the specified player ownership of the entire structure (including deployables)
Removes ownership from an entire structure (including deployables)
Checks the ownership of the entire structure (including deployables)
Checks the ownership of the structure (and only the structure)
Checks the authorization of nearby cupboards
Checks the ownership of nearby storage containers
Own/Prod2/Unown optionsCode (Text):
Check the authorization of the cupboard you are looking at. Lists all players currently authorized on cupboard.
Check the authorization of the turret you are looking at
/auth cupboard PlayerName
Gives authorization on all nearby cupboards to target player
/auth turret PlayerName
Gives authorization on all nearby turrets to target player
/deauth cupboard PlayerName
Removes authorization of all nearby cupboards from target player
/deauth turret PlayerName
Removes authorization of all nearby turrets from target player
This plugin uses Oxide's permission system. To assign a permission, use grant user <username|steamid> <permission>. To remove a permission, use revoke user <username|steamid> <permission>.
- entityowner.canchangeowners (allow auth and own commands)
Ex. grant user Calytic entityowner.canchangeowners
Ex. revoke user Calytic entityowner.canchangeowners
Ex. grant group moderator entityowner.canchangeowners
- entityowner.cancheckowners (allow prod command)
Ex. grant user Calytic entityowner.cancheckowners
Ex. revoke user Calytic entityowner.cancheckowners
Ex. grant group moderator entityowner.cancheckowners
- EntityLimit (default: 8000)
There is a hard cap on how many entities may be included in any given ownership command. By default, this cap is 8000.
- messages (Localization)
It is possible to change most of the messages sent by EntityOwner into a different language.
- DistanceThreshold (default: 3)
It is suggested to ratchet the threshold down by 1 tenth each time (2.9, 2.8, 2.7 ..) until you are satisfied with the level of precision when using commands like /own and /prod2.
The DistanceThreshold option allows you to configure how far the ownership commands will seek for other nearby entities (starting from the first entity). Changing the threshold will make ownership commands more or less precise.
// Gets the name and status of the owner player
// Returns null if no owner found
string GetOwnerName(BaseEntity entity)
// Get the BasePlayer instance (if known) of the owner player
// Returns null if no owner found
BasePlayer GetOwnerPlayer(BaseEntity entity)
// Removes the ownership data from a BasePlayer - method faster if
// BasePlayer provided.
// Changes ownership of a BaseEntity to the specified player
ChangeOwner(BaseEntity entity, BasePlayer player)
// Retrieves the owner player.userID in string format
// Returns false when no owner found
object FindEntityData(BaseEntity entity)
// Clears all entity associations with a particular player
// Grab all constructions associated with a particular player
List<BuildingBlock> GetProfileConstructions(BasePlayer player)
// Grab all deployables associated with a particular player
List<BaseEntity> GetProfileDeployables(BasePlayer player)
How To: Report Bugs