-
Posts
42 -
Joined
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by aomuu
-
Return to vanilla stack sizes when going into inventory
aomuu replied to BetterDeadThanZed's Support Request in Support
Changed Status from Pending to Fixed Changed Fixed In to 1.5.0 -
Return to vanilla stack sizes when going into inventory
aomuu replied to BetterDeadThanZed's Support Request in Support
The plugin assumes a setup where World Stack Size > TC Stack Limiter, but in your case, it seems you have it set as World Stack Size < TC Stack Limiter, is that correct? I’d like to first make sure I understand the situation correctly, so please let me know if I’m mistaken. -
Return to vanilla stack sizes when going into inventory
aomuu replied to BetterDeadThanZed's Support Request in Support
What plugin do you use to change the stack count? -
Version 2.00
10 downloads
Revolutionize your Rust gaming experience. One Hit Skinning is a lightweight and practical plugin that allows players to harvest animal carcasses with a single hit and collect all resources instantly. Key Futures - Customizable tool whitelist - Permission-based usage restrictions - Automatic inventory storage + ground drop support - Lightweight, fast, and simple design Perfect for PvE servers, fast-paced PvP, or beginner-friendly servers. Bring a smooth and satisfying harvesting experience to your server today! Permission onehitskinning.use - Only players with this permission can use the feature. Config { "Configuration Version (do not modify)": "2.0.0", "Allow all tools to skin (true = any tool works, false = use allowed tools list)": false, // "true": All damaging items including guns "Global harvest multiplier (1.0 = normal, 2.0 = x2)": 1.0, "Item-specific multipliers (final rate = global × item multiplier)": {}, "List of tools allowed for skinning (only used if 'Allow all tools' is false)": [ "rock", "bone.knife", "knife.combat", "butcher.knife", "machete", "hatchet", "stone.pickaxe", "pickaxe", "salvaged.cleaver", "salvaged.axe", "salvaged.icepick", "salvaged.sword", "longsword", "pitchfork", "mace", "bone.club", "spear.wooden", "spear.stone", "chainsaw", "jackhammer", "knife.skinning" ] "Enable debug mode (shows detailed skinning information in console)": false } Example { "Global harvest multiplier (1.0 = normal, 2.0 = x2)": 1.0, "Item-specific harvest multipliers (final rate = global × item multiplier)": { ["bearmeat.raw"] = 2.0f, // Global harvest * Item-specific harvest = 2.0 ["wolfmeat.raw"] = 1.5f, // Global harvest * Item-specific harvest = 1.5 ["fat.animal"] = 1.2f, // Global harvest * Item-specific harvest = 1.2 ["bone.fragments"] = 0.8f, // Global harvest * Item-specific harvest = 0.8 ["cloth"] = 1.5f, // Global harvest * Item-specific harvest = 1.5 ["leather"] = 1.3f // Global harvest * Item-specific harvest = 1.3 } } { "Global harvest multiplier (1.0 = normal, 2.0 = x2)": 2.0, "Item-specific harvest multipliers (final rate = global × item multiplier)": { ["bearmeat.raw"] = 2.0f, // Global harvest * Item-specific harvest = 4.0 ["wolfmeat.raw"] = 1.5f, // Global harvest * Item-specific harvest = 3.0 ["fat.animal"] = 1.2f, // Global harvest * Item-specific harvest = 2.4 ["bone.fragments"] = 0.8f, // Global harvest * Item-specific harvest = 1.6 ["cloth"] = 1.5f, // Global harvest * Item-specific harvest = 3.0 ["leather"] = 1.3f // Global harvest * Item-specific harvest = 2.6 } }$2.99 -
Calling hook OnMaxStackable resulted in a conflict between the following plugins: StackSizeController
aomuu replied to World_Gamerz's Support Request in Support
Changed Fixed In to 1.4.0 -
Calling hook OnMaxStackable resulted in a conflict between the following plugins: StackSizeController
aomuu replied to World_Gamerz's Support Request in Support
Changed Status from Pending to Fixed -
Calling hook OnMaxStackable resulted in a conflict between the following plugins: StackSizeController
aomuu replied to World_Gamerz's Support Request in Support
You cannot completely remove it without changing the code on the StackSizeController side. Although the conflict has been avoided, we recommend using Loot Table & Stacksize GUI -
Version 1.5.0
18 downloads
TC Stack Limiter lets you set custom stack limits for items inside the Tool Cupboard (TC). It’s a great way to control how much stuff players can store in the TC and help keep the game balanced. Can this plugin do that? Server operators can manage game balance by adjusting the number of items that can be stored in a TC. Key Future * Change the global stack size of items: by setting a global stack multiplier, you can change the stack size of a particular item. * Item Stack Limit in Tool Cabinet: Apply a specific maximum stack number to wood, stone, Metal Fragments, and HQMs set in the Cabinet Stack Override. (e.g. if wood: 1000 is set, only a maximum of 1000 pieces of wood can be stacked in the tool cabinet). * Notification: If enable notification is set to true, items that exceed the stack limit will be automatically returned to the player's inventory and the player will be notified. * Handling of items exceeding stack limit: If a player attempts to place an item in the tool cabinet that exceeds the limit, the excess will be returned to the player's inventory. If the player's inventory is full, the item will be dropped to the floor. Compatibility * StackSizeController * Loot Table & Stacksize GUI Although this plugin is compatible with StackSizeController, an error is triggered every time an item is placed into a Tool Cupboard due to an issue on StackSizeController's side. For this reason, we recommend using Loot Table & Stacksize GUI instead. Admin Commands /tcstack list - Displays the current configuration. /tcstack set <item shortname> <amount> - Sets the TC stack limit for the specified item to <amount>. /tcstack remove <item shortname> - Removes the stack limit (reverts to the normal stack size in the TC). /tcstack reload - Reloads the configuration. Config { "Cupboard Stack Overrides": { "wood": 1000, "stones": 1000, "metal.ore": 1000, "metal.fragments": 1000, "hq.metal.ore": 100, "metal.refined": 100, "lowgradefuel": 500, "crude.oil": 500 "fat.animal": 1000, "cloth": 1000, "bone.fragments": 1000, "charcoal": 1000, "horsedung": 500, "fertilizer": 1000, "scrap": 1000 }, "Enable Notifications": true, // Toggle whether players receive a message when an item exceeds the stack limit. "Priority Mode (TCFirst or InventoryFirst)": "TCFirst", // "TCFirst": Try placing excess items in other TC slots first, then. "InventoryFirst": Try returning to player's inventory first, then TC. "Enforce TC Limits": true, // Whether to actually apply stack limits in the TC. If disabled, limits are only visual. "Split Excess Stacks": true, // If enabled, automatically split items into valid stack sizes when inserting into the TC. "Override Other Plugins for TC": true // "true": Prioritize TCStackLimiter values inside the TC. "false": Use the minimum stack size between TCStackLimiter and other plugins. }$2.99 -
I want a way to register multiple items at once. -
いくつかのツールを使って一筆で集めることはできません。 -
I would love to have a switch in the fridge as well, since food is now rotting! -
Permissions: FirstCommand.use FirstCommand.admin FirstCommand.multi These were all incorrect, and the correct PERMISSION was the following Please refer to the following. Permissions: FirstConnect.use FirstConnect.admin FirstConnect.multi -
Buttons like add, save, etc. don't work.
- 1,050 comments
-
- 1
-
-
- #loot
- #customloot
- (and 13 more)
-
It is much easier to see! Thank you for your response! -
The quality of the streaming video is poor. Can you do something about it?
-
I am happy to see more things I can do to edit the Loot Table, but I am stressed that the UI has become harder to see and use. Also, the weather in Ore is not reflected.
-
I accidentally registered for the service while exploring to start selling. I would like to delete this.
-
The permissions for the buttons/panels created do not seem to be reflected. -
I can't get the Loot table to apply to the NPCs coming out of APC.
-
I have verified this and it is probably a bug on the game side. It seems that tags for people who have never teamed up (no history) are not dropped, while tags for people who have teamed up at least once (even if they have been disbanded) are dropped. -
Loottable may not be called regularly.
