Duels and Squad Wars
Practical guide to player 1v1 duels and team Squad Wars: bets, invitations, formats, time limits, return of players and results.
On this page
Duels and Squad Wars allow players to arrange a controlled PvP match without the manual intervention of an administrator. Duels are intended for two players; Squad Wars for two whole squads in the selected format. The module deals with invitation, bet, preparation of participants, transfer, round time, result, short loot window and return.
Difference between modes
| Duel | Squad War | |
|---|---|---|
| Participants | 1 vs 1 | Squad vs Squad |
| Enter | Target Challenge or Open Challenge | 2v2 to 8v8 Challenge with Roster Building |
| Bet | BTC amount within the allowed range | BTC amount according to team setting |
| Result | Win, Lose, Draw or Expiration | Result of both squads after round ends |
Where to find it
- Duels → Overview – current and historical duels.
- Duels → Settings - commands, bets, timing, messages, rewards and Discord.
- Duels → Squad Wars - team settings, matches and results.
- SCUM Content → Duel info and Squad Wars info - public rules for players.
What to set
Common foundations
- Activation of the module and rollout for the selected server.
- Unique commands, BTC bet range and possible bonus from the system.
- Safe arena points, player spacing and return behavior.
- Invitation, preparation, round, looting and return-command validity times.
- Messages for each stage, chat colors and optional Discord results.
Duels
You set the length of the targeted and open challenge, the reminder interval, the maximum round time, the window for mutual kills and FAME gain or loss. A return command, such as /back, has a short validity so that it cannot be abused later.
Squad Wars
In addition to the bet, you determine the allowed formats, the time to fill the lineup, the maximum age of the squad data, the spacing of the teams and the length of the team round. The squad must have enough eligible members and the roster will be locked before the start.
Recommended startup procedure
- Prepare the arena and test the transfer and return without a bet or with a minimum amount.
- Set clear public rules: what counts as a win, what happens in a tie, and how long you can loot.
- Check that commands do not conflict with BTC, Packs, Warzones or Eventzones.
- Set conservative betting limits. The maximum technical value may not be the appropriate economic value.
- Test targeted duel, open challenge, expiration without acceptance, mutual kill and return.
- For Squad Wars, test the smallest format, incomplete roster, complete roster, and end round.
- Only then enable Discord results and higher bets.
Progress for the player
Duel
- The player uses
/duelaccording to the publicly described format and enters an opponent or open challenge and enters the BTC bet. - Upon acceptance, both players, balance and arena availability will be checked.
- Players prepare and move. Countdown and round time will begin.
- The result is determined by the game events. A safe return will become available after the loot.
Squad War
- The founder uses
/squadwars, chooses the format and bet. - The other squad accepts the challenge and both teams fill the required number of seats.
- After the rosters are locked, the participants move to team positions and the round starts.
- After the result, the bet is processed, the result is published and the players return.
Example from the Main server
Status of the database as of 1 September 2026.
| Setup | Duel | Squad Wars |
|---|---|---|
| Command | /duel, return /back | /squadwars |
| Bet | 2 to 1,000,000 BTC | 5 to 1,000,000 BTC |
| Format | 1v1 | 2v2 to 8v8 |
| Challenge / roster | 180 seconds; open reminder every 30 seconds | 180 seconds to build the roster |
| Round | 300 seconds, reminder every 30 seconds | 600 seconds |
| Loot | 90 seconds, last 10 seconds countdown | 80 seconds |
| FAME | Winner +20, loser -10 | According to team setting |
Duel history contained 21 completed and 5 expired challenges. Squad Wars had 1 completed and 1 expired record. The numbers are an audit example, not a promise of community activity.
Common problems
- The challenge is not created: check module status, order format, minimum bet, balance and whether the player is already in another match.
- Squad doesn't have enough players: the current line-up and fresh membership decide, not just the squad name.
- Match Expired: the invitation or roster was not completed within the limit. Expiration is not a loss of a played round.
- The result looks wrong: check the time and kill events including the mutual kill window. Do not fix a bet manually without checking the match.
- Return does not work: the return command has limited validity and belongs only to the participant of a particular completed match.