Guild

One guild has two views. Every member reads the member view. The guild master and the officers get a second tab, the management view, beside it. A member who is neither sees no tab at all, because there is nothing behind it for them.

The member view is the banner, the figures, the members, the forum, the shared challenges and the news. The figures are the member count, the words the guild wrote this week, how many of its challenges are running and how many tournaments it has entered. Every member row carries presence, the username and the role, and a guild master who has not been active for fourteen days is tagged inactive on that row.

The forum is not built yet. The section stands with the reason in it rather than being left off the page, so it is clear that the guild has one and that it is coming rather than that this guild has nothing.

News is the guild’s own record. Welcomes, challenges, successions, removals, joins, departures and notices, newest first, each with the day it was written. An officer can post a line to it from the same section.

Shared challenges are the guild’s. Each one shows its progress against its target and a control to join it. Start challenge opens the create dialog with the guild already chosen and the sharing fixed, since a challenge started from a guild page belongs to that guild.

The management view is applications, members, analytics and, for the guild master alone, the rules. Applications carry the applicant’s own answer to every requirement, with Approve and Decline; declining asks for a reason before it goes. Members stand in a table of role, joined day, last activity, words and sittings this week, and one flag that says the member is below a requirement. Analytics is the pass rate, the member count, the churn, eight weeks of joins and leaves, and the bands the members fall into by what they wrote.

Only the guild master edits the rules. Requirements, auto-kick and the roles are on the master’s view alone; an officer reading the same tab sees applications, members and analytics and nothing else. The language requirement is read by base language unless the exact variant is asked for, so a guild that asks for English takes every English.

Auto-kick warns before it removes. With the setting on and a grace period set, the section lists the members it would warn now: below a requirement and past the grace period since their last activity. Turning it off empties that list at once.

Succession is a notice, not an action. A guild master inactive for fourteen days is tagged, and the management view says since when and the day the most active officer takes the role. Handing the guild on before that asks for a reason and writes the reason into the news.

Removing a member asks for a reason. The reason goes into the guild’s news, so a removal is a line anybody in the guild can read rather than a member who quietly stopped being there.

Try: open a guild you are an officer of and take the management tab. The requirements editor and the transfer are absent, and the applications and the analytics are there.