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
-
@Dr.D.Bug@aimacak use the /rb wipe command - do not delete files randomly. the file in question contains lifetime stats for rb ladder. just ask me i haven't changed anything regarding how the wipe works -
if you have issues with 2.7.0 performance then unload the plugin and delete your oxide/data/RaidableBasesUID.json file - this will fix the issue
-
please see my previous comment. that will fix this issue
-
sounds like the difficulty setting in each profile was reset then, or you have json errors in the loot file installing the free version would have though, and you'd need to reconfigure all premium settings / reinstall the package if you have one of my packages also possible that the premium version got installed over the top of the free version afterwards make sure to blacklist raidablebases in any update plugins or rust server manager settings do not reset themselves unless i force them to be reset and i would mention that in the update notes so it was not the update.
-
Changed Status from Pending to Closed
-
ok, make sure the plugin is unloaded and delete this file: oxide/data/RaidableBasesUID.json make sure the file name is exactly as shown this should fix any issues.
-
disable it in the config =p
-
type version in console and post back with what steam update it responds with
-
hi, the update is not going to change the difficulties of the profiles you would've had to installed the free version and then the premium version sometime afterwards make sure you have auto update turned off from any auto update plugins including rust server manager you will have to reinstall the package as this would've wiped any premium settings you can verify this by checking the profiles to see if all difficulties are set to 0 again oxide/data/RaidableBases/Profiles/
-
Destroying The Cupboard Completes The Raid is a little buggy in 2.7.0 your players just need to loot or destroy a box after destroying the TC to get around this issue until its fixed I changed the check to end the raid to only check when something is looted or destroyed, rather than every second. this helps performance a tad bit. unfortunately i didn't account for the entity not being destroyed in the same frame so it does not work properly atm. it is fixed in next update I've looked into the reported performance issues and do not see any changes that would cause this. I have this running on quite a few servers with no issue aside from the above TC bug. I suggest updating your servers to revert the Facepunch pool changes and see if that resolves the issue for you. if you're having performance issues when the base is pasting via CopyPaste but not afterwards then you need to reduce the paste batch limit in CopyPaste config from its default of 15 to 3-5. this is not a plugin issue if it continues to happen after making this config change. though this issue may have been fixed by the forced update.
-
NextTick(PurgeTemporaryRespawns); remove this code from the .cs, and update your server with the latest steam and oxide updates there's nothing else that I can see that would cause this. i believe it to be the facepunch update to pooling that they reverted afterwards.
-
ok i will check it out now
-
Changed Status from Pending to Closed
-
2.7.0 released you do not have to wait to update enjoy!
-
oh I'm not doubting that you saw walls, but you're certain there was a raid base there beforehand? I mean I know the walls were definitely there, but sometimes annoying questions need to be asked to be sure. just like a tech that asks you, "is it plugged in?" "did you turn it on?" "is the issue between the keyboard and chair?"
-
@Hawkhill walls: when a raid ends the entities despawn in the order of walls, blocks and then deployables last. they're all in the same list, so if the walls don't despawn then the base won't either. this means that the kill messages were sent to those walls, because your base despawned afterwards. its unknown why this happened. any number of things can break it such as bad server performance, other plugins blocking the kill, the server canceling the invokes, oxide throwing errors, etc. i would need more information. i suspect its an oxide issue as i have seen IOCore exceptions being thrown from OnEntityKill which can't happen unless oxide is bugged or another plugin is bugging out oxide. this was from one other report. other than that i've heard nothing else about this, and that one was bases not walls. @Aussie4life floaters: bases won't float unless you've modified a autoheight or height setting, or if the base was not copied properly to begin with. many other packages did not copy the bases properly. my packages were all copied at 1.5 meters so they will paste as intended
-
@byond1991 lmao ya thatll do it
-
Changed Status from Pending to Closed
-
hi, no problem
-
@TheRiddledNote sorry I meant to say disable Do Not Destroy Manually Converted Base When Despawn Timer Expires to prevent base despawning for /sar convert bases -
@Aussie4lifeset the radius back to 25-45. you're trying to spawn it on top of the base and thats not gonna work
-
ya they can use /sar convert they need abandonedbases.convert perm to use the command you need to set Despawn Timer to 0 if you dont want the base to despawn afterwards they can use /sar cancel to cancel the raid there is a cooldown before they can cancel, and you can require the raid be completed before canceling too. it requires abandonedbases.convert.cancel you need to configure everything. @TheRiddledNote
- 606 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
