nivex
-
Posts
4,771 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
no problem it was due to rust changes
-
you add it to the bases themselves and recopy them find what base it is by typing /rb at it. it will tell you the filename then take that filename and type /paste <filename> add boxes where you want them when finished go outside of the base, go right next to the outer most foundation, look directly at it and type /copy <filename>
-
hi. add more boxes
-
hey. it looks like you're using an outdated version of the plugin
-
in next update: each number represents the height difference from my position and its position. if it's higher than the elevation setting then that position will not spawn a base. this prevents issues where various areas of the base clip into cliffs, rocks or areas with slightly raised terrain that often obstruct boxes, tc, turrets, etc -
@KingSizeKevin while not ideal, this is from the last update. the issue is that the ownerid is not assigned to the player that uses the cancel command, nor should it. it will require a new command to claim the base instead, and assign the ownerid to that player. edit: I've added this in next update hope to release the update soon. testing is nearly finished. I refuse to release something that I don't feel is ready. just wish it wasn't so difficult so I could've released it sooner than later -
heya kevin, turrets do not spawn. this applies to ones that exist already. it would be neat if i could spawn them, by not really feasible without a ton of effort on figuring out where to place them, and then figure out how to set the direction they aim at
-
JsonReaderException errors are from someone modifying them incorrectly. It could be an additional bracket or a missing comma. Replace those files with the original and they'll work fine ya, it is intended that expert and nightmare bases may or may not have an entrance. players must find the best entry point. not intended for a hard base though so I will address that. thanks! -
@ZEODE@thepiercedweirdoaye raideasy10 is known to spawn at the wrong height because its a bunker. will be fixed when I release all the updates for the packages You can't, and how would they enter if they can't break past the external walls? They would need to fly slightly above them to enter without being above any of the foundations on entry, or the Allow Teleport option would kick them out if its set false. Not really a plausible option If you're asking how to prevent players from damaging it from outside of the dome, then you use the Block Damage Outside Of The Dome To Bases Inside option in the profiles oxide/data/RaidableBases/Profiles/
-
no problem! you can use the Use Stack Size Limit For Spawning Items option in the config
-
you need to add loot to the loot tables in order for more loot to spawn. you must also change how much loot you want to spawn in the profiles loot tables is any file inside of oxide/data/RaidableBases/ except the files inside of the Profiles folder if you want loot to ALWAYS spawn then you must add the loot in oxide/data/RaidableBases/Base_Loot AND you must set Always Spawn Base Loot Table true in the profiles these answers and more are in the documentation. read it Loot Tables, Loot Priority, and Loot Settings
-
hi, need more logs than this. it doesn't really tell me anything
-
This is a known issue. Will be fixed when I can figure out how to reproduce it.
-
#14 0x00000040517ea6 in (wrapper managed-to-native) string:FastAllocateString (int) this is where it crashed I can't fix this as its a native method that isn't in the plugin
-
I can verify this is working properly. If players cannot build a ladder then they're either doing it wrong, or you're using a plugin that is setting canBypassBuildingPermission to false. Such as an outdated BuildRevert version
-
not sure but we can try connect to FTP server folder structure is like this: ./rustserver/oxide/ ./rustserver/server ./rustserver/logs ./rustserver/ name could be anything. it's an example. ./server.log or ./log.txt usually. look for this to start. if you do not find it then look in control panel for startup parameters and -logfile filename.ext
-
Changed Status from Pending to Closed
-
glad you got it sorted!
-
as I said, I need the errors from the server log
-
hi, this is because you have the free version installed. packages do not include the plugin. this is stated in the title of the product, and in the documentation
-
"Run Every X Seconds": 10.0, this is far too often and bad on performance. I suggest no less than 1800.0 I will look into your issue Check your server log for exception error There's no reason this shouldn't work when shooting building
-
Changed Status from Pending to Closed
-
Thanks. Fixed in next update. Players who exploit this should be banned from joining any raids by using the raidablebases.banned permission.
-
I don't understand. this is how it is supposed to work. it is supposed to show you the time before it is raidable
-
hi ! you need to grant a permission to the player for it to work "Purge Settings": [ { "Permission": "abandonedbases.vip", "Lifetime (Days)": "7", "Conversions Before Destroying Base": 1 }, { "Permission": "abandonedbases.veteran", "Lifetime (Days)": "5", "Conversions Before Destroying Base": 1 }, { "Permission": "abandonedbases.basic", "Lifetime (Days)": "3", "Conversions Before Destroying Base": 1 } ],
