PvP Players Raiding and Switching to PvE to Avoid Retaliation

We're running a hybrid PvP/PvE Rust server and recently faced a serious issue. A player joined a PvP team, raided another player's base, then went to a safe zone and used /flag to switch back to PvE. The raided player couldn't retaliate, and we ended up losing players over this. We already have a 24-hour flag cooldown, safe-zone requirement, and team synchronization enabled.Is there any way to prevent players from switching to PvE for 12–24 hours after raiding someone? Also, does team synchronization bypass the normal flag cooldown?

Its been awhile, but there is compatability with the NoEscape plugin that can make it so players cannot /flag when they are raid blocked or combat blocked. That might help you in this situation?

Thanks @mr01sam! We'll try NoEscape with WarMode.

Just wanted to clarify two things:

Does NoEscape block /flag for the player who initiates a raid, or only the player being raided?

If a player joins a PvP team and gets switched to PvP automatically, will NoEscape prevent them from switching back to PvE after raiding?

Our main concern is preventing players from raiding someone and escaping retaliation by switching to PvE.

Thanks for your help!

I'm not an expert on NoEscape, and definitely let me know if it doesn't pan out to be that helpful for you.. but I think it marks the player who initiates the raiding as "raid blocked". The defending player might get marked as "combat blocked" if they defend their base, but that's a different marking than "raid blocked" and I think WarMode lets you choose which ones prevent the /flag usage.