2BN Nexus/CRCON Configuration

This page is currently being developed and may be subject to change without notice

This is the Document Release Information
Article Number:	7CAV-BATT2-012
Scope:	CRCON
Version:	Version 1.0
Effective Date:	15JUL2025
Last Modified Date:	15JUL2025
Approving Authority:	2BN Commanding Officer
Point of Contact:	2BN Executive Officer

THIS DOCUMENT MAY NOT BE EDITED WITHOUT 2-7 COMMANDER APPROVAL.

Public Scoreboards

Server Name	Scoreboard Link
Training Server 1	https://sb1.hll.7cav.us/
Training Server 2	https://sb2.hll.7cav.us/
Tactical Realism | US Central	https://sb3.hll.7cav.us/
Tactical Realism | US EAST	https://sb4.hll.7cav.us/

In Game Chat Commands

!help | !info

Description: These commands will show you the available chat commands on the server.

!next | !nextmap

Description: Displays the next map in rotation.

!wkm (who killed me)

Description: Displays your last killer name and weapon.

!seed

Description: Displays the seed conditions.

!rules | !roe

Description: Displays the server's rules.

!discord

Description: Displays 7cav discord link.

!website | !cav | !7cav

Description: Displays 7cav website link.

!wik

Description: Displays your last victim's name.

!scoreboard | !stats

Description: Displays the server stats link.

Maps

Change

You can choose a map to be loaded using filters or plain search.

The selected map will be loaded as soon as you click on the "Confirm" button, ending the current game.

Objectives

Clicking on the tactical map, you can define the objectives (cap points) to fight on the current map.

The map will be reloaded using the defined objectives as soon as you click on the "CONFIRM LAYOUT" button, ending the current game.

Records

Blacklist (Bans)

A blacklist contains a collection of bans (temporary and/or permanent), a list of servers to which they apply and a sync method.

Bans on 7cav HLL servers are synced across our 4 platforms.

Blacklist 1: Permanent Bans

 The ban will immediately be propagated to the game server. This makes it significantly less likely for players to slip through due to temporary  connection hiccups, and they will not be able to queue.

 However, they won't ever be able to see the ban reason, unless they were online at the time of being blacklisted.
 This method is not recommended if you intend to commonly edit the blacklist or any of its bans.

Status	Instant Kick	Enter the queue next time	See reason message
Player on server	Yes	No	Only one time
Player offline		No	Never

Blacklist 2: Temporary Bans

A player can join the queue and then will be kicked when they connect to the game server. They will be told why they have been kicked (ban reason).

Status	Instant Kick	Enter the queue next time	See reason message
Player on server	Yes	Yes	On each try
Player offline		Yes	On each try

Webhooks

This will only be relevant to those who review server logs. Webhooks will only be configured for Tac East and Central.

Automods

Standard Auto Mod Cycle

The standard automatic moderation cycle consists of the following four steps:

Step	Action	Notes
1	Internally Noting	X times
2	Warning via Direct Message	Y times
3	Punishment	Z times
4	Kick	Final step

Level

7th Cavalry Public Servers are not currently under level thresholds control.

Seeding Rules

The following rules apply during the seeding phase:

1. Only the middle sector is a playable objective.
2. Combat Area: Limited to the two map rows or columns that contain the central sector (dependent on map layout).
3. Armored Assets must remain in HQ and are not permitted to leave during seeding.
4. Artillery is restricted until the server reaches 20v20 (40 total players).
5. In-game Squad Leaders are expected to report any rule violations to a 7th Cavalry Admin (MP) or a member with admin tags.

Spirit of the Rule: When either team has fewer than 20 players, both sides should focus solely on the central sector with restricted use of combined arms. This ensures a balanced and enjoyable experience until there are enough players for full, vanilla gameplay.

Step	Action	Notes
1	Internally Noting	Documentation only
2	Warning via Direct Message	Issued up to 3 times (20-second interval between each)
3	Punishment	Up to 5 times (60-second interval between each)
4	Kick	Final step – 60-second grace period before removal

No Solo Tanking

• Armor must be occupied by at least 2 players; "lone-wolfing" armor is prohibited.

• Spirit of the Rule: Armor are vital team assets. Multiple players ensure their effective use, maximizing team success. Any solo armor crews must stay in the HQ until they have a second player.

Messages:

1. "warning_message": "Warning, {player_name} ! You can't play solo tank on this server ! You will be punished after {max_warnings} warnings (you already received {received_warnings}). Next check will happen automatically in {next_check_seconds}s.",
2. "punish_message": "You violated solo tank rule on this server. You're being punished by a bot ({received_punishes}/{max_punishes}). Next check in {next_check_seconds}s."
3. "kick_message": "You violated solo tank rule on this server. Your grace period of {kick_grace_period}s has passed. You failed to comply with the previous warnings."

Step	Action	Notes
1	Internally Noting	Documentation only
2	Warning via Direct Message	Issued up to x times (x-second interval between each)
3	Punishment	Up to x times (x-second interval between each)
4	Kick	Final step – x-second grace period before removal