All Activity
- Past hour
- Today
-
CharlieKillswitch joined the community -
Arsenal Jackets joined the community -
if possible could apartment.stove be made to work with simplesplitter? at the moment there are errors in console about it unable to add fuel - even though no fuel is needed thank you!
-
i opened a ticket in discord and posted my config
-
Hello maybe i missed a setting somewhere I only run one boss in the dungeons is there a setting to place the Boss Furthest from the dungeon entrance as people just go in kill him and back out without clearing it
-
Thanks for the logs. They show problems with the player entity before the SimpleStatus errors. The October 23 disconnect also has a different stack trace, involving BasePlayer and Client.Update. This suggests the SimpleStatus exception may be a consequence of the incident rather than its cause I ve prepared a fix for the destroyed-component issue in SimpleStatus 1.3.6, which I haven t uploaded yet. It addresses the SimpleStatus exception, but I can’t confirm that it will also resolve the disconnect or missing inventory AdvancedStatus is also throwing exceptions, so those are worth reporting to its developer. Once I publish 1.3.6, please test it and let me know whether the problem persists. Thanks for helping track this down
-
Idk if ur Problem is fixed, but generally the // means the line is inactive. As example: //SoundEffect(player, "assets/prefabs/missions/effects/mission_objective_complete.prefab"); <-- inactive cuz // SoundEffect(player, "assets/prefabs/missions/effects/mission_objective_complete.prefab"); <-- active. and no, thats not an update, u just fixed the Error. -
minzu joined the community -
Here's the two logs Oxide and Physgun's Only one shows me disconnecting with an error. 2026-10-17.txt 2026-10-23.txt physgun Oct-17.txt physgun Oct-23.txt
-
Miguel changed their profile photo -
Thank you very much for your kind words and for taking the time to leave a review — I’m really glad you liked the plugin. I will continue working to make it even better. -
dayala901 joined the community -
Rinne changed their profile photo -
Trap_Fr changed their profile photo -
420comp joined the community -
Changed Status from Pending to Closed
-
root1222 changed their profile photo -
RikaGmingCat changed their profile photo -
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Hi, Thanks for the follow-up, and sorry for leaving this request open for so long. As you mentioned in your last reply, this was an unusual case and you were going to report back if it happened again. Since there have been no further reports here, I'll close the request for now. If it happens again on the latest versions, please reopen it or create a new request with your VoteSystem, CustomRewards and SkillTree versions, whether you're using Oxide or Carbon, the full relevant error with sensitive information removed, and the steps that trigger it. That will help establish whether there's an interaction between the plugins or another cause. Thank you for your feedback!
-
Hi, First of all, I'm sorry for the extremely late response. I understand that you wanted players to receive RP every time they vote, rather than having to create a separate catalogue reward for every possible vote. Custom Rewards uses a progression-based catalogue: 1 point unlocks the first reward, 2 points the second, and so on. Claiming a reward doesn't spend those points, and an already-claimed catalogue reward isn't automatically reset by the next vote. That distinction explains why the setup you described didn't behave as expected. The plugins have received updates since this report. If you still want help setting up a reward for every vote, please send your current VoteSystem and CustomRewards versions, the plugin you use for RP, and the relevant reward configuration with private information removed. Please also confirm whether you want RP awarded automatically or claimed through a command/UI, so I can advise on the appropriate setup. Since this request is quite old and refers to the previous versions, I'll close it for now. If you still need assistance, please reply/reopen it or create a new support request. Again, sorry for the lack of support at the time.
-
Changed Status from Pending to Closed
-
Hi, I'm sorry for the extremely late response and for leaving you without the setup information you needed. In the current Custom Rewards 2.0.4, reward catalogues are stored in oxide/data/CustomRewards_rewards/, not in oxide/config/. Loading the plugin creates an example.json catalogue when no catalogue exists. Each reward type has its own JSON file. You can use the Custom Rewards configurator linked on the product page to create or edit a catalogue, then export it to oxide/data/CustomRewards_rewards/<Name>.json. Review the reward actions, configure a unique chat command, enable the catalogue and reload the plugin. Players need the matching customrewards.<name>.use permission. Please back up your existing CustomRewards data before updating. If the latest version still doesn't create the example in an empty catalogue folder, send me your plugin version, whether you're using Oxide or Carbon, and the console output when it loads. I'll close this request for the old version now, but feel free to reply/reopen it or create a new request if you still need help. Again, sorry for the delayed support.
-
Changed Status from Pending to Closed
-
Hi, First of all, I'm sorry for the extremely late response, and thank you for including the error log. The exception was raised inside VoteSystem's Top-Serveurs check callback. The log alone doesn't tell me whether the original cause was the API response, the configuration or the plugin's handling of that response. VoteSystem and the vote-site integrations have changed since this report, so I can't reliably diagnose the original issue or confirm whether it still occurs in the current version. If you're still experiencing this after updating, please send your current VoteSystem version, whether you're using Oxide or Carbon, the relevant Top-Serveurs configuration with the API key/token removed, and the current console error. If available, include the provider's response with sensitive information removed as well. Since this report concerns an old version, I'm going to close it for now. If the issue persists, please reply/reopen the request or create a new one with those details and I'll investigate. Again, sorry for the lack of support at the time.
-
Changed Status from Pending to Closed
-
Hi, Sorry for the very late reply. Your question refers to the old 1.0.4 configuration. In the current Raid Time Protection 2.0.0, you configure the time when raids are allowed; protection applies outside that window while Global Protection is enabled. For protection OFF at 12:00 and back ON at 00:00, set an allowed raid window starting at 12:00 with a duration of 720 minutes (12 hours) for each day you want this schedule to apply. This allows raids from noon until midnight and protects eligible targets from midnight until noon. Check that the configured UTC offset matches the timezone you want to use. It is a fixed offset and does not adjust automatically for daylight saving. You can check the current rule with /raid_date. The product page also links to the configurator and schedule guide. Back up your existing configuration before updating and verify the schedule on a private server first. I'll close this request for the old version now. If you still need help with the current configuration, feel free to reopen it and send your schedule settings and intended timezone. Again, sorry for the delay.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
@Fruster Thanks for the update. The last few changes have been great. Keep it up. Today, since I was here picking up the update, I went ahead and left a review. Thanks again!
-
Definition of a Great Plugin: Keeps Players Engaged Has PvE Settings to make event/loot protected Can be configured for someone to solo, or as many as 20 players. Ability to adjust loot tables. Configurable NPCS, Health, Roam, Vision, Damage Dealt, Damage Received, Distance Pursued, Distance Invulnerable and much more. Add Chance Percentage for Bradley To Join Event Add Chance Percentage for Heli(s) To Join Event, and when to join and how far to fly before they arrive, etc. For only $19.99, I think this is one of the best plugins you can purchase here on Codefling. I've been managing plugins for several years now and I am pretty conservative when it comes to choosing a new plugin for our server. They have to be a value in both price & playability. Also, I am rating this plugin on free of issues, always up-to-date, melds well with Bradley Tiers, Skill Tree, Server Rewards and Economics. I've been running this plugin for a few years. Look, Rust is a great game in itself. The need for Events in my opinion is more miss than hit. But, if you want to give something to your players that they will look forward to, this is the one. It's up there with Raidable Bases, BotReSpawn & Convoy, in my opinion. It can be set up not to spawn in, until a player count is reached, giving players an added challenge when the Tier 3 Monuments are getting locked down by other players. You can choose both manual settings or automatic settings. You can save alternate configs so you can do Harder Events where you can make it 5x as hard for such an event, then swap the config back and but it back to the way it was, so players can enjoy the event size you would normally run. Bottom Line, it's fun to config this plugin, because you can really set it up to your preferences across the board. Oh, and today it's $15.99? I'm not sure for much longer? I would get this plugin for sure at that price!
-
I mean, unless the most recent update addresses this specifically, it's definitely still an issue. On Armored Train, Caravan, and Convoy. It's been very consistent across these plugins for as long as I've operated my server. These are the only Events I have on my server that don't properly report to GUI announcements.
-
Excellent!
