nivex
-
Posts
5,987 -
Joined
-
Last visited
-
Days Won
201
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
thanks, this is fixed in the next update already as per the patch notes, Move Cookables Into Ovens has been disabled for now. you can of course still add items to the copypaste file Move Items Into Lockers would allow items frequently used in player kits to spawn into lockers Additional Containers To Include As Boxes could be enabled (if Destroying The Cupboard Completes The Raid is not enabled) so that lockers are required to be looted in order for the raid to end if you place high value on items in lockers lockers can hold a substantial amount of items so you must understand that you will have far fewer items in boxes as a result -
ah well I missed this response sorry about that. I would need the full NRE to figure out what's going on. you can find that in the server log file (not oxide log) it's probably best to send me that specific file in DM
-
@Dr.D.Bugheya, this is fixed in the next update already =] @Swedish Chefahhh ok, yes it's good that you clarified, and merry xmas to you and any others that celebrate it as well
-
its harmless. the rust update broke it so the game object can be null which cause it to throw a null error. previously it could never be null so it was never thrown. i've added a check for it next update
-
i assume an update fixed the hook error?
-
yeah there's nothing I can do to fix that error afaik. Rust or Oxide will have to
-
@Xandraa tree? trees are deleted by the plugin. what tree are you speaking of specifically? the exact prefab name @CraftI see no issue with this for any of my tests. make sure each profile is configured as above. the best I can do is allow a bit longer of a delay before equipping a weapon. there is no other fix
-
C means its temporarily cached and will be available when its refreshed again. it's normal.
-
@Swedish ChefIm not certain but I've heard no further reports of it causing issues for quite some time now. I just force that option so that everyone is made aware that it is a potential issue out of my control sure I can note that down for later
-
it has been reversed in 2.6.6 simply enable the main copypaste option (Enable CopyPaste Stability) in the profiles
-
@chuck norrisI don't know but I doubt it, you would have to look with /radar
-
I feel like I missed someones comment, ask again if I did =p
-
@Xandragood @RoxyGalwhich base is that
-
2.6.6 released
-
@RepeatPeteit is, that is what the conditional (ternary) operator is
-
lockout timers don't reset. it is given either when it ends or when it despawns depending on when they were flagged as a raider but not both. I've attempted to fix this but short of overriding the override for OverrideCorpseName there is no guaranteed fix, and there's simply no reason to do this as it would break a lot of other code to accomplish that. hopefully my workaround is enough for you.
-
@gamaonly the person who purchased may download the update you can fix it yourself: Senses.Init( owner: GetEntity(), memoryDuration: 5f, range: 50f, targetLostRange: 75f, visionCone: -1f, checkVision: false, checkLOS: true, ignoreNonVisionSneakers: true, listenRange: 15f, hostileTargetsOnly: false, senseFriendlies: false, ignoreSafeZonePlayers: false, senseTypes: EntityType.Player, refreshKnownLOS: true ); change that to this (you are just adding a line) Senses.Init( owner: GetEntity(), brain: this, memoryDuration: 5f, range: 50f, targetLostRange: 75f, visionCone: -1f, checkVision: false, checkLOS: true, ignoreNonVisionSneakers: true, listenRange: 15f, hostileTargetsOnly: false, senseFriendlies: false, ignoreSafeZonePlayers: false, senseTypes: EntityType.Player, refreshKnownLOS: true );
-
I may have a fix just waiting on it to be confirmed
-
good suggestion @Zoreenoit appears the rng is generating in sequence for some reason suddenly @Sveervooxya but that error means you need to update since that was what the Rust update broke, and I fixed that
-
you need to update raid bases @Sveervoox I posted an update many hours before the Rust update to avoid this =p
-
ok ill look into it guys, will add option for the mini too aimacak compile issues mean you need to update the plugin though
-
2.6.5 has been released and requires the Rust update if I missed your suggestion this round then it should be in the next non-hotfix update. I'm assuming something will go wrong since it's a Rust update please note my hours different from those hours so I will not be available when the Rust update hits until several hours later. my testing shows that the plugin compiles with the Rust update so it should be fine hopefully, which is generally the case but not always @aimacakthis is not a raid bases issue. it is true pve and belongs in the true pve thread. post your config there.
-
@aimacakthey need to be more careful then. I don't see a reason to prevent collision damage. you can do that in truepve anyway =p @Dr.D.Bugyes, Use Grid Locations In Allowed Zone Manager Zones Only, in the config
-
@aimacak Mounts Can Take Damage From Players Mounts Can Take Damage From SamSites
-
@Hawkhillah ok not sure how I missed that. its been updated thank you
