Платное Team Watch 3.0.2

TeamWatch 3.0​

TeamWatch is an advanced team monitoring, anti-team-hopping, enforcement, and abuse prevention plugin for Rust.

Originally designed as a simple team-change tracker, TeamWatch has evolved into a complete system for controlling how often players can create, leave, and switch teams while giving administrators a detailed audit trail of team activity.

TeamWatch can operate as a passive monitoring system or actively block abusive team changes, enforce cooldowns, protect raid/combat situations, track unique team relationships, and alert staff through in-game messages and Discord.

Whether you run a PvP, PvE, modded, competitive, or high-population server, TeamWatch gives you precise control over team-changing behavior without requiring constant manual monitoring.

---

Main Features​

✅ Player-Based Team Change Limits​

Set how many tracked team changes a player is allowed within a configurable rolling time period.

Example:

• Maximum Changes: 1
• Time Frame: 24 Hours

TeamWatch tracks each player's valid changes individually and automatically removes expired entries from the active tracking window.

Team creation can optionally count as a team change.

---

✅ WarnOnly & Block Enforcement Modes​

Choose how TeamWatch handles violations.

WarnOnly

Players are allowed to continue, but TeamWatch:

• Records the violation
• Warns the player
• Alerts online admins
• Sends a Discord alert
• Logs the event

Block

TeamWatch can stop the action before it happens.

Depending on your configuration, players can be prevented from:

• Joining another team after reaching their limit
• Creating a new team during restricted conditions
• Joining or creating teams during cooldown
• Changing team state during raid/combat restrictions

This lets server owners choose between monitoring-only and active enforcement.

---

✅ Verified Team Change Tracking​

TeamWatch does not blindly count every team hook as a successful change.

Team joins, leaves, and kicks are verified against the player's actual team state before being recorded.

This significantly reduces false records when:

• Another plugin blocks the action
• The team operation fails
• The player disconnects
• The expected team state was never actually applied

---

✅ Team Leave Cooldown System​

Optionally apply a cooldown after a player leaves a team.

During this cooldown, TeamWatch can prevent the player from immediately joining or creating another team.

Configuration includes:

• Cooldown duration
• Team creation restriction during cooldown
• Optional cooldown when a player is kicked

This helps prevent rapid team rotation and team-hopping abuse.

---

✅ Smart Same-Team Return Protection​

Accidental team leaves should not always be treated as abuse.

TeamWatch can allow players to return to the same team within a configurable grace period without counting the return as another team change.

Example:

• Player leaves Team A
• Same-team return grace period: 10 minutes
• Player rejoins Team A after 3 minutes

The return can be excluded from the team-change counter.

---

✅ Unique Team Tracking​

TeamWatch can record how many different teams each player has joined.

This provides administrators with much more useful information than a simple change counter and helps identify players who repeatedly rotate between different groups.

Tracked information can include:

• Current valid change count
• Unique teams
• Detailed recent team history
• Violation count
• Cooldown state

---

✅ Raid & Combat Protection Integration​

TeamWatch includes configurable support for external raid/combat blocking systems such as NoEscape.

When enabled, TeamWatch can prevent selected team actions while a player is raid or combat blocked.

Available protections include:

• Block joining teams
• Block creating teams
• Block leaving teams
• Block kicking team members

External plugin names and API hook names are configurable, allowing the integration layer to be adapted when necessary.

Raid/combat protection requires a compatible external plugin and must be enabled in the configuration.

Нажмите для раскрытия...

---

Smart Discord Integration​

TeamWatch provides separate Discord functionality for normal events and important violations.

Violation / Block Alerts​

Detailed Discord embeds can include:

• Player name
• Steam ID
• Enforcement mode
• Whether the action was blocked or allowed
• Violation reason
• Team-change count
• Allowed limit
• Tracking period
• Unique team count
• Team ID
• Current team members
• Timestamp

---

Normal Team Event Logging​

Normal team events can optionally be sent to a separate Discord webhook.

Events include:

• Team Created
• Team Disbanded
• Player Joined Team
• Player Left Team
• Player Kicked
• Team Action Blocked
• Administrative TeamWatch actions

Normal logs can use Discord embeds or compact text messages.

---

Discord Queue & Rate Protection​

TeamWatch includes an internal Discord request queue.

Configurable options include:

• Minimum delay between webhook requests
• Maximum queued webhook requests
• Violation alert cooldown per player

This helps reduce webhook spam and protects the plugin from flooding Discord during periods of heavy activity.

Webhook HTTP failures are also detected and can provide additional information while Debug Mode is enabled.

---

In-Game Staff Alerts​

Important violations can be sent directly to online administrators with the teamwatch.admin permission.

This allows staff to react immediately without constantly watching Discord or the server console.

---

Multilingual Support​

TeamWatch includes native language support for:

• 🇬🇧 English
• 🇹🇷 Turkish
• 🇷🇺 Russian

Player-facing messages automatically use the appropriate supported language through Rust/uMod localization.

---

Advanced Data Management​

TeamWatch stores significantly more information than the original version while automatically maintaining its data.

Features include:

• Rolling team-change history
• Detailed change history
• Unique team records
• Last team leave time
• Previous team ID
• Violation counters
• Configurable detailed history retention
• Automatic expired-data cleanup
• Optional reset on a new map save
• Automatic saving during server operation and unload

---

Legacy Migration​

Upgrading from the original AttackTeam or an earlier TeamWatch version is supported.

TeamWatch can migrate legacy player change history from the old AttackTeam data file when appropriate.

The old [AttackTeam] prefix is also automatically migrated to [TeamWatch] when detected in an existing configuration.

---

Configuration Validation​

TeamWatch automatically checks important configuration values during startup.

Invalid or unsafe values are corrected to usable limits where possible, including:

• Negative cooldowns
• Invalid tracking periods
• Invalid enforcement modes
• Invalid history retention
• Invalid UTC offsets
• Invalid Discord queue settings
• Missing configuration sections
• Missing permissions
• Missing integration API lists

This makes upgrades between versions much safer.

---

Advanced Logging & Debugging​

TeamWatch can independently provide:

• Server console logs
• Discord event logs
• Violation alerts
• Online administrator alerts
• Administrative audit logs
• Debug information
• Discord HTTP failure information

Debug Mode can be enabled when deeper troubleshooting is required.

---

Tracked & Controlled Events​

TeamWatch monitors or controls:

🛠️ Team Created
🙋 Player Joined a Team
🚪 Player Left a Team
🔨 Player Kicked from Team
💥 Team Disbanded
🚨 Team Change Limit Exceeded
🛑 Team Action Blocked
⏳ Cooldown Restriction
⚔️ Combat Block Restriction
💣 Raid Block Restriction
🛡️ Administrative TeamWatch Actions

---

Example Use Case​

Configuration:

• Maximum Changes: 1
• Time Frame: 24 hours
• Enforcement Mode: Block
• Leave Cooldown: 30 minutes
• Same-Team Return Grace: 10 minutes

Example:

1. A player creates Team A.
2. The valid change is recorded.
3. The player leaves Team A.
4. A 30-minute cooldown starts.
5. The player attempts to immediately join Team B.
6. TeamWatch blocks the action and explains the remaining cooldown.
7. Administrators receive an in-game alert.
8. A detailed Discord embed is generated.
9. The blocked attempt is logged.
10. The player's violation counter is updated.

If the player instead returns to Team A within the configured grace period, TeamWatch can treat it as a legitimate same-team return rather than a new team-hop.

---

Why TeamWatch?​

TeamWatch helps server owners:

• Reduce team-hopping abuse
• Enforce team-change rules automatically
• Prevent rapid group rotation
• Protect raid/combat situations
• Identify players rotating through many different teams
• Reduce false-positive tracking
• Give staff detailed player history
• Maintain a timestamped audit trail
• Receive immediate in-game and Discord alerts
• Reduce manual moderation workload
• Customize enforcement for different server styles

From passive monitoring to active enforcement, TeamWatch gives server owners complete control over player team-change behavior.