nivex
-
Posts
5,913 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@MARKUS heya, thanks for the kind words. yes you can edit Arena Walls and set Enabled to false in your profiles oxide/data/RaidableBases/Profiles/ -
@0g.Ghost.7373 not sure, that's not something that the plugin could do. maybe the server has become unstable and needs a restart, or maybe a plugin has broken physics -
@Notz hi, it will work with any PVE plugin that properly implements the required hooks which I think that plugin has.- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK np, I think I fixed it so waiting on testing results to confirm that everything is working
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yes, the smaller base next to the larger base is preventing the conversion as you suspected because the smaller base is active. I will have to fix it, but that requires properly identifying external TC versus a whole base. edit: removed some information since I cannot think clearly enough the joy. lots to think about and fix
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK see below
-
@NoxiousPluK ty. ill take a look when I get home I try not to use third party plugins as they're prone to issues too
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK you can try the ab.debug command then sar if no bases convert then it's a permission or config issue or whatever bug is happening with sar can happen with automated too
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK you can configure the max radius, but it is fine if it overlaps a base
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@NoxiousPluK hi, that is nothing to worry about and won't affect any bases that aren't abandoned. you can reduce Sphere Radius or enable Use Dynamic Sphere Radius, but it will still overlap bases when players build too closely. I recommend enabling Use Dynamic Sphere Radius so that it doesn't use Sphere Radius of 50 for every base. if you adjust Sphere Radius and it's too small and a base is larger than the actual radius of the base then it cannot work properly. by using Use Dynamic Sphere Radius it will make the radius the size it should be, and pad it slightly with Padding Added Onto Dynamic Radius. the radius will not exceed Max Dynamic Radius, so if you have large bases on your server then you will need to adjust it to accommodate the larger size bases "Sphere Radius": 50.0, "Sphere Radius (Legacy Shelter)": 25.0, "Use Dynamic Sphere Radius": true, "Max Dynamic Radius": 75.0, "Padding Added Onto Dynamic Radius": 9.0, "Min Custom Sphere Radius": 25.0, "Max Custom Sphere Radius": 75.0,
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Dead Nasty yes, that was fixed long ago
-
@muhendisbey it is working maybe you have problem from another plugin
-
@muhendisbey attach the profile
-
@muhendisbey maybe disable Kill Underwater Npcs.
-
@muhendisbey yes. settings are in those files.
-
@muhendisbey this plugin doesn't use NpcSpawn. it uses its own npcs setup in the profiles, oxide/data/RaidableBases/Profiles/
-
@muhendisbey hi, inside raid bases? it requires areas that have no obstructions outside requires the same but it must be on the navmesh too
-
@Dead Nasty ok, thank you. I have pushed update 2.1.5 to fix this
- 634 comments
-
- 2
-
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@0g.Ghost.7373 it's a dumb implementation, but I thought it worse to have all arrows visible at all times since it would take more space and be more cluttered rip
-
@0g.Ghost.7373 hi, you can click the arrows to move it to where you want it to be type /rb setui status this will save the new position to the config, and update it for every player
-
@Komorebi heya. there's an issue with your server, but that might be a game bug. SamSite.ISamSiteTarget.serverList should not contain destroyed entities which is why this error is thrown. I can still fix it though. change line 12727 in the .cs file if (server is MLRSRocket || Vector3.Distance(server.CenterPoint(), v) > raid.Options.SamSite.Range) to if (server is MLRSRocket || server is not BaseEntity entity || entity.IsKilled() || Vector3.Distance(entity.CenterPoint(), v) > raid.Options.SamSite.Range)
-
@Dead Nasty ok, try the rb queue_clear command when it happens again then. I don't think that plugin is causing it. you would need to search plugins for the StopAllCoroutines text. notepad++ is great for this. @tamwilson1979 hi, ok, I will let the developer know
-
@Dead Nasty it might be that you have a plugin calling StopAllCoroutines, which could stop everything from working in RB (including the queue) if the queue was still running but failed to find positions then there would be debug messages, but there isn't. everyone would've been kicked from queue after it failed too. so it must not be running then I bet. other possibility is an admin paused it with rb.toggle try rb queue_clear next time and tell me if they are able to re-queue and spawn then. it will refund them.
-
@Dead Nasty what is supposed to be enabled? because nothing in the screenshot is
-
@Porky np. you would use the economics settings
