nivex
-
Posts
5,932 -
Joined
-
Last visited
-
Days Won
200
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@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
-
@Porky hi, set Always Maintain Max Events to false in the config
-
@Dead Nasty I forgot to mention `rbe active` which prints output for events, as well as `rbe debug` that gives the debug from it. very helpful too
-
ok, released 2.8.9 with a few changes. please see the notes. enjoy namely a fix to the ranked ladder resetting on server restarts
-
@Dead Nasty really not sure then. I'd look for a corrupted copypaste file. it could be a profile in that directory, a file with text that ends with null, a file with text that starts with null, or a file where a key is null can be hard to find when you have no error. I don't have issue with this on my servers so that's why I think it is a corrupted file but its hard to know with so many options changing its behavior. edit: you should use rbe debug when this happens and toggle it back off. you can DM me the text
-
@Dead Nasty just to clear up any potential confusion. it would be normal for a player to see a message indicating they were added to the queue when there are no other events spawned. players will always be put into queue, even when there are no events spawned. the plugin must find a suitable location each time a base is to be spawned. if the queue stalls and requires a plugin reload then it could be a corrupt copypaste file. this can happen even if you have made no changes. there should be an error in the logs for this. I do try to prevent stalls but there are so many ways in which an error can occur. otherwise, check if there are any errors in the logs, and send me a screenshot.
-
@Dead Nasty you can't. use the below options player lockouts is for public raids buyable cooldowns are for private purchased raids
-
@Dead Nasty can you show a screenshot
-
@KingSizeKevin yep use stack size limit is an option in the config.
-
Wipe triggers when Rust protocol changes in the config is not working properly, and can cause your ranked ladder to reset the current wipe data, lifetime ladder is not affected. I will release an update to fix this later today. you can disable it for the time being.
-
@muhendisbeyhi, you need to update. @KingSizeKevinyes, you can set the stacksize in the loot table itself. { "shortname": "explosive.timed", "name": null, "blueprint": false, "skin": 0, "amount": 18, "amountMin": 18, "probability": 1.0, "stacksize": 6 },
