Your events planned once, published to Discord, tracked everywhere — with no homegrown bot to maintain

Many orgs have installed an external bot to handle their events — Raid-Helper, Sesh, Groupflows, Raid Organizer. It works at first, but you eventually hit the same walls: to create an event you have to type a /create slash command with syntax you forget every time, and if you take too long filling the fields the bot times out and you have to start over. Advanced options (RSVP roles, templates, permissions) live on a third-party web interface hosted by the bot vendor, disconnected from your org. Signup data lives with the bot's publisher, not with you. And creation rights stick to Discord roles, not to your org's real hierarchy.

Game Org takes the opposite angle. You create the event from the site — that's the only place you create, no slash command to memorize — and it gets published automatically to the Discord channel mapped to its category (category ↔ channel mapping set up once for all). The embed is clean, structured, with date, location, short briefing, and signup buttons. Your members sign up from Discord — via the embed buttons — or from the site interchangeably, and signups are bidirectional: same data, two interfaces. The bot is provided and maintained by Game Org, the data stays in your space, and creation rights follow your org's grade × role matrix, not Discord roles.

One org doesn't plan the same things as another, and even within an org not everyone creates the same kinds of events. A WoW guild wants Normal raid, Mythic+, RBG, Guild event categories. A GTA Online crew wants Heist, Street race, Business sourcing, Social event. An Arma milsim org wants Mission, Training, TTPs, Staff meeting. A Star Citizen org wants Mining ops, Patrol, Pirate hunt, Officer meeting.

Game Org hands you a set of event templates that you rename, color, and customize at onboarding to match your org's identity. Some templates keep a specific imposed behavior — typically training sessions, which inherit the concerned section's recurrence and logo — but the rest is fully in your hands. The right to create an event in each category is then granular: Game Org's permission matrix crosses grade and role to decide who can plan what. Your section leads create their section's training sessions, your officers plan the major operations, your staff reserves the NCO briefings. You stay in control, without micromanaging every creation.

Counting attendees at the start of an event is the most universal blind spot in guild tools. Ten players, you manage it by voice. Eighty, that's a quarter-hour lost while your members drift to their second screen and the briefing becomes inaudible.

With Premium, Game Org runs the roll call for you: the bot listens in real time to your org's Discord voice channel, identifies every connected member, and a « Mark all Discord attendees » button checks them in all in one click — five seconds, whether you're ten or a hundred. The event closes with a timestamped attendance rate, and latecomers get added in two clicks with undo.

On free, roll call is still there, in manual mode: you check the attendees yourself, with the same timestamped history and the same undo on every action. Automatic voice detection and bulk check-in are Premium: keeping a voice socket open with Discord costs resources continuously.