nivex
-
Posts
5,630 -
Joined
-
Last visited
-
Days Won
194
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
this would output to the server console, and being fire, it will spam quite a bit. so use tpve.trace to toggle it on then a moment later type it again to turn it off
-
also, if you could please, run a trace with truepve to see if it is blocking it. this way I am not playing the guessing game trying to figure it out. https://umod.org/community/true-pve/46912-tpvetrace-command
-
hm, ok, post your truepve config. there is no reason TruePVE should block it if it's not the game bug. RB should have full control over that.
-
ok, it might be the fire game bug then. TruePVE would block the bugged damage. try this and tell me if it solves the issue. ServerProjectileHitFix.cs
-
hi, there were no changes regarding this are you using TruePVE?
-
hi, there's no option to do that when using kits. perhaps it is the game randomly giving them the weapon, but I've not seen that happen
-
@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
-
ok, odd, but glad it works. I have seen various plugins get bogus compile errors lately. I still don't understand why. just remember those commands if you have future issues. good luck.
-
yep np did you sort the spawning
-
@Porky np. you would use the economics settings
-
@Porky hi, set Always Maintain Max Events to false in the config
-
this is bogus though. there is no such error so if you see that again then oxide/carbon needs to know about it. it might be responsible, but the above commands need to be used. they're very helpful. you also have double console output which is unrelated, but might be caused by a plugin or because -logfile parameter is not set by the host
-
@Senator heya. same advice, though 2.8.9 is current now you need to update to 2.8.9 use rb.config list rbe debug (this is a toggle. type it again to turn it off) - is showing your server was stuck in a save loop. it will not spawn anything when the server is trying to save. if you continue to see the saving message then you can type the rb savefix command to try and have the plugin fix it. the plugin did not cause the issue. save the server with server.save afterwards
-
@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.
-
hi. sure, I can add that
-
@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 },
