nivex
-
Posts
5,493 -
Joined
-
Last visited
-
Days Won
191
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
glad to know that was the issue! very common for linux users unfortunately. they can resolve this by updating their software, this has been fixed since Wings version 1.5.6, and they need to properly configure their permissions
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
this was removed. it does not work because you cannot teleport a building after it has already been spawned (without using hacky code which I refuse, and even then it would not help). it will reappear where it was in the next server frame.
-
@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 -
alright, changed fog machines to IO reverting to CanSamSiteShoot is not a fix as the sam sites will then target mounts that spawn with the base when it is intended that they target player mounts only so i've corrected the issues with targeting, which then prevented sam sites from destroying mounts outside of the dome. i have fixed that as well this means that any target within SamSite Range (350.0 = Rust default) which is 75 by plugin default will be targeted and destroyed regardless of it being within the dome or not if yourself or others do not want mounts being destroyed from outside of the dome then you must set SamSite Range (350.0 = Rust default) to the same radius as Protection Radius, which is the radius the dome uses also this is how it is intended to work and used to work before the Rust or Oxide changes broke the hooks that i was using these changes will also be compatible with my upcoming TruePVE update=]
-
ok thanks
-
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
