nivex
-
Posts
5,646 -
Joined
-
Last visited
-
Days Won
194
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
you haven't sent me the server log that is the oxide log and won't contain the full error. I don't know what is causing it without having the full error from the server log
-
hi, that is a warning not an error an error includes a message and stack trace. you have shown me the message above "NullReferenceException: Object reference not set to an instance of an object" but without the stack trace this error is not helpful
-
attach the log and I will find it unless you have restarted since then it's gone
-
hi, sorry to hear that. I would need the full error from the server log though. it should be called log.txt server.log latest.log etc and be in your server's root folder where the oxide and server folders are.
-
hi, this is intended so the items can stack. though it doesn't check if the item can stack so I will add that I've made it optional in the next update too (Use Identical Skins For All Stackable Items, in config) -
Changed Status from Pending to Closed
-
hi, I've responded to your other ticket. in short, no, it's not normal but I'll help you in the other ticket
-
Hi, floating doors that cannot be killed are a visual bug within the game client. you can ignore this as it's harmless and pertains to the CopyPaste plugin bases not despawning is a separate issue and is most commonly because 1. bad copypaste file 2. linux missing libgdiplus library 3. a bug 4. an error which I'd need the message for you can use the /rbe kill_cleanup command at any base this happens with to remove them I've closed the duplicate thread here https://codefling.com/files/support/8353-not-removing-old-bases/
-
hi, this is explained in the documentation under all 3 loot sections, and your question is too vague.
-
Changed Status from Pending to Closed
-
no problem. enjoy
-
disable Require Cupboard Access To Place Ladders in the nightmare profile
-
what does it say
-
@treasureisland1234 attach your config if you can't enter then you probably gave your raidablebases.banned perm
-
@MeinRustthank you Mein @Commo if you're going to change it in the config then you should unload the plugin and delete the UI data file. this is because each players offsets are stored so changing config will apply to new offsets or unchanged offsets only. you can use the arrow to move each ui window too to make this easy oxide/data/RaidableBasesUI.json - be careful to not delete the wrong data file.
-
no problem
-
hi, that plugin hasn't been updated in 5 years I've edited it so it should work with raidable bases now. edited to include support for pvp in raidable bases events, too NightPVP.cs
-
.
-
I don't recall what caused this for the last person with this issue. I think it was a plugin altering stacksizes.
-
no problem. yes, if you changed your loot tables then you might want to back them up first. reinstall is the best way
-
hi, tier 3 does not include the bases from tier 1 or tier 2. each tier has its own unique bases. that is the only difference between each tier. -
Amount Of Items To Spawn in the profiles, oxide/data/RaidableBases/Profiles/
-
I gave you multiple answers what does it say when the plugin loads you need to show me what it says
-
no idea what that means. if using Carbon then you'll have to ask them.
-
rbe debug command is there to help you with issues. most common reason is not enough players online. Minimum Required Players Online is under Maintained Events and Scheduled Events in the config make sure the plugin loads without any errors. make sure the copypaste files exist. you can check by typing rb.config list make sure you see the loot files being loaded after the plugin loads
