Jump to content

Paws4Luv's Wishlist

  1. More information about "Custom Event Manager"

    $16.99

    Custom Event Manager

    📝 Description:
    Custom Event Manager is a lightweight Rust plugin that automatically manages and rotates through server events. Instead of manually starting events, this plugin will periodically trigger them for you, picking randomly from multiple event lists and ensuring they don't repeat until all events have been cycled through. Disable timer starts in your plugins, and use the start command in the config, to avoid having multiple events run at the same time.
    This keeps gameplay fresh and dynamic for your players without requiring constant admin attention, and now includes Discord webhook integration to notify your community when events start!
    NEW in v2.3.0: Take full control of Rust's vanilla events! Disable automatic spawns of patrol helicopters, cargo planes, cargo ships, CH47s, Bradley APCs, and supply drops. Then optionally schedule them manually through the plugin's rotation system for complete server event control.
    ✨ Features
    Multiple event lists with independent rotation schedules Configurable delays between different event lists to prevent overlap Automatic event rotation at configurable intervals Smart rotation logic ensures no event repeats until all have been used Discord webhook integration with customizable notifications Vanilla event control - Enable/disable individual vanilla Rust events Manual vanilla event scheduling - Schedule vanilla events through the rotation system when disabled Admin commands to start, stop, and check the rotation status Simple JSON configuration for adding your own events Full permission system support Configuration ⚙️ Configuration
    The config file will be generated at: oxide/config/CustomEventManager.json
    Example:
     
    { "EnableOnServerStart": true, "PreventDuplicateEvents": true, "MaxRerollAttempts": 5, "EventCooldownSeconds": 60, "DiscordWebhookUrl": "https://discord.com/api/webhooks/YOUR_WEBHOOK_URL", "DiscordSettings": { "EnableNotifications": true, "BotName": "Event Manager", "BotAvatarUrl": "", "EmbedColor": 3447003, "NotifyOnEventStart": true, "NotifyOnRotationStart": true, "NotifyOnRotationStop": true, "NotifyOnCycleComplete": true }, "VanillaEventSettings": { "EnablePatrolHelicopter": true, "EnableCargoPlane": true, "EnableCargoShip": true, "EnableCH47": true, "EnableBradleyAPC": true, "EnableSupplyDrop": true }, "EventLists": [ { "Name": "MainEvents", "IntervalMinutes": 30, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": true, "Events": [ { "Name": "extraevents", "Command": "extraevents start", "Enabled": true }, { "Name": "guardedcrate", "Command": "gcrate start", "Enabled": true }, { "Name": "guessthenumber", "Command": "gtn start", "Enabled": true } ] }, { "Name": "SecondaryEvents", "IntervalMinutes": 45, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 5, "Enabled": true, "Events": [ { "Name": "roamtasks", "Command": "RoamTask start", "Enabled": true }, { "Name": "skilltreexpevents", "Command": "startxpevent", "Enabled": true }, { "Name": "convoy", "Command": "convoystart", "Enabled": true } ] }, { "Name": "VanillaEvents", "IntervalMinutes": 60, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": false, "Events": [ { "Name": "PatrolHelicopter", "Command": "spawnheli", "Enabled": true }, { "Name": "CargoPlane", "Command": "spawnplane", "Enabled": true }, { "Name": "CargoShip", "Command": "spawncargoship", "Enabled": true }, { "Name": "CH47", "Command": "spawnch47", "Enabled": true } ] } ] } Options
    General Settings
    EnableOnServerStart → Automatically start event rotation when the server starts. Default: true PreventDuplicateEvents → Prevents the same event from running across different event lists simultaneously. Default: true MaxRerollAttempts → Number of attempts to find a non-duplicate event before giving up. Default: 5 EventCooldownSeconds → Time (in seconds) before an event is removed from the global active list. Default: 60 DiscordWebhookUrl → Your Discord webhook URL for notifications. Leave empty to disable Discord integration. Discord Settings
    EnableNotifications → Master switch for all Discord notifications. Default: true BotName → The name displayed for the webhook bot. Default: "Event Manager" BotAvatarUrl → URL to an avatar image for the bot (optional) EmbedColor → Decimal color code for Discord embeds. Default: 3447003 (blue) NotifyOnEventStart → Send notification when an event starts. Default: true NotifyOnRotationStart → Send notification when rotation starts. Default: true NotifyOnRotationStop → Send notification when rotation stops. Default: true NotifyOnCycleComplete → Send notification when all events in a list complete. Default: true Vanilla Event Settings
    Control whether vanilla Rust events spawn automatically:
    EnablePatrolHelicopter → Allow automatic patrol helicopter spawns. Default: true EnableCargoPlane → Allow automatic cargo plane spawns. Default: true EnableCargoShip → Allow automatic cargo ship spawns. Default: true EnableCH47 → Allow automatic CH47 spawns. Default: true EnableBradleyAPC → Allow automatic Bradley APC spawns. Default: true EnableSupplyDrop → Allow automatic supply drop spawns. Default: true Important: When you disable a vanilla event (set to false), the plugin will block its automatic spawns. To schedule these events manually, enable the "VanillaEvents" list in your EventLists configuration and customize the interval and events as needed.
     
    Event List Settings
    Each event list supports:
    Name → Friendly name for the event list IntervalMinutes → Time (in minutes) between each event in this list. Default: 30 RandomizeOrder → Whether to randomize event selection. Default: true DelayAfterMainEvent (minutes) → Additional delay before starting this list's events (useful for preventing overlap). Default: 0 Enabled → Whether this event list is active. Default: true Events → Array of event definitions: Name → Friendly name for the event (used in status tracking and Discord notifications) Command → The console command to trigger the event Enabled → Whether this specific event is active. Default: true  
    🛠️ Permissions
    customeventmanager.admin Required to use the admin commands.
     
    💻 Commands
    /cem start - Starts the event rotation /cem stop - Stops the event rotation /cem status - Shows current status, how many events have run, and when the next one is scheduled /cem reload - Reloads the configuration and restarts rotation /cem list - Lists all configured event lists and their events /cem active - Shows currently active events globally /cem vanilla - shows the status of vanilla event settings ⌨️ Console Commands
    All chat commands can also be used from the F1 console by replacing /cem with cem:
    cem start cem stop cem status cem reload cem list cem active cem vanilla 🔧 How it works
    Multiple Event Lists: You can configure multiple independent event lists (e.g., "MainEvents" and "SecondaryEvents") that run on their own schedules Smart Scheduling: Each list tracks its interval and optional delay to prevent events from overlapping No Repeats: Events won't repeat until all events in that list have been triggered Discord Integration: Get real-time notifications in your Discord server when events start, cycles complete, or rotation status changes Duplicate Prevention: Prevents the same event from running simultaneously across different lists Vanilla Event Control: Block automatic vanilla event spawns and optionally schedule them through the plugin's rotation system  
    🔧 Vanilla Event Scheduliing
    To take full control of vanilla Rust events:
    Disable automatic spawns by setting the vanilla events to false in VanillaEventSettings: "VanillaEventSettings": { "EnablePatrolHelicopter": false, "EnableCargoPlane": false, "EnableCargoShip": false, "EnableCH47": false, "EnableBradleyAPC": false, "EnableSupplyDrop": false } 2. Enable manual scheduling by setting the VanillaEvents list to true
     
    { "Name": "VanillaEvents", "IntervalMinutes": 60, "RandomizeOrder": true, "DelayAfterMainEvent (minutes)": 0, "Enabled": true, "Events": [...] } 3. Customize the schedule by adjusting IntervalMinutes, adding/removing events, or changing the order
    This gives you complete control over when and how often vanilla events occur on your server!
    📌 Tips
    Disable built-in timers in your event plugins to prevent conflicts Use the DelayAfterMainEvent setting to stagger different event lists Set RandomizeOrder to false if you want events to run in a specific sequence Customize Discord notifications to match your server's style with the EmbedColor and BotAvatarUrl settings Use PreventDuplicateEvents to avoid the same event running twice at once across different lists Disable vanilla events and use the VanillaEvents list for complete control over server events Use /cem vanilla to quickly check which vanilla events are enabled or disabled
     
     
  2. More information about "BetterTC"

    $30.00

    BetterTC

    Rust / Server Plugins
    BetterTC
    Tool Cupboard ManagementRust Plugin
    Upgrade. Repair. Reskin. Make your base your own.
    Bring your most-used Tool Cupboard features together in one interface inspired by Rust’s item store. Automate building upgrades and repairs, manage authorizations, and personalize buildings, external walls, wallpapers and your TC.
    Automated upkeep tasks
    Upgrade and repair with TC resources
    Personalized buildings
    Skins, wallpapers and external walls
    Permission profiles
    Configure access, speed and costs
    01 / Video demo
    See BetterTC in action
    Take a look at BetterTC’s interface and building management features.
    Watch on YouTube
    02 / Skin ownership
    Compatibility with Facepunch’s server policy
    Facepunch’s policy prohibits granting paid skins or DLC to players who do not legitimately own them. BetterTC includes ownership validation for building skins, TC skins and wallpapers.
    Building skins: all available choices remain visible, but players can only apply skins they own or skins that are free. Wallpapers: only free, custom and owned wallpapers are visible. More custom wallpapers are planned. TC skins: only owned skins are visible and selectable. Read Facepunch’s official server policy
    Ownership checks are enabled with the following bypass option set to false:
    "Bypass DLC ownership check (⚠ only allowed on creative/test servers per Facepunch rules)": false ⚠ Very important
    Keep the bypass disabled on ordinary public PvP and PvE servers. Facepunch only permits temporary exceptions on servers specifically set up to test game mechanics, for testing purposes. A creative or training label alone is not an exemption. Misuse may result in delisting or other sanctions.
    03 / Building management
    Let the TC do the work
    Automatic upgrades
    Upgrade building grades using resources directly from the TC. Select the default appearance or an eligible building skin, and use the information button to estimate the materials required. Configure upgrade speed and costs through permission profiles.
    Automatic repairs
    Repair the building and supported deployables, including doors, trapdoors, windows and boxes, with resources from the TC. Configure a cooldown after recent damage to help prevent repair abuse during raids.
    Automatic reskinning
    Change a building’s appearance without manually replacing each piece. Players can switch from a skinned grade back to its default appearance when they prefer. The Container skin’s multicolor selection can also be disabled to reduce client rendering load.
    Building downgrades
    Allow players to return to a lower building grade when their base becomes too expensive to maintain. Downgrading charges resources as a fresh upgrade to the selected grade; it is not a free conversion. Disable this feature if it does not fit your server, or retain a separate administrator-only downgrade override.
    Configure NoEscape or RaidBlock integration to stop automatic upgrades, repairs, building reskinning, wallpaper placement and external wall reskinning when a raid block starts. Ownership and team restrictions are also configurable. 04 / Building skins
    Keep the available skins up to date
    The skin update checker adds newly available construction skins and their options to the configuration.
    After installing BetterTC, grant yourself bettertc.admin and click Check Update to populate the available skins and options. Applying paid content remains subject to ownership checks. 05 / External walls
    Change the look. Preserve the damage.
    Reskin stone external walls with their adobe or ice variants, or switch wooden external walls to Frontier and back. Supported external gates can also be reskinned to their available variants. The original wall’s health is preserved, so reskinning a damaged wall does not repair it.
    Recommended setting:
    "Only reskin on wall of the same grade": true Keep this enabled to use external wall reskinning as an appearance change. Disabling it allows wood-to-stone and stone-to-wood changes without a resource charge, because this wall system has no cost mechanism.
    06 / Wallpapers & TC skins
    Personalize the details
    Automatically place eligible wallpapers on walls, ceilings and floors. New game wallpapers are added to the list automatically. Use included custom wallpapers and add your own through the admin wallpaper commands. Configure placement on both sides of walls, including exterior sides. Apply wallpapers to both sides of a wall, including the exterior side when configured.
    Place wallpapers on boats with /wpb after sitting at the boat’s steering wheel. Let players change their TC’s appearance or deploy a TC with a skin, according to their permissions and ownership. Tool Cupboard skin selection
    Choose an eligible TC skin from the interface, or deploy a TC using the selected skin. BetterTC carries over the cupboard’s authorizations, contents and lock when replacing its appearance.
    Manual wallpaper tool menu
    Hold the wallpaper tool and open BetterTC’s selector with /wp or the configured input button. The default input is the middle mouse button. This menu must be enabled in the configuration and requires bettertc.wallpaper.toolmenu.
    Wallpaper rotation hammer
    Administrators can obtain a special wallpaper hammer with /wphammer. Hit a wallpapered floor or foundation with this hammer to rotate its wallpaper: 90° on square pieces and 120° on triangles.
    Configure the cloth cost of automated wallpaper placement. Building placement uses cloth from the TC; boat placement uses cloth from the player’s inventory. The no-cost wallpaper permission waives placement resource costs.
    Set "Wallpaper Damage": false to protect wallpapers from melee and ammunition damage. C4 and rockets can still damage them.
    07 / Authorization & inventory
    Manage access from the cupboard
    Authorized player list
    Show who is authorized on the TC, optionally including Steam IDs and Online, Sleeping or Offline status through the player-status permission. Hide administrators with the configured option and allow individual authorization removal with a separate permission.
    Automatic TC locks
    Use separate permissions to automatically attach a locked key lock or code lock when a TC is deployed. Code locks use a generated code, authorize the deploying player and notify them of the code; the notification masks it in streamer mode. The code-lock permission takes priority when both lock permissions are assigned.
    Additional TC storage
    Configure which additional item types the TC accepts: gunpowder, sulfur, sulfur ore, explosives, diesel barrels, CCTV cameras and targeting computers. Each item type has its own switch. Select a general inventory filter: Resources, ResourcesAndComponents or All. The ResourcesAndComponents mode also accepts supported building and utility tools.
    08 / Interface & integrations
    A panel that adapts to your players
    The panel keeps a consistent size across player UI scaling settings. Buttons rearrange automatically according to the functions the player can access. Authorization lists and construction skins support pagination. Building options can be automatically sorted by grade, or retain the configured order. Configure whether players can disable automatic construction effects. Most interface images load directly from the game client. Carbon servers use the built-in Image Module; Oxide servers use ImageLibrary. Configure game tip, chat and optional Notify or UINotify alerts, plus button colors and positioning. TiersMode and TCLevels
    When TiersMode is installed, BetterTC reads its maximum unlocked building grade for the upgrade menu. When TCLevels is installed, BetterTC adds a button to open its Tool Cupboard level-upgrade menu.
    09 / Permissions
    Choose the functions each player can use
    Assign feature permissions and configure the standard and advanced profiles to match your server. Grant the no-cost permissions carefully.
    Permission Purpose bettertc.admin Admin update checks; also used to hide administrators from the authorization list when configured. bettertc.authlist Show the authorized-player list button. bettertc.playerstatus Show each authorized player's status next to their name in the TC authorization list: Online (green) when connected, Sleeping (light blue) when disconnected with a sleeping character in the server, or Offline (red) when registered but no active or sleeping character is found. Without this permission, only the player name is shown. This permission only displays status; it does not grant authorization or removal rights. bettertc.deleteauth Revoke individual player authorizations. bettertc.use Use the standard speed and cost profile defined in the configuration. bettertc.vip Use the advanced speed and cost profile defined in the configuration. bettertc.repair Access automatic building repair. bettertc.repair.nocost Repair without resource costs. bettertc.reskin Access automatic building reskinning. bettertc.reskin.nocost Reskin without resource costs. bettertc.upskin Show building upgrade options with skins. bettertc.upwall Access external wall reskinning. bettertc.upgrade Access building upgrades. bettertc.upgrade.nocost Upgrade without resource costs. bettertc.wallpaper Access wallpaper placement. bettertc.wallpaper.nocost Place wallpapers without resource costs. bettertc.wallpaper.custom Show custom wallpapers. bettertc.wallpaper.toolmenu Access the manual wallpaper tool selector when enabled. bettertc.tcskinchange Change the TC skin. bettertc.tcskindeployed Deploy a TC with a skin. bettertc.autolock Automatically add a locked key lock when deploying a TC. bettertc.autocodelock Automatically add a locked code lock with a generated code when deploying a TC. Skin-related permissions do not replace paid-content ownership checks.
    10 / Commands
    Add custom wallpapers
    Command Purpose /addwp <skinid> <Wall|Floor|Ceiling> Chat: add a custom wallpaper for the selected surface type. addwp <skinid> <Wall|Floor|Ceiling> Console: add a custom wallpaper for the selected surface type. /wpb Chat: place wallpapers on boats; first sit at the boat’s steering wheel. /wp Chat: open the manual wallpaper menu while holding the wallpaper tool; requires bettertc.wallpaper.toolmenu. /wphammer Chat: give yourself the wallpaper rotation hammer; requires bettertc.admin. wphammer Player console: give yourself the wallpaper rotation hammer; requires bettertc.admin. wphammer <playername or steamid> Server console: give the wallpaper rotation hammer to a selected player. Adding wallpapers from chat or a player console requires bettertc.admin. Example for a wall wallpaper:
    /addwp 3356517390 Wall Console equivalent: addwp 3356517390 Wall 11 / Configuration
    Selected configuration options
    This excerpt covers the settings supplied with this description, including ownership checks, raid blocking, repairs, wallpapers and permission profiles. It is not the complete configuration file, and these supplied example values may differ from the defaults in your installed version. Edit the configuration generated by your installed BetterTC version.
    { "Check for updates when loading": true, "Bypass DLC ownership check (⚠ only allowed on creative/test servers per Facepunch rules)": false, "Use NoEscape Plugin": false, "Use RaidBlock Plugin": true, "GUI Buttons TC - Color Default": "0.3 0.40 0.3 0.60", "GUI Buttons TC - Color Active": "0.90 0.20 0.20 0.50", "GUI Buttons TC - OffsetMin": "280 621", "GUI Buttons TC - OffsetMax": "573 643", "GUI Buttons TC - AnchorMin": "0.5 0", "GUI Buttons TC - AnchorMax": "0.5 0", "Alert Gametip": true, "Alert Chat": true, "Alert Notify Plugin": false, "Notify: select what notification type to be used": { "error": 0, "info": 0 }, "Color Prefix Chat": "#f74d31", "Show Admin Auth List": false, "Show SteamID Auth List": true, "Upgrade Effect": true, "Colour Selection MultiColor Option": false, "Reskin Enable": true, "Reskin Wall Enable": true, "Only reskin on wall of the same grade": true, "Reskin Wall TC Distance (Default: 100)": 100.0, "Deployables Repair": true, "Repair Cooldown After Recent Damage (seconds)": 30.0, "Downgrade Enable": true, "Downgrade only Owner Entity Build": false, "Upgrade only Owner Entity Build": false, "Upgrade / Downgrade only Owner and Team": true, "Wallpaper Enable": true, "Wallpaper placement Cost (Cloth)": 5, "Wallpaper Damage": true, "Wallpaper both sides": true, "Force both sides including external sides": true, "Cooldown Frequency Upgrade (larger number is slower)": { "bettertc.use": 2.0, "bettertc.vip": 1.0 }, "Cooldown Frequency Reskin (larger number is slower)": { "bettertc.use": 2.0, "bettertc.vip": 1.0 }, "Cooldown Frequency Repair (larger number is slower)": { "bettertc.use": 2.0, "bettertc.vip": 1.0 }, "Cooldown Frequency Wallpaper (larger number is slower)": { "bettertc.use": 2.0, "bettertc.vip": 1.0 }, "Cost Modifier for repairs": { "bettertc.use": 1.5, "bettertc.vip": 1.0 }, "Allow Items in TC Inventory": { "gunpowder": false, "sulfur": false, "sulfur.ore": false, "explosives": false, "diesel_barrel": true, "cctv.camera": true, "targeting.computer": true }, "Downgrade Admin": true, "Use BetterTC Wallpaper Tool Menu (requires bettertc.wallpaper.toolmenu permission)": true, "BetterTC Wallpaper Tool Menu input button (FIRE_THIRD = middle mouse button)": "FIRE_THIRD", "Item Category Filter (Resources, ResourcesAndComponents, All)": "Resources", "Auto Sort Items by Grade": true } 12 / Known issue
    Unexpected default blue wallpapers
    If default blue wallpapers appear randomly, check whether TruePVE or a similar plugin is protecting wallpaper damage. Disable that wallpaper protection in the other plugin and use BetterTC’s own wallpaper protection instead.
    BetterTC’s protection reduces damage, especially from melee attacks, but does not block all damage.
    13 / Support
    Questions, ideas or a problem to report?
    Contact ninco90 on Discord for questions, suggestions or assistance.
    Custom server configuration is also available for an additional fee if you would like the plugin set up around your preferences.
  3. More information about "Injuries And Diseases"

    $19.99

    Injuries And Diseases

    What kind of survival game doesn't let you break your leg? With this plugin, players can sustain injuries and become infected with diseases. Currently there are 6 status conditions, each fully customizable through the plugin's configuration file.
     
     
     
     
     
     
     
     
    Status Conditions

    /inflict <player> concussion /cure <player> concussion Periodically blurs the player's vision. Chance to occur when a player is headshot. More likely to occur with more powerful weapons.
    /inflict <player> foodpoisoning /cure <player> foodpoisoning Forces the player to vomit  occasionally which damages their food and thirst levels. Caused by eating spoiled meat. Can be cured by drinking healing tea.
    /inflict <player> brokenleg /cure <player> brokenleg Prevents sprinting and causes damage when moving. Can happen when taking fall damage, chance increases the greater the height. Can also occur when being shot in the leg, this is more likely to happen the more powerful the weapon is.
    /inflict <player> rabies /cure <player> rabies Periodically deals damage to the victim and flashes their screen red. Can be rarely contracted from the bites of wild animals. There is no cure, it's best to put the victim out of their misery.
    /inflict <player> tapeworm /cure <player> tapeworm The effect of food and water consumption is greatly reduced. Can occur from consuming raw or uncooked meat. Easily treatable with anti-biotics (anti-rad pills).
    /inflict <player> z13virus /cure <player> z13virus Not much is known about this disease, however it is often mistaken for rabies. Something terrible occurs when the victim dies... Seems to occur when a player is bitten by a zombie (scarecrow).  
    Customization
    Each status condition has properties that can be customized through the plugin config. Here is a quick description of each of the properties.
    Enabled - Set to false to disable this condition.
    Likeliness - The chance (0 - 1.0) of this condition occurring through any means. For some conditions, like concussion or broken leg, this will be the MINIMUM chance for this to occur, and it will become more likely depending on how much damage is taken. This is only relevant for some conditions, other conditions may use items/entities to inflict players.
    Icon - The url of the icon for this condition.
    From Legshots - (Broken Leg Only) Set to false to disable this from occurring when a player is shot in the leg.
    From Falling - (Broken Leg Only) Set to false to disable this from occurring when a player takes fall damage.
    Damage Scale - The damage effect multiplier for the status condition. This will modify the damage taken for all types (hunger, thirst, ect.) not just health. For example, a value of 0.5 will do half damage while a value of 2.0 will do double damage.
    Show Duration - Set to false if you do not want player's to see how many seconds are remaining for this condition. There is a slight performance cost for this being set to true.
    Show Indicator - Set to false if you do not want a custom status framework indicator to show up for this condition.
    Cure Items - Item short names with corresponding chances from 0-1.0. The items listed will have a chance to cure the condition when consumed/used by the player. An item skin can optionally be specified, see Item Skins section.
    Interval Min Seconds - The minimum amount of time in seconds between a condition's symptom from occurring. Only relevant for some conditions.
    Interval Max Seconds - The maximum amount of time in seconds between a condition's symptom from occurring. Only relevant for some conditions.
    Duration Min Seconds - The minimum number of seconds a condition will last for.
    Duration Max Seconds - The maximum number of seconds a condition will last for.
    Move Items to Zombie - (Z13 Virus Only) Set to false to disable moving items from a corpse to the newly spawned zombie. The items will instead be left in a backpack.
    Reanimation Seconds - (Z13 Virus Only) The number of seconds before an infected player's corpse is reanimated into a zombie.
    Infliction Entities  - Entity short names with corresponding chance of inflictions from 0-1.0. The entities listed will have a chance to inflict the condition when dealing damage to a player.
    Infliction Items  - Item short names with corresponding chance from 0-1.0. The items that are listed will have a chance to inflict the condition when consumed/used by the player. An item skin can optionally be specified, see Item Skins section.
    Infliction Damage Action  - Determined the way that an infliction entity must deal damage in order to inflict a condition. The allowed values are "melee", "ranged" or "any".
    Item Skins
    You can optionally specify that only an item with a certain skin will count for Cure and Infliction items. To do so just append #<skin id here> to the end of the item shortname. If both a skinned item and a non skinned item definition are specified, then the skinned definition will take priority if applicable. For example if your config looks like this then...
    If Anti-Rad Pills with the Skin 12345 are consumed, then it has a 100% cure chance. Anti-Rad Pills with any other skin (including default) only have a 50% cure chance. Only Apples with the 67890 skin have a 100% cure chance. All other Apples have 0% cure chance (because they are not listed). "Cure Items": { "antiradpills": 0.5, "antiradpills#12345": 1.0, "apple#67890": 1.0 }, Creating Your Own Custom Status Conditions
    Please note, this is a WIP feature, there may be some bugs, please report them if you find them!
    As of v1.2.0 you can use the API method "CreateCondition" to create your own plugin that can register custom status conditions through Injuries and Diseases. But what if you're not a developer? No problem! I have created a plugin for you with a ton of configurable options for you to create your own status conditions. In either case, here are some guides for what you need to do to create your own status conditions.
     
    For Non-Developers
    If you are not a plugin developer and you would like to create your own custom status conditions then you can  download this plugin file  and edit the config that it generates to customize the status conditions how you like. Currently there is a limited amount of things you can do for a status condition. If there is a specific condition, trigger, or effect you would like included, please open a support ticket and make a suggestion! Or, if you want full freedom, you can see the developer section to create your own status condition plugin exactly how you would like.
    For Developers
    If you are a plugin developer and would like to create a plugin that adds some custom status conditions, then you can make use of the "CreateCondition" API method (see API section) to register any custom conditions you would like to add. To see a code example of how this will work you can refer to the plugin file download like mentioned in the "For Non-Developers" section above. That plugin contains some hints on how the plugin must operate to work with Injuries and Diseases. When creating a custom condition, there are certain aspects that Injuries and Diseases will handle, and others that your plugin will need to take care of. Here is a breakdown of some of those things:

    Injuries and Diseases will handle...
    Showing  status indicators Status duration and countdowns Showing infliction, cure and diagnosis messages (they need to be in YOUR plugin's localization file though) The effect that occurs on intervals and when the condition is first inflicted (you pass these methods into the CreateCondition method) Whether your conditions duration/indicator is shown (pass this into the CreateCondition method) Your plugin should handle...
    Registering conditions using the API Means of inflicting your condition (entity attack, item consumed, ect) Means of curing your condition Localization (Injuries and Diseases will reference some of these) Adding images to image library Any configuration options pertaining to your custom conditions Permissions
    injuriesanddiseases.admin  
    Required for admin commands  
    injuriesanddiseases.doctor Designates a player as a doctor Required for doctor commands  
    injuriesanddiseases.immune Player cannot be affected by any conditions Will also cure the player of any current conditions when granted Admin Commands
    /inflict <player> <condition> <revealed?> Inflicts the player with the specified condition (see status conditions section). Optionally, you can set if the status will be revealed or not. Default value is set in the config.  
    /cure <player> <condition?> Cures the player from all conditions. If the condition is specified, the player will be cured of just that condition.  
    /conditions <player> Returns a list of all the conditions a player is suffering from and includes the remaining duration.  
    /reveal <player> <condition> Reveals the condition to the player if it has no already been revealed.  
    Doctors (Optional)

    As an optional feature, you can assign a player as a doctor. Doctors can diagnose players, which will reveal to the player the condition that their are afflicted with. By default, this isn’t necessary, as players will automatically be notified of what their condition is. However, in the config, you can set it so that conditions are unknown to players until they get a doctor to diagnose them. Once they have diagnosed a player, the doctor will also be informed of how to cure the condition. Doctors can be assigned with the doctor perm, and have access to the following command:
    /diagnose Will diagnose any undiagnosed conditions of the player they are looking at. Will also recommend treatment if available.  
    Supported Plugins
    Injuries and Diseases has built in support for the following plugins:
    ZombieHorde The default config values contain support for ZombieHorde zombies to inflict the Z13 Virus The keyword in the config for zombie horde entities is "zombie" WalkingDead The default config values contain support for Walking Dead  zombies to inflict the Z13 Virus The Walking Dead plugin uses the "scarecrow" entity for their zombies, which is already included BotReSpawn If you want BotReSpawn entities to inflict a condition, use the keyword "botrespawn" in the infliction entities section of the condition config. Configuration
    Death Removes Conditions - Set to false if you want conditions to persist even when a player dies.
    Pause on Disconnect - Set to false if you want the condition timer to continue even when a player is sleeping. Set to true if you want it to pause when they are sleeping.
    Require Diagnosis - Set to false if you want conditions to be automatically revealed to player's when they are inflicted. Set to true if you want them to appear as unknown until a doctor diagnoses them.
    Show Doctor Indicator - Set to true if you want an indicator to appear for player's with the doctor permission.
    Messages Enabled - Set to false if you do not want messages to appear in the chat for player's when their conditions status is updated.
    Message Icon ID - The steam ID of the player portrait you want to appear for all chat messages from this plugin.
    Images - A list of image urls for various images used in this plugin.
    Status Conditions - Configuration for status conditions (see customization section).
    Version - Keeps track of what version your configuration was generated for, do not edit manually.
    Developer API
    With these developer API tools you can extend the functionality of existing conditions through code. You can add additional effects by making use of the various hooks for each condition.
    /* * Returns a list of all enabled conditions. */ List<string> GetConditions(); /* * Returns a list of conditions a player is inflicted with. */ List<string> GetPlayerConditions(ulong userId); /* * Returns true if the player has the specified condition. */ bool HasCondition(ulong userId, string conditionNameId); /* * Inflicts the player with the specified condition. */ void SetCondition(ulong userId, string conditionNameId, bool revealed); /* * Removes the condition for the player. */ void RemoveCondition(ulong userId, string conditionNameId, bool cured); /* * Removes all conditions for the player. */ void RemoveAllConditions(ulong userId, bool cured); /* * Reveals the condition to the player if it is not already revealed. */ void RevealCondition(ulong userId, string conditionNameId); /* * Create a custom condition. BETA */ void CreateCondition(Plugin plugin, string conditionNameId, string imageLibraryIconName, int minIntervalSeconds, int maxIntervalSeconds, int minDurationSeconds, int maxDurationSeconds, bool showDuration, bool showIndicator, Action<BasePlayer> beginEffect = null, Action<BasePlayer> intervalEffect = null);  
  4. More information about "Custom Buttons"

    $7.50

    Custom Buttons

    Create your own UI buttons for your rust server!
    Plugin comes with built ingame editor which makes creating proccess so much easier!
     
     

    • Features

    - Create as many buttons as you want.  
    - Attach Images or Text to buttons.
    - Set chat commands to each button.
    - UI Editor ingame
    - Toggle hide function to create small gui menu.


    • Commands

    • Permissions

    • Config Example

    • Cui Data Example


    Special thanks to @SinKohhfor contributing and testing plugin before release.  
     
  5. More information about "Radial Menu"

    $15.00

    Radial Menu

    The radial menu is a customizable quick access panel with all popular and frequently used server commands. It makes it a lot easier and faster to interact with various server mechanics, be it teleportation, trades, setting house points and various panels.
     
    Features
    Allows to almost completely eliminate the manual entry of commands by the player. Automatic calculation and arrangement of any number of sections/subsections on a circle. Several display effects. Tracks a press of the MMB or on command (can be keyed to the same MMB). Checks for the privileges of a particular command, before executing it. Ability to use your own panel images. Full customization of the location and scale of icons and panel. Support for popular plugins (NTeleportation,  TeleportGUI, Clans, Friends and Rust teams). Executing console or chat commands.  
    General settings
    Track MMB presses to open a radial menu?  - if the player has a MMB bind, the plugin will not open the Radial Menu.
    The command to open the radial menu  -  you can use both the command and the MMB tracking. When using MMB tracking and the command at the same time: If a player has a MMB bind, his bind will be executed when he clicks on it, and the Radial Menu will not open. If there is no bind, the player can use both the command and the MMB press.
    Upload images to players when they connect?  - when a player connects to the server, the plugin will automatically download 3 images of menu rings to his client. This avoids displaying black rectangles when opening the menu while the plugin is downloading the images to the client.
    Section/Subsection settings
    The plugin has main sections (level 1), subsections at level 1 (level 2) and subsections at level 2 (level 3).
    Section name - the name of the section, which is displayed under the icon.
    Enable this section? – on/off section.
    Section permission [required] - permission required for the plugin to work (without dots).  Add "_add" to the end of the name so that the plugin does not register or check permissions for child subsections.
    Section icon - direct link to the icon (recommended size 64x64).
    Fill icon with color below? -  Completely fills the icon with the color set below.
    Inactive/active section color  [HEX or Unity RGBA] - The plugin supports 2 types of colors: HEX (e.g. "#57de54" or "#57de54ff") and  Unity RGBA ("0.34 0.87 0.33 1").
    Command executed on behalf of the player - if you do not have subsections in this section, the command (without the "/" if chat) that will be executed for that player is specified here. You can specify multiple commands using commas (e.g. "radar ui, vanish, adminpanel hide"). If there are subsections in this section, the command is not specified.  Specify %steamid% or %username% so that the plugin replaces them with the data of the player on whose behalf the command is executed.  
    Command type  - Where to run this command: true - chat, false - console.
    Permissions for above command - if the command above is specified, you can specify the privileges of that command in this field (e.g. "removertool.normal, removertool.structure, removertool.external"). The plugin will check if the player has these privileges before executing the command.
    Show this section only to those with permissions above?  -  allows to draw the section automatically (without giving permissions to this plugin) if the player has command permissions.
    Show this section even to those who don't have permissions? - forcibly displays the section to all players, even those who do not have privileges to it (if you click on it, a message about lack of permissions will be displayed in chat).
    Subsections layout [n - number] - this setting is responsible for how subsections are arranged.
    0 - automatically. Suppose you have 10 subsections, then 360 degrees / 10 subsections = 36 degrees. The plugin will automatically position the 10 subsections every 36 degrees (clockwise, starting from the top). n - from the beginning. The plugin will arrange the subsections clockwise, starting from the top, not automatically, but in a certain step. For example, you have 3 subsections, but you do not want them to be automatically scattered all around the circle, you want them to be displayed at the top, with some small step, this step will be calculated due to the conditional number of subsections n (for example, 15). Now 360 degrees / 15 conditional subsections = 24 degrees, then your 3 subsections will be positioned from the beginning and there will be 24 degrees between them. -n - from the active item. The plugin will arrange the subsections relative to the active section. For example, you have 3 subsections, but you don't want them to be automatically scattered all around the circle, and you also don't want them to be arranged in some clockwise, starting from the top. By choosing this type of arrangement, the subsections will be located in the same place as the active section, in the increments you specify. It works the same way as above, only n is specified with a minus sign (for example, -15, the minus is needed for the plugin to understand what type of arrangement to use). All examples of the layout of the subsections are present in the standard config.
     
    Permissions
    It may be unclear how permissions work in this plugin. Let's figure it out with a simple example from the standard config.

    It's not hard to figure out that this is the home point section of the standard config. To exclude identical names of permissions the plugin converts them to this form.
    Because of the large number of permissions generated by the plugin, there are mechanics for reducing them. If you add "_all" to any section, in the "permission" field, the plugin will not register the permissions of child subsections. For example, if the player has the permission "_homes_all", then all displayed houses, all commands (add, remove, etc.), in general everything that belongs to the section "_homes_all" will obey and is checked by the permission "radialmenu._homes_all".  The "permission" fields of the child sections still have to be filled in for the plugin to work.
    I strongly recommend using the "Permissions Manager" plugin to set privileges for players or groups. It draws a simple interface, through which it is very easy to add or remove permissions.
     
    Teleportation
    The plugin supports work with teleportation plugins (set/remove/teleport to home point) NTeleportation,  TeleportGUI and Teleportation by OxideBro (for RU server owners).
    To do this, in the main section (level 1), you must specify the permission of the "_homes" section, this is necessary for the plugin to understand that it will work with the teleport plugin.
    Next, in the subsection "_homes" (level 2) you must add the MAXIMUM number of displayed house points, for example 5. If the player has more house points than this number, then only the first 5 will be displayed, if less, then all of them will be displayed. For each such point, you must set its unique name, which begins with "home_n", where "n" is any unique number or word (e.g. home_1, home_2, etc.). In addition to the house points here you can place a section with the establishment of the house point, its name should be "home_add", and the command "home add {0}" (command your plugin teleport), where {0} - the name of the new house point, the plugin itself will set it relative to the square in which the player at the moment is (for example D3, if there are several in the square, then D3h1, D3h2, etc.).
    After that, in the subsections (level 3) of each such house point, you can specify commands relating specifically to it. For example: "home {0}", "home remove {0}" or any other commands, where {0} is the name of the specific house, the plugin itself will substitute it when executing the command.
    If you find all of the above complicated, you can take a look at the standard config as an example.
     
    Friends
    The plugin supports work with plugins Friends, Clans by k1lly0u and Rust teams.
    Here everything is set up similar to Teleportation. But for the plugin to understand what to work with, in the main section (level 1) you must specify one of the three options:
    "_teammates" - the plugin will work with Rust teams "_friends" - the plugin will work with the Friends plugin "_clans" - the plugin will work with the Clans plugin In subsections (level 2) you must add the MAXIMUM number of displayed friends, for example 8. If the player has more friends than this number, then only the first 8 will be displayed, if less, then all of them will be displayed. For each friend you must set its unique name, which begins with "friend_n", where "n" is any unique number or word (for example friend_1, friend_2, etc.).
    After that, in the subsections (level 3) of each friend you can specify commands specific to him. For example: "tpr {0}", "trade {0}" or any other commands, where {0} is the nickname of the player, the plugin itself will substitute it when executing the command.
    An example of the configuration of this section is also present in the standard config.
     
    Plugin Config
    Example of plugin configuration in English
    Example of plugin configuration in Russian.  If you need Russian config, open it (RadialMenu.cs) before loading the plugin, and at the top set the variable "isRus = true".  Then save and upload this file to your server.

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
3.3m
Total downloads
Customers
12.4k
Customers served
Files Sold
175.9k
Total sales
Payments
3.8m
Processed total
×
×
  • 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.