nivex
-
Posts
5,396 -
Joined
-
Last visited
-
Days Won
187
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
2.4.7 released Blocked spawns on rail and railside topologies Fixed UnityEngine.Object.GetName NullReferenceException causing bases to not spawn -
disconnecting: Exception (cs:71423): NullReferenceException:
nivex replied to World_Gamerz's Support Request in Support
Changed Status from Pending to Closed -
disconnecting: Exception (cs:71423): NullReferenceException:
nivex replied to World_Gamerz's Support Request in Support
yea I don't see how this is related to Raidable Bases it is as you said likely just a teleport issue. ill have to find the game bug and prevent it from being triggered when teleporting... closing this though. you can discuss it further in the NTeleportation thread if you have more info. otherwise stay tuned for an update on umod -
Changed Status from Pending to Closed
-
hi. sure. you can find these settings in the profiles, oxide/data/RaidableBases/Profiles/ "Eject Enemies From Purchased PVE Raids": true, "Eject Enemies From Purchased PVP Raids": false, "Eject Enemies From Locked PVE Raids": true, "Eject Enemies From Locked PVP Raids": false, and these settings can be found in the config "Bypass Lock Treasure To First Attacker For PVE Bases": false, "Bypass Lock Treasure To First Attacker For PVP Bases": false, "Lock Treasure To First Attacker": true,
-
looks to be another rust bug causing this issue NullReferenceException at (wrapper managed-to-native) UnityEngine.Object.GetName(UnityEngine.Object) this should never happen. easy fix though. I will just trap the error. releasing 2.4.7 here shortly in a few minutes
-
@DiDreamersorry I don't understand. do you mean KpucTaJl fixed it? -
heya. i will need an error to fix this. i am releasing 2.4.7 shortly to fix a spawn issue due to a game bug
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
hi, this will be fixed in 2.4.7 and released shortly. thanks
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
thanks for the error. looks like another Rust bug. I have a workaround and will release 2.4.7 shortly
-
hi, players will receive the generic message that it couldn't find a position. admins will receive the LAST message of why it couldn't find a position. this is almost always a fault with the map
-
@Rubiks-Q-Bertit's released already bud
-
as posted above it is fixed in 2.4.6 @X i i K
-
Changed Status from Pending to Closed Changed Fixed In to 2.4.6
-
this is fixed in 2.4.6 sorry for the issue
-
Changed Status from Pending to Closed Changed Fixed In to 2.4.6
-
sorry everyone it's fixed in 2.4.6 you can download it now
-
sorry guys it's fixed in 2.4.6
-
@CovfefeI wouldn't know why the grid doesn't finish. But I just released 2.4.5 so try that. It does take a long time on some servers to finish btw, like 2-3 minutes
-
@chuck norriskk ill see what i can do- 599 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@chuck norrissorry can you clarify this? it is a bit confusing
- 599 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya. if players can't find their corpse then it is outside of the dome within 10 meters of it. it also draws on their screen exactly where it is. it will never despawn a corpse. it will always turn it into a backpack Eject Corpses From Enemy Raids (Advanced Users Only) you can set this false if you don't want the feature but i definitely recommend that players just get used to this and actually pay attention to their screen =p
-
@CovfefeI replied in the plugin thread also. you don't have a cost enabled. you can set the value to 5000 or the max size of your map
