Chapter settings and new abilities
Use /oga to open the addon. Chapter leaders can tighten roster rules, while eligible inviters choose how they hear about applicants. The audit still totals 100 points.
Set your chapter rules
- Log in as Lead Officer or higher (rank indexes 0 through 3), then open Chapter.
- Set a member target and the default GM/officer note prefix.
- Set inactivity days and an optional note prefix for each rank.
- Click Save chapter rules. Check the audit findings after saving.
| Setting | Default | Allowed changes |
|---|---|---|
| Member target | 980 | Whole numbers from 980 to 1000. |
| Inactivity / purge threshold | 28 days for every rank | 1–3650 whole days per rank, including longer Veteran/Honored limits. Ranks 0/1 are exempt from inactivity findings and inactivity purge lists; other members are flagged after their rank's limit. |
| GM/officer public note | Disc: followed by a value | Change the default prefix or override it for a rank. |
| Other members' public notes | Any nonblank note | Require a prefix for a rank. Blank notes always fail. |
Prefixes are literal text, matched without regard to case, followed by a nonblank value. For example, Main: Marcus passes a Main: rule; Main: alone fails. An empty rank prefix uses the GM/officer default for officers and the nonblank-note rule for other members. Prefixes allow up to 40 characters and cannot contain a pipe or newline.
Startup exceptions below 980 are not available yet. MOTD rules, recruitment requirements, and point weights cannot be changed from this tab. Purge candidates use the configured rank limits; removal still requires your manual action. Changing rules cancels an existing purge queue (after combat if necessary).
Share and retain settings
Rules are saved separately for each region and guild club ID. Saving shares them with online addon users. A client requests saved rules when logging in; a Lead Officer or higher must be online to supply a missed change. Until then, that client uses its saved rules or the defaults. Reload or log out normally to let WoW write SavedVariables.
Choose applicant notifications
Anyone with guild invite permission can use the Applicant alerts button in Recruiting to cycle through Both → Sound → Popup. You can also use /ogaalerts both, /ogaalerts sound, or /ogaalerts popup. Both is the default; there is no Off option. Preferences are saved per character.
Alerts cover pending applicants. The addon requests applicant data periodically; delivery depends on WoW returning the list. It suppresses repeated alerts for the same observed pending applicant during a login. Logging in again can alert for applicants still pending. Combat, dungeons (including Mythic+), raids, scenarios, battlegrounds, and arenas defer notifications. Enabled built-in and custom quiet-zone rules also apply to your current zone. Popups and sounds queue until you leave quiet content and combat ends; ending a key while still inside the dungeon does not release them. A visible popup is put back in the queue when you enter quiet content. Applications no longer pending are removed before queued alerts are shown.
Review the applicant before acting. Hold Ctrl+Shift and click Invite to request approval. The addon rechecks permission, guild identity, and pending status. Verify the result in Guild Finder: WoW may restrict approval from addon code, in which case use the native Invite button.
Audit scoring and MOTD
The score is earned points divided by 100. The ten categories remain worth 10 points each. MOTD, calendar/meeting, and New Member Info categories have separate 5-point checks. New Member Info and missing promotions each have their own confirmation and channel link.
MOTD checks the guild name, then the guild realm, then discord.gg/oldgods in that order. Extra text is allowed; case and repeated whitespace are ignored. The Aegwynn chapter uses its Aegwynn name for this check while retaining its technical realm for uploads. Recruitment still requires at least 26 days remaining.
Companion improvements
- The installer can start while the Companion is open and prompts you to close it before installation continues.
- Feedback Review status/type edits can be saved; validation errors are visible.
- An unregistered guild in an upload is skipped so subsequent queued items can proceed.
- New builds use
https://oldgods.iofor service, installer, and update URLs.
Older installations need an update or a new installer before the old host can be retired. The retirement plan is at least a month without legitimate old-host requests, with bots and health checks tracked separately.
Before rollout, complete the release test checklist, including live guild sync and applicant approval checks.