Overview
What LogMe replaces, and how the pieces fit together.
Most milsim units run several separate bots for verification, attendance, and leveling that don't share data, so staff end up reconciling rosters by hand. LogMe consolidates that into one system: a Discord bot for day-to-day commands, and a web dashboard for configuration, rosters, and reporting — both reading and writing the same underlying data, so a change made on one side is instantly visible on the other.
Every Discord server LogMe is added to gets its own isolated configuration and data. Nothing is shared between servers.
Getting started
From invite to first configured event channel.
2.1 Invite the bot
An administrator invites LogMe to the Discord server and grants it the Server Members and Message Content intents in the Developer Portal — required for auto-promotion and the roster to see the member list.
2.2 Follow the setup wizard
The first time an admin opens the dashboard of a freshly-added server, LogMe walks them through a short guided setup — a four-step wizard (log & voice channels, log types, promotion ladder, staff roles & Roblox group) with a progress bar. It's available in your language, and every step can be skipped and finished later. The bot also DMs a setup link when it joins a server.
The channels can also be set with the command /set_config <voice> <log channel>. Everything the wizard covers stays editable afterward from the dashboard's Admin panel.
2.3 Log in to the dashboard
Any member signs in at the dashboard with Discord OAuth and selects a server where they are an administrator and the bot is present. Officers and admins get access to additional pages based on their configured roles.
Running events
The core loop: start, track, close.
3.1 Start an event
A host runs /startevent <host>, which posts a live-updating log embed and begins tracking who is present in the configured voice channel. Members can also be added or removed manually with -add / -remove mentions.
3.2 Track attendance automatically
Attendance is counted from voice presence: a member needs roughly 15 minutes in the tracked channel during the event to be credited. Events are auto-numbered, and if one is never explicitly closed, the bot recovers it automatically rather than leaving it stuck open.
3.3 Close it out — just two commands
/update records everything in one adaptive command: result (win/loss/undeployed), MVP, notes, and every custom field your server defined. The command adapts to your server — each field shows with the right input (a text box, a dropdown for preset choices like map or server, or a real member picker to tag a co-host). Then /clearevent closes the event, finalizes attendance, and triggers the auto-promotion pass. Ending an event is only those two commands, and /update regenerates itself on your next /startevent whenever you change the fields.
Training & XP
A parallel progression track alongside events.
Officers run /training_start, add or remove attendees with _add / _remove, and end the session with _end (or cancel it with _cancel). Attendees are registered from voice presence, same as events, and completed sessions grant XP. XP feeds into member levels, a server leaderboard (/leaderboard), and can unlock XP-reward roles configured in the dashboard. /profile shows a member's own rank, event count, and XP level; /training_status shows the currently running session.
Roblox verification
Linking a Discord identity to a Roblox account.
Members link their Roblox account with /verify, which sends them a secure personal link to authorize through Roblox OAuth on the dashboard — no codes to copy. /unverify removes the link and /whois looks up who a Roblox or Discord identity belongs to. Once verified, the dashboard's Verification page can apply a verified role and a nickname template automatically, and members can self-service delete their own data (GDPR) from that same page. /sync then keeps Discord roles aligned with the linked Roblox group rank, either on demand for one member or automatically for everyone on a fixed interval.
Auto-promotions
A role ladder driven by event count and XP.
Admins define a promotion ladder in the dashboard — a sequence of roles, each unlocked at an event-count threshold, plus reward roles tied to XP level. LogMe evaluates this automatically whenever an event closes, or on demand with /checkpromotions, which also reports diagnostics (for example, a role-hierarchy problem that would silently block a promotion) so misconfiguration doesn't fail quietly.
Log embeds
Customizing what gets posted where.
/log config, /log channel, /log toggle, /log title, /log color, and /log message customize the embeds LogMe posts for events, trainings, and other tracked actions — which channel they go to, whether they're enabled, and how they look. /log list shows current settings and /log test sends a preview.
Web dashboard
Everything commands don't cover.
The dashboard mirrors and extends what the bot tracks:
- Roster — every member, verified or not, with Roblox rank, event count, XP, status, search/sort, and a weekly attendance chart.
- Leaderboard, Events, Member files — rankings, full event history with live events force-closable by staff, and per-member stats with admin edit tools.
- Auto-Promotion — the role ladder editor described above, with role-hierarchy warnings.
- Schedule — announce upcoming events with a live Discord countdown, reminders, and recurrence, using a customizable message template. Members can RSVP to an event message with a reaction (🟩 🟢 ✅), and staff DM everyone who's currently in with
/trigger_schedule— the DM text is configured on this page. - Admin panel — server config, officer/admin role assignment, Roblox rank-to-role mapping, the blacklist, log embed settings, and the live event message template.
- Bot Identity (Premium) — give the bot your server's own name and avatar on the messages it posts (logs and announcements), set from the Admin panel.
- Seasons & Audit — archive and reset the leaderboard for a new season, and review a full admin audit log of configuration changes.
Discover & advertising
Recruit new members with a free public listing.
Any server can list itself for free on the public Discover directory. From Dashboard → Advertise, an admin writes a short pitch, adds a permanent Discord invite, tags and a banner, then ticks Publish. The server appears in the directory and also gets its own shareable recruitment page at /discover/your-clan — with a custom link of your choice and a clean preview when shared. Un-publish at any time to go offline.
Listings are self-service, but moderated: the LogMe team can take down anything abusive.
FAQ
Common questions when setting up.
Q. Do I need the Roblox integration?
No — verification and rank sync are optional. Event tracking, training, and promotions work without a Roblox OAuth app configured.
Q. What happens if an event is never closed?
LogMe auto-recovers events that are left open, so attendance data isn't lost even if a host forgets to run /clearevent.
Q. Can multiple servers use the same bot instance?
Yes — LogMe is fully multi-server. Each guild's configuration and data are completely isolated from every other guild.
Q. Where can I ask more questions?
Contact vitchapo on Discord, or see the Terms & Privacy page for data-handling details.