0xBADF00D

Because it's not possible to use the vanilla loot table for the locked crate and add a custom loot table without the plugin clearing the vanilla loot table to add my custom loot table. So if I want to use the vanilla loot table and, for example, add a custom item on top of the vanilla loot table, that's not possible unless I use the Helicrate extra loot, but I don't want to do that.

Hello, when I use this config, it spawns my item with a 100% chance in every crate instead of using my Chance (0 - 100)”: 5.0, "Extra Loot Options": { "Use extra loot table (NOTE: Total of crate loot + extra items cannot exceed 12)": true, "Minimum number extra items to add to crate": 0, "Maximum number extra items to add to crate": 1, "Allow duplication of extra items": false, "Maximum number of BPs in each crate": 2, "Extra loot table": [ { "ShortName": "supply.signal", "Chance (0 - 100)": 5.0, "Min Amount": 1, "Max Amount": 1, "SkinID": 0, "Custom Display Name (leave blank unless creating custom items)": "", "Item Text Field ('Item.text', default is blank)": "", "Blueprint Chance Instead of Item, 0 = disabled. (0 - 100)": 0.0 } ] },

Hello, can you add Extra loot table for locked crate please?

When I pick up the recycler, it doesn't have a skin, so whenever I try to rebuild it, a repair bench spawns.

I'm using Armored Train and it gets stuck in the loop. In that case, if you don't want to remove this, which I totally understand, then I suggest changing this path so that it uses the vanilla logic for a siding/parking path instead of the default path. That way, if the player wants to go around the loop, they have to choose the left or right direction. And it’s the same for me, I don’t want to add a loop detection feature to the plugin either, simply because the path doesn’t follow the vanilla logic

Yes, I know they're removed when there are foundations, but not all players are aware of that, and often they see the bushes and then leave, or maybe they just don't want to have to place foundations everywhere just to remove the bushes.

There are still some custom-built locations with bushes inside.

Hey, can you remove that blue path? Because plugins that run trains automatically and go straight ahead get stuck in that loop and never get out, and besides, that path serves no purpose.

Regarding the 1.33 update, did you check to make sure the trains run everywhere, or did you just fix the issues that were reported?

Yes, several players have told me that it bothers them. And I think it makes more sense for the bushes not to stick out above the ground. Thanks for fixing this! Even though I'd already done it, at least it'll be taken care of for the next time I need to download it again.

Hey, In every custom-built location of this type found in the jungle, there is this

You can create your own cargoship path in rustedit, or move the harbor. Or maybe the terrain isn't deep enough, I don't know, but please fix it

Same problem with the Q8 and P8 grids, and there are probably others as well

Yes, that's what I ended up doing, editing the JSON file directly, but I still wanted to report this bug

Combat Stats -> Damage Range Can't set -1 value plugin say "You have entered an invalid value for this parameter" from the GUI /preset Even though the description says, "Use -1 for unlimited range." While I'm here, I have a suggestion: it would be nice to add a toggle setting that notifies the player with a message like "You can't damage this NPC because you're too far away."

@aimacak My suggestion would be: npcspawn.preset.read - allows players to open /preset and view all presets npcspawn.preset.manage.own - allows players to create, edit, rename and delete their own presets npcspawn.preset.manage.others - allows players to edit, rename and delete presets created by other players npcspawn.preset.spawn - allows players to use /spawnpreset The following commands should use the same preset-management permissions: /SetWears /SetBelts These commands do not need separate permissions. A player with npcspawn.preset.manage.own should be able to use them on their own presets, while a player with npcspawn.preset.manage.others should be able to use them on presets created by other players. Btw these commands are missing from the plugin description, I just discovered them It would also be useful to display the preset owner’s name and SteamID somewhere in the preset GUI.

Hello, could you set up a permissions system instead of using IsAdmin please?