nivex
-
Posts
6,120 -
Joined
-
Last visited
-
Days Won
202
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
hi, I was not able to reproduce this and haven't seen it happen again since if you find that this still happens and provide steps to reproduce then I'll gladly fix it. closing this for now.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
you have the raidabebase.banned permission
nivex replied to Double_Tapper69's Support Report in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
@Boozo heya, you can use the Block Damage Outside Of The Dome To Bases Inside option for this I have implemented workbench level options next update too. Added "Allow players to raid with items up to what workbench level?" (-1 or 3 allows everything, but -1 is future-proof) - restrictions check weapons, loaded ammunition, fired projectiles, and explosives -
heya, harmless bug but annoying and easy to fix in RaidableBases.cs on line 14809 change: if (config.BlockPaidContent && config.DestroyLootedContainer && to: if (config.BlockPaidContent && config.DestroyLootedContainer && !container.IsKilled() &&
-
@KILLFARM88 heya, the bases are in the rb-tier-3.zip in the oxide/data/copypaste folder -
hi, thanks for reporting and providing steps to reproduce. this will be fixed in the next update.
-
@Devil-Steph Your screenshot above with the two messages shows you leaving and then re-entering the event. Did you leave and re-enter, or only enter? Your screenshot above with C4 is cropped, so I cannot see any important information. I need a full screenshot. This is likely an issue with your Advanced Protection Radius in the profiles, it is 50 by default. oxide/data/RaidableBases/Profiles/ "Advanced Protection Radius": { "Buyable Events": 50.0, "Maintained Events": 50.0, "Manual Events": 50.0, "Scheduled Events": 50.0, "Obstruction Distance Check": -1.0 },
