Sessions & dropmaps

How sessions work

A lobby session is one lobby of an event. When an event runs multiple lobbies at once, each lobby is its own session and they share a session key — that's how Zyron knows they belong together. For each lobby, Zyron provisions a dedicated Discord surface: a category with registration, chat, teams, dropmap, and keys channels, plus a participant role that gates them.

Every session carries a few core choices:

• Team mode — Solos, Duos, Trios, or Squad (with an optional custom team-size override).
• Gamemode — Build, Zero Build, Reload, or Reload Zero Build. This decides the playlist the hosted match loads into.
• Access role — the lowest role allowed to sign up at all.
• Priority levels — an ordered list of roles that get to register earlier (see below).

Creating a session

Create sessions from the dashboard's Sessions page: set the name, dates, team mode and gamemode, pick the access role and priority levels, and configure the dropmap and scoring. On create, Zyron builds the channels and roles and schedules registration — nothing else to wire up. Sessions can also be created and managed programmatically via the Sessions API.

Registration & priority

Registration opens at the scheduled time (or instantly with the Open now action). Members sign up as teams — a captain registers and invites teammates, who confirm to activate the team. When the lobby is full, new teams go to the waitlist and are promoted automatically when a spot frees up.

Priority levels stagger the start: the first level's roles can register the moment registration opens, each following level waits one delay step longer, and members holding only the access role go last. This is how servers give boosters or subscribers an early window without running separate events.

The dropmap

The dropmap lets registered teams claim their landing spot on the current Fortnite map, so drop contests are settled before the first match. Depending on the session's draw mode, teams either draw a free-form area, pick a named zone, or both. Claims are exclusive by default (one team per zone, no overlaps), with a configurable cap for shared zones.

• Opening — the dropmap opens on schedule, optionally in tiers so higher-priority teams claim first. You can also open it manually at any time.
• Claiming — captains claim from the dropmap panel in the session's dropmap channel. Admins can place, reassign, or remove any claim regardless of tier windows.
• Locking — at the lock time (or manually), claiming freezes and Zyron posts the final map image with every team's spot rendered. A configurable warning goes out before the lock. Locked maps can be unlocked if plans change.

Hosting matches

When it's time to play, host a match from the session. Zyron creates a customs session pre-seeded with every active team's players and starts key delivery: the bot pool friends each player in Fortnite, joins their party, and enters the match key in-game — no key ever needs to be pasted in chat. The host is DM'd and confirms when ready.

Results & leaderboard

After each game, players upload their .replay file in the session's replay channel (or on the web). Zyron parses every replay, merges the reports into one authoritative result, scores it with the session's point system, and posts the match results. The leaderboard updates live across matches — standings, points, placements, and eliminations per team.

Fill requests

Teams drop out; lobbies should still be full. After registration closes, open fill requests for the number of empty spots — members who missed registration can claim them first-come, first-served from the fill channel, and claimed teams slot straight into the lobby.

Next steps

The whole flow is scriptable: create sessions, register teams, control the dropmap, and host matches via the Sessions, Teams, Dropmap, and Matches & leaderboards APIs — and subscribe to webhooks to react to signups and results in real time.