The_Kiiiing

Say goodbye to configuration and data files. This plugin lets yo edit the loot of (almost) every lootable object directly over a custom UI. It also includes a graphical stack size editor thus making it ideal for anyone who is not familiar with editing config files. Do not use in combination with any other stack size controller or loot plugin. NEW with version 2.2.7: You can now add new items to all your configurations with the click of a button on the settings page. This only works for items that have been newly added with the last rust update. Amount and drop chance will be set to the vanilla values. This can also be done via command loottable add_new_items NEW with version 2.1.16: Improved item search You can now search for hidden items by adding h: to the start of your search (e.g. the search h:cable will show the cable tunnel item which is hidden by default). This works in both item editor and stack size controller. Full support for CustomItemDefinitions NEW with version 2.1.7: Direct Loot Refresh Players with the permission loottable.test can use a button to directly refresh the loot in the crate they are currently looting. Features: User friendly GUI - no need to edit config files Loot configuration for every prefab in the game Stack size controller supports individual stack sizes for every prefab Support for custom items Support for third party plugins Fully backwards compatible with version 1.x.x Default config included for every prefab Configuration for Smelting Speed, Recycler Speed and Efficiency Supply Drop configuration Supported prefabs: Crates, Barrels NPCs Trees, Ores, Animal corpses Excavator, Quarries Christmas Presents, Eggs, Loot Bags Collectables like Hemp, Corn, etc. Additional Configuration: Smelting Speed Supply Drop Recycler Speed / Efficiency Commands: loottable - Open the Loottable UI loottable reload - Manually refresh loot loottable remove_dlc_items - Remove all DLC items from your loot configs. This action can not be undone loottable add_new_items - Add all new items from this months rust update to your configurations. This action can not be undone Permission: loottable.edit - Required to use the Loottable UI Required Dependencies (Oxide only): Image Library: https://umod.org/plugins/image-library Translations: This plugin fully supports translation. Out of the box only english is included. For item names to be translated, the plugin https://umod.org/plugins/rust-translation-api is required. English translations are located in /oxide/lang/en/Loottable.json For Developers: Loot Api: Developers can use the Loot Api to register loot profiles for custom NPCs or other plugin related loot. It is highly recommended to use the provided wrapper to access the API. Documentation is also included: https://gist.github.com/TheKiiiing/53a37e8bbb48d8a24c8e8b21b9da37ac Loot Api Example: void OnLoottableInit() { LoottableApi.ClearPresets(); LoottableApi.CreatePresetCategory(this, "Crates"); LoottableApi.CreatePreset(this, "c_locked", "Locked Crate", "crate_hackable"); LoottableApi.CreatePreset(this, "c_elite", "Elite Crate", "crate_elite"); LoottableApi.CreatePreset(this, "c_military", "Military Crate", "crate_military"); LoottableApi.CreatePreset(this, "c_normal", "Normal Crate", "crate_normal"); LoottableApi.CreatePresetCategory(this, "NPCs"); LoottableApi.CreatePreset(this, true, "npc_cargo", "Cargo Ship NPC", "npc_militunnel"); LoottableApi.CreatePreset(this, true, "npc_control", "Control Center NPC", "npc_militunnel"); } void SpawnNpc() { // Spawn NPC here ScientistNPC npc; // Assign a loot preset to the NPC LoottableApi.AssignPreset(this, scientist, "npc_control"); } void SpawnCrate() { // Spawn crate here LootContainer crate; // Assign a preset to the crate if (LoottableApi.AssignPreset(this, container, "c_locked")) { // The container has been filled with loot return; } else { // The container is not handled by Loottable // Default loot logic goes here } } The resulting configuration page would look like this: Custom Items API: Developers can use the Custom Items Api to add a custom item to the Loottable item list. If an item is marked as persistent it will remain in the custom item list until it is removed by ClearCustomItems. All non-persistent items will be removed after the plugin that registered them has been unloaded. (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, bool persistent) //(v1.0.27 or higher) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName, bool persistent) //(v1.0.27 or higher) (void) ClearCustomItems(Plugin plugin) //(v1.0.27 or higher) Hooks: (void) OnLoottableInit() This hook is called when Loottable is ready to receive API calls. This happens either on server boot or when the plugin is loaded. Use this hook to register custom items and loot presets. (object) OnContainerPopulate(LootContainer container) This hook is called every time a loot container is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that crate. (object) OnCorpsePopulate(LootableCorpse corpse) This hook is called every time an npc corpse is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that corpse. (object) OnCustomAirdrop(SupplySignal signal) This hook is called every time a custom supply drop is about to be delivered. Returning a non-null value will cancel the custom supply drop. Outdated documentation for Version 1: New with version 1.0.27: Custom Items can now be created and edited directly in the GUI. They can be created from any existing item and modified in the Item Select menu You can now create and load backups of your configuration. Commands (F1 or Server Console): loottable.backup load <name> - Load backup with the given name from the backups folder (will wipe your current configuration) loottable.backup create <name> - Create backup of everything with the given name Backups will be created in the data/Loottable/backups folder. To load a backup, the backup file needs to be present in that folder. When creating backups in the in-game console, the permission loottable.debug is required. IMPORTANT: DO NOT LOAD BACKUPS FORM SOURCES YOU DO NOT TRUST, they might cause harm to your server New with version 1.0.16: Custom Items: Now you can add custom items used by other plugins directly to your loot table. Other plugins can can register these items using the api (documentation below). Screenshots: Overview of crates and their current loot table Stacksize Editor Commands: loottable - Open the editor loottable refresh - Manually refresh crate loot loottable flags - List available flags (explained below) loottable flags <name> <1|0> - Enable / disable a certain flag loottable reload_vanilla_profiles - Manually re-download vanilla loot profiles (only for debuging) Permission: loottable.edit - Required to use the editor Flags: There are flags to disable some limits in the editor. Only enable these flags if you really need to as they might cause unexpected behavior of the editor. There are currently 3 flags available: Debug If enabled, the Debug flag provides more detailed information about errors and other actions in the editor. Don't enable this flag unless you want your console full of spam. UnlockGatherMultiplier allows you to use gahter multipliers less than one and higher than 1000. Note that multipliers less than one might lead to unexpected results in some cases. DisableItemLimit Probably the safest flag to use is DisableItemLimit as it simply lets you set stack sizes and every other item amount in the editor as high as 2,147,483,647 which is the biggest possible value of a 32-bit integer. UnlockFurnaceMultiplier lets you use any value as the furnace speed multiplier. Don't enable this flag unless you know what you are doing, since the default value range from 0.1 to 100 should cover most use cases and larger values might impact server performance. UnlockItemMultiplier unlocks the multiplier when multiplying a loot table. DisableStackingHooks will disable all stacking related hooks. Enable if you encounter problems when stacking items. RefreshLootOnExit controls if all crates get refreshed after closing the editor or when reloading the plugin. Enable this only for testing, there might be an increase in entities. Refer to the Commands section for more information about enableing flags. Vanilla Configurations: Since version 1.0.7 there are vanilla loot profiles available for most crates and NPCs. These profiles can be loaded using the "Load default loot table" button at the top center of the editor. DISCLAIMER: The vanilla loot profiles in the editor might not exactly match the vanilla loot distribution of the game as it uses a completely different loot distribution system than Rust. These profiles rather serve as a reference point for custom loot profiles. Important for Carbon users: In order for this plugin to work with carbon, Harmony references need to be enabled. This can be done with the following command: c.harmonyreference 1 Required Dependencies (Oxide only): Image Library: https://umod.org/plugins/image-library Custom Items API: Add a custom item to the item list. If an item is marked as persistent it will remain in the custom item list until it is removed by ClearCustomItems. All non-persistent items will be removed after the plugin that registered them has been unloaded. (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, bool persistent) //(v1.0.27 or higher) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName, bool persistent) //(v1.0.27 or higher) (void) ClearCustomItems(Plugin plugin) //(v1.0.27 or higher) Example: Its recommended to delay the call a little bit to make sure Loottable is loaded private void Init() { timer.In(1f, () => { Loottable?.Call("AddCustomItem", this, -946369541, 2664651800, "High Quality Fuel"); }); } Hooks: (object) OnContainerPopulate(LootContainer container) This hook is called every time a loot container is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that crate. (object) OnCorpsePopulate(LootableCorpse corpse) This hook is called every time an npc corpse is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that corpse. (object) OnCustomAirdrop(SupplySignal signal) This hook is called every time a custom supply drop is about to be delivered. Returning a non-null value will cancel the custom supply drop.

This plugin brings a completely new wounding system to your server. When players get wounded, they will have to wait for a medic to pick them up, otherwise they will respawn after a predefined time. Medics can see the position of wounded players on the map and get a chat message informing them about newly wounded players. While a player is wounded, they can not be picked up or killed by other players. Features: Highly customizable Wounding system is only active if enough medics are online Wounded players can not be picked up or damaged by other players Medics can see the position of wounded players on the map Time until respawn can be adjusted in the config A custom message to be displayed to wounded players can be set in the config Ideal for roleplay servers New Features in vesion 1.0.1: A payout can be configured for medics for reviving players and for working a certain time (To disable payouts, just set the payout amount in the config to 0) Players can no longer hurt active medics (can be disabled in config) Active medics can no longer hurt players (can be disabled in config) Medics now have a configurable cooldown for using weapons after they stop working New Features in version 1.0.2: ZoneManager is now supported Medic system can be configured to only work in certain zones Medic system can be blocked in certain zones New Features in version 1.0.3: Added support for ServerRewards and Economics Added the option to disable crawling for wounded players Wounded players can now be revived by everyone with a configurable chance of success Added game tips for medics (can be disabled in config) Moved chat messages to lang file How it works: Players with the permission medic.medic can type /medic in the chat, then they are active medics and get notified about wounded players. If the system is active, only medics can pick up players by holding right-click on them with a medical syringe. In the config there is a number that determines how many medics have to be active for the system to work. If not enough medics are active, the default wounding system will be used. The command /medicinfo informs players about the number of currently active medics and wether the default wounding system is active. Configuration: { "Wounded time before death (seconds)": 300.0, "Health after player has been revived (0 = start health)": 0.0, "Reset metabolism after player has been revived": true, "Use default wounding if less than x medics are active": 2, "Display message to wounded players": "You are currently wounded and a medic has been informed", "Medic symbol (should be rectangular)": "https://i.imgur.com/3CDQncQ.png", "Medic symbol position on screen": { "x": 0.29, "y": 0.03 }, "Medic symbol size on screen": { "x": 0.07, "y": 0.07 }, "Map marker color for wounded players (in hex format)": "FF0000", "Language Settings": { "medic_start_shift": "You are now working as a medic", "medic_end_shift": "You are no longer working as a medic", "medic_info": "There are currently {0} active medics, the default wounding system is {1}", "medic_revived": "{0} has been successfully revived by {1}", "player_revived": "You have been revived by {0}", "medic_wounded": "{0} is wounded at {1}. Without medical aid, {0} will die in {2} seconds", "medic_death": "Any help came too late for {0}. {0} is dead now", "medic_payout": "You received {0} x{1} as a payout for your work", "medic_revive_payout": "{0} x{1} has been added to your account for reviving {2}. You will receive it at the end of your shift.", "medic_no_damage": "You can not hurt an active medic!", "medic_no_attack": "You can not hurt other players while you working as a medic", "medic_attack_cooldown": "You can not hurt other players because you recently worked as a medic. Remaining cooldown: {0} seconds.", "enabled": "enabled", "disabled": "disabled", "wounded": "wounded" }, "Currency item shortname": "scrap", "Currency item skin id": 0, "Currency item custom name": "", "Minimum coherent work time for work payout (in minutes)": 10.0, "Work payout amount per time defined above": 50, "Payout for reviving player": 10, "Active medics can not be hurt by other players": true, "Active medics can not hurt other players": true, "Cooldown for attacking players after medic stopped working (minutes)": 5.0, "Zone restrictions (0: none, 1: Allow Medic only in specified zones, 2: Don't allow Medic in specified zones)(reqires ZoneManager)": 0, "Zone list: (zone ids)": [ "zone1", "zone2" ] } Permissions: medic.medic - Permission for medics medic.debug - Debug permission (explained below) Required dependencies: Marker API: https://codefling.com/plugins/marker-api Image Library: https://umod.org/plugins/image-library Zone Manager (optional): https://umod.org/plugins/zone-manager Developer API Check whether a player will become wounded or die when damaged (bool) CanDie(BasePlayer player) Check if the default wounding or the custom medic system is active (bool) UseDefaultWounding() Debuging: Players with the permission medic.debug have access to the command /recover which allows them to pick themselves up when they are wounded. Useful when testing the plugin.