Raidable Bases 3.0.5

9 hours ago, KingSizeKevin said:

Hello, quick question..

When players run a tugboat into the Raid Bases dome, the tugboat goes flying half across the map.  Any way to make it just bounce back a little instead?

that one is funny

As a the owner/admin of the server why would I be getting this message entering into a raidbase zone? I thought I entered the commands for my permissions but no matter what it keeps saying that. Anything else I need to do?

@Trick

Hi, the only way to see this message is if you've been granted the raidablebases.banned permission. People do this often enough that I've created a command to revoke it, useful for those who don't remember what group they granted it to.

/rb unban

Hi,

I changed the notify part in config to:

"Notify Plugin - Type (-1 = disabled)": 1,

Now it would sometimes use notify but sometimes not. Is there any other part I have to change ?

@Andariel

Hi, what message are you not seeing?

"Notification Interval": 1.0,

You can try adjusting this to 2.0

Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]: [RaidableBases] MakeAnnouncements ERROR: Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: ". Path 'ModeNightmare', line 111, position 2.
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonTextReader.ParsePostValue () [0x00179] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonTextReader.Read () [0x0005a] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateDictionary (System.Collections.IDictionary dictionary, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonDictionaryContract contract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, System.String id) [0x0028b] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x002a8] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0006d] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000d9] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00053] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value) [0x00000] in <271c58b7a8684db5a2c92be17a81f252>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Core.Libraries.Lang.GetMessageFile (System.String plugin, System.String lang) [0x00067] in <d59b507fd76240e5b62228d0eae39b73>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Core.Libraries.Lang.GetMessageKey (System.String key, Oxide.Core.Plugins.Plugin plugin, System.String lang) [0x00036] in <d59b507fd76240e5b62228d0eae39b73>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Core.Libraries.Lang.GetMessage (System.String key, Oxide.Core.Plugins.Plugin plugin, System.String userId) [0x00017] in <d59b507fd76240e5b62228d0eae39b73>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Plugins.RaidableBases.mx (System.String key, System.String id, System.Object[] args) [0x00006] in <1397cba66f414a7797f3a5c684824a57>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Plugins.RaidableBases+RaidableBase.mx (System.String key, System.String id, System.Object[] args) [0x00000] in <1397cba66f414a7797f3a5c684824a57>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Plugins.RaidableBases+RaidableBase.LangMode (System.String userid, System.Boolean strip) [0x0001c] in <1397cba66f414a7797f3a5c684824a57>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Plugins.RaidableBases+RaidableBase.MakeAnnouncements () [0x00134] in <1397cba66f414a7797f3a5c684824a57>:0
Jul 31 21:25:22 foxxservers.com start_rust_main.sh[1754721]:   at Oxide.Plugins.RaidableBases+RaidableBase.TryInvokeMethod (System.Action action) [0x00000] in <1397cba66f414a7797f3a5c684824a57>:0

version 3.0.5

@PhatBlinkie

Hi, it's an issue with a language file, likely the French language file (unless you changed something else)

Here's the fixed French file

RaidableBases.json

@nivex

Hi, I have a problem with raid bases. If a player goes into the easy base, it gives them ownership and they can raid, but in medium and hard it doesn’t work. It doesn’t give them ownership. I have it set so that bases are free and activate on entry. I don’t have any cooldowns, but it just doesn’t work. Players automatically get the permission raideasy but that’s all, nothing else. How is this usually resolved?

On 7/28/2025 at 5:04 PM, nivex said:

@Andariel

Hi, what message are you not seeing?

"Notification Interval": 1.0,

You can try adjusting this to 2.0

Will get this error:

[RaidableBases] Newtonsoft.Json.JsonReaderException: Input string '2.0' is not a valid integer. Path '['Event Messages']['Notify Plugin - Type (-1 = disabled)']', line 690, position 47.
  at Newtonsoft.Json.JsonTextReader.ParseNumber (Newtonsoft.Json.ReadType readType) [0x0027b] in <271c58b7a8684db5a2c92be17a81f252>:0 

@Tay

Hi, as explained earlier, bases do not lock on entry. It locks on explosive/melee damage, killing an npc, or destroying part of the base.

If it locks on one difficulty then it will lock on every difficulty, unless you have the others spawning as PVP when they should be PVE. You can send me the profiles and config in DM though.

@Andariel

Hi, the error says 2.0 is not a valid integer, so it needs to be written as 2 instead, under Notify Plugin - Type

3 hours ago, nivex said:

@Tay

Hi, as explained earlier, bases do not lock on entry. It locks on explosive/melee damage, killing an npc, or destroying part of the base.

If it locks on one difficulty then it will lock on every difficulty, unless you have the others spawning as PVP when they should be PVE. You can send me the profiles and config in DM though.

@Andariel

Hi, the error says 2.0 is not a valid integer, so it needs to be written as 2 instead, under Notify Plugin - Type

@nivex
 

I fixed it by setting the difficulty to 1 in all profiles. I had it set to 2 in medium and 3 in hard, but after changing everything to 1, it works correctly. I'm not exactly sure what I messed up before, but at least it's working now. The player even automatically received the raidmedium permission as well.

2 hours ago, Tay said:

@nivex
 

I fixed it by setting the difficulty to 1 in all profiles. I had it set to 2 in medium and 3 in hard, but after changing everything to 1, it works correctly. I'm not exactly sure what I messed up before, but at least it's working now. The player even automatically received the raidmedium permission as well.

You should not configure it this way. Every difficulty requires its own level, not to be shared with another difficulty

send me the files in DM

@Tay

I've responded in DM.

I've tested Easy, Medium, and Hard from Maintained Events using your files and each event locks to the player (on damage, never on entry) as expected. I changed Difficulty Level for each back to its respective value (0=easy, 1=medium, 2=hard, etc).

This must be from some error, or an issue with RealPve, as no such issue exists in RB. Several people use both RealPve and RB so I am sure you can sort it out if you ask that developer. He has his own RB implementation, which deviates from mine, so he will be the only one that knows what the issue is since it's not my code.

@nivex
When a player enters a raid and has an active cooldown, they don't get any message saying they have a cooldown. How can I enable that, please?

@Tay

Heya, relevant messages are shown already.

Buyable Cooldowns
Buyable Cooldowns do not restrict event entry. They are used to limit how frequently players can purchase events. When a purchase is blocked due to a cooldown, a message is always displayed explaining the reason. This is not used with public events.

Player Lockouts
Player Lockouts prevent players from entering public events. When a lockout is triggered, a message is displayed and any active lockouts are listed in the Lockout UI. If no message appears, the lockout is either not configured or you do not have a lockout for that difficulty. This is not used with purchased events.

Bypassing Lockouts
Vanish, noclip, and the permissions raidablebases.lockoutbypass or raidablebases.canbypass will allow you to enter. This is intended so you can easily assist players without interfering with game play.

Cooldowns and lockouts are not interchangeable. They serve different purposes and are named differently for that reason.

15 hours ago, nivex said:

@Tay

Hej, relevantní zprávy se již zobrazují.

Zakoupitelné cooldowny
Zakoupitelné cooldowny neomezují vstup do událostí. Používají se k omezení toho, jak často si hráči mohou události zakoupit. Když je nákup zablokován kvůli cooldownu, vždy se zobrazí zpráva s vysvětlením důvodu. Toto se nepoužívá u veřejných událostí.

Uzamčení hráčů
Uzamčení hráčů brání hráčům ve vstupu do veřejných událostí. Po spuštění uzamčení se zobrazí zpráva a všechna aktivní uzamčení jsou uvedena v uživatelském rozhraní uzamčení. Pokud se žádná zpráva nezobrazí, uzamčení buď není nakonfigurováno, nebo pro danou obtížnost nemáte nastavené uzamčení. Toto se nepoužívá u zakoupených událostí.

Obcházení uzamčení Pomocí
Vanish, noclip a oprávnění raidablebases.lockoutbypass nebo raidablebases.canbypass se můžete dostat do hry. To vám umožní snadno pomáhat hráčům, aniž byste jim narušovali hru.

Cooldowny a lockouty nejsou zaměnitelné. Slouží různým účelům a proto se také různě nazývají.

@nivex

 

Okay, but in the lang file it is set that when a player enters a Raid Base, they should get a message saying that the raid has been locked for them and their team, but I’m not getting any such message.

@Tay

Hi,

I think the confusion is coming from the translation. First, it said "cooldown," now it says "locked," which changes the meaning. 

This option doesn’t lock the raid to the player — it locks the player to the raid. That means they should finish that raid before they can start another one.

Set to true in the config:

Quote

Lock Players To Raid Base After Entering Zone

This message is shown, OnLockedToRaid:

Quote

You are now locked to this base.

If instead you want the raid to lock to the player, that happens when the player deals damage, not when they enter. That behavior is enabled by default, and there’s no message shown when it happens. It is displayed in an update to the Status UI, visible only when the player is inside of an event.

I hope this clears things up. I understand translating is difficult when it's not accurate.

14 minutes ago, nivex said:

@Tay

Ahoj,

Myslím, že zmatek pramení z překladu. Nejdřív se psalo „cooldown“, teď se píše „locked“, což mění význam. 

Tato možnost neuzamkne raid pro hráče – uzamkne hráče k raidu. To znamená, že by měl dokončit daný raid, než bude moci začít další.

V konfiguraci nastavte na hodnotu true:

Zobrazí se tato zpráva: OnLockedToRaid:

Pokud chcete, aby se raid uzamkl pro hráče, stane se tak, když hráč způsobí poškození, nikoli když do něj vstoupí. Toto chování je ve výchozím nastavení povoleno a v takovém případě se nezobrazí žádná zpráva. Zobrazí se v aktualizaci stavového rozhraní, které je viditelné pouze tehdy, když se hráč nachází v nějaké události.

Doufám, že tohle věci objasní. Chápu, že překlad je obtížný, když není přesný.

@nivex
But what I mean is that no message appears, for example that the raid is locked for a player or that a player has a cooldown. The messages are present in the lang config, but it doesn’t show me anything!

@Tay

What messages? Paste them.

Everything is working as intended. By default, if you do not see a message, then it's intended that you do not see it in the way you expected.

I'll post again shortly to explain each message, the related options, what they apply to, and how they're triggered.

Message: OnLockedToRaid
Option: Lock Players To Raid Base After Entering Zone
Applies To: Buyable / Manual / Maintained / Scheduled Events
Shown when a player enters an event. This option locks the player to the raid, NOT the raid to the player. Locking the raid to the player uses separate options.

Message: BuyCooldown
Option: Buyable Cooldowns
Applies To: Buyable Events
Displayed when a player attempts to use the /buyraid command while still on cooldown.
This message does not prevent entering a raid, nor does it show the cooldown when entering a raid — it only blocks purchasing them, and is only shown when being blocked from that purchase. 

Message: LockedOut
Option: Player Lockouts
Applies To: Maintained / Scheduled Events
Shown when trying to enter a public event while on a lockout. Not related to Buyable Cooldowns, and not related to Buyable Events.