Raidable Bases 2.9.4

Do the stats of /rb ladder no longer reset after wipe (v2.7.0)?
Can i reset them by command?

2 hours ago, Dr.D.Bug said:

Do the stats of /rb ladder no longer reset after wipe (v2.7.0)?
Can i reset them by command?

u can delete data file, about command dont know, sorry

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

@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

Lockout timer starts upon raid being finished, but then resets once it despawns Essentially adding extra time to the players lockout timer. Bug or missing a setting somewhere?

3 hours ago, Rubiks-Q-Bert said:

Lockout timer starts upon raid being finished, but then resets once it despawns Essentially adding extra time to the players lockout timer. Bug or missing a setting somewhere?

cooldown is intended to reset so that it is effectively applied when the raid despawns. this is not configurable, its to prevent exploiting the mechanic and is why it was added

lockouts do not reset though

ok guys 2.7.1 released, sorry for the rough update with 2.7.0!

Quote

                player.State.pointsOfInterest?.Remove(note);
                note.Dispose();
                player.DirtyPlayerState();
                player.SendMarkersToClient();

this code deletes the map marker after you place it. if you don't like that then delete the code above in the .cs

please don't bother me with this otherwise. there is no good solution that everyone will like. no i cant make you use a different keybind. all i can do is make you have to press a second keybind to use it and thats dumb too. deal with it i guess idk im tired of it already =\

6 hours ago, nivex said:

cooldown is intended to reset so that it is effectively applied when the raid despawns. this is not configurable, its to prevent exploiting the mechanic and is why it was added

lockouts do not reset though

So here, despawn time is set to 30 minutes, gives people time to find loot they missed or w/e. Lockout is 15 for easy and 30 for medium. I can do an easy and be back at base and the lockout timer will disappear after 15 minutes and then pop up another 15 minutes later once it despawns. Same with medium, right after the initial lockout ends, it despawns and then gives another 30 minute lockout. So that's intended?

Edit: I don't know what exploit you're referring to. I assume jumping from raid to raid. But you could already limit players by not allowing them to enter other raids until the first one is done. Excuse my ignorance, just trying to wrap my head around this.

@Rubiks-Q-Bert

Lockout timers (public raids) - starts when the raid is completed, and is checked a second time when the raid despawns. this time cannot reset itself while active, but it can be applied a second time should it expire before the raid despawns. it was originally intended that the lockout time exceed the despawn time so that this does not happen, but a lot has changed since then so perhaps it should be flagged to not happen now. I don't know that i want to change what everyone is accustomed to though.

Cooldown timers are different (purchased raids) - applied for the full duration of the raid and reset when the raid ends. the exploit is buying another raid before the current raid despawns. blocking someone from entering multiple raids is not the same as blocking them from purchasing multiple raids

2 hours ago, nivex said:

@Rubiks-Q-Bert

Lockout timers (public raids) - starts when the raid is completed, and is checked a second time when the raid despawns. this time cannot reset itself while active, but it can be applied a second time should it expire before the raid despawns. it was originally intended that the lockout time exceed the despawn time so that this does not happen, but a lot has changed since then so perhaps it should be flagged to not happen now. I don't know that i want to change what everyone is accustomed to though.

Cooldown timers are different (purchased raids) - applied for the full duration of the raid and reset when the raid ends. the exploit is buying another raid before the current raid despawns. blocking someone from entering multiple raids is not the same as blocking them from purchasing multiple raids

 

Interesting. I was more trying to understand it all. But if it's what people know and it's doing what it's meant to do, keep it. Short version is the server I worked for closed for awhile and re-opened late last month so this change was new to us. Just wanted to understand it a bit better is all. Thanks for the explanation!

Here  is a medium base that didnt despawn after it got raided.
2 players on my server raided it 15min before server restart.....
Anything i can do to prevent this? Add command to unload raidable bases before restart?

@Hawkhill

no idea without an error, unless you're using linux and your host didn't install libgdiplus

send me the server log in DM

Hello,
remove markers doesn't seem to work (version 2.7.1).
I got this error which seems to be related:
'RustCore v2.0.5788' is using deprecated hook 'OnMapMarkerRemove', which will stop working on Sunday, 31 December 2023. Please ask the author to update to 'OnMapMarkerRemove(BasePlayer player, List<MapNote> mapMarker, int index)'
Est-ce qu'il faut l'activer quelque part dans la config ?

it works, and that warning is from RustCore, not Raidable Bases

2 hours ago, Dad Frog said:

Hello,
remove markers doesn't seem to work (version 2.7.1).
I got this error which seems to be related:
'RustCore v2.0.5788' is using deprecated hook 'OnMapMarkerRemove', which will stop working on Sunday, 31 December 2023. Please ask the author to update to 'OnMapMarkerRemove(BasePlayer player, List<MapNote> mapMarker, int index)'
Est-ce qu'il faut l'activer quelque part dans la config ?

oxide tried to fix this problem a couple of hours after the release of the main update for the game update, I think this error will disappear in the next oxide update.

On 4/9/2023 at 3:13 PM, aimacak said:

oxide tried to fix this problem a couple of hours after the release of the main update for the game update, I think this error will disappear in the next oxide update.

Thank you aimacak,
Everything is up to date now on my server (oxide,rust) and the problem is still present.
But I also use MapMyPlayer and I think the error comes from this plugin.

7 minutes ago, Dad Frog said:

Thank you aimacak,
Everything is up to date now on my server (oxide,rust) and the problem is still present.
But I also use MapMyPlayer and I think the error comes from this plugin.

the last time I saw this error was with RustCore v2.0.5794, now it's 5798, there are no errors in the logs.
Are you sure you still have this error?

'RustCore v2.0.5794' is using deprecated hook 'OnMapMarkerRemove', which will stop working on Sunday, 31 December 2023. Please ask the author to update to 'OnMapMarkerRemove(BasePlayer player, List<MapNote> mapMarker, int index)' 

that's not an error, and it is from RustCore. ignore it

can you disable the right click teleport thing as i cant place map markers with it active

Search the config and set it to false.

    "Automatically Teleport Admins To Their Map Marker Positions": true,

 

thank you my host site is down atm will try this as soon as i can

On 4/9/2023 at 7:58 AM, nivex said:

@Hawkhill

no idea without an error, unless you're using linux and your host didn't install libgdiplus

send me the server log in DM

i also get this as the server is restartin or crashes i know my host uses linux is this what causes them not to despawn

@aaronman1

yes, it can cause many issues because it is required by Rust to convert byte array to bitmap. you would need to ask your host to install libgdiplus if its not installed

though you can safely ignore the RustCore warning. it isn't an error

Hi,

quick question because i didn´t find it in the config or somewhere else.. Can i configure the announcement texts in chat? Like color or whats highlighted? Or the icon? Like an own png which could be loaded for the announcements? I am sure it is somewhere in the sourcecode but it would be nice if i can change these settings.

If they are not somewhere in the config is it possible to add these options?