Section I
Charter Purpose
This Charter is the governing document of Bastion of Azeroth [BASTN].
It defines the guild’s rules, leadership structure, standards, member expectations, and code of conduct. It exists so the guild can run with clarity, consistency, and accountability.
This Charter also carries forward the rules and standards built during the guild’s time as Canonically Kings [CANON]. The name changed. The responsibility did not.
When there is confusion, disagreement, or no clear process, this Charter is the first point of reference.
Section II
Guild Identity
1. Official Name
The official name of the guild is Bastion of Azeroth [BASTN].
The former name, Canonically Kings [CANON], is retired from active use. Guild operations, announcements, branding, recruitment, event naming, Discord structure, and member-facing materials should reflect Bastion of Azeroth [BASTN].
2. Identity
Bastion of Azeroth was built on the foundation established under Canonically Kings. CANON carried the belief that all are royalty and that shared strength gives the guild its identity. BASTN carries that same spirit forward in a new form: not as a throne, but as a stronghold.
The name Bastion of Azeroth reflects what the guild aims to be for its members: stable, organized, dependable, and united. The guild exists to create structure, community, and forward progress for the people in it.
Strength in Unity.
4. Cultural Standard
Welcoming Open to people who strengthen the space.
Reliable Members mean what they say and follow through.
Respectful The guild rejects needless contempt and ego.
Organized Structure exists to reduce confusion and drift.
Cooperative Members support shared effort when it matters.
Growth-Minded Improvement is expected, not perfection.
Ambitious The guild values momentum, progress, and intent.
Section III
Core Values
1. Unity
The guild is built to support shared play, mutual support, and a strong community. Members are encouraged to contribute to that environment while remaining free to enjoy the game in their own way.
2. Reliability
Commitments matter. Attendance, communication, follow-through, and consistency all count.
3. Respect
Members and leadership are expected to treat each other with respect, even during disagreement, correction, or conflict.
4. Growth
No one is expected to be perfect. People are expected to be honest, coachable, and willing to improve.
5. Communication
Clear communication prevents confusion, resentment, and unnecessary problems. Members should speak up early when something needs to be addressed.
6. Stewardship
Guild resources, benefits, and opportunities exist to support the guild as a whole. They should be used responsibly.
Section IV
Leadership Structure
1. Current Leadership
- Cheese (Dakota) — Guild Master
- Vynos (Emilio) — Advisor
- Neilla (Featured/Joe) — Officer
- Daemoni (Logan) — Officer
- Thelarius — Officer
No other members are recognized as active guild leadership at this time.
2. Leadership Role
Leadership is responsible for the guild’s direction, stability, coordination, and standards. This includes communication, decision-making, member support, conflict handling, and protecting the long-term health of the guild.
Leadership is expected to lead clearly, act consistently, and reinforce guild standards through both conduct and follow-through.
3. Leadership Standard
- Communicate clearly
- Address issues early
- Support members without enabling avoidable dependency
- Avoid favoritism and mixed messaging
- Protect the guild’s culture, structure, and stability
- Act with accountability, not entitlement
4. Leadership Access
The guild maintains an open-door leadership policy. Members may bring reasonable questions, concerns, suggestions, or problems to leadership.
That access exists to support trust and clarity. It does not remove the expectation that members communicate respectfully and handle minor issues maturely when they can.
5. Defined Leadership Roles
- Guild Master — Primary guild leader and final authority on guild direction, standards, and major decisions.
- Advisor — Strategic support to leadership, guidance on guild operations, counsel on structure, direction, and problem-solving, and Chief Discord Operator.
- Head Officer — Chief Officer responsible for higher-level operational support, internal coordination, and leadership reinforcement across guild functions, including assisting with Discord management under the Advisor.
- Officer — General operational leadership responsible for supporting members, reinforcing guild standards, and assisting with guild stability and day-to-day function.
- Raid Leader — Responsible for raid leadership, raid organization, and raid-night direction.
- Event Planner — Responsible for planning, organizing, and running social-focused guild and community events.
- Treasurer — Guild Accountant and Wealth Director, responsible for oversight of guild financial resources, resource stewardship, and economic stability where applicable.
6. Open Leadership Roles
- Head Officer
- Raid Leader
- Event Planner
- Treasurer
7. Leadership Changes
Any leadership appointment, removal, reassignment, or newly recognized position should be made clear by guild leadership before it is treated as official.
Section V
Guild Rank Framework
1. Purpose of Rank
Guild rank exists to create structure, clarify responsibility, and recognize trust, contribution, and involvement within the guild.
Rank is not meant to function as vanity, favoritism, or social hierarchy for its own sake. It should reflect role, reliability, and earned confidence.
2. Basis for Advancement
- Consistency
- Reliability
- Contribution
- Conduct
- Trust
- Willingness to support the guild and its members
Advancement is not automatic and should not be treated as an entitlement tied only to time spent in the guild.
3. Role of Rank
- New or incoming members
- Established members
- Trusted contributors
- Operational support
- Leadership responsibility
Exact rank names, permissions, and internal distinctions may be adjusted by guild leadership as needed, so long as the purpose of rank remains consistent with this Charter.
4. Standard
Rank should serve function first. Titles may carry meaning, but responsibility, conduct, and trust matter more than presentation.
Section VI
Membership Expectations
1. Age Requirement
Bastion of Azeroth [BASTN] is an 18+ guild. No exceptions.
2. General Expectations
- Represent the guild with basic respect
- Use guild systems as intended
- Communicate when plans change
- Participate in good faith
- Contribute to a cooperative atmosphere
- Avoid unnecessary hostility, disruption, or drama
3. Equal Standing
Every member is an adult and should be treated as an equal. Members may differ in experience, skill, knowledge, or history, but no one should be talked down to, belittled, or treated as lesser.
4. Freedom of Play
The guild supports social play, group activity, and community involvement, but members are not required to play the game in one narrow way.
Solo play, casual play, group play, progression play, and social play all have a place in the guild. What matters is that members do not undermine the guild environment while choosing how they engage with the game.
5. Community Standard
Members are encouraged to engage with the guild as a community, not just a tag over their character’s name. That includes conversation, participation, mutual support, and general presence where possible.
Not every member will contribute in the same way, and that is understood. What matters is a pattern of good-faith membership.
6. Accountability
Membership does not remove personal responsibility. Repeated disregard for guild standards, communication, conduct, or shared resources may result in leadership intervention.
Section VII
Discord Policy
1. Discord Requirement
Discord is the guild’s primary out-of-game communication platform. Members are expected to join and maintain access to the guild Discord in order to stay informed, communicate effectively, and remain connected to guild activity.
2. Purpose of Discord
- Announcements
- Guild communication
- Community interaction
- Event discussion and coordination
- Leadership access
- Ongoing guild presence outside the game
- A safe, enjoyable guild environment
3. Operational Standard
Members are expected to use Discord in a way that supports communication, clarity, community health, and mutual respect.
Discord should not be treated as optional by members who want to remain informed and involved in guild operations.
4. Conduct in Guild Spaces
Guild spaces include in-game chat, Discord, voice, and any guild-run community spaces.
Guild spaces are not the place for politics or religion.
Mature or sensitive topics may come up in an 18+ community, but they must be handled with awareness, restraint, and respect. Members are expected to know the difference between discussion and provocation.
Members should communicate with respect. Cooperation should come through requests, discussion, and willingness, not through hostility, barking orders, or treating others like subordinates.
5. Event Rule
Discord may be used for event discussion, reminders, and coordination, but the official RSVP system for guild events is the in-game calendar.
6. Branding Standard
All Discord channels, roles, onboarding messages, pinned content, bots, graphics, and other member-facing Discord materials should reflect Bastion of Azeroth [BASTN].
Retired CANON references should be removed, updated, or archived where appropriate.
Section VIII
In-Game Calendar and Event Policy
1. Official RSVP System
The in-game calendar is the official system for scheduling guild events and tracking RSVPs.
Members are expected to use it to review events, respond accurately, and keep their availability up to date when possible.
2. RSVP Standard
An RSVP should reflect real intent, not guesswork or placeholder interest.
If a member’s availability changes, they are expected to update their response or notify leadership as soon as reasonably possible.
3. Event Visibility
Guild events should be scheduled clearly, named clearly, and presented in a way that avoids confusion.
4. Operating Rule
Discord can support discussion and reminders, but the in-game calendar remains the authoritative record for guild event participation.
Section IX
Raid Operations
1. Raid Schedule
Official guild raid nights are:
- Tuesday at 8:00 PM EST
- Saturday at 8:00 PM EST
These times reflect the current raid schedule, but may be adjusted based on the vocalized needs of the majority, as determined by guild leadership.
2. Standard Raid Window
The standard raid window is 2 hours. Longer sessions may happen when needed.
3. Raid Expectations
- RSVP through the in-game calendar
- Show up on time when committed
- Come reasonably prepared
- Communicate absences, delays, or changes as early as possible
- Respect raid leadership and raid structure
- Maintain a team-first attitude during progression, wipes, and learning
4. Raid Leadership
The guild recognizes Raid Leader as an official leadership role responsible for raid organization, raid-night direction, and raid standards.
If the role is unfilled, raid operations may be handled by leadership or by a designated acting lead until the role is formally assigned.
5. Raid Standard
The guild should approach raiding with seriousness, discipline, and realism, without turning raid nights into a source of unnecessary burnout, hostility, or ego-driven behavior.
Section X
Guild Benefits and Resource Stewardship
1. Guild Benefits
The guild may provide shared benefits, resources, or support systems for its members. These may include:
- Guild-funded repairs
- A private housing neighborhood
- Limited shared resources through the guild bank
- Other benefits established by guild leadership over time
2. Stewardship Standard
Guild resources exist to support the health, function, and quality of the guild as a whole.
Members are expected to use shared benefits responsibly. Abuse, waste, exploitation, or habitual one-sided use of guild resources may result in limits, intervention, or loss of access.
3. Oversight
As the guild grows, the handling of shared resources may become more formal. The role of Treasurer exists in part to support oversight, accountability, and long-term sustainability where needed.
4. Standard
Guild generosity is a strength, but it is not unlimited. Shared resources should be treated with respect.
Section XI
Recruitment and Onboarding Principles
1. Recruitment Standard
Recruitment should reflect the guild as it actually is: welcoming, organized, community-minded, and clear about expectations.
The guild should not recruit through false promises, inflated claims, or misleading presentation.
2. Onboarding Standard
New members should be introduced to the guild’s basic operating structure, including:
- Leadership
- Discord use
- In-game calendar use
- Event and raid expectations
- Guild culture and standards
- Available guild benefits and shared resources
3. Representation
Recruitment messages, welcome materials, announcements, and onboarding content should present Bastion of Azeroth [BASTN] consistently and accurately.
4. Goal
Recruitment should bring in people who fit the guild’s standards, strengthen its community, and support its long-term stability.
Section XII
Conduct and Conflict Standards
1. Conduct Standard
Members are expected to conduct themselves in a way that does not damage the guild’s environment, operations, or community.
Respect is mandatory. Zero tolerance applies to hate or harassment. Racism, sexism, slurs, bigotry, targeted harassment, or similar conduct may result in immediate removal.
Hostility, manipulation, repeated disruption, bad-faith behavior, or conduct that corrodes trust may also lead to leadership action.
2. Handling Issues
When problems arise, members should handle them as directly and maturely as the situation allows.
- Address the issue respectfully with the person involved
- Bring the issue to leadership privately when direct handling is not appropriate or has failed
- Avoid gossip, dogpiling, public spirals, or unnecessary faction-building
3. Leadership Response
Leadership is expected to address recurring or serious issues with reasonable speed, fairness, and clarity.
4. Corrective Action
When guild standards are repeatedly ignored or seriously violated, leadership may respond with measures such as warning, role or access limits, event exclusion, resource restriction, or removal from the guild.
Some violations justify immediate removal.
Corrective action should reflect the severity, pattern, and impact of the issue. Enforcement does not require prolonged argument or public back-and-forth.
Section XIII
Operational Continuity from CANON to BASTN
1. Continuity
Bastion of Azeroth [BASTN] is the continuation of the guild built under Canonically Kings [CANON].
The name changed, but the guild’s community, standards, responsibilities, and core spirit carried forward.
2. Rebrand Standard
The transition from CANON to BASTN should be reflected across guild operations, including:
- In-game naming
- Event naming
- Discord channels and roles
- Recruitment materials
- Welcome and onboarding content
- Announcements
- Graphics and visual assets
- Other member-facing systems and references
3. Historical Reference
CANON remains part of the guild’s history and foundation, but it is no longer the active operating identity of the guild.
4. Standard
Guild-facing operations should not rely on outdated CANON naming, branding, or structural references where BASTN has replaced them.
Section XIV
Amendment and Review
1. Living Document
This Charter is a living document. It may be revised, expanded, or clarified as the guild grows and its needs change.
2. Authority to Amend
Guild leadership holds the authority to amend this Charter.
3. Standard for Change
Changes to the Charter should support the guild’s clarity, stability, fairness, and long-term health.
4. Communication of Changes
Major changes should be communicated clearly to the guild before they are treated as active operating standard.
Section XV
Closing Statement
Bastion of Azeroth is built through consistency, trust, effort, and shared responsibility.
Its strength does not come from image alone. It comes from the people who contribute to it, protect it, and help it endure.
Strength in Unity.