Raidable Bases 2.9.7

Quick question.   Is there a way to split stacks between containers?  I put the setting to split between all boxes, but the same item just spawns in 1 box as a large stack.  Is there a way to better distribute the loot like if there is a stack of 16 C4,  it might split into stacks of 3, 5, 4 and 4 between multiple chests instead of 1 big stack?

@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
  },

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.

54 minutes ago, nivex said:

@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
  },

 

Could it just respect the vanilla or stacksizecontroller set stack sizes and auto split that way?  If players can only have 10 C4 in a stack, can that just be done automatically?  If not, would be a much appreicated feature. I just want to mimic the servers stack sizes

@KingSizeKevin

yep use stack size limit is an option in the config.

I get a weird issue where there are no raids out but it tells players they are in queue, i have to reload the plugin and everything works fine. It happens randomly but 2x today within 2 hours. 

@Dead Nasty

can you show a screenshot

7 minutes ago, nivex said:

@Dead Nasty

can you show a screenshot

ill try to get one. 

Also, how to you go about limiting how may raids a player can do per day, the 2 settings i see only pertain to how many is on the map at once.

Thanks

@Dead Nasty

you can't. use the below options

player lockouts is for public raids

buyable cooldowns are for private purchased raids

1 minute ago, nivex said:

@Dead Nasty

you can't. use the below options

player lockouts is for public raids

buyable cooldowns are for private purchased raids

Ah darn, ty anyways. 

@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. 

1 hour ago, nivex said:

@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. 

i dont see anything in logs or raidbase logs. there is also poop ton of stuff in there. but yea they get added to a never ending que til it relaods. 

@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

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

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

Nivex: Thanks for all your help! My total overhaul of Zone PVx Info has been released here as Super PVx Info, and uses your latest hooks.

Edit: I guess it's still in review.

what settings do you change so no raids spawn unless purchased with buyraid
this is so they only spawn when someone wants one?

thanks

@Porky

hi, set Always Maintain Max Events to false in the config

Thanks for the lightning fast reply Nivex,
if i want them to use ecomics instead of screp do i just delete scrap and type economics or do you put it in as a custom plugin?
( i ask as there is option for custom currency )

@Porky

np. you would use the economics settings

@nivexThanks my man, you are a legend!

On 8/5/2024 at 12:09 PM, nivex said:

@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

This is what the debug gave me. it didnt happen for a couple days then puts them in an eternal que.

@Dead Nasty

what is supposed to be enabled? because nothing in the screenshot is

@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.