Teams, Playbook and variants

A team space (Teams) is private: only its members see its content. It brings together the members, a Playbook of strategies sorted by map and side (the Atlas), the team’s matches and training.

Create a team and invite

1. 1

   Create the team

   In Teams, give it a name: you are its owner.

2. 2

   Invite your players

   Members section: create an invite link (limited in time and uses, shown only once) or invite a CStonx account directly by SteamID64; they get a notification.

3. 3

   Accept

   The invitee accepts from the Teams page or opens the link they received.

The team workspace

Each team has its own sidebar, which can be collapsed (a menu on mobile): Overview, then Organisation (Calendar, Sessions, Availability), Tactics (Playbook, Map atlas), Competition (Preparations, Matches) and Team (Members, Activity, Settings). The switcher at the top moves between teams.

The Overview gathers what needs your attention: next session (answer in one click), expected answers, next match and how its preparation is going, strategies to review and recent activity. A badge on Calendar counts the sessions you have not answered yet.

Roles and rights

The Playbook and the Atlas

Each strategy has a map, a side, a zone, roles, paths, grenades, steps and notes. It follows a status: Draft, To review, To train, Validated or Archived. Every change creates a version: you can compare and restore, nothing is erased.

The tactical board is edited on the radar: move waypoints, set timings, add grenades, link them to a throw from the Stuff catalog or open the Nade Solver. Simulated trajectories are never mixed up with real throws.

In the editor, the toolbar on the left picks the tool (shortcuts V select, P path, G grenade, N note); Ctrl+S saves, Ctrl+Z undoes. The save status stays visible above the board. Switching tabs keeps your changes, and leaving the strategy without saving asks for confirmation.

A strategy opens in reading mode: next to the board, your role, the players, the utility in order (with a link to its lineup), the steps and the instructions. Click a role to fade the others, or Show only my role. If you can edit it, Edit (or E) opens the editing tools and Done goes back to reading.

The Playbook shows as a table or a gallery (your choice is remembered). Each strategy shows its objective (the first line of its description) and your role. The Favorites, My role and Active (in training or validated) shortcuts, the map, side, status and zone filters and search combine and stay in the page address, so you can share a filtered view. The ⋯ menu of a row offers a preview without leaving the list, duplication and Create a variant. New strategy only asks for the map, side and name, then opens the board. A coach can select several strategies and add them at once to a session or a preparation.

Under each Atlas map, {map} atlas (for example “Mirage atlas”) opens a page gathering what the team knows about that map: strategies and variants per side, zones, reference rounds linked to strategies, the team record (with the number of matches), sessions and preparations. Each block shows whether it is Team (private), Personal (your Nade Solver lineups) or Public (Stuff catalogue).

Turn an execution into a variant

1. 1

   Open a round

   In the 2D replay, pick a round then Turn into a variant; or, from the Playbook, Add a variant from a demo.

2. 2

   Pick the parent strategy

   The main strategy never changes: the variant is an independent copy.

3. 3

   Check the matching

   Players are paired with the plan’s roles. An uncertain pairing is flagged and must be fixed by hand.

4. 4

   Compare and choose

   Overlay plan and real execution, then keep the plan or the real one role by role and grenade by grenade.

Positions and grenades come from the demo; only values marked reconstructed are estimated (for example a throw position deduced from the path). The provenance (map, round, date) stays displayed, and the variant survives the demo disappearing.

Team matches

The Matches section lists games where enough members played on the same side: by default every member (5 at most), adjustable by a coach. Each member chooses whether to share their games with the team; withdrawing consent removes the matches involving them. Games that were never imported or analysed cannot appear.

Preparing a match

The Preparations section follows each opponent through Scout → Prepare → Train → Play → Analyse → Adapt. A coach sets the opponent, competition, date, format (BO1, BO3, BO5) and map pool, then links Playbook strategies, sessions and, after the game, the matching team matches and a debrief. Players read it without editing.

A preparation page follows the order Opponent → Scouting → Veto → Strategies → Checklist → Match, with a table of contents that ticks the sections already filled in. The step shown at the top is computed by CStonx from the preparation’s content.

A preparation can also hold a scouting report (maps, sides, tendencies, players to watch, representative rounds, with the sample, period and sources), a veto simulation (common BO1, BO3, BO5 templates or a custom sequence; always check your competition’s rules) and a pre-match checklist where each step can have an owner. No step is mandatory.

Decision tree, discussions and sharing

A strategy’s Decision tree tab describes the planned adaptations: if a condition comes up (area lost, player killed, timing), the team switches to an alternative plan, falls back or shifts its timing. Conditions are written in plain words and judged during the round.

In the Discussion, a message can target a round (with a range of seconds), a grenade, a role, a step or a branch; you can reply, mark it resolved, and each message has its own link. The Playbook exports to a JSON file, without SteamIDs or demo provenance; import shows a preview and lets you choose copy, merge or nothing for each strategy.

Training and tracking

A coach plans sessions: strategies to work on, grenades to learn, assigned roles, objectives. Three levels of evidence stay distinct: mastery declared by the player, mastery validated by the coach, and performance measured on linked real rounds. A rate is only shown as reliable from 5 rounds. The Activity section gives the team report and the change log.

The Calendar shows sessions, preparations and matches by month, week or as a list; the Sessions section gives attendance for each session (Present, Absent, Excused, or Pending until you answer) and Utility programs (grenades to learn in order: everyone declares their status, the coach validates). The Activity section compares two periods (matches, strategy rounds, sessions, attendance), always showing the sample size.

In Availability, the My week tab holds your typical week, in your time zone: left click adds hours, right click removes them, and holding the button while sweeping over cells changes them all (on a touch screen, a tap flips a cell). Shortcuts fill weekday evenings or the weekend, Undo (Ctrl+Z) reverts the last change, and everything is saved automatically. Add your unavailable days (holidays, LANs) next to it. The Team tab shows the Common slots in your own time zone: each cell shows the profile pictures of the available players (“+n” beyond 4), the darker it is the more complete the team, and the darkest shade means the full team. The week’s best slots are suggested, and a coach schedules a session straight from a slot. Availability is not attendance: attendance is always confirmed on the session. In Members, the coach sees who will not get the Discord reminder before sessions (Discord not linked, reminders off or DMs closed).

After a CS2 update, a verified grenade becomes potentially affected if the map version changed; it is never declared invalid without a check. Coaches are notified and the map’s Atlas lists the grenades to review.