TruePVE

I’m really sorry to bother you again…

This time, I have a question about integrating with your masterpiece plugin, TruePVE.

On my server, TruePVE is being used to enforce PvE rules.

Is the following configuration possible?

Allow players to raid PvE raidable bases without allowing them to damage other players’ bases.

As far as I can tell, damage between players is properly blocked.

However, if I block damage to structures to prevent base raiding, it also prevents damage to raidable bases—so in order to allow those to be raided, I end up having to allow player base damage too.

I’m trying to find a way to solve this.

Please, I would really appreciate your help!

TruePVE.json RaidableBases.json

heya maxalt

none of this is required.

RB has its own configuration, and requires zero changes to your TruePVE config.

if damage is not working properly in RB, then you have a misconfigured profile (oxide/data/RaidableBases/Profiles), or another plugin is breaking it. 

i've fixed your invalid TruePVE config. do not modify it for RB.

TruePVE.json

secondly, in regards to your samsite rules. they were invalid, and replaced with flags.

PlayerSamSitesIgnorePlayers will block targeting (and damage) from player-owned samsites to players/vehicles.

StaticSamSitesIgnorePlayers will block targeting (and damage) from non-player samsites to players/vehicles. this includes the Launch Site, which you should remove if you want samsites at the Launch Site to kill players.

Thank you very much.

Actually, one of the players on my server recently got shot down by a SAM site they had placed themselves while flying a minicopter, and I was trying to figure out how to prevent that.

I’m sorry for suddenly changing the topic from RaidableBases to something completely different… But I truly appreciate your help.

Just to confirm, does the TruePVE config you shared mean the following?

Players cannot damage structures or deployables owned by other players, but can damage structures from RaidableBases.

While flying in a helicopter or minicopter, they might get shot by static SAM sites (like the ones at the Launch Site), but not by SAM sites placed

hi, you're welcome. that is what it means with the exception that you need to remove StaticSamSitesIgnorePlayers flag for launch site to fire at players.

Thank you so much.

You’re a genius.

There’s one more thing I wanted to ask about RaidableBases,but I feel like I’ve already asked too much… so I’ll come back another time

lol you can ask, it's fine

Really, truly, sincerely thank you!

Then if I may take you up on your offer…

Here’s what I’d like to do with RaidableBases:

 Cooldown After Raid Completion

After completing a Raidable Base (whether from a scheduled spawn or via the /buyraid command), I want to prevent the player/team from raiding again for 3 hours.

During this cooldown, they should not be able to enter any dome, regardless of difficulty level.
(e.g. even if a player finishes a Nightmare base, they should not be able to enter a Medium base dome within the 3-hour cooldown).

Ideally, this cooldown should apply to everyone in the team.

Additionally, players should not be able to bypass the cooldown by:

Leaving their team,

Joining another team.

Max Simultaneous Raids & Queue System

I want a maximum of 10 Raidable Bases on the map at once, regardless of how they were spawned (Scheduled or /buyraid).

If someone tries to run /buyraid while the cap is already hit, they should be forced to wait until a raid is completed and despawns.

Ideally, when /buyraid is used while the limit is reached:

A queue line is created.

Once a raid finishes and a slot becomes available, the base spawns for the player at the front of the queue.

Would such a setup be possible with RaidableBases?

4分前、maxaltは言った：

本当に、本当に、心からありがとう！

では、あなたの申し出を受け入れてもよければ...

 

RaidableBasesでやりたいことは次のとおりです。

 

レイド完了後のクールダウン

レイダブルベースを完了した後（スケジュールされたスポーンからでも/buyraidコマンドからでも）、プレイヤー/チームが3時間再びレイドするのを防ぎたいです。

このクールダウンの間、彼らは難易度に関係なく、どのドームにも入ることができないはずです。
（例えば、プレイヤーがナイトメアベースを終えたとしても、3時間のクールダウン内にミディアムベースドームに入ることはできません）。

理想的には、このクールダウンはチームの全員に当てはまります。

さらに、プレイヤーは次のことによってクールダウンを迂回することはできません。

彼らのチームを去り、

別のチームに参加する。

 

 

最大同時レイドとキューシステム

どのように生成されたか（スケジューリングまたは/buyraid）に関係なく、一度に最大10の襲撃可能な基地をマップに表示したい。

誰かがキャップがすでにヒットしているときに/buyraidを実行しようとした場合、レイドが完了してデスポーンするまで待つ必要があります。

理想的には、制限に達したときに/buyraidが使用される場合：

キュー行が作成されます。

レイドが終了し、スロットが利用可能になると、基地はキューの先頭のプレイヤーのためにスポーンします。

 

RaidableBasesでそのような設定は可能でしょうか？

Additional note!

For example, even if there are already 10 Raidable Bases on the map (the maximum allowed number),

I still want the scheduled Raidable Bases to spawn.

hi,

Quote

Leaving their team,

Joining another team.

lol, players will always exploit. Block Players From Joining A Clan/Team To Exploit Restrictions is a config option that will help, but it is impossible to fix all exploits. ban the player.

Cooldowns:

• Player Lockouts (public events: maintained and scheduled)
• Buyable Cooldowns (private events: buyraid events)

Limit events per type:

• Max Buyable Events
• Max Scheduled Events

there is no global limit. you must set a limit per type only.

if you set Max Buyable Events to 10 and Max Scheduled Events to 10 then the total is 10+10=20

Got it! If the behavior is bad, I’ll go ahead and ban them.

I’ll share the .json file from /config, so could you take a look at my current cooldown settings?

As far as I know, I intended to set:

・3-hour cooldown for buyable raids

・3-hour cooldown for scheduled raids as well
…but I’m not sure if it’s working as intended.

RaidableBases.json

hi,

this will not apply when in vanish, noclip, or raidablebases.canbypass permission (never give that permission to a player, by the way)

scheduled/maintained are not configured for a 3 hour cooldown.

use this:

      "Player Lockouts (0 = ignore)": {
        "Apply Lockouts To PVE": true,
        "Apply Lockouts To PVP": true,
        "Apply All Lockouts Everytime": true,
        "Block Clans From Owning More Than One Raid": true,
        "Block Friends From Owning More Than One Raid": true,
        "Block Teams From Owning More Than One Raid": true,
        "Block Players From Joining A Clan/Team To Exploit Restrictions": true,
        "Time Between Raids In Minutes (Easy)": 180.0,
        "Time Between Raids In Minutes (Medium)": 180.0,
        "Time Between Raids In Minutes (Hard)": 180.0,
        "Time Between Raids In Minutes (Expert)": 180.0,
        "Time Between Raids In Minutes (Nightmare)": 180.0
      },

buyable cooldowns are missing quite a few cooldowns, and several were set to 1800 not 10800. this will never apply to admin.

use this:

        "Easy": {
          "VIP Permission: raidablebases.vipcooldown": 10800.0,
          "Admin Permission: raidablebases.allow": 0.0,
          "Server Admins": 0.0,
          "Normal Users": 10800.0
        },
        "Medium": {
          "VIP Permission: raidablebases.vipcooldown": 10800.0,
          "Admin Permission: raidablebases.allow": 0.0,
          "Server Admins": 0.0,
          "Normal Users": 10800.0
        },
        "Hard": {
          "VIP Permission: raidablebases.vipcooldown": 10800.0,
          "Admin Permission: raidablebases.allow": 0.0,
          "Server Admins": 0.0,
          "Normal Users": 10800.0
        },
        "Expert": {
          "VIP Permission: raidablebases.vipcooldown": 10800.0,
          "Admin Permission: raidablebases.allow": 0.0,
          "Server Admins": 0.0,
          "Normal Users": 10800.0
        },
        "Nightmare": {
          "VIP Permission: raidablebases.vipcooldown": 10800.0,
          "Admin Permission: raidablebases.allow": 0.0,
          "Server Admins": 0.0,
          "Normal Users": 10800.0
        }

Thank you so much!

Thanks for sticking with me for so long.

Is it okay if I ask you again if something comes up…?

you're welcome

yes, just create a new ticket and i will answer you there

Changed Status from Pending to Closed