Server setup and troubleshooting

Invite AniGame using the official link, then open setup to review command areas, drop destinations and who can manage the bot's server configuration. Keep gameplay in channels where players know to find it.

The bot checks setup access before allowing changes. Follow the dashboard's bootstrap instructions if your server has no setup managers yet. Review permission-change confirmations carefully and test the player experience after changing channel access.

Select AniGame in Discord's slash picker; another bot may have a command with the same name. Some AniGame commands are message-only and some entries are command groups whose actions live in subcommands. Use the command reference's format labels.

Message examples use the default period prefix. Ask a setup manager if the server changed it, and check that the bot can access the channel. A configured command scope can make a command unavailable outside the intended channels even when the bot appears online.

Read the specific response first: registration, verification, account eligibility, cooldowns, resource requirements and event phase are different issues. Start with start for onboarding, cooldowns for timers, or cardcheck for a particular card.

For an event command, check ev info or the relevant event hub. If you cannot join a raid, ask the leader to confirm the code, state and requirements. Repeated attempts will not bypass an unmet requirement.

Check AniGame status and current announcements for a wider issue. If you still need help, use the bot's support flow or official community and explain the command, what you expected and the message you received.

For a missing vote reward, inspect the vote dashboard's history and recovery controls first. For trades, raids or purchases, use the relevant in-game record when explaining the issue. Never share passwords, login tokens or private payment details in a public channel.