.gif.bcbfcbd37caec464281e2dcf487d352c.gif)
-
Posts
368 -
Joined
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by fullwiped
-
Still, make sure to open the files in oxide/data/RaidableBases/Profiles and verify that the following setting is set to -1, as this ensures proper base spawning, which also fixes the crate issues: "Force All Bases To Spawn At Height Level (0 = Water)": -1.0, Then, restart the plugin by running the following command in RCON: o.reload RaidableBases -
Hello, this might be one of the issues caused by the force wipe. I'm currently putting in a lot of effort to update the bases, and in the coming days, I will release a new update aimed at fixing certain bugs.
-
Changed Status from Pending to Closed Changed Fixed In to 3.1.36
-
Also, the latest version of AlphaLoot has been released. Don't forget to update it during the installation, as that might also be the cause. https://chaoscode.io/resources/alphaloot.13/updates#resource-update-5024
-
It is caused by an incorrect configuration setup. Check the installation guide.
-
If you have created a custom config and these settings are not included in your config, the loot tables will not work properly. Check this and restart the plugin Path: /home/rustserver/serverfiles/oxide/config "Loot Table Name": "fullwipedmain", "Heli Loot Table Name": "fullwipedheli", "Bradley Loot Table Name": "fullwipedbradley", -
Can you send me the config you're using via private message? I checked these files for 2x, and everything is working fine for me right now.
- 17 comments
-
- 1
-
-
- #alpha
- #alphaloot
- (and 45 more)
-
For example, there are 4 different tags: [SUPREME] [ELITE] [GOLD] [DOCTOR] When I type /tag [SUPREME], all tags are hidden. Sometimes, from my admin account, I type /tag [ADMIN], and strangely, instead of hiding the ADMIN tag, the SUPREME tag gets hidden, while the others remain visible. There seems to be a mix-up, but I don’t fully understand it, so I opened a support request. If you could check, that would be great. Thanks!
-
If your server's gather rate is higher than 2x, I recommend choosing the Enhanced profile. This will provide a more balanced loot distribution based on the increased gathering rates. Additionally, you can adjust the number of items that spawn in bases by editing the files in the profiles folder. Use the following setting to configure it. For example, on a 2x server, around 200 items would be ideal: "Amount Of Items To Spawn": 200,
-
-
These three screenshots can greatly help you ensure the correct configuration. Additionally, place the 30 KB RaidableBases.json file from our config folder into the following directory: /home/rustserver/serverfiles/oxide/config Then, restart the server.
-
For the loot system to work, the files in the following path should match the structure shown in the screenshot: /home/rustserver/serverfiles/oxide/data/RaidableBases/Base_Loot
-
The files in the following path should match the structure shown in the screenshot: /home/rustserver/serverfiles/oxide/data/RaidableBases/Profiles
-
Bases should be uploaded to the following path as shown in the screenshot: /home/rustserver/serverfiles/oxide/data/copypaste
-
Under normal circumstances, the downloaded config file and the contents of the data folder should work successfully without requiring any additional actions from you. However, it is important to remove the old Raidable files first.
-
Raid bases can be a bit confusing and difficult to configure. My advice to you is to delete all Raidable Base files found in the config and data folders. Then, replace them with the downloaded files and restart the server or the plugin. This way, you won't have to deal with commands.
-
Summary of Commands to Add New Bases: rb.config add "Easy Bases" fullwipedeasy1 fullwipedeasy2 fullwipedeasy3 fullwipedeasy4 fullwipedeasy5 fullwipedeasy6 fullwipedeasy7 fullwipedeasy8 fullwipedeasy9 fullwipedeasy10 fullwipedeasy11 fullwipedeasy12 fullwipedeasy13 fullwipedeasy14 fullwipedeasy15 fullwipedeasy16 fullwipedeasy17 fullwipedeasy18 fullwipedeasy19 fullwipedeasy20 fullwipedeasy21 fullwipedeasy22 fullwipedeasy23 fullwipedeasy24 fullwipedeasy25 fullwipedeasy26 fullwipedeasy27 fullwipedeasy28 fullwipedeasy29 fullwipedeasy30 rb.config add "Medium Bases" fullwipedmed1 fullwipedmed2 fullwipedmed3 fullwipedmed4 fullwipedmed5 fullwipedmed6 fullwipedmed7 fullwipedmed8 fullwipedmed9 fullwipedmed10 fullwipedmed11 fullwipedmed12 fullwipedmed13 fullwipedmed14 fullwipedmed15 fullwipedmed16 fullwipedmed17 fullwipedmed18 fullwipedmed19 fullwipedmed20 fullwipedmed21 fullwipedmed22 fullwipedmed23 fullwipedmed24 fullwipedmed25 fullwipedmed26 fullwipedmed27 fullwipedmed28 fullwipedmed29 fullwipedmed30 rb.config add "Hard Bases" fullwipedhard1 fullwipedhard2 fullwipedhard3 fullwipedhard4 fullwipedhard5 fullwipedhard6 fullwipedhard7 fullwipedhard8 fullwipedhard9 fullwipedhard10 fullwipedhard11 fullwipedhard12 fullwipedhard13 fullwipedhard14 fullwipedhard15 fullwipedhard16 fullwipedhard17 fullwipedhard18 fullwipedhard19 fullwipedhard20 fullwipedhard21 fullwipedhard22 fullwipedhard23 fullwipedhard24 fullwipedhard25 fullwipedhard26 fullwipedhard27 fullwipedhard28 fullwipedhard29 fullwipedhard30 rb.config add "Expert Bases" fullwipedexp1 fullwipedexp2 fullwipedexp3 fullwipedexp4 fullwipedexp5 fullwipedexp6 fullwipedexp7 fullwipedexp8 fullwipedexp9 fullwipedexp10 rb.config add "Nightmare Bases" fullwipednight1 fullwipednight2 fullwipednight3 fullwipednight4 fullwipednight5 fullwipednight6 fullwipednight7 fullwipednight8 fullwipednight9 fullwipednight10
-
If you are going to use the config files inside the downloaded profiles folder, you don't need to add them separately. However, if you have your own custom config files inside the profiles folder, you need to add the bases using a command.
-
Hello, Use the optional config file we provide for configuration. If there is a command in the JSON file inside your config folder that prevents buildings from spawning, they will not appear because the settings are not configured correctly. If you are having difficulty configuring the settings, you can use the optional config we provide. It is also important to correctly place the JSON config files inside the profiles folder. I have no doubt that you will be able to resolve this by carefully following the guide multiple times. Of course, don’t forget to restart the server or the plugin afterward. Additionally, you can refer to the plugin's guide for a more detailed tutorial. : https://codefling.com/plugins/raidable-bases
-
It seems to have stopped working after the mandatory update. Is there a chance you could check it? Thank you.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.0.4
-
If you are going to use our profile configs, the dome and marker settings are disabled in ours. To enable them, edit the files located at the following path: Path: /home/rustserver/serverfiles/oxide/data/RaidableBases/Profiles "Spawn Silently (No Notifcation, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5,
-
supply.drop_enabled "false" Additionally, if the above setting exists in your server.cfg or serverauto.cfg files, change it to true. That is, update it as follows: supply.drop_enabled "true"
-
I have provided a new update in the config regarding a potential drop bug in some crates related to signals, but I did not detect any issues in food crates. Please try the clean installation I recommended earlier with the new version and let me know about the signals.
.thumb.gif.68f654d7cf3293f24f2e66aba569e415.gif)
