All Activity

Yes there was a major update for version 2.0.0 where the old data files wore not compatible with the new versions. Im guessing @MerlinTheWizard95you have fixed the issue by removing the data folder also?

Hi nivex, Here are the requested files: /oxide/data/RaidableBases/Base_Loot/ (folder) /oxide/data/RaidableBases/Difficulty_Loot/ (folder) /oxide/data/RaidableBases/Profiles/ (folder) /oxide/config/RaidableBases.json (file) Please check them and let me know what is wrong. Also, I have the paid version of the plugin from Codefling. Version 3.1.3 is currently installed. Thank you for your help. archive-2026-05-11T213400+0300.tar.gz 14.89 KB RaidableBases (1).zip

Yeah, something is wrong with your version of the map.

I tried on a bigger map and it seems i have less suicide .... maybe it was the problem ...

Thanks for your help. This tp gate looks so cool that I don't want to give it up and switch to /gate If you have a moment, please take a look at the issue with 2 sides! Thanks again!

As far as I've tested, everything should actually be fine. I'll check the backpacks again tomorrow, though, and let you know if you need to fix anything or not.

If you enter the door, you will reach all the spawned doors. To not delete the Custom Gate, you need to modify the plugin's data storage, currently it is created after a configuration in which monument gates and custom gates are stored in the same place. As a feature, it is a good idea, but I can't promise a date when I will create it. ""2 Way Player Teleport? (Both Side?)": false," -> I will test and fix the two-way blocking option soon if necessary.

"2 Way Player Teleport? (Both Side?)": false, I set it up this way, but it doesn't seem to be working... Or maybe I misunderstood: does this mean players can teleport from Door 1 to Door 2, but not from Door 2 to Door 1? and could you add a feature where doors manually placed by admins aren't deleted during a wipe? I want to place one on my custom monument, and it's a bit of a hassle to manually add the door again after every wipe ^ ^

You can change these texts in the config of the SimplePVE then find "Purge Schedule Status" list.

hi, zip the data files from oxide/data/RaidableBases/ and the config. attach them here or DM. this includes: oxide/data/RaidableBases/Base_Loot/ oxide/data/RaidableBases/Difficulty_Loot/ oxide/data/RaidableBases/Profiles/ oxide/config/RaidableBases.json furthermore, your above mentioned steps are not the correct way to solve this. I already provided the two best solutions for that. attach the requested files and I will find what the issue is with your files.

Summary of Failed Fixes – Raidable Bases v3.1.3 Despite multiple attempts, the plugin still fails with the same error: text System.NullReferenceException: Object reference not set to an instance of an object ERROR: Grid has failed initialization. No valid profiles exist! What we tried – all unsuccessful: Changed profile difficulty from English to Russian – "Easy" → "Легкий" (and also tried "Лёгкий") Removed all additional/extra fields from the profile JSON – kept only the absolute minimum structure (Name, Enabled, Difficulty, PVE, Spawn Chance, Rewards) Created a brand new profile named Test.json with minimal valid structure Deleted all problematic files in the Profiles folder – Easy Bases.json, RaidableBases.json, etc. Confirmed proper file locations – base file in CopyPaste/, profile in Profiles/ Reloaded the plugin multiple times – oxide.reload RaidableBases Removed ALL profiles from the folder – left the folder completely empty, which produced the error No valid profiles exist! Added a minimal profile back – still got the same error Checked the plugin source code – confirmed private const bool en = false; (Russian mode) Confirmed the issue is not profile-specific – even a perfectly formatted minimal JSON causes NullReferenceException Conclusion: The problem is NOT in the profile files. The problem is NOT in the difficulty name (Лёгкий vs Легкий). The problem is NOT in the JSON structure. The real issue: Raidable Bases version 3.1.3 is outdated and incompatible with the current version of Rust. The NullReferenceException occurs inside the LoadProfiles method of the plugin itself when trying to parse any JSON file. This means the plugin is fundamentally broken on this server. Required solution: The plugin must be updated to the latest version (4.x) from Codefling (paid version). Version 3.1.3 is no longer functional with current Rust. Use this to explain to the plugin author or server admin why the plugin still isn't working.

A lot of the time when players try to link they get "LinkBot is not active. try later" and it doesn't explain to the admins in the console etc what the issue is.

What exactly did you do? Show the files before/after

This is my POV ever time I try to use skinner these days.

That's awesome! Thank you so much