nivex
-
Posts
4,789 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
this would be Rust limitation due to LOS issue. it sucks but only option is to disable those npcs for now. I will add an option to reduce their vision range which should solve this for short-range encounters only though, such as going into a room
-
@chuck norrisI don't know but I doubt it, you would have to look with /radar -
i don't believe so. ill note it down and check again
-
I feel like I missed someones comment, ask again if I did =p
-
@Xandragood @RoxyGalwhich base is that
-
ok thanks will check it out
-
are you sure you're using the newest version 2.6.6? I fixed this and it was confirmed to be working
-
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.
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
@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 );
-
heya, im aware of the issue and its fixed in the next update
-
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
-
thank you guys and this is good info. should help narrow it down @frostyty1
-
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
-
Changed Status from Pending to Closed
-
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.
-
I didn't manage to get it added in time but it's on my next update todo list! 2.6.5 released and requires the Rust update
-
@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
-
Odd loot behavior on just 1 item...5.56 rounds
nivex replied to Light Hammer's Support Request in Support
Changed Status from Pending to Closed -
Odd loot behavior on just 1 item...5.56 rounds
nivex replied to Light Hammer's Support Request in Support
ya you can remove any of those or simply set their amounts to 0 -
sure i can note this for later
