nivex
-
Posts
5,808 -
Joined
-
Last visited
-
Days Won
198
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
ok, well it is saying that the base files do not exist in the copypaste folder so you'll have to figure out where you moved them to and move them where they belong, oxide/data/copypaste/ usually if it works on one server and you install it the same on another server and it doesn't work then it means you only thought you installed it the same. that is the case for this, as indicated by it saying it does not exist. if it did then it wouldn't say that unless! you do not have file permissions for some odd reason (applicable to Linux server only) then you can set the file permissions to 777 to fix it but also, if using Linux then you must make certain that libgdiplus is installed on the machine. it is a library for linux. thought from the looks of it the issue is the files were moved to the wrong directory so just make sure they are where they belong and those messages will stop saying file does not exist then
-
C means its temporarily cached and will be available when its refreshed again. it's normal. -
kk ill note that too ty
-
type rb.config list and post what it says if it is copied correctly then it will work just as it does on your other server
-
@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
-
hi, the bases need to go in the oxide/data/copypaste folder
-
it has been reversed in 2.6.6 simply enable the main copypaste option (Enable CopyPaste Stability) in the profiles
-
You may not use Admin Cheats in this area
nivex replied to BetterDeadThanZed's Support Request in Support
revoke the raidablebases.block.fauxadmin permission -
this most definitely works. post your config
-
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
