-
Posts
902 -
Joined
-
Last visited
-
Days Won
12
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by Martian
-
Recycler limits are controlled by these config options: Standard MaxRecyclers Industrial MaxRecyclers Vip1 Standard MaxRecyclers Vip1 Industrial MaxRecyclers Vip2 Standard MaxRecyclers Vip2 Industrial MaxRecyclers There was an issue where purchase and give commands did not consistently count recycler items that were still in the player's inventory. This could allow players to obtain more recyclers before placing them. This has been fixed in version 1.9.0. The plugin now checks both placed recyclers and recycler items in the player's inventory. Players with industrialrecycler.admin remain unlimited.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.9.0
-
This error means the industrial storage sorter found a null or invalid item entry while sorting the container. The plugin had a few transfer and stacking paths that could leave an invalid item reference after an item was fully consumed or removed. These paths have been rewritten, and the recycler now cleans invalid entries from its containers before processing transfers. This is included in version 1.9.0. If the same error still appears after updating, please send a new log so I can check whether another plugin is modifying the same industrial storage.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.9.0
-
Thank you for the detailed report. You were correct about the cause. Both player.inventory.Take() and item.Remove() could affect the same stack, leaving an invalid item reference in the collected inventory list. I rewrote the purchase deduction process so it creates a removal plan first and then safely consumes each stack only once. Purchases containing several different resource types, split stacks, or repeated cost entries are now handled correctly in version 1.9.0.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.9.0
-
Thanks for the error log. The issue was in the purchase item removal process. The plugin could keep references to item stacks after they had already been removed, causing the NullReferenceException when processing the next purchase requirement. This has been fixed in version 1.9.0. Purchase resources are now validated first and each stack is only consumed once.
-
1.9.0 - What's New Fixed weapon attachments being sent to the player's inventory instead of the recycler output storage. Fixed purchase errors when using multiple resource types or split item stacks. Fixed cases where resources were deducted but the recycler was not delivered. Fixed purchase command conflicts that could bypass the purchase UI and resource costs. Fixed recycler limits not counting recycler items in player inventories. Improved industrial storage item handling to prevent sorting errors. Improved purchase safety with duplicate-click protection and automatic refunds on delivery failure.- 73 comments
-
- 1
-
-
- #recycler
- #industrial
- (and 2 more)
-
Another player has also opened a support ticket reporting an error with the recycler purchase and provided some additional details. I’ll investigate the issue and should have an update ready tomorrow.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.8.94
-
Changed Status from Pending to Fixed Changed Fixed In to 1.8.94
-
3.9.6 - What's New Improved NPC behavior when players try to attack from behind walls or corners. NPCs now react better when they are damaged but cannot clearly shoot back. Added better combat memory, so NPCs can keep pressure on the last known attacker for a short time. NPCs can now try to reposition when they lose sight of a player during combat. Nearby NPCs can now be alerted when another dungeon NPC is attacked. Added small movement adjustments during combat so NPCs feel less static while fighting. Improved animal spawning support for servers using Rust’s newer navmesh system. Improved dungeon light cleanup/save handling. -
Changed Status from Pending to Fixed Changed Fixed In to 3.9.6
-
Changed Status from Pending to Not a Bug
-
Hello, yes, that’s normal. The dungeon is at the maximum height. If it goes higher than that, problems occur and it won’t be built because there is a limit in the game.
-
Changed Status from Pending to Can't Reproduce
-
Hi there, I tested this on my side and couldn’t find anything wrong with the loot system itself. The NPC loot is dropping according to what is configured in: oxide\data\DungeonEvents\Easy\npc_loot.json or, if no specific loot file is being used: oxide\data\DungeonEvents\Default_Loot.json From what you described, it sounds like another plugin may be interfering with the corpse/bag or loot behavior. I’m not sure which one could be causing it, but I’d suggest checking any plugins that modify NPC corpses, bags, death handling, or loot drops. You can try temporarily disabling those related plugins one by one to see if the issue stops happening.
-
I’ll see what I can do. Maybe I can update it so the dungeon spawn points work in fixed areas
-
NewNavmesh support is being investigated. The plugin currently uses custom movement inside procedurally generated dungeons because Rust’s native navmesh does not cover dynamically spawned dungeon structures.
-
Changed Status from Pending to Fixed Changed Fixed In to 3.9.5
-
3.9.5 - What's New Improved purchased dungeon portal placement. Updated animal compatibility after the latest Rust changes. Replaced the old wolf with the new wolf model used by Rust. Existing configs will automatically update old wolf entries to the new wolf. Improved gen2 animal head movement so they face the player correctly. Added a new admin-only console/RCON command to reload the configuration without restarting the plugin. Improved NPC behavior when players hide behind walls or corners. NPCs now try to relocate when they are being attacked but cannot shoot back. Improved boss spawning priority, so bosses are less likely to be skipped when the dungeon has limited spawn points.
-
Changed Status from Pending to Fixed Changed Fixed In to 3.9.5
-
Hi hairybeanstalk, Thanks for the report. I checked this behavior and added an improvement for it. NPCs should now react better when they are being attacked but cannot properly shoot back. Previously, if a player abused a wall/corner angle, the NPC could stay in place and keep taking damage without relocating. With the new update, when an NPC is hit and does not have a clear line of sight to the attacker, it will try to move/reposition so it can engage the player instead of standing still. This should make wall-peeking/headshot cheesing much harder. Best regards.
