Manual
Every GuildOS feature, in the game, on the site and in Discord: what it does, who sees it, how it should behave and what looks like a bug but is not. If what you saw contradicts what is written here, it is a bug. Tell us.
On the site
Sign in to GuildOSmemberThe site's front door: you sign in with your Discord account.
- What it does
- Every sign-in button on the site leads to this page. You sign in with Discord, with no new account and no password, and go back to where you were. It is through Discord that the site knows which guilds you can see.
- Who sees it
- Anyone. Whoever is already signed in does not even see the page: they go straight to where they were going.
- Where to find it
- In Sign in, in the corner of the header, or at guildos.me/entrar. It is also where someone goes who tries to reply to a raid through the link without having signed in.
How it should behave
- If you have already signed in, the page asks nothing and sends you straight to where you were going.
- After signing in, you go back to the page you came from. An address that leads outside the site is never followed: in that case, you land on Your guilds.
- If you cancelled on Discord and tried again, you still go back to where you were going, for example to the raid from the link you opened.
- Coming from a raid's link, the page says which raid you are going back to, with the day and time in your time zone.
- The site asks Discord for your name, your avatar, the servers you are in and your roles in them. Never your email or your messages.
This is not a bug
- “Discord did not confirm” appears when the Discord window is closed before authorizing, or when authorization is denied. Nothing was saved: just try again.
Your guildsmemberThe list of guilds you reach through your Discord servers.
- What it does
- Shows each guild tied to a Discord server you are in, with how many members and items it has and in which servers it answers. Here you also mark the nights that usually work for you to raid. Whoever manages a server links one more server to a guild of theirs. With no guild at all, the page leads to the wizard or to saying who you play.
- Who sees it
- Whoever signed in with Discord. Each person sees only the guilds of the servers they are in.
- Where to find it
- In Your guilds, in the header, or in My guilds, in your account menu. Address: guildos.me/dashboard.
How it should behave
- All guilds tied to any Discord server you are in appear, and only them.
- The guild carries the “admin” tag when you have Manage Server in one of its servers. On the others, “member”.
- “When I can raid” has one row per guild, not per server. It is not a signup: nobody is marked on any raid because of it.
- The days you mark show to officers when they schedule a raid, and on the raid page while you have not replied.
- Linking a server to a guild takes two things: Manage Server on that server, with the bot in it, and managing the guild.
- With no guild at all, whoever manages a server sees the wizard's buttons. Whoever does not manage one sees the path to say who they play.
This is not a bug
- Just joined the guild's Discord and it does not show up? The site keeps your server list for about a minute. Reload in a little while.
- When Discord does not answer, the list is empty and the page warns that it could not reach it. Signing out and in again usually fixes it.
Start hereofficerThe wizard that links your guild to GuildOS, from Discord to the first roster.
- What it does
- The door says what you need before sitting down and the four places the path goes through: in the browser (server, bot, guild and the first raid), on Windows (the companion), in the game (the addon sends the first roster) and with the guild (invite, the /register roles and page). You can do it all at once, or only part today: only the raid on Discord, or only the roster from the game. Each step says what to do and follows live what happens outside the page.
- Who sees it
- The door is public: anyone reads it before authorizing anything. The steps ask you to sign in with Discord and only work on a server where you have Manage Server. Whoever manages no server goes straight to picking their character.
- Where to find it
- In Start here, in the header, or at guildos.me/start. While something is missing, the Set up badge in the header and the “guild N of M” ring on the guild bar also lead here.
How it should behave
- Nothing is stored to know whether a step is done: the wizard looks at what already exists. Closed the tab midway? When you come back, it continues from the right step.
- The chosen server only counts if you have Manage Server on it. Someone else's server is ignored.
- The companion step is only done when the companion has talked to the site, or when a roster has arrived. Creating the code is not enough.
- “Call the guild” is done when at least half the roster has the addon.
- In the full suite, the first raid, the invite, the roles and the page are optional and can be skipped. A step that depends on another not yet done does not open.
- While it waits for something from outside, the page refreshes itself: every 5 seconds waiting for the bot, 15 waiting for the first raid, 30 waiting for the companion and the roster.
- “Send to my PC” sends you at most one message per minute.
This is not a bug
- Clicked Start here and landed on Your character? You do not manage any Discord server, and for someone who only plays, saying who their character is is everything.
- “The companion has not shown up yet” after 3 days with the code created: no companion has talked to the site with that code. It is almost always the Windows warning or the code not pasted.
- Played and the roster did not arrive? The game only saves the roster when you do /reload or leave the game, and only after /gos web on.
- “The guild name did not match”: the name on the site has to be the game's. Capitals and the < > signs do not count; accents and spaces do. “Use the game's name” fixes it with one click.
Your charactermemberWhere you say which character is yours, so signups show the real you.
- What it does
- You pick your character from the guild roster, accept one the site found for you, or register one by hand. Once linked to the roster, it shows item level and attendance on signups. If you registered before the guild sent the roster, the page says what is missing and lets you tell the officers.
- Who sees it
- Whoever signed in with Discord. Each person sees and edits only their own characters.
- Where to find it
- In My characters, in your account menu and in Your guilds; in “Pick my character”, in Start here; and in the registration link from a raid. Address: guildos.me/start/character.
How it should behave
- The list to pick from brings whoever in the roster of your guilds has no owner yet and has already been measured by the addon, from highest item level to lowest, up to 12 at a time.
- You can only take a character from the roster of a guild tied to a Discord server you are in.
- A roster character who already belongs to someone else is not offered to you.
- If you came from a link, such as a raid's, the page sends you back there as soon as you have a character.
- “Tell the officers” sends the message at most once a week. Deleting and registering the character again does not reset that count.
- In WoW: Forever, if you registered only the first name and the roster has the full name, the page asks “The roster has … Is that you?”. Nothing is linked without you saying “That's me”.
- Once confirmed in the roster, the character shows the item level, or “no addon” with the button to install.
This is not a bug
- Your name is not on the list? It only brings whoever the addon has already measured. Open “None of these are mine, let me type it” and write the name.
- The roster list disappears once you have a character. To register an alt, use the form.
- “declared” next to the character means no roster has confirmed it yet. When the roster brings the same name, it links by itself if you have already signed up for a raid of the guild; otherwise, the page offers “That's me”.
- The “waiting for the guild” box and the “Tell the officers” button only appear for whoever registered through /register on Discord. The site's form does not know which Discord you came from.
Guild dashboardmemberThe guild's first page: what needs you now, the next night and the latest ones.
- What it does
- For whoever manages a guild's Discord server, it is the dashboard: the next step at the top, with the why, what comes after, the guild's health and what happened in the last 14 days. For everyone else, it is the guild's page: the join requests waiting, the next night with what is missing by role and the latest recorded nights. When nothing needs you, it says so and does not invent a task.
- Who sees it
- Whoever shares at least one Discord server with the guild. For anyone else, the page answers that it is not here. The dashboard with the next step is only for whoever has Manage Server on one of the guild's servers.
- Where to find it
- In dashboard, on the guild bar; by clicking the guild in Your guilds; or at guildos.me/guild/… The Monday summary the bot sends to officers also leads here.
How it should behave
- It only opens for whoever is on some Discord server tied to the guild. For anyone else, the page answers that it is not here, whether the guild exists or not.
- The next step is always the most urgent: first what blocks the roster (upload refused, companion stopped), then whoever is waiting for an answer, then the wizard, and last what improves the guild.
- “The companion stopped” appears after 3 days without an accepted roster, and only if a roster has arrived before.
- “Remind me in a week” hides an item for 7 days, only in this browser. Upload refused, companion stopped, join requests and required steps cannot be postponed.
- In the next night, the count by role uses only whoever said yes or is arriving late and is in: the waitlist and declined do not count.
- Dates and times appear in your time zone, your browser's.
- Upload refused, companion stopped and companion out of date appear in a strip at the top of the guild pages, for whoever sets up the guild. On the dashboard, the same warning comes as the next step, and the strip does not repeat.
This is not a bug
- A night with bosses and “nobody was measured”: the addon of whoever recorded it noted the bosses, but not the group snapshots. It does not mean nobody was there.
- Without having signed in, the page asks you to sign in first, whether the guild exists or not. The site does not say whether a guild is here to someone who has not said who they are.
- “Could not confirm with Discord”: who can open the page comes from Discord, and it did not answer. Trying again usually fixes it.
- You set up the guild and do not see the dashboard? It is for whoever has Manage Server on a Discord server of the guild. A role with permission on the site is not enough.
RostermemberEveryone in the guild, and how much of it the addon measures.
- What it does
- The list of every character the game sent, with level, rank, item level and professions. The top says how many the addon measures and how to reach the rest: the bot calls by DM whoever has Discord linked, and the invite in the channel reaches whoever does not. Each name opens the person's sheet: gear, attendance night by night, what they got in loot, their other characters and how many times they said yes and did not show up.
- Who sees it
- Whoever shares a Discord server with the guild. Each member's Discord name, the call buttons and the list of unmatched registrations are only for whoever has Manage Server on a guild server.
- Where to find it
- In roster, on the guild bar. A person's sheet opens by clicking their name here, on a recorded night or on loot.
How it should behave
- The roster changes when an officer's companion sends what the game saved. The game only saves when the officer leaves the game or does /reload.
- An older upload never overwrites a newer one: with two officers sending, the most recent data for each person wins.
- An officer with an out-of-date addon does not erase what a newer addon already sent, such as gear.
- Measured means having an item level, and only the addon measures it. “no addon” is whoever no addon has measured yet.
- The default order is “needs attention first”: whoever has a warning, then the measured from highest item level to lowest, and last whoever has no addon, in alphabetical order.
- “Call by DM” calls each person at most once a week. The row shows “queued” or “called” with the day, in place of the button.
- On the sheet, “20+ lockouts” counts only raids of 20 people or more. Two nights in the same raid in the same week are a single chance.
This is not a bug
- Empty roster: it appears when the first roster arrives from the game. Whoever manages the server sees the button to turn it on.
- “no addon” is not the member's fault. The game tells everyone the name, class, level and rank; item level, gear and professions only exist for whoever has the addon.
- “said yes and did not show up” only counts raids that someone recorded with the addon. With no absences, the block does not even appear.
- The “officers” filter counts only the guild's two highest ranks in the game. A lower rank does not count, even with “officer” in its name.
RaidsmemberThe guild's schedule: the scheduled raids and the nights the addon recorded.
- What it does
- Lists the raids of the guild's Discord servers, with what is missing by role and who is on standby. You can see the upcoming ones, the past ones, the cancelled ones, all of them, or the month on a calendar, and subscribe to the schedule in your phone's calendar. Below are the nights the addon recorded, marked as a raid here or not. Officers approve requests, edit, lock, cancel, open the signup link and manage the fixed weekly raids.
- Who sees it
- Whoever shares a Discord server with the guild. The buttons and the reading of each signup (item level, attendance, warnings, time without loot) are only for whoever can schedule a raid; the others see who is going and in which role.
- Where to find it
- In raids, on the guild bar.
How it should behave
- The list brings the raids of all Discord servers tied to the guild.
- A raid stays in Upcoming until 6 hours after it starts: during the night, it does not vanish from the screen.
- Each tab says how many raids it has, so none looks erased.
- Each raid's day and time appear in your time zone.
- A fixed weekly raid shows the time in the time zone it was created in, with the city name, without converting to yours.
- Each signup's item level, attendance, warnings and weeks without loot only appear for whoever can schedule a raid.
- In a raid with approval, whoever asked to join stays in “Waiting for an officer” and does not take a spot until accepted.
This is not a bug
- On the first visit, the times may change right after the page opens: it starts on the guild's time and redoes itself in your time zone as soon as the browser says which it is.
- A recorded night with “no raid scheduled”: the addon recorded it, but nobody marked that night as a raid here. It counts toward attendance all the same.
- “outside the guild” on a night: the addon did not count it as a guild raid, because fewer than half the group was from the guild. It does not count toward anyone's attendance.
Schedule a raidofficerThe form that schedules a raid and announces it in the Discord channels.
- What it does
- You give a title, the day and time, pick the raid from the list (or write another), the size, the composition and the channels to announce in. You can repeat it every week, warn ahead, close signups some hours before, close when it fills up and require an officer to approve each signup. On creating, the bot posts the raid with button signup in each chosen channel.
- Who sees it
- Whoever can schedule a raid on the site, through a Discord role with that permission in the configuration, or whoever has Manage Server on a guild server. The others go back to the raids list.
- Where to find it
- In Schedule a raid, at the top of the raids page. The wizard's first raid step also brings you here.
How it should behave
- The day and time you type are read in your time zone, the one that appears next to “When”.
- The raid list is the one for the guild's game. A night that is not on the list goes through the free field.
- If no channel accepts the post, the raid is not created, and the page shows the reason Discord gave.
- Past a role's limit, the signup goes to the waitlist, in the order people replied. Nobody is turned down.
- “Repeat every week” turns the chosen day and time into the fixed time and keeps 1 to 8 weeks up (3, if you do not change it).
- With no size chosen, the size of the raid from the list applies, and the spots by role come from it.
- The channels where the last raid was announced come already ticked.
This is not a bug
- The soft reserve option does not show: the soft reserve site does not have WoW: Forever raids.
- “No channel available”: the bot only offers channels it can see and where it can post. Check its permissions in the channel.
- The “who usually can” line only appears when someone marked the nights that work in Your guilds.
- A raid scheduled only with the free field never links itself to the night the addon records: only a raid chosen from the list links. Link it by hand on the night's page.
Raid pagememberA whole raid on one screen: who is coming, what is missing, the groups and, afterwards, who showed up.
- What it does
- Shows the day and time, what is missing by role, the signups (confirmed, waitlisted, waiting for an officer and those not coming) and the buttons to reply with your character. It says how many signups the site does not know can go, because they have no addon, and, after the raid, compares who said they were coming with who the addon saw there. Officers also approve requests, build the groups, tag in the raid's thread whoever has no addon and copy the text that carries the list into the game. With the link open, the raid also has a public address, for people who are not in the guild's Discord.
- Who sees it
- The guild page: whoever shares a Discord server with the guild. The public address: anyone with the link, while an officer keeps the link open, and to reply you must sign in with Discord. It only shows how many of each role are going, never names. With the link closed, the address answers that the page is not here.
- Where to find it
- By clicking the raid's title in raids, in the dashboard's next night, or in “See the raid” in Your character. The public address (guildos.me/r/…) is the one the officer copies when opening signup by link.
How it should behave
- Spots go in order of reply. “Running late” takes a spot like “I'm in”; “Maybe” and “Can't make it” do not.
- After the signup deadline the raid closes: nobody joins or changes their answer, on the site or in Discord. Only Leave, on the site, still works.
- When someone leaves, the first on the waitlist for that role moves up.
- “Take into the game” takes only the confirmed with a character the roster confirmed. Waitlist, absent and those not in the roster are left out.
- Opening signup by link also turns on approval: every request that arrives through the link waits for an officer.
- “Tag in the raid's thread” goes out only once per raid, and only before it starts.
- Whoever can schedule a raid sees who said, in Your guilds, that day of the week works and has not replied yet.
This is not a bug
- The “The night” block does not appear: it only exists when someone's addon recorded the raid. Without a recording, there is no way to say who came.
- “no addon · unknown” accuses nobody: item level comes from each person's addon, and without it the site only has the name.
- There are no boss assignments or buff coverage: the site does not yet know the bosses and buffs of WoW: Forever raids.
Recorded nightmemberA night the addon recorded: who was there, what dropped and who said they were coming.
- What it does
- Shows the duration, the bosses (killed and wipes), who was there and the loot that dropped at that time. If the night is linked to a scheduled raid, it puts side by side how many said yes and how many the addon measured, and names who said yes and did not come and who came without replying. Whoever can schedule a raid links the night to a raid, or unlinks it.
- Who sees it
- Whoever shares a Discord server with the guild. Linking and unlinking is for whoever can schedule a raid.
- Where to find it
- In raids, in the list of recorded nights; in the dashboard, in the latest nights; in the attendance squares on a person's sheet; and in the post the bot makes on Discord after the night.
How it should behave
- “Agreed vs measured” only appears when the night is linked to a scheduled raid. The number of who said yes stays on screen and is never replaced by the measured one.
- The night links itself to a raid of the same instance when it starts between 2 hours before and 8 hours after the scheduled time. Outside that, it stays without a raid.
- To link by hand, the list brings the guild's raids from 7 days before to 7 days after the night, except cancelled ones.
- Whoever came without replying counts the same as whoever replied.
- “Dropped here” gathers loot by instance and by the night's time: the loot does not know which night it came from.
- The bot only posts the night on Discord if it is up to 48 hours old, and only in the channels where the pinned raid list is.
- The day and times appear in your time zone.
This is not a bug
- “nobody was measured” with bosses on the list: the addon recorded the bosses, but not the group snapshots. It does not mean nobody was there.
- Whoever said yes without a character confirmed in the roster does not appear in “said yes, did not come”: without a character, there is nobody to compare.
- “Nobody marked this night as a raid here” even with a scheduled raid: it did not have the instance chosen from the list, or started outside the window. Choose the raid from the list and link it by hand.
LootmemberWhere the loot went, and who keeps raiding and gets nothing.
- What it does
- At the top, whoever shows up most on the nights and for 8 weeks or more gets nothing, or never has. Below, the latest handouts, from newest to oldest: who got it, the item, the raid and the day. Each name opens the person's sheet.
- Who sees it
- Whoever shares a Discord server with the guild.
- Where to find it
- In loot, on the guild bar.
How it should behave
- The list shows the latest 200 handouts, from newest to oldest.
- “Who shows up most and gets nothing” considers only whoever the addon measured and is at the level cap.
- It includes whoever was on any recorded night and has gotten nothing for 8 weeks or more, or never has. Whoever was there most comes first.
- When nobody is in that situation, the block does not appear.
- Loot arrives from the game together with the roster. Sending the same upload again does not duplicate any item.
- Dates appear in your time zone.
This is not a bug
- Someone still leveling, or a bank character, does not appear among those who get nothing: the block is for people who raid.
- Whoever has never gotten anything but has also never appeared on a recorded night is not on the list: they are not waiting for anything.
- “No items recorded yet” until the first loot arrives from the game.
CraftersmemberWho in the guild makes what, by recipe and by profession.
- What it does
- Search for a recipe by name and see who in the guild knows how to make it. Below, a section per profession that someone has: how many crafters, how many of the game's recipes the guild covers, and each crafter with level, specialization and how many recipes they know. The professions nobody has go in a line at the end.
- Who sees it
- Whoever shares a Discord server with the guild.
- Where to find it
- In crafters, on the guild bar.
How it should behave
- The search needs at least 2 letters and looks in the recipe's name in the language you read: Portuguese for Portuguese readers, English for every other language.
- The search shows up to 50 recipes. If there are more, the page says how many and asks for more of the name.
- In each profession, whoever has the addon comes first, from highest level to lowest. Whoever does not comes last.
- Whoever does not have the addon appears with the profession the game's roster reports, as “no addon”, with no level and no recipes.
- “N of M recipes” counts the game's recipes for that profession that at least one person in the guild knows.
- The professions nobody in the guild has appear in a single line, at the end.
This is not a bug
- Empty page: the professions appear when someone in the guild publishes with the updated addon.
- A crafter without the addon never shows up in the recipe search: the site only knows the recipes of whoever has the addon.
Reminders on DiscordofficerWhat the bot sends officers in a direct message, and when.
- What it does
- Shows who the officers are and whether each one has the companion running, the guild's target (at least 2, or all) and the four alerts to switch on and off: Monday summary, companion stopped, officer without companion and upload refused. Beside them, the messages as Discord will show them, in the server's language.
- Who sees it
- Only whoever has Manage Server on a guild Discord server. For the others, the page answers that it is not here.
- Where to find it
- On the dashboard, in the “reminders on Discord” card, under “See the messages”; or in the configuration, under Reminders on Discord.
How it should behave
- An officer is whoever has an officer rank in the game (the leader, the rank right below, or a rank with one of these words in its name: officer, leader, master, vice, GM, oficial, líder or mestre) and linked the character to Discord through /register. Whoever created the guild on the site or a companion code also counts, unless the roster shows the person playing without an officer rank.
- An officer has a companion when a code they created was used in the last 7 days.
- The summary goes out on Monday, from 10am in the time zone of the guild's Discord server, which today is Brasília's for every guild. With nothing to do, it does not go out.
- “Companion stopped” goes out once per stoppage, after 3 days without a roster, and only if a roster has arrived before.
- “Officer without companion” asks each officer at most once a week, and stops asking when they answer that they do not use Windows.
- “Mute for 1 week” silences only the Monday summary. The problem alerts continue.
- The messages go out in the language of the guild's main server.
This is not a bug
- No officer on the list: they appear when the roster arrives and each one links their character through /register.
- A guild created this week does not get a summary until the next Monday.
- An officer gets only one message at a time: whoever just got the companion stopped alert does not get the summary on top of it.
ConfigurationofficerWhere the guild is adjusted: name, public page, servers, permissions, roles and companion codes.
- What it does
- Changes the name and where the guild lives (ruleset and region) and writes the public page. Switches Discord servers on and off, picks the main one and each one's language. Says which Discord roles can schedule raids, set up the guild and change permissions, and which roles /register hands out. Creates and revokes companion codes, picks the channel for the pinned raid list and for the officers' alert, and switches the public character pages on or off.
- Who sees it
- Whoever has Manage Server on a guild server, or a role with the permission to manage the guild or to manage permissions. Anyone else who opens the page sees the notice that they need to manage a server tied to the guild.
- Where to find it
- In settings, on the guild bar (only shows for whoever can). The warnings at the top and the wizard also bring you here.
How it should behave
- Renaming the guild changes the key the addon uses: the next roster has to come from a guild with that name in the game.
- Whoever has Manage Server can do everything. With no role configured, only those people can act.
- Whoever only has the permission to manage the guild opens this page, but does not change permissions: that is for whoever has Manage Server or the permission to manage permissions.
- The guild's last server cannot be switched off.
- A server's language applies to what the bot posts in its channels. The reply only you see follows your Discord's language.
- A companion code appears only once, when it is created. Lost it? Create another and revoke the old one.
- Switching off the public pages takes down each character's page and the randomly picked characters on the guild page.
This is not a bug
- The server's language only has Português and English: what the bot posts in channels still comes out only in those two.
- /register did not hand out a role? The bot needs Manage Roles and its own role above the ones it hands out. And the member role only goes to whoever the roster confirms.
- The officer alert does not arrive before every raid: it only speaks when there is a problem, such as a gap in tank or healer. With no problem, the bot stays quiet.
- Switching off the public pages does not take down the guild page: it only takes down each character's pages and the random pick.
Guild pagememberThe page the guild sends to whoever asks: who they are, when they play and what the game said about them.
- What it does
- Opens with the name, where the guild lives, how many are in the roster, the guild's tagline and the button to its Discord. Shows a few randomly picked characters, the schedule, the average item level and attendance, the pace of the last eight weeks, what the guild is looking for, how loot works, the upcoming raids and the whole roster. Each name opens the character's page, with gear and what the addon published about them. What came from the game and what the guild wrote appear with different marks.
- Who sees it
- Anyone, without signing in. Whoever manages a guild server also sees a strip, for officers only, with what makes the page weaker. Character pages exist while public pages are switched on in the configuration.
- Where to find it
- In page, on the guild bar; in the public guilds list; or at guildos.me/g/… A character's page is at guildos.me/c/…
How it should behave
- With public pages switched off, each character's page answers that it is not here, and the guild page does not pick anyone.
- The characters at the top are up to 4, drawn again on each visit among whoever the addon measured. Nobody chooses who appears.
- The team's numbers count whoever the addon measured and is at the level cap. While nobody has reached the cap, all the measured count.
- The times of upcoming raids appear in the reader's time zone.
- The top says how long ago the roster was published.
- Without the guild's tagline, a visitor does not see an empty space. Only whoever manages sees the place to write.
This is not a bug
- Progression by raid does not show: the site does not yet know how many bosses WoW: Forever raids have.
- Nobody at the top of the page: the addon has not measured anyone yet, or public pages are switched off.
- A character with initials in place of the portrait: the site does not know their look yet. They appear anyway.
Public guildsmemberThe list of guilds on GuildOS, each with what the game said about it.
- What it does
- One row per guild, in alphabetical order: the Discord crest, the name, where it lives and what the game said, such as how far it got in the raid, the average item level and how many raiders. Clicking opens the guild's public page.
- Who sees it
- Anyone, without signing in.
- Where to find it
- In public guilds, in the site footer; in “see all guilds”, on the home page; or at guildos.me/guilds.
How it should behave
- All GuildOS guilds are included, in alphabetical order.
- Only what the guild has already published appears: a guild without a roster does not show item level 0 or 0 bosses.
- Raiders and average item level count whoever the addon measured and is at the level cap, or all the measured while nobody has reached it.
- Clicking a guild opens its page in the language you are reading in.
This is not a bug
- Your guild appears here even with public pages switched off: that switch applies to each character's pages.
- A guild with only a name, without numbers: it has not published anything from the game yet.
Saw something different from what is written here? Then it is a bug, and we want to know.