nivex
-
Posts
4,791 -
Joined
-
Last visited
Everything posted by nivex
-
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
-
Changed Status from Pending to Closed
-
the UI doesn't randomly disappear and reappear unless you leave the area it is also not meant to remain when it despawns unless you have a lockout timer.
-
Changed Status from Pending to Closed
-
great glad its sorted
-
i assume an update fixed the hook error?
-
heya. yes, everyone is expected to configure the plugin to their liking. every servers gather rates and stack sizes differ in some capacity, so it is literally impossible to create a one-size-fits-all package. the idea is you aren't doing it from scratch. doing it from scratch would take so much longer and i can't emphasize this enough. this is quite literally an expansion to the game so its not easy undertaking for anyone to setup on their server. it is extremely complex and the combinations of options make it unique enough for everyone yes, there are over 600 items in the game so it's going to take a considerable amount of time to go over all of them, except that you're going to scroll past the items you deem useless. there's no easier way to do this i do not work with Rust Server Manager, nor do I know what that is. you will need to exclude the free version on umod from updating, or request that they do so or implement a means to do so. no service of an auto updater should come without the ability to exclude specific plugins nitpicking in general will not solve anything because everyone is entitled to their own opinion. if you feel a base is not up to par then you're free to mention the filename and ill see about upgrading it or replacing it.
-
yeah there's nothing I can do to fix that error afaik. Rust or Oxide will have to
-
didn't I answer this in discord? they must restart the machine after installing the library
-
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
