Marte6
-
Posts
677 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Marte6
-
IMPORTANT UPGRADE NOTICE (Breaking Changes) This version changes the configuration format and resets settings on first run. Back up your old config before updating, especially the loot tables. Make a copy of oxide/config/DungeonEvents.json. After installing the update, review the new files and manually merge your custom values—pay extra attention to the new per-tier settings and loot tables. Tier system reworked to allow creating any number of tiers. Loot config moved out of the main config into \data\DungeonEvents: one global Default_Loot.json plus per-tier files (e.g., Easy\boss_loot.json, Easy\lootbox.json, Easy\npc_loot.json). New global settings: “Prevent Drop Backpack” and “Teleport Player To Outside On Death.” New per-tier settings: “Enable Auto Spawn,” “Enable Buy,” “Marker Color Hex,” “Max Auto Spawn (0 = Unlimited),” “Max Buy (0 = Unlimited),” “Per-Tier Buy Cooldown (seconds, 0 = use global),” “Max Items Per Box,” “Max Items Per NPC,” and “Max Items Per Boss NPC.” Fixed validation for loot/NPC item rolls to avoid bugs when min or max is 0 (skips empty rolls). Buy UI rebuilt; adds scrolling automatically when many tiers exist. Startup converted to a coroutine that cleans leftover data and waits smartly based on player count for smoother restarts. Buy cooldowns are now per tier (not global), with per-user, per-tier tracking. Optional safer “teleport on death”: snaps to terrain/water surface to prevent players spawning inside terrain. Codebase refactored across the board for readability and performance. -
Changed Status from Pending to Work in Progress
-
Hello, I’ll check what it could be. I think it might be because the item is set with a minimum of 0, but I’ll also look for a way to prevent the error when that’s the case.
-
Changed Status from Pending to Work in Progress
-
Hello! Yes, a big update is coming this week — I’m going to implement that, and you’ll be able to create as many tiers as you want.
-
Hi @kin8642 ! I’m working on a big update right now and will look into this. Whenever you have this kind of issue, please open a support ticket.
-
Hey! Sorry, but that’s not possible with this plugin — it doesn’t use an actual recycler, since the recycling process is handled directly by the plugin itself. If you’d like, my other plugin, Industrial Recycler, does use a real one, and I can give you a 50% discount on it. -
I recommend that you delete this configuration and adjust what is needed in the new one that will be generated.
-
Changed Status from Pending to Work in Progress
-
Hello, from what I can see you’re using a very old version of the plugin. Please download the new one again, update it, and see if it fixes the problem.
-
Hello, what matters is the “Priority”; see which one is higher. “Name”: “Vip1”, “Need Permission”: true, “Priority (Highest priority overrides others)”: 1, -
Hello, can you send me your config file?
-
NPC's Have Vanished And Turrets Are Missing Weapons Since Update
Marte6 replied to MatthiasBM's Support Request in Support
I found the issue: loading weapon values during OnServerInitialized was causing the problem—moving that initialization into a NextTick fixed it. Please restart the server after updating the plugin for the errors to stop. **Turbo Weapons - 2.3.2 - What's New** Fix: after the latest Rust update, placing weapons in turrets (including via plugins like RaidableBases) could cause NREs—TurboWeapons now initializes weapon data post-startup with safer checks; update and restart the server to apply. -
I found the issue: loading weapon values during OnServerInitialized was causing the problem—moving that initialization into a NextTick fixed it. Please restart the server after updating the plugin for the errors to stop. -
NPC's Have Vanished And Turrets Are Missing Weapons Since Update
Marte6 replied to MatthiasBM's Support Request in Support
Hello, I’m the author of TurboWeapons. Sorry for the delay... I’ll check now to see if it might be a problem with it, and I’ll reply here and update the plugin if it’s something on my end. -
Hi, I changed the base item that used to be the arcade; now it's a small wooden box. -
@OvO Sorry about that! I just updated it and the bug should be fixed now
-
I will check right now
-
Since many requested it, I’ve updated it and now there are 8 groups. Turbo Weapons 2.3.0 - What's New New groups created from VIP1 to VIP8. New UI redesigned, now with scrolling.
-
Changed Status from Pending to Not a Bug
-
Since many requested it, I’ve updated it and now there are 8 groups. Turbo Weapons 2.3.0 - What's New New groups created from VIP1 to VIP8. New UI redesigned, now with scrolling.
-
Hi there, Thanks for the suggestion! Actually, it's already possible to disable auto spawn for a specific tier using the configuration below: "Tiers": { "Easy": { "Enabled": false, By setting "Enabled": false, the tier will be completely disabled, and no auto spawns will occur for it.
-
Oh, sorry, I didn’t quite understand — I thought you already had the dungeons and were having a conflict with the other plugin hahaha. I don't think it would cause any issues with the other plugin. I just create two portals and connect them the same way the game does with regular dungeons.
-
That option already exists in the configuration settings: "Max Active Dungeons Auto Spawn (It is not recommended to exceed 10)": 6, "Max Active Dungeons Buy (It is not recommended to exceed 10)": 6,
-
I'm not exactly sure what could be causing that. If you'd like, you can open a support ticket and mention the author of the other plugin with an @ so they can grant me access to it. I can also give them access to my plugin, and we can try to adjust things together to fix the issue.
