A quest the guides also do alone is no longer counted as a group quest just because one guide offers an extra way to do it with a group (8 Alliance and 11 Horde quests).
A chain that no class would do even on Hard is now dropped from the route when
it is built (Human: The Missing Diplomat, Night Elf: Nessa Shadowsong), and the
level gaps are worked out again. The grind marks no longer count the xp of
chains that Casual leaves out, so the "grind to level N" steps show up where
Casual really needs them. The route test now checks every chain in the data
file, and the Casual walk in the run test skips the same chains.
- Quests the safe way of playing drops, or that friends rated Hard, are marked and give no xp in the plan on Casual.
- Quests that go into a cave, mine or crypt are marked (a warning only).
- Every danger fact is also stored by quest number, so any guide can use it, not only the plan.
- The route test lists how many quests each zone loses to the new rules.
- Quests that really are inside a dungeon are marked; ones that only mention a dungeon (Westfall Stew, cauldron and Scourgestone quests) no longer are.
- Group quests are marked from the game's own quest facts and the guides' group steps.
- Dungeon quests are now left out on every difficulty; group quests on Casual and Medium.
- Escort quests also come from a short checked list.
- a step that names two people (or one for each class) no longer gives one of them the other's place; Darla Harris is no longer in Arathi Highlands or Stormwind, Bragok no longer in Tanaris
- flights table: 45 flight masters in 40 zones
- the builder scans Data/Guides.lua for flight masters (pfQuest second) and puts the arrow of every flight leg on its flight master; a name neither knows stops the build
- Data/Route.lua gets a flights table for the zones on each faction's paths
- test-route.js check 13 reads the travel table back with the game's reader and checks every move of every race
- every move of every path has an entry; the build stops on a missing or unused entry and on any wording rule (leg count, kind, digits, semicolon, equals sign, two ways, length, start and end zone)
- 17 moves with little data behind them are marked check, counted by the build and listed for the owner in the local TRAVEL.txt
- test 10 also walks a two-leg move (flight, then walk)
- tools/route-travel.js holds the travel words by hand; the builder checks them and writes a travel table into Data/Route.lua
- the reader gets ReadTravel; each zone starts with one step per leg that points at the leg's place and ticks when the zone is reached
- the step is left out when the player already stands in the zone it leads to
- test 10 covers Durotar to Orgrimmar
- tools/build-route.js plays each path with the casual model and marks the quests the player is too low for (Data/Route.lua version 2, sixth field of the Q lines)
- RouteReader.lua reads the grind field
- RouteRun.lua puts a Grind to level step before a giver whose quests are too high, and at the end of each zone
- test-route.js checks version 2 and the grind field; test-route-run.js walks the Orc steps with the xp model
- Hillsbrad Foothills 30-32 between Wetlands and Arathi Highlands: the Arathi chain Hints of a New Plague? starts there
- Stormwind City short stop at 44, before the Hinterlands: To The Hinterlands starts there
- Ironforge short stop at 52, before Western Plaguelands (Burning Steppes 49-52, Western Plaguelands 52-57): A Call to Arms: The Plaguelands! starts the cauldron chain
- a second or third visit of a zone is marked again by the ladder file itself
- the outline names each left-out quest in every zone, with its level, the reason and how many guides do it
- test: the RestedXP share, the quest count (8 or 2 per level) and the guide agreement are checked in every zone
- a quest that drops in a battleground and in the open world (Runecloth) is no battleground quest
- a quest does not wait for a prerequisite that has no giver on the map, or for a go-and-talk-to quest most of its guides skip
- a quest RestedXP does in a later zone stays here when that zone cannot take it (the Undead Apothecary line, Teldrassil, Mulgore)
- Human gets a Stormwind stop at 28 and Dwarf and Gnome an Ironforge stop at 54, each on the way between two zones
- every short stop in a city lists the quests the guides give there at other levels
- zones from level 20 name the left-out quests a guide does whose work is in the next zone
- no quest qualified for a 'pick it up here, do it in the next zone' rule, so none was added
- far work stays (marked long walk) when any guide does it
- a go-and-talk-to quest no guide does no longer holds back a quest a guide does
- inside an area, quests of the same level go in order of how many guides do them
- more than 3 quests for the next zone: the ones more guides do stay
- outlines name which guides do the extra quests and end named left-out lines with (in N guides)
- route test: check 11 also needs VanillaGuide rows, new check 12 prints what the guides agree on per zone
- new tools/build-guide-index.js reads the TourGuide files as text and writes tools/data/guide-index.tsv (facts only)
- the builder reads the index on every run, no archive needed
- zone rule: RestedXP's zone only keeps a quest out when it is a later zone of the ladder or no other guide picks it up here
- outlines say which zone RestedXP uses and which guide picks it up here
- route test check 11 looks over the guide index
- outlines list each left-out quest of a zone below 20 with its level and reason
- test check 10: every zone below 20 keeps at least 8 quests
- item objectives count the three best drop places in every zone, not only in the world
- a quest needed only through quests other races do is no longer held back (Barrens chains for Orc, Troll, Undead)
- Tauren stop in Thunder Bluff at 10 for the quests that start the Barrens chains
- ladders for Human, Dwarf, Gnome, Night Elf, Orc, Troll, Tauren and Undead, each on one continent
- the first quests of a chain may sit a few levels under a zone's window, so the chain is not cut off
- battleground quests are left out; a long walk between areas is shortened; a quest the character is too low for waits until the others in its area are done
- Data/Route.lua holds the 8 paths, one per line
- check 5: a quest comes after the quest its Data/Zones.lua row says it needs
- check 7: no hop between two areas above 0.7 of a zone side, no zone walk above 15000 yards
- the builder names an area after a person rather than a board or a chest
- reads RestedXP's quests from Data/Guides.lua: a quest RestedXP does in another zone is not taken here, and inside an area RestedXP's order comes first
- the work of a quest must be in the zone; hand-ins at a capital stop or at the next zone (at most 3) stay in, marked x; quests done only inside a dungeon are left out
- work far from its area moves to a later area close to it, is marked as a long walk, or is left out when it is very far
- flags e d s c f x k, quests come after the quests they need, only one of an either-or pair stays
- each zone starts where the last one ended (world yards)
- the outline says what was left out and why, and marks the quests RestedXP skips
- test-route check 8: hand-in places
- tools/lib/pfdb.js loads the pfQuest, pfQuest-turtle and pfExtend data
- tools/lib/xpmodel.js has the experience rules used for levels and gaps
- tools/route-ladder.js holds the hand-kept zone order (Orc for now)
- tools/build-route.js builds Data/Route.lua (not loaded by the game yet) and the plain-text outline