Skip to main content
Most Seshy issues trace back to one of three root causes: a missing permission, a misconfigured channel, or a module that isn’t enabled. Work through the relevant section below and you’ll have the problem resolved in a few steps. If nothing here fixes it, the support server at seshy.lol is the fastest path to a solution.

​
Bot and Commands

Start by confirming Seshy is online at seshy.lol/status. If the status page shows a degraded or offline state, the issue is on Seshy’s side and will resolve on its own.If Seshy is online but still not responding:
  1. Verify that Seshy has the Use Slash Commands permission in the channel you’re using. Check the channel’s permission overrides under Server Settings → Channels → Permissions.
  2. Check that slash commands are actually appearing when you type /. If they don’t appear, Seshy’s slash commands may not be registered for your server yet.
  3. Try re-inviting Seshy using the invite link at seshy.lol. Re-inviting with the standard invite URL re-registers slash commands without removing any existing configuration.
  4. If commands appear but do nothing, confirm Seshy has Send Messages and Embed Links in that channel — without these, Seshy can receive your command but cannot reply.
Seshy enforces a permission hierarchy for staff commands. If a command returns a denial message, the user’s Discord role does not have the required permission level configured in Seshy.
  1. Run /settings and navigate to Roles & Permissions to review which Seshy permission level is assigned to each role.
  2. Check that the user has a role mapped to a permission level that includes the command they’re trying to run. Some commands are restricted to specific levels (for example, starting a session may require a higher level than submitting an LOA request).
  3. If the user should have access, update their role’s permission level in /settings → Roles & Permissions and have them try again.
Seshy’s permission hierarchy is separate from Discord’s built-in role permissions. A user with the Discord Administrator permission still needs the correct Seshy permission level to run Seshy staff commands.

​
ER:LC Integration

If the ER:LC integration isn’t pulling live data, work through the following:
  1. Verify the API key — go to your ER:LC Private Server settings in-game and copy the API key fresh. Paste it again in /settings → ER:LC Integration. Keys can change when the Private Server is reset or transferred.
  2. Confirm your Private Server is online — the integration can only pull data when your ER:LC server is actively running. If the server is shut down in-game, live data pauses until it comes back up.
  3. Run a connection test — use /settings → ER:LC → Test Connection to run a live verification. The test result will tell you whether the key is valid and whether Seshy can reach the server.
  4. If the test passes but data still looks stale, give it a minute. Some data types update on a polling interval rather than in real time.

​
Ares Security

If Ares appears to be inactive or isn’t stopping suspicious actions:
  1. Check Seshy’s permissions — Ares requires Administrator to reverse dangerous changes. If Seshy’s role doesn’t have Administrator, Ares can detect threats but cannot respond to them fast enough to prevent damage.
  2. Run /ares status — this command shows whether the Ares module is currently enabled and lists which protection layers are active.
  3. Check the whitelist — run /settings → Ares → Whitelist and confirm the account or role performing the action is not accidentally whitelisted. Whitelisted users bypass all Ares protections.
  4. Confirm Seshy’s role is high enough — if Seshy’s bot role sits below the role being abused in the role hierarchy, Discord will not let Seshy reverse those changes. Move Seshy’s role to the top of the role list.

​
Sessions

If /ssu or /ssd runs successfully but no embed appears:
  1. Check the session channel — run /settings → Sessions → Channel and confirm a specific channel is assigned for session embeds. Without a channel configured, Seshy has nowhere to post.
  2. Check channel permissions — Seshy needs Send Messages and Embed Links in the configured session channel. Check the channel’s permission overrides and confirm those are granted to Seshy’s role.
  3. Check Seshy’s role position — if the session channel is locked to specific roles and Seshy’s role isn’t included, the permission override may be blocking the embed. Add Seshy’s role explicitly to the channel permissions.

​
Welcome Module

If new members aren’t receiving a welcome message or aren’t getting the welcome role:
  1. Confirm the Welcome module is enabled — run /settings and check that the Welcome module is toggled on. If it’s off, welcome messages won’t fire regardless of other settings.
  2. Verify the welcome channel — navigate to /settings → Welcome and confirm a welcome channel is set. The bot needs an explicit channel assignment to know where to send the message.
  3. Check channel permissions — Seshy needs Send Messages and Embed Links in the welcome channel. Without these, the bot can’t post the embed when a member joins.
  4. Test with a fresh join — if settings look correct, have a test account join the server to confirm whether the module fires. Welcome messages only trigger on new member joins, not for members already in the server.

​
Community Tools

If a giveaway reaches its end time but doesn’t announce a winner:
  1. Check bot uptime around the end time — if Seshy restarted or experienced downtime during the scheduled end window, the giveaway timer may have been interrupted.
  2. Run /giveaway reroll — this command manually selects and announces a winner for a giveaway that has already ended. Use it any time a scheduled end was missed.
  3. Check the giveaway channel permissions — Seshy needs Send Messages and Embed Links in the giveaway channel to post the winner announcement. If those permissions were removed after the giveaway started, the announcement will fail silently.

​
Staff Module

If a staff member submits an LOA request but it doesn’t appear for reviewers:
  1. Check the staff review channel — navigate to /settings → Staff Module and confirm an LOA review channel is configured. Without this, submissions have nowhere to go.
  2. Verify the submitter’s role — the member submitting the LOA must have a role recognized by Seshy’s Staff Module as a staff role. Check /settings → Roles & Permissions to confirm their role is mapped correctly.
  3. Check channel permissions — Seshy needs Send Messages and Embed Links in the review channel to post the LOA request card. Confirm those are granted in the channel’s permission settings.

​
Still Need Help?

If the steps above haven’t resolved your issue, the Seshy support team is the fastest next step.

Join the Support Server

Get help directly from the Seshy team and community. The support server responds fast and has an active member base.

Check System Status

View live uptime and incident reports for all Seshy services. If there’s a known outage, it will be listed here.