Bot and Commands
Bot isn't responding to commands
Bot isn't responding to 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:
- 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.
- 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. - 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.
- 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.
Staff commands being denied
Staff commands being denied
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.
- Open the Seshy dashboard and navigate to Staff to review which Seshy permission level is assigned to each role.
- 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).
- If the user should have access, update their role’s permission level in the dashboard under Staff 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
ER:LC integration not connecting
ER:LC integration not connecting
If the ER:LC integration isn’t pulling live data, work through the following:
- Verify the API key: go to your ER:LC Private Server settings in-game and copy the API key fresh. Paste it again in the Seshy dashboard under ER:LC Integration. Keys can change when the Private Server is reset or transferred.
- 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.
Ares Security
Ares isn't blocking threats
Ares isn't blocking threats
If Ares appears to be inactive or isn’t stopping suspicious actions:
- 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.
- Check The Seshy Dashboard Ares Page: this page shows whether the Ares module is currently enabled and shows which protection layers are active.
- Check the whitelist: open the Seshy dashboard and go to **Ares → Trust **to confirm the account or role performing the action is not accidentally whitelisted. Trusted users bypass all Ares protections.
- 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
Session embeds not posting
Session embeds not posting
If
/ssu or /ssd runs successfully but no embed appears:- Check the session channel: open the Seshy dashboard and go to Sessions → Session Channel to confirm a specific channel is assigned for session embeds. Without a channel configured, Seshy has nowhere to post.
- 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.
- 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
Welcome messages not sending
Welcome messages not sending
If new members aren’t receiving a welcome message or aren’t getting the welcome role:
- Confirm the Welcome module is enabled: open the Seshy dashboard and check that the Welcome module is toggled on. If it’s off, welcome messages won’t fire regardless of other settings.
- Verify the welcome channel: navigate to the dashboard under Welcome and confirm a welcome channel is set. The bot needs an explicit channel assignment to know where to send the message.
- 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.
- 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
Giveaway not ending on schedule
Giveaway not ending on schedule
If a giveaway reaches its end time but doesn’t announce a winner:
- 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.
- 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. - 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
LOA request not appearing in the review channel
LOA request not appearing in the review channel
If a staff member submits an LOA request but it doesn’t appear for reviewers:
- Check the staff review channel: open the Seshy dashboard and go to the Staff Module to confirm an LOA review channel is configured. Without this, submissions have nowhere to go.
- 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 the dashboard under the **Roles **category to confirm their role is mapped correctly.
- 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.
Web Dashboard
My Changes not saving
My Changes not saving
If your changes aren’t saving on the Seshy Dashboard, check the reason. Under the save message it should say the error. The most common error is forgetting to set the logs channel for some categories. You can fix it by finding the logs category in the module or by finding the Logs feature in a row.
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.Join here!
Check System Status
View live uptime and incident reports for all Seshy services. If there’s a known outage, it will be listed here.Check the Status here!

