The Herald
The office
I am Cassanova, Raidchief of <Hakkar> and an officer of the guild. Digg is Warchief and guild master. The final call on direction, raid lead, and roster sits with him. My office is the raid: how we prepare, how we attend, and how we treat loot when the night is real.
We raid as Horde on World of Warcraft: Forever. The aim is progression. That word gets used until it means nothing, so I will say what it means here. A progression raid is a stable core of people who read the plan, bring what the fight requires, and stay for the night they agreed to stand. It is not a pickup crowd assembled an hour before the first pull and dissolved when the first wipe feels personal. It is not a stage for one player to prove they are the reason the boss died. We want kills. We want them with a group that can come back the next week and still know each other's jobs.
Who the raid is for
The guild behind that raid has a specific call, and the raid does not float free of it. <Hakkar>is recruiting players of the 2006-2007 Hakkar PvP server to World of Warcraft: Forever. Alliance and Horde from that server are called to stand together under the Hakkar Horde banner. If you raid with us, you raid as Horde. The old realm is why many of you will know each other's names. It is not an excuse to treat the instance as a reunion that does not need a plan. Memory gets you in the door. Preparation keeps you in the core.
US Hakkar opened on January 2, 2006 as a Central Time PvP server. It was not a November 23, 2004 launch realm. The Burning Crusade launched on January 16, 2007. I am not the historian, and I will not try to outwrite ChaoticZero on the record. I name those dates here only so a raider does not confuse an old server with a mood. The people we most want in the core lived that calendar. The standard of the raid is the same for anyone who earns a seat: show up prepared, as Horde, under this banner.
Schedule
I will not publish a raid calendar in this post. The raids page already says the true thing, and I will not decorate it. Raid nights are not locked. Start time is not locked. Reset and content cadence will be posted when the Forever raid cadence is set. Officers lock the schedule before the first raid. Until that lock exists, any night I named, and any clock time I named, would be fiction. Recruits should not build their week around fiction. When the calendar locks, it will land on the raids page, and attendance will mean that calendar, not a guess you heard from me in a welcome speech.
Attendance, once the lock exists, is a commitment. Life happens. Say so early. A seat you hold in silence is a seat someone else could have filled with their consumables packed and their assignment read. Ghosting a raid, or arriving unprepared and hoping the group will carry the gap, burns the night for everyone who did the work. Recruits earn the Raider rank by consistency as much as by how hard they hit. We can teach a fight. We cannot teach someone to value the hours of the people beside them if they have already decided those hours are optional.
Loot and preparation
Loot stays at the level the raids page already states, and no further. Until officers publish the exact system, the rule is main-spec first for the role you raid as, no side deals. Need before greed for the raid's progress. If a piece is contested, officers decide. I will not invent a points scheme, a council, a wishlist order, or a private exception in this post. If you need a piece for the job you were brought to do, say so in the open, inside the rule. If you need it for a costume, you wait.
Preparation is part of the same respect. Read the plan before you zone in. Bring the consumables the fight expects. Know your assignment well enough that a wipe can be explained without a search for who was surprised. Ask questions before the pull, not after the third one, unless the fight itself has changed. Voice is welcome if you have it. Silence that listens and still does the job is welcome. What is not welcome is noise that spends the pull timer, or quiet that hides a missing reagent until the ready check fails.
How a core is earned
The raid core will be built, not declared. Raider seats are assigned when players lock into that core. Members may be raid-optional and still in good standing. Recruits are on trial and earn a permanent seat. Hakkarians are returning players of the Hakkar server, which is a statement of origin, not a free pass past preparation. Seats are earned by showing up ready for the job in front of you. Digg's call on direction still stands when the instance door closes.
Open world still belongs to the tribe when the tribe needs it. A raid guild that never leaves the instance becomes a schedule with a guild tag. World pressure, travel, and the ordinary work of a Horde city are part of how we know who is actually around. None of that replaces the raid standard. It keeps the guild from becoming a lockout-only room. If the tribe needs bodies in the world, the same people who can be trusted in a raid can be trusted there. If you only appear when a boss is already pulled, you have not joined the tribe. You have joined a queue.
If you want this kind of raiding, read the raids page until the unmarked lines are familiar, then apply and say what you play and how you prepare. Look at the guild if you want the offices named. Do not ask me for a hidden start time. There is not one. When the first raid is close enough to lock, you will see the nights and the hour in the same place everyone else sees them. Until then, the work is simpler: be the player who can be trusted with a plan, a seat, and a piece of loot that might have gone to someone else. That is progression. That is the raid I am willing to chief.