Jump to content

Search the Community

Showing results for tags 'control'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Plugins
  • Carbon
  • Harmony
  • Maps
  • Monuments
  • Prefabs
  • Bases
  • Tools
  • Discord Bots
  • Customizations
  • Extensions
  • Graphics

Forums

  • CF Hub
    • Announcements
  • Member Hub
    • General
    • Show Off
    • Requests
  • Member Resources
    • For Hire
    • Creators Directory
  • Community Hub
    • Feedback
  • Support Hub
    • Support
    • Site Support

Product Groups

  • Creator Services
  • Host Services
  • Memberships

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 8 results

  1. Version 0.1.6

    521 downloads

    A plugin creating a trigger box around Monuments and CargoShips to track entry and exit of players, npcs and entities from it. The list of all monuments can be viewed in the: Vanilla - *SERVER*\oxide\data\MonumentsWatcher\MonumentsBounds.json Custom - *SERVER*\oxide\data\MonumentsWatcher\CustomMonumentsBounds.json Note: MonumentsWatcher is utilized as an API for other plugins. You won't obtain any functionality beyond displaying monument boundaries without an additional plugin. The ability to automatically generate boundaries for vanilla and custom monuments; The ability to automatically regenerate boundaries for monuments on wipe; The ability to automatically adding languages for custom monuments; The ability to manually configure boundaries for monuments; The ability to track the entrance and exit of players, npcs and entities in a Monument and CargoShip; The ability to display boundaries. monumentswatcher.admin - Provides the capability to recreate or display monument boundaries. { "Chat command": "monument", "Use GameTip for messages?": true, "Is it worth recreating boundaries(excluding custom monuments) upon detecting a wipe?": true, "List of tracked types of monuments. Leave blank to track all": [], "Wipe ID": null, "Version": { "Major": 0, "Minor": 1, "Patch": 6 } } Monument bounds example: "airfield_1": { "Center": { "x": 335.881531, "y": 9.936, "z": 2096.53345 }, "CenterOffset": { "x": 0.0, "y": 15.0, "z": -25.0 }, "Size": { "x": 360.0, "y": 60.0, "z": 210.0 }, "Rotation": { "x": 0.0, "y": 44.06058, "z": 0.0 } }, ... Custom Monument bounds example: "exit69": { "MonumentType": 12, "Center": { "x": 336.676483, "y": 47.65218, "z": -39.02194 }, "CenterOffset": { "x": 0.0, "y": 0.0, "z": 0.0 }, "Size": { "x": 100.0, "y": 100.0, "z": 100.0 }, "Rotation": { "x": 0.0, "y": 0.0, "z": 0.0 } }, ... Note: MonumentType can be found in the Developer API section. ENG: https://pastebin.com/nsjBCqZe RUS: https://pastebin.com/ut2icv9T Note: After initialization, the names of custom monuments will also be added here. rotation - Sets the monument rotation based on the argument or the player's view direction; recreate - Recreating boundaries for all monuments; show - Displays the boundaries of the monument in which the player is located, either by specified ID or key. Example: Rotation: /monument rotation - Rotation of the monument towards the player's head direction, in which the player is located /monument rotation gas_station_1_0 256.5 - Monument rotation with specified arguments: monument ID and Y coordinate Display by monument key(Will display all monuments with such a key): /monument show gas_station_1 Display by monument ID(Will display one monument with the specified ID): /monument show gas_station_1_4 void OnMonumentsWatcherLoaded() Called when the MonumentsWatcher plugin has fully loaded. void OnCargoWatcherCreated(string monumentID, string type) Called when a watcher is created for a CargoShip. void OnCargoWatcherDeleted(string monumentID) Called when a watcher is removed for a CargoShip. void OnMonumentsWatcherLoaded() { Puts("MonumentsWatcher plugin is ready!"); } void OnCargoWatcherCreated(string monumentID, string type) { Puts($"Watcher for monument {monumentID}({type}) has been created!"); } void OnCargoWatcherDeleted(string monumentID) { Puts($"Watcher for monument {monumentID} has been deleted!"); } Entered hooks: void OnPlayerEnteredMonument(string monumentID, BasePlayer player, string type, string oldMonumentID) Called when a player enters any monument void OnNpcEnteredMonument(string monumentID, BasePlayer npcPlayer, string type, string oldMonumentID) Called when an NPC player enters any monument void OnEntityEnteredMonument(string monumentID, BaseEntity entity, string type, string oldMonumentID) Called when any other BaseEntity enters any monument void OnPlayerEnteredMonument(string monumentID, BasePlayer player, string type, string oldMonumentID) { Puts($"{player.displayName} entered to {monumentID}({type}). His previous monument was {oldMonumentID}"); } void OnNpcEnteredMonument(string monumentID, BasePlayer npcPlayer, string type, string oldMonumentID) { Puts($"Npc({npcPlayer.displayName}) entered to {monumentID}({type}). Previous monument was {oldMonumentID}"); } void OnEntityEnteredMonument(string monumentID, BaseEntity entity, string type, string oldMonumentID) { Puts($"Entity({entity.net.ID}) entered to {monumentID}({type}). Previous monument was {oldMonumentID}"); } Exited hooks: void OnPlayerExitedMonument(string monumentID, BasePlayer player, string type, string reason, string newMonumentID) Called when a player exits any monument void OnNpcExitedMonument(string monumentID, BasePlayer npcPlayer, string type, string reason, string newMonumentID) Called when an NPC player exits any monument void OnEntityExitedMonument(string monumentID, BaseEntity entity, string type, string reason, string newMonumentID) Called when any other BaseEntity exits any monument void OnPlayerExitedMonument(string monumentID, BasePlayer player, string type, string reason, string newMonumentID) { Puts($"{player.displayName} left from {monumentID}({type}). Reason: {reason}. They are now at '{newMonumentID}'."); } void OnNpcExitedMonument(string monumentID, BasePlayer npcPlayer, string type, string reason, string newMonumentID) { Puts($"Npc({npcPlayer.displayName}) left from {monumentID}({type}). Reason: {reason}. They are now in {newMonumentID}"); } void OnEntityExitedMonument(string monumentID, BaseEntity entity, string type, string reason, string newMonumentID) { Puts($"Entity({entity.net.ID}) left from {monumentID}({type}). Reason: {reason}. They are now in {newMonumentID}"); } [PluginReference] private Plugin MonumentsWatcher; There are 13 types of monuments: SafeZone(0): Bandit Camp, Outpost, Fishing Village, Ranch and Large Barn. RadTown(1): Airfield, Arctic Research Base, Abandoned Military Base, Giant Excavator Pit, Ferry Terminal, Harbor, Junkyard, Launch Site; Military Tunnel, Missile Silo, Power Plant, Sewer Branch, Satellite Dish, The Dome, Train Yard, Water Treatment Plant. RadTownWater(2): Oil Rig, Underwater Lab and CargoShip. RadTownSmall(3): Lighthouse, Oxum's Gas Station, Abandoned Supermarket and Mining Outpost. TunnelStation(4) MiningQuarry(5): Sulfur Quarry, Stone Quarry and HQM Quarry. BunkerEntrance(6) Cave(7) Swamp(8) IceLake(9) PowerSubstation(10) WaterWell(11) Custom(12) There are 22 api methods: GetMonumentDisplayName: Used to retrieve the nice name of the monument, considering the player's language. Returns an empty string on failure. To call the GetMonumentDisplayName method, you need to pass 3 parameters: monumentID as a string; userID as either a string or a ulong. You can provide 0 or empty string to get default(eng) language; displaySuffix() as a bool. Should the suffix be displayed in the name if there are multiple such monuments? This parameter is optional. (string)MonumentsWatcher?.Call("GetMonumentDisplayName", monumentID, player.userID, true); (string)MonumentsWatcher?.Call("GetMonumentDisplayName", monumentID, player.UserIDString, true); GetMonumentType: Used to retrieve the monument type. Returns an empty string on failure. To call the GetMonumentType method, you need to pass 1 parameter: monumentID as a string. (string)MonumentsWatcher?.Call("GetMonumentType", monumentID); GetMonumentPosition: Used to retrieve the position of the monument. Returns Vector3.zero on failure. To call the GetMonumentPosition method, you need to pass 1 parameter: monumentID as a string. (Vector3)MonumentsWatcher?.Call("GetMonumentPosition", monumentID); GetMonumentsList: Used to retrieve an array of monumentIDs for all available monuments. (string[])MonumentsWatcher?.Call("GetMonumentsList"); GetMonumentsTypeDictionary: Used to retrieve a dictionary of all available monuments with their types. (Dictionary<string, string>)MonumentsWatcher?.Call("GetMonumentsTypeDictionary"); GetMonumentsByType: Used to retrieve an array of all available monuments by type. To call the GetMonumentsByType method, you need to pass 1 parameter: monument type as a string. (string[])MonumentsWatcher?.Call("GetMonumentsByType", "SafeZone"); GetMonumentPlayers: Used to retrieve a list of players in the monument. Returns null on failure. To call the GetMonumentPlayers method, you need to pass 1 parameter: monumentID as a string. (HashSet<BasePlayer>)MonumentsWatcher?.Call("GetMonumentPlayers", monumentID); GetMonumentNpcs: Used to retrieve a list of npc players in the monument. Returns null on failure. To call the GetMonumentNpcs method, you need to pass 1 parameter: monumentID as a string. (HashSet<BasePlayer>)MonumentsWatcher?.Call("GetMonumentNpcs", monumentID); GetMonumentEntities: Used to retrieve a list of entities in the monument. Returns null on failure. To call the GetMonumentEntities method, you need to pass 1 parameter: monumentID as a string. (HashSet<BaseEntity>)MonumentsWatcher?.Call("GetMonumentEntities", monumentID); GetPlayerMonument: Used to retrieve the monumentID of the monument in which the player is located. Returns an empty string on failure. To call the GetPlayerMonument method, you need to pass 1 parameter: player as BasePlayer or userID as a ulong. (string)MonumentsWatcher?.Call("GetPlayerMonument", player); (string)MonumentsWatcher?.Call("GetPlayerMonument", player.userID); GetNpcMonument: Used to retrieve the monumentID of the monument in which the npc player is located. Returns an empty string on failure. To call the GetNpcMonument method, you need to pass 1 parameter: npcPlayer as BasePlayer or NetworkableId. (string)MonumentsWatcher?.Call("GetNpcMonument", npcPlayer); (string)MonumentsWatcher?.Call("GetNpcMonument", npcPlayer.net.ID); GetEntityMonument: Used to retrieve the monumentID of the monument in which the entity is located. Returns an empty string on failure. To call the GetEntityMonument method, you need to pass 1 parameter: entity as a BaseEntity or NetworkableId. (string)MonumentsWatcher?.Call("GetEntityMonument", entity); (string)MonumentsWatcher?.Call("GetEntityMonument", entity.net.ID); GetPlayerMonuments: Used to retrieve an array of monumentIDs for the monuments in which the player is located. Returns null on failure. To call the GetPlayerMonuments method, you need to pass 1 parameter: player as BasePlayer or userID as a ulong. (string[])MonumentsWatcher?.Call("GetPlayerMonuments", player); (string[])MonumentsWatcher?.Call("GetPlayerMonuments", player.userID); GetNpcMonuments: Used to retrieve an array of monumentIDs for the monuments in which the npc player is located. Returns an null on failure. To call the GetNpcMonuments method, you need to pass 1 parameter: npcPlayer as BasePlayer or NetworkableId. (string[])MonumentsWatcher?.Call("GetNpcMonuments", npcPlayer); (string[])MonumentsWatcher?.Call("GetNpcMonuments", npcPlayer.net.ID); GetEntityMonuments: Used to retrieve an array of monumentID for the monuments in which the entity is located. Returns an null on failure. To call the GetEntityMonuments method, you need to pass 1 parameter: entity as a BaseEntity or NetworkableId. (string[])MonumentsWatcher?.Call("GetEntityMonuments", entity); (string[])MonumentsWatcher?.Call("GetEntityMonuments", entity.net.ID); GetMonumentByPos: Used to obtain the monumentID based on coordinates. Returns an empty string on failure. To call the GetMonumentByPos method, you need to pass 1 parameter: position as a Vector3. (string)MonumentsWatcher?.Call("GetMonumentByPos", pos); Note: This method returns the first encountered monument. Occasionally, there may be multiple monuments at a single point. Therefore, it is recommended to use the GetMonumentsByPos method. GetMonumentsByPos: Used to obtain a string array of monumentIDs based on coordinates. Returns null on failure. To call the GetMonumentsByPos method, you need to pass 1 parameter: position as a Vector3. (string[])MonumentsWatcher?.Call("GetMonumentsByPos", pos); IsPosInMonument: Used to check if the specified position is within the monument. Returns a false on failure. To call the IsPosInMonument method, you need to pass 2 parameters: monumentID as a string; position as a Vector3. (bool)MonumentsWatcher?.Call("IsPosInMonument", monumentID, pos); IsPlayerInMonument: Used to check if the player is in the monument. Returns a false on failure. To call the IsPlayerInMonument method, you need to pass 2 parameters: monumentID as a string; player as a BasePlayer or userID as a ulong. (bool)MonumentsWatcher?.Call("IsPlayerInMonument", monumentID, player); (bool)MonumentsWatcher?.Call("IsPlayerInMonument", monumentID, player.userID); IsNpcInMonument: Used to check if the npc player is in the monument. Returns a false on failure. To call the IsNpcInMonument method, you need to pass 2 parameters: monumentID as a string; npcPlayer as a BasePlayer or NetworkableId. (bool)MonumentsWatcher?.Call("IsNpcInMonument", monumentID, npcPlayer); (bool)MonumentsWatcher?.Call("IsNpcInMonument", monumentID, npcPlayer.net.ID); IsEntityInMonument: Used to check if the entity is in the monument. Returns a false on failure. To call the IsEntityInMonument method, you need to pass 2 parameters: monumentID as a string; entity as a BaseEntity or NetworkableId. (bool)MonumentsWatcher?.Call("IsEntityInMonument", monumentID, entity); (bool)MonumentsWatcher?.Call("IsEntityInMonument", monumentID, entity.net.ID); ShowBounds: Used to display the monument boundaries to the player. Note: Since an Admin flag is required for rendering, players without it will be temporarily granted an Admin flag and promptly revoked. To call the ShowBounds method, you need to pass 3 parameters: monumentID as a string; player as a BasePlayer; displayDuration as a float. Duration of displaying the monument boundaries in seconds. This parameter is optional. MonumentsWatcher?.Call("ShowBounds", monumentID, player, 20f);
    $1.99
  2. Version 1.0.0

    2 downloads

    Control Center is designed to make managing your base easier and more efficient by providing you with a user-friendly interface for interacting with key base elements such as Tool Cupboards, Code Locks, and Auto Turrets. 1. Tool Cupboard Management: Authorize Players Easily: With Control Center, you can easily authorize or deauthorize players from Tool Cupboard. Simply use the GUI to manage access in a few clicks. View Owners and Resources: You can check who currently has access to your Tool Cupboard and even view a detailed breakdown of the upkeep costs for your base. This helps you stay on top of your resource needs and ensure that your base remains protected from decay. The Owner is the first person to gain auth on Tool Cupboard and will have control over who can have full access to control center for that TC area if players have limited access the can view Control Center but not make any changes. 2. Code Lock Management: Authorize Friends: No need to give your friends the code for your Code Locks and have them go all over to find every lock, just add them to the lock you want them to access from inside the GUI. Lock and Unlock with Ease: Players can lock or unlock any Code Locks directly through the Control Center interface, which makes it faster to manage secure doors and boxes in your base. Set Custom Names: You can set custom names for each Code Lock, making it easier to identify which lock belongs to which part of your base. 3. Auto Turret Management: Authorize Friends: Easily add your team to every Auto Turret inside your base without the need of shutting you turrets down and going around each one. Switch Modes Quickly: Control your Auto Turrets through the GUI. You can easily switch between hostile and passive modes. Assign Custom Names: Similar to Code Locks, you can assign custom names to your turrets for easier management and identification. Control Center adds an easy-to-use interface that allows you to manage all these elements from one central location. You can open the interface to see a clear overview of your Tool Cupboards, Code Locks, and Auto Turrets. The GUI also allows you to add or remove friends or other players from these entities with just a few clicks, instead of having to manually interact with each one. If enabled, the plugin integrates with Steam to display your friends directly in the management interface, making it simple to add them to your base’s Tool Cupboards, Code Locks, or Turrets. With Control Center players have a powerful tool at their fingertips to better manage base security, access, and upkeep—providing a smoother and more convenient Rust experience. Chat Commands: /cc Opens Control Center. /name Used near a Code Lock or Auto Turret to add a name. Permissions controlcenter.useGui To allow players to use /cc command. controlcenter.useName To allow players to use /name command. Supported Language: English, French, German, Polish, Russian and Spanish ControlCenter.json
    $15.00
  3. Version 0.1.0

    104 downloads

    Useful plugin for managing temporary permissions, temporary groups and temporary permissions for groups. This is done through chat commands, built-in Oxide commands, and API methods. This is an alternative to the well-known TimedPermissions plugin, which was abandoned about three years ago, and it offers more advanced features. Note: The dates is in UTC format. The ability to grant players temporary permissions by specifying either the number of seconds or an exact expiration date; The ability to add players to temporary groups by specifying either the number of seconds or an exact expiration date; The ability to grant groups temporary permissions by specifying either the number of seconds or an exact expiration date; The ability to revoke temporary permissions from players and groups prematurely; The ability to remove players from groups prematurely; The ability to perform all the above actions using existing and familiar console commands (e.g. o.grant), simply by adding the number of seconds or the expiration date at the end; The ability to perform all the above actions using a chat command (by default /tperm); The ability to perform all the above actions using API methods; The ability to remove all temporary permissions and groups upon wipe detection. temporarypermissions.admin - Grants access to the chat command(by default /tperm). { "Chat command": "tperm", "Expiration Check Interval": 1.0, "Is it worth removing temporary permissions and groups when unloading the plugin or when a player disconnects?": true, "Is it worth using console logging?": true, "Is it worth clearing all temporary permissions upon detecting a wipe?": false, "Wipe ID": null, "Version": { "Major": 0, "Minor": 1, "Patch": 0 } } EN: { "MsgPermissionNotFound": "Permission not found!", "MsgPlayerNotFound": "Player not found!", "MsgGroupNotFound": "Group not found!", "MsgGrantWrongFormat": "Invalid command format! Example: /tperm grant user/group *NameOrId* realpve.vip *secondsOrDateTime*", "MsgRevokeWrongFormat": "Invalid command format! Example: /tperm revoke user/group *NameOrId* realpve.vip", "MsgUserGroupWrongFormat": "Invalid command format! Example: /tperm group add/remove *NameOrId* *groupName*", "MsgUserGranted": "Permission {0} granted to player {1}", "MsgGroupGranted": "Permission {0} granted to group {1}", "MsgUserGroupAdded": "Player {0} has been added to group {1}", "MsgUserRevoked": "Permission {0} has been removed for player {1}", "MsgGroupRevoked": "Permission {0} has been removed for group {1}", "MsgUserGroupRemoved": "Player {0} has been removed from group {1}" } RU: { "MsgPermissionNotFound": "Пермишен не найден!", "MsgPlayerNotFound": "Игрок не найден!", "MsgGroupNotFound": "Группа не найдена!", "MsgGrantWrongFormat": "Не верный формат команды! Пример: /tperm grant user/group *NameOrId* realpve.vip *secondsOrDateTime*", "MsgRevokeWrongFormat": "Не верный формат команды! Пример: /tperm revoke user/group *NameOrId* realpve.vip", "MsgUserGroupWrongFormat": "Не верный формат команды! Пример: /tperm group add/remove *NameOrId* *groupName*", "MsgUserGranted": "Пермишен {0} выдан игроку {1}", "MsgGroupGranted": "Пермишен {0} выдан группе {1}", "MsgUserGroupAdded": "Игрок {0} был добавлен в группу {1}", "MsgUserRevoked": "Пермишен {0} был удален для игрока {1}", "MsgGroupRevoked": "Пермишен {0} был удален для группы {1}", "MsgUserGroupRemoved": "Игрок {0} был удален из группы {1}" } grant - Grants a temporary permission to a player or group. user *NameOrId* realpve.vip 3600 true/false - Grants a temporary permission to a player by specifying the player's name or Id, the permission name, the number of seconds and true/false(optional). If true, the specified seconds will count from the current moment, otherwise(default), they will be added to the existing time; *NameOrId* realpve.vip "2024-08-19 17:57" "2024-08-19 16:57" - Grants a temporary permission to a player by specifying the player's name or Id, the permission name, the expiration date and the assigned date(optional). If not specified, the assigned date will default to the current date, otherwise, it will be set to the provided date. group *GroupName* realpve.vip 3600 true/false - Grants a temporary permission to a group by specifying the group's name, the permission name, the number of seconds, and true/false(optional). If true, the specified seconds will count from the current moment, otherwise(default), they will be added to the existing time; *GroupName* realpve.vip "2024-08-19 17:57" "2024-08-19 16:57" - Grants a temporary permission to a group by specifying the group's name, the permission name, the expiration date and the assigned date(optional). If not specified, the assigned date will default to the current date, otherwise, it will be set to the provided date. revoke - Revokes a temporary permission from a player or group. user *NameOrId* realpve.vip - Revokes a temporary permission from a player by specifying the player's name or Id and the permission name; group *GroupName* realpve.vip - Revokes a temporary permission from a group by specifying the group's name and the permission name. add - Temporary addition of a player to a group. *NameOrId* *GroupName* 3600 true/false - Temporary addition of a player to a group by specifying the player's name or Id, the group name, the number of seconds, and true/false(optional). If true, the specified seconds will count from the current moment, otherwise(default), they will be added to the existing time; *NameOrId* *GroupName* "2024-08-19 17:57" "2024-08-19 16:57" - Temporary addition of a player to a group by specifying the player's name or Id, the group name, the expiration date and the assigned date(optional). If not specified, the assigned date will default to the current date, otherwise, it will be set to the provided date. remove *NameOrId* *GroupName* - Removal of a player from a temporary group by specifying the player's name or Id and the group name. Example: /tperm grant user iiiaka realpve.vip 3600 true /tperm grant user iiiaka realpve.vip "2024-08-19 17:57" "2024-08-19 16:57" Note: To access the commands, the player must be an admin(console or owner) or have the temporarypermissions.admin permission. P.S. Templates for the commands above can also be used with existing console commands. For example: o.grant user iiiaka realpve.vip 3600 true OnTemporaryPermissionsLoaded: Called after the TemporaryPermissions plugin is fully loaded and ready. OnTemporaryPermissionGranted: Called after the player has been granted a temporary permission. OnTemporaryPermissionUpdated: Called after the player's temporary permission has been updated. OnTemporaryPermissionRevoked: Called after the player's temporary permission has expired or been revoked. OnTemporaryGroupAdded: Called after the player has been temporarily added to the group. OnTemporaryGroupUpdated: Called after the player's temporary group has been updated. OnTemporaryGroupRemoved: Called after the player's temporary group has expired or been removed. OnGroupTemporaryPermissionGranted: Called after the group has been granted a temporary permission. OnGroupTemporaryPermissionUpdated: Called after the group's temporary permission has been updated. OnGroupTemporaryPermissionRevoked: alled after the group's temporary permission has expired or been revoked. void OnTemporaryPermissionsLoaded() { Puts("The TemporaryPermissions plugin is loaded and ready to go!"); } void OnTemporaryPermissionGranted(string userID, string perm, DateTime expireDate, DateTime assignedDate) { Puts($"Player {userID} has been granted the temporary permission {perm} from {assignedDate} until {expireDate}."); } void OnTemporaryPermissionUpdated(string userID, string perm, DateTime expireDate, DateTime assignedDate) { Puts($"Player {userID}'s temporary permission {perm} has been updated. New expiration date: {expireDate}. Assigned date: {assignedDate}."); } void OnTemporaryPermissionRevoked(string userID, string perm, bool isExpired) { Puts($"Player {userID} has had the temporary permission {perm} revoked. Permission expired: {isExpired}."); } void OnTemporaryGroupAdded(string userID, string groupName, DateTime expireDate, DateTime assignedDate) { Puts($"Player {userID} has been added to the temporary group {groupName} from {assignedDate} until {expireDate}."); } void OnTemporaryGroupUpdated(string userID, string groupName, DateTime expireDate, DateTime assignedDate) { Puts($"Player {userID}'s temporary group {groupName} has been updated. New expiration date: {expireDate}. Assigned date: {assignedDate}."); } void OnTemporaryGroupRemoved(string userID, string groupName, bool isExpired) { Puts($"Player {userID} has had the temporary group {groupName} revoked. Group expired: {isExpired}."); } void OnGroupTemporaryPermissionGranted(string groupName, string perm, DateTime expireDate, DateTime assignedDate) { Puts($"Group {groupName} has been granted the temporary permission {perm}, valid from {assignedDate} until {expireDate}."); } void OnGroupTemporaryPermissionUpdated(string groupName, string perm, DateTime expireDate, DateTime assignedDate) { Puts($"Group {groupName}'s temporary permission {perm} has been updated. New expiration date: {expireDate}. Assigned date: {assignedDate}."); } void OnGroupTemporaryPermissionRevoked(string groupName, string perm, bool isExpired) { Puts($"Group {groupName} has had the temporary permission {perm} revoked. Permission expired: {isExpired}."); } [PluginReference] private Plugin TemporaryPermissions; There are 23 methods: IsReady User's Permissions: GrantUserPermission RevokeUserPermission UserHasPermission GrantActiveUsersPermission GrantAllUsersPermission RevokeActiveUsersPermission RevokeAllUsersPermission UserGetAllPermissions User's Groups: AddUserGroup RemoveUserGroup UserHasGroup AddActiveUsersGroup AddAllUsersGroup RemoveActiveUsersGroup RemoveAllUsersGroup UserGetAllGroups Group's Permissions: GrantGroupPermission RevokeGroupPermission GroupHasPermission GrantAllGroupsPermission RevokeAllGroupsPermission GroupGetAllPermissions IsReady: Used to check if the TemporaryPermissions plugin is loaded and ready to work. The IsReady method returns true if it is ready, or null if it is not. (bool)TemporaryPermissions?.Call("IsReady");//Calling the IsReady method. If the result is not null(bool true), the plugin is ready. GrantUserPermission: Used to grant a temporary permission to a player. Returns true if the grant was successful. To call the GrantUserPermission method, you need to pass 5 parameters, 2 of which are optional: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>permName - The name of the permission; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date; <bool>checkExistence - Optional. Whether to check for the existence of the permission. (bool)TemporaryPermissions?.Call("GrantUserPermission", player.UserIDString, "realpve.vip", 3600, true, true);//Calling the GrantUserPermission method with the specified number of seconds to add. (bool)TemporaryPermissions?.Call("GrantUserPermission", player.UserIDString, "realpve.vip", expireDate, assignedDate, true);//Calling the GrantUserPermission method with the specified DateTime for the end and start of the temporary permission. RevokeUserPermission: Used to revoke a temporary permission from a player. Returns true if the revoke was successful. To call the RevokeUserPermission method, you need to pass 2 parameters: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>permName - The name of the permission. (bool)TemporaryPermissions?.Call("RevokeUserPermission", player.UserIDString, "realpve.vip"); UserHasPermission: Used to check if a player has a temporary permission. Returns true if the player has the specified temporary permission. To call the UserHasPermission method, you need to pass 2 parameters: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>permName - The name of the permission. (bool)TemporaryPermissions?.Call("UserHasPermission", player.UserIDString, "realpve.vip"); GrantActiveUsersPermission: Used to temporarily grant a permission to all online players. Returns the <int>number of successful grants of temporary permissions to players. To call the GrantActiveUsersPermission method, you need to pass 3 parameters, 1 of which is optional: <string>permName - The name of the permission; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date. (int)TemporaryPermissions?.Call("GrantActiveUsersPermission", "realpve.vip", 3600, true);//Calling the GrantActiveUsersPermission method with the specified number of seconds to add. (int)TemporaryPermissions?.Call("GrantActiveUsersPermission", "realpve.vip", expireDate, assignedDate);//Calling the GrantActiveUsersPermission method with the specified DateTime for the end and start of the temporary permission. GrantAllUsersPermission: Used to grant a temporary permission to all players. Returns the <int>number of successful grants of temporary permissions to players. To call the GrantAllUsersPermission method, you need to pass 3 parameters, 1 of which is optional: <string>permName - The name of the permission; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date. (int)TemporaryPermissions?.Call("GrantAllUsersPermission", "realpve.vip", 3600, true);//Calling the GrantAllUsersPermission method with the specified number of seconds to add. (int)TemporaryPermissions?.Call("GrantAllUsersPermission", "realpve.vip", expireDate, assignedDate);//Calling the GrantAllUsersPermission method with the specified DateTime for the end and start of the temporary permission. RevokeActiveUsersPermission: Used to revoke a temporary permission from all online players. Returns the <int>number of successful revokes of temporary permissions to players. To call the RevokeActiveUsersPermission method, you need to pass 1 parameter: <string>permName - The name of the permission. (int)TemporaryPermissions?.Call("RevokeActiveUsersPermission", "realpve.vip"); RevokeAllUsersPermission: Used to revoke a temporary permission from all players. Returns the <int>number of successful revokes of temporary permissions to players. To call the RevokeAllUsersPermission method, you need to pass 1 parameter: <string>permName - The name of the permission. (int)TemporaryPermissions?.Call("RevokeAllUsersPermission", "realpve.vip"); UserGetAllPermissions: Used to retrieve all temporary permissions of a player. Returns a Dictionary<string, DateTime[]> where the key is the permission name and the value is an array of 2 DateTimes: the first date is the assignment date and the second date is the expiration date of the permission. To call the UserGetAllPermissions method, you need to pass 1 parameter: IPlayer or BasePlayer or <string>playerID - The player object or their Id. (Dictionary<string, DateTime[]>)TemporaryPermissions?.Call("UserGetAllPermissions", player.UserIDString); AddUserGroup: Used to temporarily add a player to a group. Returns true if the addition was successful. To call the AddUserGroup method, you need to pass 5 parameters, 2 of which are optional: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>groupName - The name of the group; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date; <bool>checkExistence - Optional. Whether to check for the existence of the group. (bool)TemporaryPermissions?.Call("AddUserGroup", player.UserIDString, "vip", 3600, true, true);//Calling the AddUserGroup method with the specified number of seconds to add. (bool)TemporaryPermissions?.Call("AddUserGroup", player.UserIDString, "vip", expireDate, assignedDate, true);//Calling the AddUserGroup method with the specified DateTime for the end and start of the temporary permission. RemoveUserGroup: Used to remove a temporary group from a player. Returns true if the removal was successful. To call the RemoveUserGroup method, you need to pass 2 parameters: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>groupName - The name of the group. (bool)TemporaryPermissions?.Call("RemoveUserGroup", player.UserIDString, "vip"); UserHasGroup: Used to check if a player has a temporary group. Returns true if the player has the specified temporary group. To call the UserHasGroup method, you need to pass 2 parameters: IPlayer or BasePlayer or <string>playerID - The player object or their Id; <string>groupName - The name of the group. (bool)TemporaryPermissions?.Call("UserHasGroup", player.UserIDString, "vip"); AddActiveUsersGroup: Used to temporarily add a group to all online players. Returns the <int>number of successful additions of the temporary group to players. To call the AddActiveUsersGroup method, you need to pass 3 parameters, 1 of which is optional: <string>groupName - The name of the group; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date. (int)TemporaryPermissions?.Call("AddActiveUsersGroup", "vip", 3600, true);//Calling the AddActiveUsersGroup method with the specified number of seconds to add. (int)TemporaryPermissions?.Call("AddActiveUsersGroup", "vip", expireDate, assignedDate);//Calling the AddActiveUsersGroup method with the specified DateTime for the end and start of the temporary permission. AddAllUsersGroup: Used to temporarily add a group to all players. Returns the <int>number of successful additions of the temporary group to players. To call the AddAllUsersGroup method, you need to pass 3 parameters, 1 of which is optional: <string>groupName - The name of the group; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date. (int)TemporaryPermissions?.Call("AddAllUsersGroup", "vip", 3600, true);//Calling the AddAllUsersGroup method with the specified number of seconds to add. (int)TemporaryPermissions?.Call("AddAllUsersGroup", "vip", expireDate, assignedDate);//Calling the AddAllUsersGroup method with the specified DateTime for the end and start of the temporary permission. RemoveActiveUsersGroup: Used to remove a temporary group from all online players. Returns the <int>number of successful removals of temporary groups from players. To call the RemoveActiveUsersGroup method, you need to pass 1 parameter: <string>groupName - The name of the group. (int)TemporaryPermissions?.Call("RemoveActiveUsersGroup", "vip"); RemoveAllUsersGroup: Used to remove a temporary group from all players. Returns the <int>number of successful removals of temporary groups from players. To call the RemoveAllUsersGroup method, you need to pass 1 parameter: <string>permName - The name of the permission. (int)TemporaryPermissions?.Call("RemoveAllUsersGroup", "vip"); UserGetAllGroups: Used to retrieve all temporary groups of a player. Returns a Dictionary<string, DateTime[]> where the key is the group name and the value is an array of 2 DateTime values: the first date is the assignment date and the second date is the expiration date of the group. To call the UserGetAllGroups method, you need to pass 1 parameter: <string>permName - The name of the permission. (Dictionary<string, DateTime[]>)TemporaryPermissions?.Call("UserGetAllGroups", player.UserIDString); GrantGroupPermission: Used to grant a temporary permission to a group. Returns true if the grant was successful. To call the GrantGroupPermission method, you need to pass 5 parameters, 2 of which are optional: <string>groupName - The name of the group; <string>permName - The name of the permission; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date; <bool>checkExistence - Optional. Whether to check for the existence of the permission. (bool)TemporaryPermissions?.Call("GrantGroupPermission", "vip", "realpve.vip", 3600, true, true);//Calling the GrantGroupPermission method with the specified number of seconds to add. (bool)TemporaryPermissions?.Call("GrantGroupPermission", "vip", "realpve.vip", expireDate, assignedDate, true);//Calling the GrantGroupPermission method with the specified DateTime for the end and start of the temporary permission. RevokeGroupPermission: Used to revoke a temporary permission from a group. Returns true if the revoke was successful. To call the RevokeGroupPermission method, you need to pass 2 parameters: <string>groupName - The name of the group; <string>permName - The name of the permission. (bool)TemporaryPermissions?.Call("RevokeGroupPermission", "vip", "realpve.vip"); GroupHasPermission: Used to check if a group has a temporary permission. Returns true if the group has the specified temporary permission. To call the GroupHasPermission method, you need to pass 2 parameters: <string>groupName - The name of the group; <string>permName - The name of the permission. (bool)TemporaryPermissions?.Call("GroupHasPermission", "vip", "realpve.vip"); GrantAllGroupsPermission: Used to temporarily grant a permission to all groups. Returns the <int>number of successful grants of temporary permissions to groups. To call the GrantAllGroupsPermission method, you need to pass 3 parameters, 1 of which is optional: <string>permName - The name of the permission; <int>secondsToAdd or <DateTime>expireDate - The time in seconds to add, or the end date; <bool>fromNow or <DateTime>assignedDate - Optional. true/false to specify whether the seconds should be added to the current date or to the existing time, or an exact assignment date. Defaults to the current date. (int)TemporaryPermissions?.Call("GrantAllGroupsPermission", "realpve.vip", 3600, true);//Calling the GrantAllGroupsPermission method with the specified number of seconds to add. (int)TemporaryPermissions?.Call("GrantAllGroupsPermission", "realpve.vip", expireDate, assignedDate);//Calling the GrantAllGroupsPermission method with the specified DateTime for the end and start of the temporary permission. RevokeAllGroupsPermission: Used to revoke a temporary permission from all groups. Returns the <int>number of successful revokes of temporary permissions to groups. To call the RevokeAllGroupsPermission method, you need to pass 1 parameter: <string>permName - The name of the permission. (int)TemporaryPermissions?.Call("RevokeAllGroupsPermission", "realpve.vip"); GroupGetAllPermissions: Used to retrieve all temporary permissions of a group. Returns a Dictionary<string, DateTime[]> where the key is the permission name and the value is an array of 2 DateTimes: the first date is the assignment date and the second date is the expiration date of the permission. To call the GroupGetAllPermissions method, you need to pass 1 parameter: <string>groupName - The name of the group. (Dictionary<string, DateTime[]>)TemporaryPermissions?.Call("GroupGetAllPermissions", "vip");
    Free
  4. Version 1.3.3

    198 downloads

    Introducing Total Control, a comprehensive admin tool designed for Rust game servers. This plugin is built with a full GUI, providing an intuitive and user-friendly interface for server administrators. With Total Control, you can customize every aspect of your Rust server to create a unique gaming experience for your players. Here are some of the features that set Total Control apart: Settings Page (New!): The latest addition to Total Control, the Settings page introduces powerful options for customizing server-wide gameplay systems: Skip Night: Automatically skip night cycles or use a voting system where players can vote to skip night. Time Freeze: Freeze time to any time of the day you choose. Day and Night Settings: Configure the start and end of the day, set the percentage of votes required to pass a day skip, and adjust the delay for voting messages. You can also limit the number of nights players can skip before requiring a full night cycle. Custom Vote Command: Define the vote day command, with /day as the default. PvE/PvP Mode: Set basic PvE or PvP modes, which can be toggled on a timer, or be set to stay permanently on. PvE or PvP mode can be displayed on the player HUD. Raid Protection: Implement raid protection with the same flexible settings as the PvE/PvP modes, including timers and toggles. StackSize Page: A new addition to Total Control, the StackSize page allows you to set up multipliers for individual items or entire categories, offering greater control over item stacking in your server. Item Gather Rate Control: Customize the gather rate for every item in the game to balance resource acquisition and gameplay progression. Smelting and Cooking Control: Adjust the smelting speeds for furnaces, mixing tables, campfires, and oil refineries. You can also control the charcoal output amount, the cooked output amount, and the amount of fuel used. Reward System: Set up rewards for various in-game actions such as killing scientists, and players, or picking up or mining different items. Rewards can be given in the form of economics (if the Economics plugin is installed) or server rewards (if the ServerRewards plugin is installed) or even scrap. Bradley APC and Patrol Heli Rewards: Players can be rewarded for dealing damage to or destroying the Bradley APC and Patrol Heli. There’s also a setting to divide the loot among all players who dealt damage or give all the loot to the player who deals the final blow. Total Control allows you to create a Rust server tailored to your community’s playstyle. Whether you’re looking to create a hardcore survival experience or a more casual, resource-rich environment, Total Control gives you the tools to make it happen. Accessible In-Game: One of the key features of Total Control is its accessibility. Any admin with the correct permissions can alter any settings directly in the game, even if they don’t have access to server files. Simply open the UI using the /tc command and change any settings as needed. Permissions: TotalControl.OpenGui To allow access to the Ui for admin. Chat Commands: /tc To Open the Ui for any player with the correct permission
    $20.00
  5. Version 1.0.1

    92 downloads

    ABOUT Allow players to change their individual fuse timers on all types of thrown explosives. Also control dud chance values. Fully configurable per type, individual settings stored in data folder. Now comes with a UI which can be used to change the appropriate values. The permission "use" is necessary for full functionality. The new permission for "nodud" is only to be granted if you want the players to have no duds. If this is not granted then it will return vanilla behaviour for dud chance. to apply the use permission in server console: o.grant <user/group> <username or groupname> explosivescontrol.use I highly recommend permissions manager by steenamaroo to handle perms through an in game interface CONFIG { "itemNames": { "beancan": 1840822026, "c4": 1248356124, "flare": 304481038, "flashbang": -936921910, "grenade": 143803535, "satchel": -1878475007, "smokegrenade": 1263920163, "surveycharge": 1975934948, "lunar.firecrackers": -1961560162 }, "items": { "1248356124": { "itemId": 1248356124, "itemName": "c4", "defaultFuseTime": 8.0, "minFuseTime": 3.0, "maxFuseTime": 30.0, "DudChance": 0.0 }, "1263920163": { "itemId": 1263920163, "itemName": "smokegrenade", "defaultFuseTime": 5.0, "minFuseTime": 1.0, "maxFuseTime": 5.0, "DudChance": 0.0 }, "143803535": { "itemId": 143803535, "itemName": "grenade", "defaultFuseTime": 2.0, "minFuseTime": 1.0, "maxFuseTime": 5.0, "DudChance": 0.0 }, "1840822026": { "itemId": 1840822026, "itemName": "beancan", "defaultFuseTime": 2.0, "minFuseTime": 1.0, "maxFuseTime": 5.0, "DudChance": 0.0 }, "-1878475007": { "itemId": -1878475007, "itemName": "satchel", "defaultFuseTime": 8.0, "minFuseTime": 3.0, "maxFuseTime": 30.0, "DudChance": 0.0 }, "1975934948": { "itemId": 1975934948, "itemName": "surveycharge", "defaultFuseTime": 1.0, "minFuseTime": 1.0, "maxFuseTime": 5.0, "DudChance": 0.0 }, "304481038": { "itemId": 304481038, "itemName": "flare", "defaultFuseTime": 30.0, "minFuseTime": 10.0, "maxFuseTime": 60.0, "DudChance": 0.0 }, "-936921910": { "itemId": -936921910, "itemName": "flashbang", "defaultFuseTime": 2.0, "minFuseTime": 1.0, "maxFuseTime": 10.0, "DudChance": 0.0 }, "-1961560162": { "itemId": -1961560162, "itemName": "lunar.firecrackers", "defaultFuseTime": 8.0, "minFuseTime": 3.0, "maxFuseTime": 30.0, "DudChance": 0.0 } }, "itemBlacklist": [ 1397052267, 1556365900, 1975934948, 304481038, -1961560162 ], "fallbackItemConfig": { "itemId": 0, "itemName": "", "defaultFuseTime": 8.0, "minFuseTime": 3.0, "maxFuseTime": 30.0, "DudChance": 0.0 }, "enableOnUserConnected": true, "connectMessage": "To change your explosive fuse timer, you can use /fuseui", "Title Bar Red": 10, "Title Bar Green": 10, "Title Bar Blue": 10, "Side Bar Red": 200, "Side Bar Green": 200, "Side Bar Blue": 200, "Item Panel Red": 128, "Item Panel Green": 128, "Item Panel Blue": 128, "Item BG Red": 80, "Item BG Green": 80, "Item BG Blue": 80, "Item Name Background Red": 150, "Item Name Background Green": 150, "Item Name Background Blue": 150, "Fuse Input Field Red": 80, "Fuse Input Field Green": 80, "Fuse Input Field Blue": 80, "Button Colour (must be <= 1) The last number is transparency in this string and is required to generate the button correctly. R G B A": "0.5 0.5 0.5 1" } COMMANDS /fuseui will bring up the UI where your players can edit each explosive type within the specified range (changes inside config file should be reflected in the UI) <Must have the "use" permission to use the plugin fully, bonus "nodud" permission is exactly as it sounds> all credit for the new logo belongs to 4yzhen, many thanks
    $4.00
  6. Version 2.0.7

    268 downloads

    Loadout controller is made to assist in allowing your battlefield or even PVE community to thrive with customizable loadouts. FEATURES - Multiple permission groups - You can set different saveable items for each permission group - You can set different default loadouts for each permission group - You can set the amount of saveable personal loadouts for each permission group - You can limit the amount of items that are able to be saved in each permission group - Very nice UI that tells you what can and cannot be saved and if a partial bit of a stack can be saved - You can view what is in your loadout right in the UI - Supports multiple loadouts for each player - Admins can set new loadouts for each permission group right in the UI - Automatically applies loadout on respawn
    $19.99
  7. Version 1.0.8

    3,282 downloads

    UI spawn amount/time control for monument crates, keycards, barrels, etc. MonumentSpawnControl provides a UI per vanilla monument, listing each spawn group for that monument, with controls for spawn population, respawn timer, and max amount to respawn per cycle. Each group can be emptied, filled, enabled, or disabled, with one click. Respawn durations are in minutes. Where there are multiple monuments of the same name (e.g. Lighthouse), they are all controlled by the same settings. Notes Does not offer control over RustEdit created monument spawns. Does not govern spawners which are part of a puzzle, as these have their own reset criteria. Chat commands. /msc - Usable by admin, or with permission. Permissions. monumentspawncontrol.allowed Configuration. ButtonColour "0.7 0.32 0.17 1" ButtonColour2 "0.4 0.1 0.1 1" - Used for disabled / inactive. Config also stores an entry per monument with information per spawn group. There is no need to edit or view this - It’s all controllable by in-game UI. Useful tool for picking CUI colours - RGB Decimal.
    Free
  8. VORON

    APControl

    Version 1.0.9

    5 downloads

    The "APControl" plugin is designed for Rust game servers to manage and control various plugins based on user permissions. It allows server administrators to load and unload specific plugins for different user groups such as all players, admins, moderators, VIPs, and test users. Features: 1. Permission-Based Plugin Control: Define permissions for different user groups to control access to specific sets of plugins. Permissions include apcontrol.use.allp, apcontrol.use.adminp, apcontrol.use.moderp, apcontrol.use.vipp, apcontrol.use.testp, apcontrol.use.pvp, and apcontrol.use.pve. 2. Configurable Plugin Lists: Each user group has its own list of plugins that can be configured and managed. Default plugin lists for each group are set in the configuration file. Added support for blacklisting plugins, which will be automatically unloaded before loading the main plugins. 3. Console Commands for Plugin Management: Server administrators can use console commands to load and unload plugins based on the user group. Commands include allp, adminp, moderp, vipp, testp, pvp, and pve. Added support for delayed execution of commands (e.g., /pvp on 300 to execute after 300 seconds). 4. Automatic Configuration Management: The plugin automatically loads the configuration on initialization and ensures it is correctly formatted. If the configuration file is missing or corrupted, a new one is generated with default settings. State of plugin execution is saved in a data file and restored upon server restart. 5. Multilingual Notifications: All messages are in English by default, but can be changed to Russian or any other language through the configuration file. Commands: allp [on/off] [delay]: Load or unload plugins for all players with the appropriate permission. adminp [on/off] [delay]: Load or unload plugins for administrators. moderp [on/off] [delay]: Load or unload plugins for moderators. vipp [on/off] [delay]: Load or unload plugins for VIP players. testp [on/off] [delay]: Load or unload plugins for test users. pvp [on/off] [delay]: Load or unload plugins for PvP scenarios. pve [on/off] [delay]: Load or unload plugins for PvE scenarios. Permissions: apcontrol.use.allp : Permission to use the allp command. apcontrol.use.adminp : Permission to use the adminp command. apcontrol.use.moderp : Permission to use the moderp command. apcontrol.use.vipp : Permission to use the vipp command. apcontrol.use.testp : Permission to use the testp command. apcontrol.use.pvp : Permission to use the pvp command. apcontrol.use.pve : Permission to use the pve command. Usage: 1. Initialization: The plugin is initialized by loading the configuration and registering permissions and console commands. 2. Loading plugins: Use the appropriate console command followed by on to load plugins for the group. Example: adminp on to load all plugins listed in the adminp group. 3. Unloading plugins: Use the appropriate console command followed by off to unload plugins for a group. Example: adminp off to unload all plugins listed in the adminp group. 4. Configuration: The configuration file defines lists of plugins for each user group. Administrators can edit the configuration file to add or remove plugins from the list of each group. { "CommandConfigs": { "allp": { "Permission": "apcontrol.use.allp", "Blacklist": [], "Plugins": [] }, "adminp": { "Permission": "apcontrol.use.adminp", "Blacklist": [ "AdminESP", "AdminMenu" ], "Plugins": [ "AdminESP", "AdminMenu", "CheckCupboard", "ConvertStatus", "ItemShortname", "PlayerAdministration", "TPOnMap", "Vanish", "XScan" ] }, "moderp": { "Permission": "apcontrol.use.moderp", "Blacklist": [], "Plugins": [ "AdminESP", "AdminMenu", "CheckCupboard", "ItemShortname", "PlayerAdministration", "TPOnMap", "Vanish", "XScan" ] }, "vipp": { "Permission": "apcontrol.use.vipp", "Blacklist": [], "Plugins": [ "TPOnMap", "XScan", "ItemShortname" ] }, "testp": { "Permission": "apcontrol.use.testp", "Blacklist": [], "Plugins": [ "Vanish" ] }, "pvp": { "Permission": "apcontrol.use.pvp", "Blacklist": [], "Plugins": [] }, "pve": { "Permission": "apcontrol.use.pve", "Blacklist": [], "Plugins": [] } }, "Messages": { "CommandUsage": "Usage: {0} <on/off> [delay]", "InvalidDelay": "The second argument must be a number indicating the delay in seconds.", "CommandScheduled": "Command {0} {1} will be executed in {2} seconds.", "ConfigFileNotFound": "Configuration file not found or empty, creating a new configuration file.", "ConfigFileLoaded": "Configuration file loaded successfully.", "ConfigFileLoadError": "Error loading configuration file: {0}", "LoadingPlugin": "Loading {0} plugin...", "UnloadingPlugin": "Unloading {0} plugin..." } } Installation: Place the APControl.cs file in the oxide/plugins directory of your Rust server. Start or restart the server to load the plugin. Configure the plugin by editing the configuration file located at oxide/config/APControl.json.
    $2.50
1.4m

Downloads

Total number of downloads.

6.9k

Customers

Total customers served.

102.1k

Files Sold

Total number of files sold.

2m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.