WoW Legacy Raid Mount Farming: Build a Valid Weekly Plan

An efficient legacy raid mount farm starts with eligible attempts. A fast clear on the wrong difficulty, a visit to the wrong version of an instance, or a second kill after loot eligibility is spent does not advance the mount you wanted.

This guide is for collecting raid mounts in modern World of Warcraft. It gives you a method for planning characters, checking lockouts, and organizing travel. Classic realms and temporary event versions need their own rules; the familiar name of a raid does not make those versions identical.

Make a target card before making a route

Write down five details for each mount: its exact name, its source, the raid version, any difficulty or encounter condition, and your character's remaining eligibility. Start with the Mount Journal and the relevant raid entry in the Adventure Guide. Change the difficulty filter when checking loot rather than assuming every version has the same table.

A named boss can appear in more than one instance. Ashes of Al'ar, for example, is associated with Kael'thas Sunstrider in The Eye at Tempest Keep. A Kael'thas kill in another location is not a substitute. Record both the boss and the instance so your weekly notes cannot be misread later.

Blizzard's Burning Crusade mount guide identifies the boss and location for Ashes of Al'ar.

Two verified targets illustrate why your source card should name both boss and instance:

Mount	Boss	Raid to record
Ashes of Al'ar	Kael'thas Sunstrider	The Eye, Tempest Keep
Fiery Warhorse's Reins	Attumen the Huntsman	Original Karazhan raid

These are boss-drop targets. For achievement mounts, read the individual criteria before killing bosses that may be needed alive.

Understand the two questions behind a lockout

First ask whether you can enter and fight the encounter. Then ask whether you remain eligible for its loot. Those are related questions, but entering an instance is not proof of another mount attempt.

World of Warcraft has used several raid-lockout systems. Some older content ties progress to an instance or shares boss eligibility between sizes or difficulties. Warlords-era raid design introduced separate weekly difficulty lockouts. That distinction is a reason to identify the raid's rules, not permission to apply the newest system to every older instance.

Use Raid Info to inspect the character you intend to play. In the Social window, open the Raid tab and select Raid Info. Check the saved raid, difficulty, defeated bosses, and reset information before traveling. If the displayed state differs from your notes, resolve the difference before killing anything.

A manual instance reset is not a fresh weekly loot allowance. Nor does another player's invitation automatically remove a saved boss or create a new eligible drop opportunity.

Keep special cases visible in your plan

Use a separate note for anything that changes the ordinary route. This prevents a helpful shortcut from quietly becoming an incorrect loot assumption.

Situation	Planning decision
One mount appears only in a specific difficulty's loot table	Schedule that difficulty explicitly; other clears serve different goals
Two difficulties share boss eligibility	Choose the wanted version before spending the shared opportunity
Difficulties have separate lockouts	Count only versions that actually contain the mount
A raid skip is available	Check that the intended character and difficulty can use it
A Timewalking or Remix version exists	Check that event's current availability, reward source, and separate rules
A partly cleared saved instance is offered	Read which bosses are already defeated before accepting it

Reworked instances and encounter-specific rewards deserve an individual check. In particular, a mount appearing in an event reward pool does not establish that it drops from every ordinary version of that raid.

Build a character-by-target worksheet

For each eligible character, create one row per target and relevant difficulty. Include a status such as “ready,” “completed this reset,” or “needs access check.” Record a completed attempt immediately after the encounter, while the character and difficulty are still obvious.

Here is a hypothetical worksheet for three characters collecting Ashes of Al'ar:

Character	Source recorded	Status	Next action
Main	Kael'thas, The Eye	Completed this reset	Wait for the displayed reset
Alt A	Kael'thas, The Eye	No conflicting save; access checked	Make the planned visit
Alt B	Kael'thas, The Eye	Access and saved state unchecked	Check eligibility before travel

This is not three confirmed attempts. One is already spent, one is ready, and one still needs checking. That distinction is useful when an alternate character has recently joined a friend's run or has not visited the content before.

Check each character separately, alongside any reward-specific account restriction.

Save travel time without multiplying the workload

Group targets geographically only after confirming eligibility. A nearby raid is worth adding when it contains something you genuinely want. Adding every instance in a zone may make a route longer without making the main target arrive sooner.

Choose a primary target and an optional secondary objective. For example, your Tempest Keep visit might prioritize Ashes while also checking for appearances you still want. Decide whether that broader clear is enjoyable enough to repeat. If it is not, keep the route focused on what you can sustain.

Parking an eligible alt near an entrance can save travel. Include the return journey when budgeting your time.

Treat raid skips and saved instances carefully

A built-in skip can save time reaching a later encounter, but it does not automatically grant another loot attempt. Check its unlock requirements and which difficulties it covers. When the target is earlier in the raid, using a shortcut past it defeats your own plan.

Shared saves can contain defeated bosses you wanted, and later progress may be linked to that instance. Begin with a fresh eligible character and a known route.

Do not extend a lockout simply because a guide mentions extending saves. Extension preserves progress; decide whether preserving those dead bosses actually serves your target.

Measure a routine you can keep

Track eligible completions and time spent, not a promised date for the mount. A rare drop does not become due because you have been unsuccessful for a long time. Additional eligible attempts give you more opportunities, but a schedule should leave room for the other content you enjoy.

Temporary bonuses also need an expiration check. The earlier Collector's Bounty event boosted selected legacy rewards during a defined window. Its old announcement is not evidence that the bonus is active today. Use current in-game event information before changing your route around a bonus.

Frequently asked questions

Can I run every difficulty for the same mount each week?

Only when those difficulties provide separate eligibility and the mount is available from each one. Either condition can fail. Check the target's loot table and the raid's saved state before treating another difficulty as another attempt.

Will changing characters reset my main character's lockout?

No. An alternate character has its own saved state to inspect; logging into it does not clear the main character's progress. Use separate worksheet rows, and check any reward-specific account restrictions.

Does legacy loot guarantee a mount?

No. Legacy loot rules govern how loot is distributed in eligible older content. They do not turn a rare mount into a guaranteed reward or remove encounter and difficulty requirements.

Why does my old farming guide say the raid resets daily?

It may describe a temporary event. The Pandaria Remix period, for example, changed selected raid lockouts and explicitly scheduled a return to weekly resets afterward. Check the guide's game version and event dates against the reset shown in your current client.

How many characters should I use?

Start with the number you can check and play consistently. Add another when your records are accurate and the extra run still fits your time. A smaller routine of verified attempts is easier to maintain than a large schedule containing duplicate or ineligible visits.

Browse the World of Warcraft hub for related collection service categories.