Talk to us

Those are two different things. Adding the bot puts it in your Discord; attaching tells the site which server is yours. Both happen in one press on the website, in the founding stepper or under Manage, Discord, so if the bot got in some other way the second half never happened. Use that button and pick the server even though the bot is already in it: nothing is added twice, and that press is what records it.

Nobody reads it back, including you. It is encrypted before it is stored and the only thing that ever decrypts it is the connection being made on your behalf; every screen that shows a server shows it without the password, and a rank that may manage servers can replace one but never see the old one. Reaching it needs the Manage game servers permission on somebody's rank in your unit.

No, and setup will let you past it. Without one the calendar, roster, ranks and muster all still work; the bot simply has nowhere to post your schedule, so members answer on the site instead of on a card in Discord. Manage, Discord sets a channel whenever you decide you want one, and the schedule starts posting from then on.

Because it is not the permission that is missing, it is the position. Discord only lets anyone hand out roles that sit below their own, and it puts a new bot at the bottom of your role list. Open Server Settings, Roles, and drag the bot's role above your rank roles. It cannot do this itself: Discord will not let a bot lift its own role, whatever permissions you grant it. Your community's Manage, Discord page shows where the bot currently sits and which roles that leaves out of reach.

A channel can deny what the server allows. Even with Send Messages granted server-wide, a channel that denies it to a role the bot holds wins. Open that channel's permissions, add the bot's role, and allow Send Messages and Embed Links. Nothing is lost in the meantime: when the bot cannot post a roll it hands it back to you privately rather than dropping it.

A promotion swaps rank roles: it adds the new rank's role and removes every other rank's, so nobody carries two. That is wrong for the base member role most units map to their lowest rank to open their channels. Edit that rank and turn on Keep this Discord role after a promotion, and it will be left alone from then on. Anyone already stripped needs the role handing back once in Discord.

Check where that rank sits in your ladder. A new rank is created at the bottom, below every existing one, so a role mapped to it is worth less than the base member rank people already hold. Drag the rank to its proper place in the list and it applies. Moving somebody down is a separate question: under Add only, the default, a sync never demotes anyone, so only Full will take a rank away when the role goes.

Almost always the role is a bot's own. Discord marks those managed and will not let a person hold one, so there is no one to add and never will be; pick the role your members actually wear. Otherwise the import did run and found nobody new: it skips bots, and it leaves alone anyone already on the roster at that rank or above. The roster's Sync from Discord button reports exactly what it scanned and why it changed nothing.

The roster is who is actually in your unit, including people who are only in your Discord and have never made an account here. The members list counts site accounts alone. The bot musters the roster, which is why it is the wider of the two.

Yes. A player serves with one unit, but any unit may carry them on its roster as a mercenary so it can muster them when they field with it. Add them the same way you add anyone else, by Discord account; nothing has to be different about them. They keep their own unit and their own rank there.

That search needs the Server Members Intent, which is enabled for the application rather than in your server. If it is off, the bot can still act on people you name directly, but it cannot browse your member list to find them.