GUILDEDYOUR GUILD, CONNECTED.

Guilded: install and connect

For guildmates using WoW Forever, Classic Era/Hardcore, Burning Crusade Classic, Mists of Pandaria Classic or Retail. You do not need Node.js, a database, or a Discord bot token.

In the latest published release, choose the addon ZIP ending in forever, classic-era, classic-tbc, classic-mists or retail for your client. ZIPs without an edition suffix are Forever builds. The Windows companion installer supports every edition; connect each guild/edition in its own profile. Enable Load out of date AddOns if the client requests it. Real-client and two-PC checks remain pending follow-up.

Français : choisissez le ZIP de votre édition (forever, classic-era, classic-tbc, classic-mists ou retail). Les ZIP sans suffixe sont pour Forever. Le même compagnon Windows prend en charge toutes les éditions, avec un profil par guilde/édition. Les vérifications en jeu restent à effectuer.

Français · Quick setup · EPGP workflow · Optional hosted bot

Use it in game only

The addon alone is the default path. Install it and use In-game only. Current releases start in this mode automatically. Older builds may show a chooser. Reopen the choice with /guilded setup or Home > Guilded setup. Gear checks, dungeon recording, raid attendance and loot tools work without Discord or core signups. Officers can publish local standings to online guildmates. Save with /reload or logout and back up SavedVariables.

Discord/companion setup below is optional. Verified seasonal scores and online rosters/signups need the connection. Choosing in-game only preserves existing points and rosters and does not stop an already-running companion.

Want the bot for your guild?

Add Guilded to your server

The hosted bot is free. Adding it puts your server on Guilded Lite right away (setup, help, bug reports, dungeon groups, basic signups); KCaron's approval unlocks addon sync, EP/GP, seasons and the guild page. Run /setup start, then, once approved, open the online companion and choose Sign in with Discord, then follow the confirmation shown by your companion. You do not need to host a bot or database for this path. See the hosted bot guide. Independent hosting is also available. Any financial support is optional and never buys approval.

For automatic Windows syncing, install Guilded Companion from Microsoft Store. The standalone GitHub installer is also available. Store installations receive updates through Microsoft Store; check its listed version because Store certification and GitHub releases can finish at different times. Close your existing companion before switching editions; the Store copy keeps separate connection settings.

Français : installez le compagnon Windows depuis le Microsoft Store. Les mises à jour passent par le Store. Vérifiez la version proposée et fermez l'autre compagnon avant de changer d'édition; la version Store conserve ses propres paramètres de connexion.

Ask your officer for the addon download. Start with the addon; the online companion and Windows app are optional. If you want companion sync later, ask for your guild's online link. Use the matching release your officer specifies. Public releases belong on GitHub Releases and CurseForge; only use a version actually listed there. The stores can update separately, so confirm the version on the selected download. Private candidate packages are for acceptance testing only. Install the complete addon folder and keep your SavedVariables. See the latest release notes. Guilded Games remains a separate optional Alpha.

1. Install the addon

  1. Close WoW. Open the folder for the client you actually play: the one beside the game executable you launch. (The Forever beta used _classic_beta_ beside WowB.exe; from launch on 4 November 2026, find the live game executable first.)
  2. Extract the addon's Guilded folder into Interface\AddOns there. The result must be Interface\AddOns\Guilded\Guilded.toc, with no extra nested Guilded folder.
  3. Start WoW, enable Guilded in the AddOns list, and enter the game. Click the gold minimap coin to open Home. /guilded menu also opens the window.
  4. Type /reload once to create or update the saved-data file.

Success: Home opens without a Lua error. If you only want the in-game addon, you can stop here. Discord sync needs the steps below.

  1. In Discord, press Link my WoW character / Lier mon personnage WoW in the welcome panel, or run /character pair. The private reply starts with one line in a box, such as /guilded verify ABCD-EFGH.
  2. Copy that line, paste it into WoW chat on any of your characters and press Enter. That's all, also for your alts.

Characters you play in this guild on that WoW account can then link, the first one as your main, after an online officer's addon receives their guild data and that officer saves and syncs it. Both players need matching addons. You get a Discord DM for each one; /character list shows the result. Not your character? /character unlink removes it, and the code will not link it again. The line is the same every time you run /character pair.

If no officer's companion has synced for two weeks, the reply also shows the manual way: in WoW type /guilded character, copy the line, then in Discord use /character import and paste it into code with main unset (once per character). Without a guild, /guilded verify has nothing to link: the addon works on its own. If you do not want Discord character linking, skip this.

Optional: connect the online companion

Open the online companion link supplied by your guild (ending in /companion/), or press Connect optional companion / Connecter le compagnon (facultatif) in the /character pair reply and use its Open online companion button. In Connection & setup, choose Sign in with Discord: your browser opens, pick your server and press Connect. Nothing to type: the page knows the request came from your own companion (only the command-line companion still shows a short code to type). Then save preferences. Sync your intended main first if no character is linked yet; later characters become alts. The Windows app is optional and the addon is still required. Each device you sign in stays connected; manage them under Connections on the website.

Main already linked? Keep your working companion: log in on an alt, /reload, then Sync now. It links as an alt without changing your main; nothing new to type for each alt. Run /character list after syncing to check the result. Companions older than 7.2 have no Sign in with Discord: use the one-time code from /character pair under Older companions or your guild's own bot. Community-only members can skip WoW setup entirely.

If you see Choose SavedVariables folder (enhanced browser build on supported desktop Chrome/Edge): choose your account's WTF/Account/<account>/SavedVariables folder containing Guilded.lua. After /reload, Sync now rereads the latest file; you do not need to select it each time. Save standings to addon asks for <client>/Interface/AddOns/Guilded and writes only Standings.lua there. Then /reload again to load them: the addon switches to the Discord standings by itself (unless you chose in-game only with /guilded setup). Do not select SavedVariables as the output folder.

Folder choices and the Discord connection are remembered locally on that browser/device. Closing the tab does not require signing in again. Disconnect clears the saved connection and folders; use it when finished on a shared computer. The browser may ask you to approve folder access again. If site storage is unavailable, the companion warns that it cannot remember connection/folder choices. Forget selected folders clears remembered choices; browser site settings let you revoke file permissions. Disconnect also clears the remembered folders. Once the addon folder is configured and write access is allowed, Sync now uploads and saves standings together. Nothing syncs after closing the page. Connection and folder retention after reopening passed on the owner's browser on 5 October; permission recovery and other-browser tests remain pending.

If you see Choose Guilded.lua / Download standings: select Guilded.lua after each /reload, then Sync now. Download Standings.lua, place it in <client>/Interface/AddOns/Guilded, then /reload. This is the fallback for other browsers and older deployed companions.

The desktop app below is optional for automatic file watching, background sync and PoE2 log tracking, especially useful for leaders and officers.

Optional Windows companion: automatic sync

  1. Install Guilded Companion Setup <version>.exe from your guild's release link, then open Guilded Companion. The installed app does not need Node.js. Current installers are unsigned; verify the download source before running one.
  2. Open Connection & setup (new installations open it automatically) and choose Sign in with Discord. Your browser opens: pick your server and press Connect. Nothing to type.
  3. Guild with its own bot (not the hosted one)? First paste Your guild's bot address from your officer, ending in /api/v1/addon-imports, under Older companions or your guild's own bot. Companions older than 7.2 use the one-time code from /character pair there instead (it expires after 15 minutes).
  4. Enable World of Warcraft. Press Find it, then verify the selected Guilded.lua belongs to your current client and account. If several accounts are found, use Browse to select the right one: <client>\WTF\Account\<account>\SavedVariables\Guilded.lua. Do not select the addon code in Interface\AddOns.
  5. Press Save & start syncing. In WoW, /reload. Check Activity for a successful upload and the message that your character is linked.
  6. Let the companion refresh standings, then /reload again: the addon loads and uses the Discord standings by itself.

Success: a fresh successful upload appears and the correct character is linked. 0 ledger entries, 0 new characters is normal when nothing new needs importing. An officer's guild upload may wait for review if automatic import is off.

Leave the companion in the tray while playing. New game data reaches disk on /reload or logout. Open each crafting profession normally: recipe detection is automatic; /guilded recipes mine is only a way to inspect the stored result.

Signing in on another companion adds a device; your other companions stay connected. Remove a device under Connections on the website. Update now on the Overview page opens the new version's installer, which shows its progress and restarts the companion; if an update does not finish, the next start offers Run the installer.

Quick fixes

What you see What to do
Guilded missing from the AddOns list Check the actual client folder and the exact Guilded.toc path above; restart WoW.
Find it finds no Guilded.lua Log in with Guilded enabled and /reload, then Browse to your account's SavedVariables.
Sign in with Discord fails Check full Guilded approval and, for a guild with its own bot, its address; then choose Sign in with Discord again. Companions older than 7.2: use a new /character pair code (one use, 15 minutes) and keep it private.
/guilded verify did not link yet Linking happens on the next upload from an officer's companion: ask an officer to /reload and Sync now. /guilded verify in game says whether your code is saved.
Link revoked or unauthorized This device was removed under Connections, or your server access changed. Ask an officer about membership/access, then sign this device in again.
Cannot reach bot Use Test connection. Ask the owner whether the bot and its HTTPS address are online.
Guild is not initialized / 404 Confirm this bot is approved and set up in your server. The owner runs /setup start. Check the server ID only if an older companion or Advanced preferences asks for it.
Upload says it is awaiting review An officer reviews/applies it with /import apply; ordinary members cannot apply guild ledgers.
Upload applied entries but some are on hold An officer runs /import held to see each reason. Do not award again: applied GP and a held loot record can belong to the same award. For an unlinked character, the officer uses /officer character link to select that character and its actual Discord owner; the next upload retries the existing entry. A missing core raid needs officer review of the raid recording/match.
Upload works but standings look old Check the companion's separate standings status; refresh standings, wait for success, then /reload.
Profession list seems empty Open the profession window and let it finish loading. If still empty, send the profession name and current diagnostic output.
No tray icon Check the hidden-icons arrow beside the Windows clock, then open Guilded Companion from Start.
Lua error Capture the error and /guilded diag; note the timestamp. Saved diagnostic history can include older notices.
One computer sees a guildmate's map dot but the other does not Follow the map check below. A full character logout/login restored delivery in the tested Forever beta case.

For help, use Activity → Download support summary, or copy the exact error, the addon/companion versions, client build and time of failure. Review attachments before sharing; do not upload config.json, credentials, bot tokens or pairing codes. The AI help prompts include a member troubleshooting prompt.

Guild map: a dot is missing

Map sharing and map dots start enabled. Both players need Guilded, membership in the same in-game guild, and an available outdoor position. Stay out of combat while testing. The minimap only shows players who are nearby.

Run /guilded map check on both computers. Check the module, sharing and dots settings and whether your own position is available. Peers 0 means no usable guildmate position is currently stored; changing map zoom cannot repair that. Send counters marked accepted mean the client accepted an outgoing update, not that another player received it. A last outcome of self can be a normal echo of your own message; it does not prove another character was misidentified.

If reception works in one direction, check whether an ordinary guild-chat message from the missing character reaches the other player. Verify guild-chat permissions and any ignore/block settings that the actual client exposes. Do not assume the beta has the same menus as another WoW version.

During testing on Forever beta 1.60.1, both map settings, guild permissions and the receiving player's ignore status were correct, but the other player's messages did not reach the receiver. Logging the missing character out and back into the game, then waiting 35 seconds outdoors, restored the dot. /reload alone had not resolved it. This is a verified recovery step for that case, not a guarantee for every missing dot. If it persists, provide both map-check outputs and say whether ordinary guild chat arrives.

Installation et connexion en français

L'addon fonctionne sans Discord. Il ne faut ni compte d'hébergement, ni base de données, ni jeton de bot pour jouer. Client ciblé : WoW Forever 1.60.1. Les sites peuvent être mis à jour séparément : vérifiez la version du fichier choisi. Les versions candidates privées servent aux tests d'acceptation. Installez le dossier complet de l'addon et conservez vos SavedVariables. Consultez les dernières notes de version. Guilded Games reste un addon Alpha séparé et facultatif.

Pour ajouter le bot à votre guilde, utilisez le lien Add Guilded ci-dessus. Le serveur passe tout de suite en Guilded Lite; l'approbation de KCaron débloque la synchro de l'addon, l'EP/GP et les saisons. Lancez /setup start. Le bot hébergé est gratuit; tout soutien financier est facultatif et ne donne aucune priorité.

  1. Téléchargez l'addon depuis GitHub Releases ou CurseForge, avec la version choisie par votre guilde. Aucun passage par Discord n'est requis.
  2. Fermez WoW. Installez le dossier Guilded dans Interface\AddOns du bon client (le dossier à côté de l'exécutable du jeu que vous lancez; la bêta utilisait _classic_beta_), puis relancez WoW.
  3. Ouvrez Guilded avec la pièce sur la minicarte. /reload enregistre les données.
  4. L'addon seul est le choix par défaut. Vous pouvez arrêter ici. Pour lier vos personnages à Discord sans compagnon : appuyez sur Lier mon personnage WoW ou lancez /character pair, copiez la ligne affichée (par exemple /guilded verify ABCD-EFGH) et collez-la une seule fois dans le chat de WoW. Vos personnages de cette guilde peuvent ensuite se lier, le premier comme principal, après qu'un officier en ligne a reçu, enregistré et synchronisé leurs données. Les deux joueurs doivent avoir les addons correspondants. Vous recevez un message privé Discord. Vérifiez /character list. Si aucun compagnon d'officier n'a synchronisé depuis 2 semaines, la réponse montre aussi la méthode manuelle : /guilded character en jeu, puis /character import → code sur Discord avec main vide.
  5. Compagnon facultatif : dans Lier mon personnage WoW, choisissez Connecter le compagnon (facultatif), ou utilisez /character pair. Ouvrez Ouvrir le compagnon en ligne.
  6. Dans Connection & setup, choisissez Sign in with Discord : le navigateur s'ouvre, choisissez votre serveur et appuyez sur Connect. Rien à taper. Les compagnons plus anciens que 7.2 utilisent plutôt le code à usage unique de /character pair (15 minutes), sous Older companions or your guild's own bot. Sélectionnez le dossier SavedVariables de votre compte et, avec Save standings to addon, le dossier Interface/AddOns/Guilded.
  7. Après /reload, cliquez sur Sync now. Synchronisez votre principal d'abord si aucun personnage n'est encore lié. Vérifiez l'envoi et le classement, puis faites /reload : l'addon charge et utilise le classement Discord tout seul. Le navigateur garde la connexion et les dossiers si le stockage est disponible.

Le compagnon Windows reste facultatif pour la synchronisation automatique en arrière-plan et le suivi PoE2, particulièrement utile aux chefs et officiers.

Principal déjà lié et compagnon connecté ? Connectez-vous sur un alt, faites /reload, puis Sync now dans le même compagnon. Votre principal reste le même; rien à refaire pour chaque alt. Se reconnecter avec Sign in with Discord remplace la connexion compagnon précédente. /character list montre le résultat après la synchro. Update now ouvre l'installateur de la nouvelle version, qui montre sa progression et redémarre le compagnon; si une mise à jour ne se termine pas, le prochain démarrage propose Run the installer.

Vous n'avez pas besoin du jeton du bot. Ne partagez jamais un code à usage unique de /character pair. /guilded lang fr sélectionne le français dans l'addon.

Vérification : la fenêtre s'ouvre sans erreur Lua. Si vous utilisez la synchronisation facultative, vérifiez l'envoi réussi, le bon personnage et les classements après /reload. Un envoi en attente de révision doit être examiné par un officier; ne recréez pas une attribution déjà importée.

En cas de problème, joignez les versions de l'addon et du compagnon, le build du client, les étapes et l'heure du problème. Anonymisez les captures. Ne partagez jamais config.json, un jeton, un code de liaison ou vos données de compte.

Comprendre le fonctionnement EPGP · Bot Discord facultatif