nivex
-
Posts
4,798 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
@Craft the issue is that the dome spawns too soon but that bug shows which bases are not centered though @Kobani if you have this issue then your bases are not centered. update your tier package and install the copypaste files only all tier packages were centered in 1.0.8 -
@Dead Nasty send me the base from your screenshot and it's profile and I'll check it myself
-
@Chevelle config options such as Convert PVP to PVE will override Allow PVP settings in the profiles. disable Convert PVP to PVE and enable Convert PVE to PVP in the config @Dead Nasty autoheight is in the profiles. it's helpful, but it isn't needed if the base is copied properly, but it won't fix your issue of the base rotating into terrain when it spawns if recentering with Fortify doesn't work then you have to copy it using /copy and then use /paste to ensure that it spawns properly. I copy while clipped into the center foundation. it's a bit tricky but just keep trying and you'll figure it out. @original4d hi, no this wasn't removed. it's in the profiles, oxide/data/RaidableBases/Profiles/ @Senso-GR update to 2.8.2 if you still have issues then you can use these commands to figure out why. rb.config list to ensure all the bases exist rbe debug to see why bases aren't spawning. do not type it until the grid fully loads. type it a second time to turn it off
-
2 issues 1. dome is bugged and I will fix it 2. your copypaste file is not centered to begin with it should be recopied from the center of the base using Fortify if using any of my tier packages then you need to update and install the latest copypaste files if the copypaste file for the base is not centered properly then it can rotate into terrain when CopyPaste spawns it
-
@Kobani thats with /buyraid?
-
@Namsaknoi it's in the .cs it's not the plugin it's a workaround to suppress the error the issue is something on your server I have said this already @Kobani ok I will look
-
Allow Teleport (false) option in RB config will eject you whenever you teleport into the event ya I will add it here in a later update this requires 2 steps to work 1. conversion of your RB installation files using the Convert EN to RU tool. instructions in the below zip archive. 2. changing this value to false in the .cs private const bool en = true; Convert EN to RU.zip
-
Changed Status from Pending to Closed
-
for anyone else curious it's in the profiles, oxide/data/RaidableBases/Profiles/ enjoy
-
public static bool IsKilled(this BaseNetworkable a) => (object)a == null || a.IsDestroyed; you can change that to this in .cs public static bool IsKilled(this BaseNetworkable a) { try { return (object)a == null || a.IsDestroyed || a.transform == null; } catch { return true; } } this is a workaround, and you should find the cause on your server so it can be fixed.
-
@Namsaknoi heya, that isn't the plugin. player and entity are null checked correctly. if transform throws an error when IsDestroyed is false then that's the server.
-
annoying bug use 2.8.2 if your custom spawn points stopped working
-
2.8.0 released
-
@Bear Grills hi, seconds, and it is the time between each spawn after the first. -
ya, update is nearly ready:)
-
Bradley and helicopters to help bases?
nivex replied to Beaverthelieber's Support Request in Support
ok, no ETA, but I will note it down -
Bradley and helicopters to help bases?
nivex replied to Beaverthelieber's Support Request in Support
I'm not aware of anything if you had a plugin that could issue that as a console command from the player then maybe but the primary issue with this is the players would just exploit it in one of two ways 1. cause the heli to deal free damage to the base, in which case you'd have to enable Block Helicopter Damage To Bases 2. hide securely in the base while fighting the heli, essentially getting a free kill on it. if the base is immune to damage from the above option then there is no risk to the player I'm not opposed to either idea but 1 and 2 really take the fun out of the idea. what do you think? -
@QingNing heya, use the commands rb.config list rbe debug
-
@Dead Nasty so there's 2 potential issues here 1. if bases are spawning in cliff sides then the base wasn't copied from its center. you can easily fix this by using the center option within Fortify and resaving the base. I actually did this with all of my bases in my tier packages in 1.0.8 so make sure to update with those new copypaste files if you haven't already 2. and seperate issue is that rocks should not spawn on top of any rock unless it is less than 2 meters in height. it was reported by one other user that a base spawned on top of a 9 meter tall rock, but I was not able to observe or reproduce this. I assume thats what you're referring to since you did not specify a cliff, but both are worth mentioning.
-
@Dead NastyI worked with imthenewguy to come up with a solution for this -
@Dead Nasty there is no safe way for me to do this given other bases can be in the bubble. I can remove any entities they deploy within the events base, but not outside of it because there's no elegant way to determine if another base built that or if a raider did. I can do it for those who are actively participating in the event, but then it will miss all entities deployed before they become an active participant. so that wont work either Deployable Nature can hook OnAbandonedBaseEnded to remove the entities safely when the event ends
-
no problem you too
-
@Hawkhill ok great I will remove the blacklist on the instruments then Player Building Restrictions is in the profiles to prevent them from upgrading their own buildings. if you have a plugin that bypasses the OnStructureUpgrade hook then it may not work
-
hi, the convar server.pve true does this it cannot be bypassed. you would have to set server.pve false and use a plugin like TruePVE to control PVE elements of the server.
-
@KlotzQc heya. the same answer applies to you or anyone else with this issue if it's not explicitly blocked in the config or profiles then it is caused by another plugin.
