What Layering Does to a Farming Route
Forever has no realms. You do not pick a server, you are placed in a copy of the world — and which copy you land in quietly decides how much you gather in an hour.
A layer is a copy of the world
The realm list is gone. Everybody who picked the same ruleset is in one space, and the game keeps several copies of each zone running so that no copy is packed. Walk into Elwynn and you see the players in your copy; the rest are elsewhere, in the same zone, invisible to you.
A recent account from the RP ruleset puts numbers on what that feels like. The player reported being placed on layer 48 and, on the day after launch, walking through a capital that was close to empty: a handful of characters by the bank, no crowd at the mailbox, trade chat moving slowly enough to read every line. The zones outside told the same story — nodes standing untouched, no one contesting a route that would have been a queue on a single realm. The copy was not broken, it was simply one of many running at once, and most of the population was somewhere else.
Two things follow from that, and they pull in opposite directions. Competition for nodes drops, because the people racing you are only the ones sharing your copy, and on a high-numbered layer that can be very few. Trade gets thinner for the same reason: the city around you is not the market, and anything that depends on people standing nearby — a shout for a quick craft, a buyer found in chat, a group assembled on the spot — takes longer than the auction house, which is the part of the economy of Forever that does not care which copy you are standing in. We have not verified how many copies run per ruleset or how layer numbers are assigned, so treat 48 as one player's report rather than a ceiling.
Chat is cut the same way the world is. General and trade channels reach the players in your copy and nobody else, so a service you advertise is offered to whoever happens to be sharing the zone with you at that moment, not to the whole ruleset. That matters most for work that cannot be posted on the auction house: enchanting an item the buyer already owns, crafting from materials somebody hands you, opening a lockbox on request. All of it ends in a face to face trade, so buyer and seller have to be standing in the same copy of the world before the order exists at all.
Trade chat deserves to be read as a local board rather than a market feed. A line you post is seen by the players sharing your copy of the zone at that moment, and lines posted in the other copies never reach you, so the volume of chatter you see is a measure of how busy your copy is and nothing more. A slow trade channel does not mean demand is low across the ruleset, and a fast one does not mean you have found the best place to sell. Two players on the same ruleset, in the same capital, can spend the same evening with completely different impressions of what people are asking for.
Language cuts the same channel a second time. The preferred language you set when you create a character is used to place you in the world, but it does not always follow through to chat: players report sitting in a copy where the general population is speaking one language while their own Trade channel stays tied to the language they picked, with very few people in it. The result is a trade board that is quiet for a reason that has nothing to do with demand — the buyers are present, they are simply reading a different channel in the same zone.
If you sell services rather than listed goods, that is worth checking before you decide a copy is dead. Look at whether the lines scrolling past are in the language you chose, and whether the channel you are posting into is the one the crowd around you is using. We have not confirmed how the language setting maps to channels in every case, or whether it can be changed after a character exists, so treat this as something to verify on your own character rather than a rule. The auction house is unaffected either way, which is one more reason crafters with an uncommon pattern tend to post the finished item instead of advertising the work.
The practical edge of that shows up with rare patterns. If the only person on the ruleset who knows a recipe is standing in another copy, the advert never arrives, and neither does the crafter, because the materials have to change hands in person. So the demand does not disappear, it moves: the buyer stops shouting and goes to the auction house, which is the one place where listings are shared regardless of which copy the seller was in when they posted. That is why finished goods tend to clear reliably while commissioned work stalls, and why crafters who hold an uncommon pattern usually post the output rather than wait for someone in range to ask for it. The same split runs through most of the economy of Forever: anything that can be listed behaves like one market, anything that needs two people in the same zone behaves like several small ones.
The service market is therefore thinner and less predictable than the goods market, and the two move in opposite directions. A quiet copy is good for gathering and poor for selling labour, because there is nobody in range to read the advert; a crowded one does the reverse. Sellers describe working around it by sitting in a capital during the busy hours, re-posting after copies are folded together because the audience around them has changed, and taking a group invite to reach the copy a buyer is already in. We have not measured how much service volume moves that way, so treat it as how sellers describe the problem rather than a figure you can plan against.
The quiet copy is not the only thing players report, and the opposite case is the one that breaks routes. Forever runs as a single space rather than a list of realms, and part of the player base treats that as the root of the problem: with everyone on one ruleset instead of spread across separate servers, the copies that are running get filled from a much larger pool than a classic realm ever drew from. The complaint that keeps coming back is density at a single point — 30 or more players stacked on one spawn, not in a capital at prime time but on a weekday afternoon, in a zone that should have been half empty. We cannot confirm how copies are allocated or whether any cap exists on how many players share one, so this is what players describe rather than something we can measure.
Rare spawns are where that density turns into wasted hours. A hunter camping Broken Tooth in the Badlands is not racing the ruleset, only the players in the copy standing with him, and the wait is long enough that the copy itself becomes the risk. Players describe sitting on the route for 6 hours and then losing all of it at once: a group invite, a zone change, or copies being folded together drops the character into a different copy of the world, where the timer that was being tracked means nothing and the camp starts from zero. The same thing happens in reverse — a transfer can put a player onto a spawn somebody else had been watching all afternoon. We have not verified how spawn timers behave when a character moves between copies, so treat the 6 hours as what hunters report losing rather than a measured rule.
Stranglethorn Vale shows the other half of the problem. Reports from the zone describe 5 hunters per copy waiting on the same rare cat, each of them unaware of the others sitting on identical spawn points elsewhere, so the real number of people chasing one tame across the ruleset is far higher than anything visible on screen. For a gold route the lesson is the same as with nodes: time spent waiting on a single contested spawn is only worth it if the payoff is large and the wait is short, and neither condition holds for a rare that several players per copy are already camping. Farming that moves — a gathering circuit, a mob pack with several spawn points — survives a transfer, because nothing about it depends on a timer you cannot see.
The complaints that arrived in the days after launch are about movement between copies rather than crowding inside one. Players report being pulled into another copy without warning and with no prompt to accept: mid fight, with the mob reset and the health bar back to full on the other side; mid cast on a herb or a vein, with the node gone from under the character and the cast wasted; and in at least some accounts with loot left behind, including chests that had been opened but not emptied. Nobody we have read describes a way to refuse the move or to get the node back afterwards, and we cannot confirm what triggers it or how often it happens, so treat it as a reported failure mode rather than a schedule you can plan a route around.
For a gatherer that is a straightforward loss of money, not an inconvenience. A route is a sequence of spawns walked in order, and a forced move drops you into a copy where that sequence has already been picked over by somebody else, so the run restarts from whatever is left rather than continuing. The same reports mention the zeppelin and boat routes behaving as a merge point, with passengers who boarded in different copies arriving together, which is the opposite problem: a quiet route can turn contested the moment the transport lands. If you gather on a timed loop, it is worth noting how often a run ends early for this reason before you judge whether a zone is worth the travel at all.
What that costs a gatherer is the off-peak window. The usual plan for a contested route is to run it at an hour nobody else wants, and that plan assumes the population rises and falls over the day. If the pool feeding every copy is large enough, the dead hour stops existing: the copy you log into at an odd time is filled by whoever else is awake across the whole ruleset, and the spawn you were counting on has already been taken by somebody who arrived 30 seconds earlier. Routes that depend on being alone are the first to stop paying, while anything that can be listed and sold without standing next to a buyer is less affected — the same split that runs through the economy of Forever elsewhere.
Two behaviours around this have come up often enough on the forums to be worth naming. The first is layer hopping: players grouping with someone in another copy of the world, taking the port, and checking whether a camp there is running dense. Hyperspawn pockets — mobs respawning the moment the last one dies, because a tag of players is clearing them faster than the zone expects — are what the hoppers are looking for, since a camp like that pays better per hour than a quiet route. The method is old and the reports of it are current, but we have not tested how reliably a group invite moves you between copies in Forever, so treat it as a practice players describe rather than a step we can confirm works on demand.
A timed fishing contest is the clearest case of the same mechanic, because the prize goes to whoever fills a quota first and the pools that count are a fixed, visible resource sitting on the water. Inside one copy the race is readable: you can see the boats, you know roughly how many people are working the same stretch of coast, and a pool you swim to is either yours or already being fished. Across copies none of that holds. A competitor who hops into a quieter copy is fishing the same contest against a different set of pools, and the player who stayed behind has no way of knowing whether the stretch they lost was crowded or empty. The contest is scored once, but it is being run in several worlds at the same time.
That is why the recurring suggestion on the forums is to lock players to the copy they were in when the event started, for as long as the event runs, so that a contest decided by who reaches a pool first is at least decided inside one world. The counter-argument is the usual one: a locked copy that happens to be busy punishes everyone in it, and a locked copy that happens to be empty hands the result to whoever landed there. We have not seen a statement on whether timed fishing events run on Forever, or whether any lock of that kind is in place, so treat the whole exchange as a dispute among players rather than a setting you can plan a morning around. The general lesson holds regardless of how it is resolved, and it runs through most of the economy of Forever: anything scored against other players, rather than listed for sale, depends on which copy you were standing in.
The clearest money motive for moving between copies showed up around a fishing event with a limited number of payouts. Players reported wins landing around 20 minutes after the start and argued that the speed came from hopping: the same pools exist in every copy of the zone, so somebody who can reach a fresh copy works a stretch of coast nobody has touched yet instead of queueing behind the crowd in their own. Whether that is what happened in any particular run is not something we can verify, and nothing has been published about how competitors are placed, so read the complaints as a description of the incentive rather than a settled account of the result.
The same threads carried the opposite complaint: being pulled into another copy in the middle of a cast. Copies are folded together and rebuilt as population shifts, and a player moved while the bobber is in the water arrives somewhere else with the pool gone and the cast wasted. None of that is specific to the event — it is the same mechanic that empties a gathering route halfway through — but it bites harder when payouts are limited and timing decides who gets one. If a prize is attached to what you are fishing, it is worth treating a forced move as a normal interruption and planning to return to a spot rather than counting on finishing it in one pass.
The second is the cost of being moved without asking for it. Copies are folded together and rebuilt while people are playing, and a forced move lands on whatever you were in the middle of. Players on the forums have stopped describing this as an inconvenience and started counting it in gold: a craft cancelled part way through, a reagent that was already spent when the cast broke, a station or a tool left on its cooldown while the character is standing somewhere else. None of that shows up as a loss in the log, which is why it goes unnoticed until someone adds up an evening of it.
The exposure is uneven. Gathering survives a move almost intact, because a node you lose is replaced by a node in the new copy. Multi-step crafting is the opposite: the longer the chain and the more expensive the input, the more a single interruption costs, and anything tied to a timer suffers twice, since the timer keeps running while you walk back. We have not confirmed which interruptions refund materials in Forever and which do not, or how often copies are merged on a normal evening, so treat the shape of the loss as reported and the size of it as something to watch on your own crafts. The practical answer sellers give is dull and works: start long chains when you are already parked where you intend to stay, and keep the expensive step for a moment when you are not expecting to be moved.
The clearest use of that is AoE farming, where the whole income depends on packs arriving faster than you can clear them. The pattern players describe is simple: pull a camp, measure how quickly it refills, and if the respawn is slow enough that you are standing around between pulls, take an invite into another copy of the world and test the same camp there. A copy where several groups have been grinding the spot already has mobs coming back on top of each other, so an AoE pull that was waiting on respawn in one world runs back to back in the next. The farmer is not looking for an empty zone in this case — the opposite, a busy copy is the point, because the pressure on the camp is what keeps it dense.
Two limits are worth stating plainly. The pocket is temporary: when the other groups leave or the copies are folded together, the camp drops back to ordinary respawn and the hour stops paying at the rate you planned it at. And we have not measured how much faster a contested camp refills, or whether the effect holds across every AoE spot, so this is a method players report rather than a number you can budget against. Priced honestly, an AoE session is a bet on conditions you do not control, which is why most people pair it with gathering or crafting income when they plan an evening against the economy of Forever.
The second is the complaint about copies being folded together. When population in a zone drops, the copies are collapsed into fewer of them, and players report this landing all at once rather than gradually: a route you had to yourself fills with gatherers in one moment, nodes you were cycling are already stripped, and a camp you were holding is suddenly shared. The grievance is about timing rather than the mechanic — there is no warning before it happens, so a plan built on an empty copy can stop paying mid-session. Anyone budgeting an hour of gathering against the economy of Forever should assume the copy around them is temporary and price the route on contested conditions, not on the quiet ones.
It is worth being precise about what a copy covers. A layer is cut per zone, or per small group of zones, not per continent — so the copy you were placed in on one side of a border does not follow you across it in any way a player can read from inside the game. Walking into the next zone is a fresh placement, and a quiet route behind you says nothing about how contested the one ahead is. The same logic explains why a shared ride matters: anything that moves a block of players into a zone at the same moment, like a boat or a zeppelin, tends to hand them the same copy when they step off.
The second point follows from that and is the one most plans get wrong. Folding copies together does not thin the crowd inside the copy you end up in; it does the opposite. Nodes, mobs and respawn timers are counted per copy, so when two copies become one the gatherers add up while the route stays the same size. That is why the crush after a collapse does not settle by itself — the merge creates no extra nodes, it only puts more people on the ones already there. Pressure drops when players log off or spread across the hours, not when the number of worlds goes down.
One measured session shows what that costs in plain time. After a collapse, a quest step asking for 10 kills of a single mob type took 40 minutes to finish, because respawn on that camp runs from 4 minutes and the spawns were being split between everyone standing on them. The same step in a quiet copy is a few minutes of pulling. Nothing about the quest changed — the kill requirement, the respawn timer and the size of the camp were identical. The only variable was how many people the merge had put on the same spawns.
The same forced move lands on gathering routes, and players report it as the more expensive case. One account describes farming whelps for Specks of Dream Dust on a spawn nobody else was working, then being told the copy was closing and the character would be moved. The destination was a copy where the same whelps were already camped by several players, so the route that had been paying a steady drop rate turned into waiting for tags on mobs somebody else had pulled. Nothing about the farm changed except how many people were standing on it.
There is a complaint that runs the other way, and it is the one posted most often. Players report that every copy they are placed in is packed, that the mobs in a camp are taken the moment they appear by people running tag macros, and that the camp does not recover at any hour they have tried — late night included. Whether that holds across all rulesets we cannot say, and we have not measured how many copies are running when it happens, so read it as a complaint with a consistent shape rather than a measured condition.
What matters for planning is that it describes a second kind of competition. The node pressure above is about ore and herbs standing in the world; this is pressure on the mobs themselves, and it hits a different set of income. Grey vendor trash and cloth come off kills, so a camp held by faster taggers pays you nothing per hour no matter how long you stand on it. Skinning is the clearest case, because the skin exists only if you got the tag, and the same applies to any profession levelled off drops rather than off nodes. If you are pricing an evening against the economy of Forever, treat kill-based income as the part most exposed to a crowded copy, and keep a gathering route or a crafting queue as the fallback when the camp is not giving you tags.
The complaint that followed launch was not about nodes at all. Players report that the number of copies running per ruleset was cut back once the opening rush thinned out, and the loudest objections came from people killing mobs rather than mining them. A herb or a vein is contested once and then gone; a camp is contested on every pull, because the spawn goes to whoever lands the first hit and the loot belongs to that tag. On a crowded copy that turns a grind into a queue you cannot see — the mobs are up, they are simply tagged before you reach them.
Quest drops are where this shows up as lost income rather than lost patience. An item that only drops from a mob you tagged yourself cannot be shared, so a step that wants a stack of them scales with how many people are standing on the same spawns, not with how fast you kill. That is the part a route plan usually ignores: travel time and clear speed are under your control, tag availability is not, and after a collapse the second number is the one setting your hour. We have not seen published figures for how many copies run now versus at launch, so the scale of the cut is a player claim rather than something we can confirm. The practical response is the same either way — when planning an evening against the economy of Forever, treat kill-based steps as the first thing to move off peak hours, and leave gathering for the windows when the camps are full.
The move is not instant. Players describe a notice that the copy is closing and a window of roughly 10 minutes before the character is pulled across, which is enough time to finish a pull, empty a node you have already tapped, or ride to a mailbox rather than being dropped mid-route. We have not confirmed that the window is always the same length, so treat 10 minutes as what players report rather than a timer you can plan a long gathering loop around. The practical use of it is small and real: when the notice appears, stop starting new work and bank what is in your bags.
What sits underneath all of this is a spread in income that has nothing to do with skill. Landing in a near-empty copy is the best hour a gatherer gets — every node on the circuit is standing, nobody is cutting the route ahead of you, and a loop that normally returns half-stripped comes back full on the first pass. Half an hour later the same character can be folded into a packed copy where the identical circuit is picked clean before you reach the second node. Same route, same hour, same character, two very different results. That is why a single good session is a poor basis for a plan: price your week on the contested copy, treat the quiet one as the exception, and keep income that does not depend on the copy around you — crafting stock, auction listings, anything settled through the economy of Forever — in the mix.
The part worth planning around is that the prompt only lets you postpone. Players describe a timer that can be pushed back while they finish a pull or empty a bag, but not a way to stay where they are, so the move arrives eventually whatever the route is doing. That makes a quiet spawn a condition you are borrowing rather than holding, and it is the reason an hour of gathering priced against the economy of Forever should be budgeted on the contested version of the camp. We have not measured how long the delay runs or how often it is offered, so treat the behaviour as reported rather than fixed.
Kill steps are the forgiving case, because a slow camp only costs you time you can see draining. Escort quests are the other kind: the NPC walks with you, and if the world around you is swapped mid-walk the escort does not come along. Players report this on the long ones specifically — the Homing Chicken runs in Tanaris and Feralas, the Tooga escort across Tanaris, and the Burning Steppes steps feeding into the Blackrock Depths chain. All of them share a shape: a fixed route, an NPC moving at its own pace, and no checkpoint between the start and the hand-in.
What makes it expensive is that there is no warning before a move. You do not get a prompt, a countdown or a chance to finish the walk first, so the first sign is the escort being gone and the quest sitting back at its starting state. Everything spent getting the NPC that far is spent again from the beginning, and on a long escort that is the bulk of the run. If you are planning an evening of quest income against the economy of Forever, treat escorts as the steps to do when you can finish them in one sitting, and leave the interruptible work — gathering, mob camps, anything that resumes where you stopped — for the parts of the session you expect to be broken up. We have not measured how often a forced move lands mid-escort, so this is a risk to plan around rather than a frequency we can quote.
There is a second source of movement that has nothing to do with players logging off. In a hotfix dated 9 November, Blizzard stated it was reducing population in zones carrying significant population density. That is a deliberate adjustment, applied from outside the game, not the automatic folding and splitting that happens as people come and go. It confirms something the forum reports only implied: how many players share a copy of a zone is a value that gets turned by hand when a zone is judged too crowded.
For anyone planning a route, the practical consequence is that density is not a stable property of a zone. A circuit timed in a heavily populated area before a change like that may run differently afterwards, and the opposite can hold too — a camp that was dense because of the crowd on it can thin out once the crowd is spread across more copies. The hotfix did not say which zones were affected or by how much, and we have not measured the result, so the honest version is that the setting exists and is adjusted, not that any particular route got better or worse. Budget an hour of gathering against the economy of Forever on what you can see in front of you that evening, and re-test a route you have not run in a while rather than trusting notes taken under older conditions.
Nodes are the half of this that people plan around, but mobs are split per copy in exactly the same way, and the rules on them are harsher. A kill belongs to whoever tagged it; there is no shared tag that credits everyone who hit the same mob, so a camp holding more players than spawns resolves by who lands the first hit, not by who has been standing there longest. Grouping removes that problem for a handful of people and no more, and it does not reach across the faction line at all — you cannot invite a player of the opposite faction, so part of the crowd on a contested point stays competition you have no way to merge with.
One player's count from a quest point in Arathi puts a size on it: roughly 60 people working the same spawns, with about 1 kill per minute coming out of it. That is an estimate made from inside the crowd rather than something we can verify, and the only thing it is good for is the shape of the problem — an objective worth a few minutes in a quiet copy turns into a long sit when the copy is full. Price kill steps and mob-drop farms the way you price a gathering route against the economy of Forever: assume the contested case, and keep a second task ready for the stretches when the camp gives you nothing.
The number of players a copy holds is not fixed either. During launch week the staff adjusted the population limit per layer, which changes how many copies run at once and therefore how many gatherers share a route. The direction of the change matters more than the figure: raising the limit packs more people into each copy and fewer copies exist, lowering it spreads the same population thinner across more of them. We have not seen the limits published as numbers, so what follows is the behaviour players described rather than a setting you can look up.
The developers have also said the increase is not finished. Their stated intent is to keep raising how many players a single copy holds, which means fewer copies running side by side and more people placed into each one. No schedule and no target figure have been published, so the only thing a farmer can plan around is the direction: routes are meant to get busier, not quieter, and a copy that feels comfortable this week is not a baseline for the next adjustment.
That is exactly the pressure players are already complaining about. The two recurring grievances are competition for gathering nodes and queues at quest NPCs — a herb or vein cycled by several gatherers on the same path, and a quest giver or a named target surrounded by people waiting on the same respawn. Raising the population limit makes both worse by definition, because nodes, mobs and NPC spawns are counted per copy and the count does not grow when the headcount does. If you price an evening against the economy of Forever, the safer assumption is contested conditions on the common routes, with the quiet hours and the less obvious zones doing the work that an empty copy used to do for free.
What came back after the adjustment was a run of complaints about quest zones being unplayable — objectives stripped on sight, named mobs taken the moment they spawned, and the early questing zones carrying a crowd that the kill requirements were never written for. Gathering routes in the same zones read the same way. The point for anyone planning an hour is that this density is set by the administration and changed on their schedule, not produced by player habits, so a route that paid yesterday can be contested today with nothing on your side having changed. Price the hour on the crowded case and treat the quiet copy as the exception, the same way the rest of the economy of Forever rewards planning against the worse conditions rather than the better ones.
Gatherable quest objects behave worse, because they cannot be shared at all. With 12 players waiting on the same set of ground items, the route turns into a queue: you walk the circuit, find every object taken, and wait out the respawn with everyone else doing the same. A kill can at least be tagged by a group; a pickup goes to one person and the other 11 start the timer again. If you are planning an hour against the economy of Forever, price collection steps on those conditions rather than on the quiet copy you started in, and keep a second objective in the same zone to fall back on while the first one refills.
The Stranglethorn fishing tournament is the sharpest example of this, because it puts a timed payout on top of a resource that is counted per copy. Players report the schools of fish being stripped inside 20 minutes of the start, which is fast enough that anyone who spent the opening stretch flying to the coast has already lost the run. The arguments afterwards are about the rule rather than the fishing: nobody can say from inside the game whether the cap on winners is applied to the copy you are standing in or to the whole ruleset, so a tournament that pays a handful of people may be paying that handful once, or once per copy, with no way to read which from the shore.
The practical response people describe is the same one used for camps — take an invite into another copy and look for a stretch of coast where the schools have not been worked yet. We have not verified how the winner limit is counted, whether school density differs between copies, or how reliably a hop lands you somewhere with fish left, so treat all of it as player discussion rather than a method with known odds. What is worth taking from it is the structural point: any event that hands out a fixed prize on a fixed clock sits awkwardly on a world that is cut into copies, and the hour you spend on it is priced against conditions you cannot see before you arrive. Steadier income lines in the economy of Forever do not have that problem.
One cave in Thousand Needles shows the seams in this better than open ground does. A Russian-language report describes the copies inside that cave as only partly separated: characters from other copies are not drawn, so the room looks quiet, but their area damage and their silence effects still land on you. You take damage from a pull you cannot see and lose a cast to a silence with no visible source, which reads as a bug from the inside until you know the copies are overlapping there.
Two costs follow from that for anyone running the quest chain through the cave. The named mobs in the chain are contested by everyone in the overlapping copies, not only by the players on your screen, so a spawn can be taken by a group you never saw and the wait is longer than the room suggests. And credit for a quest item is sometimes not registered on pickup; the players reporting it say logging out and back in makes the item count, which is worth trying before you go looking for another one. We have not reproduced either behaviour ourselves, and we do not know whether other caves are cut the same way, so treat this as one zone where the usual rule — what you see is who you compete with — does not hold.
Rare spawns sit awkwardly on top of all this, and it is the part of layering that costs the most time for the least visible reason. A rare is not a node you can walk past and come back to — it is a timer attached to a zone, and a copy of the world that was spun up a few minutes ago carries no history of that timer. Players camping a spot on a fresh copy describe the same outcome: the mob is not there, nothing is on cooldown, and the wait simply does not end, because the window they are waiting on belongs to a zone state that this copy never had.
Collapsing makes it worse in the other direction. A camp you have been holding for a long stretch can be folded into another copy, and what you arrive in is somebody else's zone state rather than the one you were counting down. Whether the clock continues, restarts, or was never yours to begin with is not something a player can read from inside the game, so the practical effect is a wait that resets without notice. This is why people trade invites looking for older copies — a world that has been running for hours is more likely to have a rare due than one opened this evening — and why a rare-spawn plan is a poor way to fund anything. We have not verified how spawn timers are handled when copies are created or merged, and Blizzard has published nothing on it, so the honest reading is that rare camping on layered worlds is unpredictable, and gathering or crafting income priced against the economy of Forever is the steadier half of the hour.
The layering change deployed on 6 November is the clearest example of how a retune lands on a gathering route. Players reported NPCs appearing cloned, the same quest giver or vendor standing in two places at once, and general lag in populated zones while the copies settled. Boats and zeppelins were reported as putting everyone aboard on a shared layer, so a crossing that used to scatter arrivals across copies dropped the whole deck into one — which means the players stepping off at the dock with you are the ones you will be racing for the first nodes inland. In Boulder Lode Mine, nodes and mobs were reported as invisible: present in the world, counted by the server, but not drawn for the player standing next to them.
Roguefeather Den is the case that shows what a partial merge does to a camp. Players describe the cave as a place where the copies overlap only halfway: characters from another world are drawn and move around you, but their targets are not, so you watch someone fight nothing. Area effects land on you from a fight you cannot see, and packs die to damage with no visible source. The interesting part for anyone farming there is the rare spawn behaviour — a rare that appears in the cave is taken immediately, often before the player standing closest to it has a chance to tag, because the people competing for it include everyone in the copies stitched together at that spot rather than the handful you can count on screen.
That turns the den into competition for spawns rather than for nodes, and the two price differently. A stripped ore vein tells you the route is contested and you can move on; a rare that dies out of sight tells you nothing about how long the next wait will be, because you cannot see the group that beat you to it or know which copy they came from. We have not verified how the overlap is produced or which parts of a cave merge and which do not, so treat this as a reported behaviour rather than a rule. An hour planned around a rare in that cave is a bet on conditions you cannot read, which is why gathering and crafting income priced against the economy of Forever is the part of the evening worth planning first.
The follow-up on 7 November went the other way and cost more. The number of copies per zone was cut, and the complaints that came after it were all about density: respawn felt slower relative to the crowd, players queued for named mobs and for ore and herb nodes, and several reported that killing anything contested now meant bringing a group simply to get the tag in before someone else did. None of that is a new mechanic — it is the same zone carrying more people per copy — but it lands directly on income, because a route priced on a quiet world pays a fraction of that when four other gatherers are cycling the same spawns.
The practical reading for a farming plan is that layer counts are a setting, not a constant, and the setting can move between one evening and the next without warning. A route worth keeping is one that still pays when the copy around you is busy: respawn-heavy camps you can clear with a group, gathering lines long enough that a stripped node is not the end of the loop, and crafting or auction income that does not depend on who is standing beside you. Anything budgeted against the economy of Forever should be priced on the contested version of the zone, since that is the state a reduction in copies produces.
The same round of changes also raised spawn rates, but only inside a bracket: the increase to quest objects and gathering nodes was applied to zones up to 30, and nothing above that was reported as touched. In the low-level zones that works as a cushion against a crowded copy — more of the thing you came for, coming back sooner, so a herb loop still pays something when two or three other gatherers are running it in the same direction. The crowding is still there, it just costs less per lap.
Above 30 the cushion is gone and the crowding is not. A copy that has been folded together, or a zone fed by a boat that put the whole deck in one world, puts the same number of gatherers on a route with ordinary spawn density, and the only thing that decides who gets the node is who reaches it first. The practical reading is to treat sub-30 supply as elastic and 30-plus supply as fixed: a route in the upper zones should be priced on the assumption that every competitor in your copy is drawing from the same unchanged pool, and the hour is worth planning against the economy of Forever with that in mind rather than against a quiet lap you had last week.
The part of that change players felt for longer than the visual bugs is density. Packing more characters into fewer copies does not split evenly across activities: anything shared by the group is unaffected, and anything that goes to whoever touches it first gets worse. Ore veins, herbs, chests, quest objects and tagged mobs all belong to one player, so a denser copy turns a route into a race decided by travel speed and who happened to be closer when the node drew in. Gatherers reported the same spots paying less per hour after 6 November without anything changing about the spots themselves — the loot was simply going to someone else before they arrived.
The same density works the other way for anyone grinding mobs instead of picking nodes. More players clearing the same camp pushes it into hyperspawn, where the next pack is up before the last one is looted, and an AoE pull that used to wait on respawn runs continuously. That is why the complaint and the opportunity arrived together: the player cycling a mining loop lost an hour of income to competition, while the player parked on a camp in the same copy gained one. Neither effect is something we can measure, and the density of any given copy changes without notice, so the practical reading is to pick the activity that benefits from a crowd when you land in one, and to price gathering routes against the economy of Forever on contested conditions rather than on the quiet copy you started in.
Once those fixes settled, the complaint inverted. Instead of empty capitals and untouched routes, players reported starting zones carrying 300+ characters at once, capitals with hundreds of people standing between the bank and the auction house, and mobs respawning directly on top of the players already farming them. The copies are fuller than they were in the first days, and the competition that layering was supposed to spread out now sits inside a single copy of the world.
For a gathering or grinding route that changes what an hour is worth. A node you ride toward is more likely to be taken before you land on it, a camp you clear refills with mobs that somebody else is already tagging, and the quiet copy that made a route look profitable in the first week is not what you should be planning against now. The practical response is the same one that applies to collapsing: price the route on a contested copy, keep a second spot in mind for when the first one is crowded, and treat auction-house income as the part of the economy of Forever that does not depend on how many people are standing in your zone. We have not measured how density varies by zone or time of day, so these are player reports rather than figures you can budget against.
For a gatherer that last one is the worst case, because an ore vein you cannot see is an ore vein you cannot route around either — you walk the circuit, find nothing, and have no way to tell an empty mine from a rendering fault. The practical response is the same one that applies to copies being folded together: when a route stops paying for no visible reason, check whether the world around you has been reconfigured before concluding that the zone is farmed out, and judge the hour against the economy of Forever rather than against one bad lap. We have not verified which of these reports were resolved afterwards or how long each lasted, so treat them as what players described on the day rather than standing behaviour.
That has one consequence worth stating before anything else, because it frames every price on this site: copies split the world, not the market. In Classic each realm carried its own economy, and the same stack of herbs could be worth one thing on a full server and something else entirely on a dead one. Forever removes the object those differences were attached to. There is no realm to compare against, no low-population server to buy from, and no transfer to move goods along that gap. Everybody who picked the same ruleset is drawing on one pool of buyers and sellers rather than dozens of separate ones.
So the habit of checking prices elsewhere before listing has no equivalent here, and neither does the whole class of cross-realm arbitrage that older guides treat as a standard trick. What remains is competition inside a single market, where the only lever is timing and what you choose to supply — which is the ground the economy of Forever is written on. One caveat stays open: nobody has published whether the auction house is shared across copies of the world, or across rulesets at all, so one ruleset, one market is the honest framing and one game, one market is not.
Unconfirmed. Players testing on the beta say the PvE and the PvP ruleset post into the same auction house, so a listing made under one ruleset shows up for buyers under the other. We have not checked this from two rulesets at the same time, and Blizzard has published nothing on it, so treat it as a claim going around the testers rather than a rule to build a plan on.
It is worth holding in mind anyway, because of what it would mean if it turns out to be right. The people you race for a node are the ones in your own copy of the world, and that stays true either way. What changes is who sets the price of what you carry out: under a shared auction house, every gatherer in both rulesets is feeding one pool of listings, so a quiet farming route does not translate into a quiet market. You would be competing for ore with a handful of players and competing for buyers with everybody, which is the part that decides what an hour of gathering is worth across the economy of Forever. If the rulesets turn out to be separate markets, the second half of that pressure disappears and supply stays local to your ruleset.
The forums have been arguing a different arrangement for the same problem, and the thread count on it is rising rather than settling. The request is to drop copies of the world entirely and bring back named realms, but with the auction house kept common across them. The reasoning is economic rather than nostalgic: a realm that empties out still has a working market if its listings sit in the same pool as everybody else's, so the thing that usually kills a quiet server — nothing to buy, nobody to sell to — stops being fatal. People making that case tend to frame layers as the cost of fixing crowding and a shared market as the part worth keeping from it.
The standard reply in those threads is that the old arrangement already exists and is still running: the Classic realms work the way they always did, with a realm list to choose from and a market attached to each one. Whether that answers the request or dodges it depends on who is posting. Nothing has been said by Blizzard about changing how Forever handles either side of this, so it is a discussion between players and not a signal about the design. For our part we have not verified on the beta whether listings are shared between copies of the world, and until somebody checks it from two copies at the same time, that stays an open question rather than a fact to plan around when reading the economy of Forever.
There is a second open question behind that one, and it is about geography rather than copies. On the beta everybody testing a ruleset is in one world, with no regional split of any kind, and players from different continents end up standing in the same zones. A recurring expectation on the forums is that this will not survive launch — that separate worlds per region will follow, for latency reasons if nothing else. Blizzard has published nothing about regional worlds, so that expectation is a player reading of how previous versions were run and not an announcement.
One part of this has been addressed by the developers rather than guessed at. In a podcast appearance they described how placement works for players outside the main regions: someone playing from Oceania can be put into the same world as North American players, while separate Australian servers also exist. Which of the two you end up in is not something you set once and forget. When a group forms, the system picks one of the worlds for that group, so the people you queue with decide where you play for as long as you are together.
Placement is not stable once you are in, either, and that is the part that touches farming directly. Beta testers report being moved to another copy of the world roughly every 30 minutes, often without warning and sometimes into a copy that is close to empty. For a solo gatherer that is mostly neutral, and occasionally good: fewer people on your route. For two players running the same route together it is the opposite, because one of them can be pulled out mid-circuit and the pair has to sort out how to get back into one world before they can share anything they find.
A bug on top of that makes the sorting harder. Players report that joining a group does not always move them to the copy their friends are in, so the party is formed on paper while everybody still stands in a different world. The workarounds people pass around are a relog or walking into another zone, and both are reported to work often enough to be the first thing to try. The developers have asked testers to check the manual side of this rather than only the automatic one: when a blue system message offers to move you, use the Update now button and report whether the transfer actually lands you where the group is. None of this is settled behaviour, so plan a shared farming session on the assumption that you will be separated at least once and that the tools for fixing it are still being tested, which is worth remembering before building an hour of gathering into any plan drawn from the economy of Forever.
There is a step in that process people miss, and it costs whole evenings. Joining a group does not move you into the group's copy of the world by itself. The invite goes through, the names appear in the party frame, and you are still standing in whichever copy you logged into. The move is a manual action: an arrow appears in the chat window, and you have to click it. Until somebody does, the party is spread across 2 or more copies of the same zone, which is why you can be told a node is up and see nothing but bare ground where it should be.
It shows up most clearly in the two situations where it hurts: farming a route together and meeting to hand something over. In the first, every member who skipped the arrow is gathering their own copy's nodes, so the route looks far richer than it is and the split at the end does not match what anyone expected. In the second, two players can stand on the same coordinates, call out the same landmark, and never open a trade window, because they are not in the same copy at all. The habit worth building is simple: after joining, click the arrow, then confirm you can actually see the other characters standing next to you before anybody starts running.
The other thing to plan around is that the game can move you between copies of the world on its own, and it does not do it silently. A notice goes up with a countdown attached, so you get a warning before the move rather than after it. What the countdown does not do is wait for you: when it runs out you are placed in another copy of the same zone, with the same character and the same bags, but with different players around you and different nodes already picked.
That is survivable for anything short and ruinous for anything long. An escort quest that depends on an NPC walking a set path, a gathering loop built around the respawn order of a circuit, a group slowly working across a zone together — all of these are chains that assume nothing underneath them changes for the next stretch of time. A move breaks the chain at whatever point it happens, and the usual outcome is restarting the escort or finding that the first half of your route is now someone else's. When the notice appears, the cheap response is to finish the current step and park, rather than to start the next long one; the cost of a broken chain is counted in the time it took to set up, which is the same way everything else gets measured across the economy of Forever.
The same boundary appears to run through the chat channels, which is the part that catches sellers rather than gatherers. Players testing on the beta report that trade and general are scoped to the copy of the world you are standing in: a line posted in trade reaches the people in your copy and nobody else. We have not confirmed this from 2 copies at the same time and Blizzard has published nothing on it, so treat it as a player observation. If it holds, it means a shout for a buyer, an enchant, a summon or a crafting order is addressed to a fraction of the ruleset rather than all of it, and silence after posting says little about actual demand.
That splits the two halves of selling apart. An auction listing sits in a pool that at minimum covers everybody in your ruleset, while anything sold by direct contact — services, bulk handovers, anything negotiated in whispers — only finds a buyer inside one copy of the world. The practical consequence is that goods which depend on chat to move are worth repeating over a longer stretch of time, and that grouping with somebody and clicking through to their copy is also a way of changing which audience hears you. It is a smaller version of the same question that runs through the economy of Forever: how wide the market for a given item actually is, and whether the answer is the ruleset or the copy you happen to be in.
Unconfirmed. A forum summary going around before launch counts the worlds on offer as 9 PvE, 9 PvP, 4 RP-PvP and 3 RP, with 1 Australian world inside each of those rulesets, and reports that part of the US PvE side was already marked full. Blizzard has published no such list, we have not counted it ourselves, and the numbers in a post like that go stale the moment anything is opened or closed, so treat it as a player tally rather than a published structure.
What it is useful for is scale, not precision. If the split is roughly that shape, the PvE and PvP rulesets carry most of the population and the RP side carries a fraction of it, which is the number that matters when you are deciding what to supply: a smaller ruleset means fewer gatherers racing you for the same nodes and fewer buyers for whatever you carry out. The Australian worlds sit inside the same rulesets rather than beside them, so they are a placement question of the kind described above and not a separate set of rules. How any of this maps onto listings stays the open question running through the economy of Forever, since nobody has shown whether those worlds share an auction house.
The first 24 hours after launch turned the crowding argument on its head. The complaint in the forums and on the subreddit was not queues or packed starting zones but the opposite: players describing quiet leveling routes, an Ironforge that felt half-furnished, and a trade chat that went minutes between lines. Blizzard acknowledged that layering had been set aggressively to absorb the opening rush and said the numbers would be adjusted during scheduled downtime. No figures were published for what the setting was or what it was moved to, so the only thing on record is the direction of the change and the fact that it is being tuned rather than fixed.
That is worth reading as a market problem and not just an atmosphere one. An empty copy of the world is a quiet farming route, which sounds like an advantage until you try to sell: the same emptiness shows up as a trade chat nobody is reading and fewer people searching the auction house in the hours you happen to be listing. Node competition and buyer demand move together here, and a thin layer trims both sides at once — which is the trade-off behind every timing decision in the economy of Forever.
The standing answer in those threads is social rather than technical. Being in a guild, or in a party with people you want to play beside, pulls members into the same copy of the world, so the fix for a dead layer is usually a group invite rather than a relog. That also means the density you farm in is partly a choice: run solo and you take whatever copy you are placed in, run with a group and you concentrate yourself, the competition and the buyers in one place.
The same logic has a side that gets less attention, and it shows up in the first days rather than later. A thin copy of the world is pleasant to gather in: nodes stand where they spawned, the respawn timer is yours alone, and a route you would have had to share runs clean. The cost arrives when you try to turn that into gold. Trade chat in a quiet copy goes long stretches with nothing in it, nobody is shouting for the materials you just pulled, and the people who would have bought a stack off you directly are standing in some other copy of the zone. An empty layer converts an hour of gathering into stock, not into coin, and the two are not the same thing when you are trying to fund a mount or a crafting push.
How much that matters depends on the question running through this whole topic. If listings are pooled across copies of the world, then only the direct side of selling dries up — trade chat, whispers, filling a group for an instance — and the auction house still carries your goods to buyers you never see. If each copy keeps its own pool, a quiet layer is quiet on both ends and the stack sits until you move. Nobody has checked this from two copies at the same time, so the practical reading is the cautious one: treat a sparse layer as good time to gather and plan to list when you are somewhere busier, which is the same timing problem that runs through the economy of Forever.
Launch, 5 November. The opening day produced the opposite of the problem layers exist to solve. Copies of the world came up thinly populated rather than packed: starting zones were quiet, and players described running a mining route and taking node after node without anyone contesting one of them. Blizzard addressed it and said the figures behind layer population were being corrected, so the sparse version of the world is not the one the design is aiming at.
That is worth holding on to as an example rather than as a grievance, because it is the clearest demonstration of what this guide is about. Nothing changed in the zones themselves — the same veins, the same respawn behaviour, the same route. What changed was how many people the system placed beside you, and that alone decided whether ore was something you raced for or something you simply picked up. The practical reading: an easy first day of gathering is not a baseline to plan against, and a route that felt generous while copies were thin can tighten considerably once the setting is tuned, which is the supply side of the economy of Forever.
There is one setting Blizzard has asked people to check on their own, separately from any of the placement questions above: Preferred Language. It is not a client text option in the way it reads. It feeds into which copy of the world you are put in, so it decides what language the players standing next to you are most likely to be speaking while you run a route. The request was to open it and confirm it says what you expect before you start playing, rather than to assume the default is correct.
The reason that request exists is worth repeating plainly: players reported the setting had moved to French on its own, without them touching it. Nobody has explained why, and we have not reproduced it, so the honest version is that it happened to some accounts and the cause is unpublished. The practical effect is small but real for anyone selling rather than only gathering — competition for nodes is the same whoever is beside you, but trade chat, whispers and the usual back-and-forth over a price all get slower when the people reading them work in another language. Checking the setting costs nothing and the alternative is finding out after you have already picked a farming spot.
The framing that matters on day one is that launch runs on a single megaserver per ruleset rather than a list of realms. Everybody who picked the same ruleset enters one world and gets spread across copies of it, so crowding is handled by adding copies instead of by splitting the population into separate servers with separate markets. That is why the competition questions on this guide are about which copy you land in, and not about which realm you rolled on.
The practical side of a single entry point is the login queue. Players going in on the first days expect to wait before they are placed in a world, and the wait is longest at the usual evening peak in each region. We have no published figures for how long that takes, and anything circulating now is a guess, so plan around the shape of it rather than a number: log in earlier than you intend to play, stay logged in through a session rather than hopping out between tasks, and treat the first hours after a queue clears as the point where the economy of Forever starts moving rather than the moment you first click play.
The launch window is the part of this that gatherers ask about most, and it is also the part nobody has published. The expectation running through the forums is that the opening days will be handled the way crowded launches usually are: more copies of each zone than the game will keep later, plus faster respawn on ore, herbs and quest objects while the starting zones are full. Both of those are player predictions drawn from how previous launches were run, not something Blizzard has described for Forever, so plan around them loosely rather than building a route on them.
If it does play out that way, the effect on competition points in two directions at once and they partly cancel. More copies means fewer players standing between you and any given node, which helps. Faster respawn means the node you just took is back before you finish the loop, which helps more. Against that, every player in the game is in the low zones at the same time, gathering the same copper and the same low herbs, so the thing that gets scarce is not nodes but buyers — supply arrives faster than anyone needs it. The usual consequence is that early gathering pays worst exactly when it is easiest, and the same route is worth more once the crowd has moved on and the extra copies and the extra respawn are gone. That timing question is the one worth reading alongside the economy of Forever before deciding what to stockpile.
For a gathering route that is worth planning around, because it means your competition is not fixed. Join a group and you may be moved into a world with a different set of players in it; leave or regroup later and the choice can land somewhere else again. So a zone that was quiet while you were solo is not guaranteed to stay that way once you are grouped, and a route you tested alone tells you less than it would have on a named realm. The developers did not say how the world is chosen when a group is mixed, and we have not seen that measured, so the mechanism behind the pick stays unstated.
Language works the same way inside that picture: it sorts people, not markets. A Russian-speaking guild recruiting right now is doing it on NA, Horde side, PvP ruleset, with a start date of 4 November — and it keeps professions and crafting inside the roster, so members gather for each other and have guild crafters cover the recipes nobody wants to level twice. None of that places them anywhere separate. They queue, group and farm in the same world as every other NA player on that ruleset, and anything they do list goes into the same pool of buyers.
That is the part worth carrying into trade planning. There are no language realms to move to, so the usual answer — roll where your language is — has nothing to point at. The Preferred Online Language setting exists and feeds into placement, but testers on the beta reported it did not keep a language community together in practice: people who set the same preference still ended up spread across copies of the world, and groups formed across languages anyway. Nobody has published how heavily that setting weighs against the rest of the placement logic, so how much it does for you is unmeasured rather than zero.
For selling, that means the channel and the language you use are a choice you make per trade, not something the server decides for you. Auction listings carry no language at all, so anything you post is read the same way by every buyer in the pool — which is why bulk gathering output and crafted stock are the safest things to move through the economy of Forever without thinking about who is on the other end. Chat trade is where it bites: guild and whisper work in whatever language your roster uses, while zone and trade chat are mixed, and threads on the forums already show people promising to report posts written in a language they do not read. Expect general channels to be an unreliable place to advertise, and keep the deals that need words inside a guild or a contact list where the language is agreed in advance.
The addon side of this says the same thing from a different angle. One of the group-finding addons written for Forever, LFG Forever, filters listed groups by role, by class and by level, and it also carries a filter for finding groups that use a language other than your own. Nobody builds that last filter unless players are running into the problem it solves. It is indirect evidence rather than a measurement, but it points in a clear direction: the sorting by language is felt strongly enough in group finding that a tool exists to work around it.
For a gathering plan that matters because grouping decides which world you are placed in. If language narrows the pool of groups you actually join, it narrows the set of worlds you rotate through, and the people you keep meeting on a route start to repeat. The filter does not change where the goods end up — the listings still go into the same pool of buyers — but it does change who you are racing for a node while you fill the bags.
That is the practical reason rates and prices get read by region and not by language. A language community changes who you talk to, who you run dungeons with and who supplies your crafts, and a guild that handles its own gathering takes a slice of its materials demand out of the open market entirely. It does not create a second price for ore or a second set of listings, because there is nothing for a separate market to attach to — the ruleset is still the unit everything hangs on, which is the frame the economy of Forever is written in. Region is a line the game draws; language is a line players draw across the same world.
It is worth being exact about what you pick at character creation, because the old wording keeps getting reused. There is no realm to choose. You choose a ruleset, and the ruleset is the whole of your world: everyone who made the same choice is in it, with copies underneath used only to keep zones from packing. A realm name used to be the unit that a market, a guild roster and a reputation all hung on. Here that unit is the ruleset, and there is nothing smaller to sit under it — which is why competition for a herb node and competition for a buyer are the same crowd, and why one market per ruleset is the frame to plan in.
That crowd is the reason node respawn has become a standing question on the forums. With no realm list to spread people out, a popular gathering zone fills with players who all picked the same ruleset, and the only thing holding the route together is how fast a mined vein or a picked herb comes back. The questions being asked are specific: whether a respawn timer runs per copy of the world or is shared across copies, whether a copy with more players in it refreshes nodes any faster, and whether being moved into a different copy mid-route resets what you had already cleared.
None of that has been answered in public. Blizzard has published nothing on how node respawn interacts with copies of the world, and the beta reports we have seen are people comparing one route against another rather than measuring anything. So the honest position is that respawn behaviour under layering is unknown, and a route built on an assumption about it — that a quiet copy means faster nodes, or that a crowded one is compensated for — is built on a guess. What is not a guess is the competition itself: the gatherers you race are in your copy, and the buyers you price against sit in the economy of Forever either way.
There is a smaller cost to a forced move that nobody counts until it happens, and it is paid in consumables rather than in time. Anything you put on the ground belongs to the copy of the world you put it in. A campfire, a fish tub, a repair bot — none of them travel with you. When the game pulls you into another copy you arrive next to empty ground, the items are spent, and the engineering gear that dropped the bot goes on its equipment cooldown of 1 hour regardless of whether anybody got to use it.
The usual way this plays out is a group assembling at a dungeon entrance. Somebody drops a repair bot and a cooking fire while the last two players run in, those two get placed in a different copy on the way, and they stand at the same doorway with nothing in front of them. The person who paid for the bot cannot drop a second one for an hour, so the group either repairs later or waits. It is not a large sum on its own, but it is a recurring one for anybody who supplies the stations for a raid night, and it is worth factoring into what those materials cost you rather than treating them as a single purchase.
Some of what this guide describes from the beta has since been changed by Blizzard, and the changes all point the same way: fewer moves between copies of the world, and more control over when they happen. Joining a group no longer drags you across on its own — you get a prompt asking whether to move to the group's copy, and declining leaves you where you are. Forced moves were also tuned down after the beta feedback, so being pulled out of a zone mid-route is described as less frequent than testers reported. Connectivity between adjacent zones is now set by hand rather than left to the system, with Durotar and Orgrimmar named as the example: crossing that boundary is meant to keep you with the same people instead of reshuffling you on the way in.
For a farming route that is the part worth reading twice. A prompt instead of an automatic pull means a gathering run no longer ends because somebody invited you, and fewer forced moves means a cleared circuit is more likely to still be yours when you come back around. What has not changed is the crowd you compete with: the gatherers racing you for a vein are still the ones in your copy, and the buyers you price against still sit in the economy of Forever. One limit was stated outright — copies will not be stretched to hold large PvP gatherings at launch, so a zone that fills up with a mass fight is not going to be given extra room for it. Nothing has been published about how any of this interacts with node respawn, so the open question above stays open.
On forced moves between copies there is at least something on the record. In the sixth developer podcast the team said that by the end of the beta the number of forced transfers between copies of the world had been cut down considerably: the conditions that trigger a move were loosened, and settings were added that give more control over when one happens. They also said a bug was fixed where players vanished from view after leaving a capital city, which is the same system misfiring rather than a separate problem.
For a farming route that changes the weight of the risk without removing it. A move mid-route is still possible, so the practical habits stay the same — finish the node you are on, expect the gatherers around you to change, and do not plan a circuit that only works if you stay in one copy for the whole loop. What the podcast does not say is how often a transfer happens now, under which conditions exactly, or whether the new settings survive into live in the same form. None of that has been published in numbers, so the part worth carrying into a plan is the direction of the change and not a figure. Where you sell what you gathered is unaffected either way, since buyers sit in the economy of Forever rather than in your copy of the world.
The outer edge of a ruleset is the region. Joining players from different regions into one world is not something the current technology does, so whatever ruleset you pick is bounded by the region you play in rather than spanning all of them. The beta is not evidence against that: it runs as a single test world because it is a test, and players from several continents standing in the same zone there says nothing about how launch will be arranged. What stays unpublished is the inside of the region — whether one region is further split into separate worlds, and on what basis. Until that is stated, assume your competition and your customers are the people who picked the same ruleset in the same region, and nobody further out.
One detail of the client complicates the language picture before you even reach character creation. The Russian client does not offer the Forever rulesets at all, and character names are accepted in Latin characters only. The practical result is that Russian-speaking players come in through the English client or another European one, which means a language setting is not a clean label for who is behind the characters around you.
So when you use the language setting to steer which crowd you farm beside, read it as a rough filter rather than a sorting rule. An English-language world holds people who chose English and people who had no other way in, and the same is true of the other European options. Nothing about this is published as a policy, it is what the client currently allows, and it may change without notice — but while it holds, do not expect the language you pick to tell you much about the players competing for the same nodes.
Forum threads draw a line that this description of copies tends to blur, and it is worth keeping. On Classic Era a layer is a copy of the whole world: you are assigned to one, and you stay in it while you cross zones, so the people around you in Westfall are broadly the people who were around you in Elwynn. What testers describe in Forever works per zone instead — each zone hands out its own copy, and moving between zones means being handed a new one. Same word, different mechanic, and the second one does not keep a stable set of players around you for more than one zone at a time.
Faction balance sits a level above all of this. What Blizzard describes is a ruleset-wide arrangement: the Alliance and Horde populations are weighed against each other for the ruleset as a whole, not for each copy of a zone. Nothing has been published about balancing the two sides inside a single copy, and we have not seen it stated anywhere official. What exists is player reports from the beta, where testers describe copies that felt heavily one-sided while the ruleset as a whole looked even. Treat that as an observation going around the testers rather than a confirmed rule.
If it holds, it matters for the part of this guide about racing other players to a node. A balanced ruleset tells you nothing about who is standing in the zone with you, because the copy you were handed can lean one way and the next copy you get on crossing a border can lean the other. On a contested ruleset that changes the risk on a route from one zone to the next, and on any ruleset it changes how many people are working the same spawn points as you. The practical reading is to judge a route by what you see in front of you rather than by the faction split quoted for the ruleset, and to treat a crowded copy as a condition that moving zones may or may not fix. How much that costs an hour of gathering is the same question the economy of Forever deals with everywhere else: supply you can reach, and how many others can reach it.
Unconfirmed. Alongside that, testers report a promise that the worst of the forced moves will be addressed by launch: being handed a new copy while riding a boat, a zeppelin or a flight path, and the same thing happening on the approach to a capital city. Those are the two cases players complain about most, because both interrupt you while you are not in control of your character. We have not seen a primary source for it — no patch note, no post — so it is a second-hand account of what is planned rather than a change you can count on being there on day one.
What nobody has claimed, in that account or anywhere else, is anything about zone borders. If each zone hands out its own copy, then crossing from one zone into the next is a reassignment by design and not a fault to be fixed, and the transport cases are the exception rather than the rule being withdrawn. For a farming route that distinction matters more than the transport fix does: a loop that crosses a border every few minutes is the one exposed to it, and planning around which copy you gather in is part of reading the economy of Forever. Until a first-hand source says otherwise, treat borders as unchanged.
Two things move you between copies, and both of them matter if you gather for a living. The first is a zone border. Crossing one hands you a copy of the zone you are entering, chosen at that moment, so a route that runs Hillsbrad into Alterac is not one continuous world but two assignments in a row. The practical effect is that a zone you just emptied of ore tells you nothing about the next one: the players you outran are behind the border with the copy you left, and the copy waiting on the other side has its own set of gatherers who have been working it for however long. A loop that returns to the first zone gets a fresh assignment on the way back as well, which is why nodes sometimes look untouched on a second pass and stripped on a third.
The second trigger is a group invite. Accepting one can pull you into the copy the party leader is standing in, which is the intended behaviour — it is how a group ends up in the same world at the same time — but it fires whether or not you wanted to move. A gatherer who accepts an invite mid-route is handed a new copy of the zone and loses whatever respawn timing was being tracked, and the same applies when somebody invites you while you are standing on a node. Declining until a run is finished is the only control there is. We have not tested whether leaving the group puts you back where you started, and nothing has been published on it, so treat the move as one-way until somebody checks it. What does not change either way is who you sell to: assignments shuffle the crowd around a node, not the pool of buyers that the economy of Forever runs on.
The practical half of that, as players on the beta describe it, is that gathering nodes belong to the copy rather than to the zone. A vein you can see is a vein the people in your copy can see, and the ones standing in the same spot in another copy are looking at their own set. That is why a route can feel empty and still be contested: the crowd you are racing is only the crowd you can actually see, and it changes when you cross into the next zone and are handed a new copy.
The same testers report that respawn does not appear to track how many people are nearby — a busy copy and a quiet one seem to bring nodes back on the same rhythm, so a heavily farmed area simply stays stripped longer. We have not timed this ourselves, and Blizzard has published nothing on how node respawn is handled, so treat it as a player observation rather than a mechanic to plan a route around. If it holds, the lever that matters is route length and where you start, not finding a quiet copy, which is the part worth carrying into the economy of Forever.
The clearest report of that mechanic comes from a beta stress test, where a large group tried to move through a zone together. Testers describe the raid being split across several copies on entry, with no way to step over to the copy their group members were standing in: there is no join option, and relogging moved people around unpredictably rather than putting them back with the rest. Some got placed correctly on the first try, others cycled through several attempts and ended up somewhere else again. Nothing here is a published rule — it is what players saw during one test — but it matches the per-zone description above, and it is the part of layering that hurts most when a lot of people want to be in one spot at once.
The request that came out of those threads is narrow rather than a call to scrap the system: turn copies off when a crowd forms on purpose, so a raid, a world boss attempt or an organised event lands everyone in the same instance of the zone, and leave the splitting in place for ordinary open-world traffic. Blizzard has said nothing about it, and we have no way to tell whether grouping behaviour is final or a known gap in the test build. For farming it has a practical edge: if you plan around meeting someone at a spawn, assume you may not end up in the same copy, and that the quickest fix players have found is leaving the zone and coming back rather than relogging in place. That uncertainty is worth factoring in before treating a group route as a reliable way to work the economy of Forever.
The stress test on 21 October is the clearest public look we have at how that assignment behaves under load. With roughly 1000 players online, the recurring complaint was that Stormwind and Elwynn were unplayable: nodes and quest mobs taken on sight, and the city itself slow enough that testers logged out rather than push through it. That is a small number of players for a capital zone, which is the part worth noticing — the crowding people reported was not a headcount problem by itself.
The other half of the reports points at distribution. Testers described very uneven placement across copies of the world: some players standing alone in a zone with nothing contested, others dropped into the crowd that produced the complaints above, with no visible reason for the difference and no way to choose. If that behaviour carries over, then two gatherers running the same route at the same hour are not doing the same job, and neither of them knows in advance which version they got. It is the practical reason a farming plan cannot be judged by one session, and it feeds straight into how the economy of Forever prices what gets gathered. This was a test rather than live service, so treat it as a description of what went wrong once, not a rule about launch.
From the beta. Testers report that the number of copies running at once is high even in the capitals, so a city that should be busy can look close to empty. Two behaviours come up repeatedly alongside that. The first is a timer: players describe being moved out of the copy they are standing in roughly every 30 minutes, without doing anything to trigger it. The second is the zone border — crossing one often drops you into a copy with nobody in it, rather than into the crowd you could see a moment earlier. None of this is documented by Blizzard, and beta behaviour is not a promise about launch, so treat it as what testers are seeing rather than a rule.
If it holds, it has two practical effects on gathering. Competition for a node is thinner than the player count suggests, because the people chasing the same ore are only the ones in your copy at that moment, and that set keeps being reshuffled. Grouping is the harder half: a party assembled to farm together can be split by the timer or by the first zone border it crosses, so plan on re-forming rather than on staying put, and expect a route worked solo to be the easier thing to keep stable. The pricing side is unchanged by any of it, since the economy of Forever runs on one pool of listings regardless of which copy you gathered in.
A third proposal keeps coming back in the same threads, and it is the opposite of the current arrangement rather than a variation on it. The request there is for named realms with no copies of the world running underneath them at all: a fixed set of neighbours, population drift handled by quiet merges instead of transfers, and layering switched on only when traffic actually spikes — launch evening, the first hours of a content patch, a world event that pulls everybody into one zone. The argument is that crowding is a problem for a few days at a time, not a permanent condition, and that running copies of the world continuously costs more in stable competition than it saves in queue time.
For a farming route the difference is concrete. Under that model the people racing you for a node would be the same people most days, which makes a route something you can learn and defend, and contested nodes would cluster into the peak windows where layers are on rather than spreading across every hour. Under the current arrangement there is no such stability to learn, which is why timing and supply choice carry so much of the weight in the economy of Forever. Blizzard has said nothing about merges, named realms or peak-only layering in Forever, so this stays a player proposal and not a direction, and it is listed here because the argument is about competition for nodes rather than nostalgia.
Being moved to another copy of the world is not free, and the cost is easiest to read as gold rather than as inconvenience. The move fires when the group changes — somebody joins, somebody leaves, and the world around you is swapped for a different one mid-route. What you had already killed stays behind: corpses you had not looted yet are gone along with what was on them, and the time you spent clearing to them is gone with them. On a route where the drops matter more than the kills, that is the whole value of the last few minutes wiped in one step.
A fight in progress is the expensive version. A quest mob you were part way through resets in the copy you left, at full health, while your character arrives in the new one with whatever health was left and whatever was chasing you unaccounted for. Dying there adds the run back to your body and a repair bill on top of the lost loot, and the quest still has to be done from the start. The practical habit is simple enough: do not accept or drop a group invite while you are pulling, and finish the pack before you sort out who is in the party. It is a small discipline, but it is the one place where layering takes money out of a farming hour directly rather than through competition, which is the slower drain described across the economy of Forever.
That per-zone handling had a gold consequence, and it is the reason one old habit stopped paying. A fresh copy of a zone comes with a fresh set of world objects, so players worked out that a chest could be looted, the zone left and entered again, and the same chest looted a second time from a different copy. Chest loot was cut in response — the reduction was aimed squarely at that loop, not at the players who open a chest once in passing. What a chest gives out now is small enough that it does not carry a route, and the copies you pass through on the way do not change that.
The knock-on effect lands on the dwarf racial that marks treasure on the minimap. It still works and still shows you chests, but the thing it points at is no longer worth much, so picking dwarf for gold reasons gets you very little back. If you want the race, take it for the other reasons; as a money choice it is close to neutral. The gathering and crafting side is where an hour of play still converts into something, which is the ground the economy of Forever is written on.
The same mechanic shows up in forum complaints from a different direction, and those threads are the clearest evidence that the switch is not purely automatic. The recurring report is from open-world fights: an opponent about to lose drops out of the fight, is gone from the zone for a short while, and comes back at full health with the fight reset. People posting it describe the move as deliberate rather than a disconnect, call it an exploit, and ask either for it to be ruled against or for copies of the world to be dropped entirely. Blizzard has published nothing on either request, and we have not reproduced the move on the beta, so what the complaints establish is the pattern being reported and not the method behind it.
What matters for gathering is the part the complaints assume without arguing it: if a player can leave one copy of a zone and return to another on their own initiative, then the copy you are standing in is at least partly a choice. That cuts straight across node competition. A route that is crowded in your copy is not necessarily crowded in the next one, and a gatherer who can trigger the switch does not have to wait out a competitor on a herb circuit — they step sideways instead. Whether the move is reliable, how long it takes, and whether it survives launch are all open, which is why we treat it as a reported behaviour rather than a technique to build an hour of farming on in the economy of Forever.
The triggers players keep listing are mundane ones: walking into a city, stepping off a boat or zeppelin, joining a group, and crossing any zone border — reportedly including while in combat, which is the complaint that comes up most often. For a farming route the practical effect is that the crowd you are racing for nodes resets every time the route leaves a zone, so a circuit that felt empty on one lap can be contested on the next without anybody having logged in or out. Plan a route as a sequence of separate zone-level contests rather than one shared world, and treat the people you see as the current occupants of that zone copy only. None of this changes who buys your stack at the end, which still comes down to one market per ruleset.
Two reported behaviours move you between copies without you asking, and both of them land on gatherers. The first is grouping: leaving a party does not only reseat the player who left, it also moves the group leader to a different copy. So a 2-person herb run that ends with somebody logging off leaves both of them somewhere other than where they were farming, with a fresh set of neighbours and a node layout nobody has walked yet. The second is geography. Zones are not all held on the same copy, and crossing a border can hand you a different one — players have described it moving between Dalaran and Silverpine Forest, and between Tirisfal Glades and the Ruins of Lordaeron. A route that loops across a zone line is therefore not one continuous farm but a sequence of separate ones, and the stretch you cleared 10 minutes ago behind you says nothing about what is standing there when you come back around.
Plan routes to sit inside a single zone where the gathering supports it, and treat every border crossing as a reset of who you are competing with rather than a continuation. Developer Tim Jones has called the layering system work in progress in a podcast, so the specific triggers above are what players are seeing now and not a settled design — worth re-testing on your own route rather than building a fixed circuit on, especially if the hourly value of that circuit is what you are measuring against the economy of Forever.
The copies also get in the way of the simplest thing two players do together, which is hand each other an item. Beta reports describe groups forming and then finding themselves in different copies of the world, with trade windows out of reach because the other character is not standing anywhere you can see, and with attempts to post the goods instead running into problems of their own. Nobody has published what governs this — whether grouping pulls members into one copy, how long that takes, or which of the reported mail failures are deliberate and which are bugs being worked through before launch. Treat the current behaviour as unfinished rather than as the shipped rule.
The wording is worth fixing, because the two arrangements behave differently. Sharding cuts a single zone into pieces that appear and dissolve as the crowd moves, so the players around you change while you stay where you are. Forever runs the other one: a ruleset carries 1 realm, and that realm is kept as several parallel copies of the whole world. You belong to a layer rather than to a fragment of the field you are standing in, and you keep that layer until something moves you off it.
The reason players care about which copy they are in is rarely abstract. On the forums the example that comes up first is Black Lotus: the spawn points are few, they are contested, and a picked node is gone for everyone standing in that copy of the world. The argument runs that if a player can move to another copy, the same spawn point is untouched again, and the same logic is applied to rare mobs with long respawn timers and to chests on fixed routes. Nobody has published how moving between copies is triggered, how often it is possible, or whether anything limits it, so the discussion is about what players expect to be able to do rather than about a described mechanic.
That scenario shows up again in the proposal for separate PvP copies of the world. The people asking for it name hopping between copies to reach unfarmed high-value herbs and rare spawns as one of the things such a split would have to restrict, on the grounds that contested spawn points stop being contested if the contest can be left behind. Neither the proposal nor any restriction attached to it has been confirmed by Blizzard, and it is worth reading alongside how a single ruleset market prices goods that only a handful of nodes produce.
That description is disputed, and the dispute is worth carrying rather than resolving. Players testing the beta report being moved to a different set of neighbours at points where nothing about their position changed much: stepping off a boat or a zeppelin, and in some reports simply walking across a zone border. If that is what the system does on every transition, it behaves less like a layer you belong to and more like the retail arrangement, where the crowd around you is assembled when you arrive and taken apart when you leave. The two readings are not compatible, and nobody has published which one is correct.
The practical difference is who you are competing with. A stable copy means the gatherers working your route are the same people hour after hour, so you can learn their timing and work around it, and so the supply reaching a single ruleset market comes from a crowd you can at least picture. Re-phasing at every border means the competition on a circuit that crosses zones is a fresh draw each lap, and a quiet node run tells you nothing about the next one. Until somebody tests it deliberately — two characters, one transition, checking whether they still see each other — treat route planning that assumes a fixed set of rivals as the weaker assumption of the two.
The beta complaints are about those moments. Players report being pulled onto another copy when crossing a zone boundary, again when walking through a capital city gate, and again when accepting a group invite — the last one landing at the worst possible time, since the invite is usually sent precisely so that two people can farm or trade together. For a gatherer the practical effect is that a route planned around known spawns can finish in a world where the nodes were already taken by somebody you never saw. Nobody has published what triggers these moves or how often they fire, so the sound approach is to treat every zone and city transition as a point where your surroundings may be replaced, and to keep any chain that depends on uninterrupted farming short, which is the plain version of gold making in Forever.
It matters for anything that depends on moving materials between characters: a gatherer feeding a crafter, a guild bank run, a split between two accounts in the same household. If the handoff cannot be assumed to work on demand, the sensible arrangement is to keep the chain short and finish on one character wherever possible, which is the plainer way to approach how gold actually gets made in the first weeks. Whether regional worlds appear after launch is still unanswered, and if they do, the same handoff question returns in a different shape — so it is worth retesting rather than assuming the beta behaviour carries over.
What does exist at character creation is a language preference, and it is worth knowing exactly what it offers before you assume it will sort you into a crowd that matches you. On North America the listed choices are English, Brazilian Portuguese and Latin American Spanish. French is not among them. A French-speaking player on North America therefore picks one of the three listed options like everybody else, and whatever grouping the setting produces, it is not going to be a French-speaking one on that side.
The limits of the setting are also unpublished. Nobody has shown whether the preference is a hard condition for placement into a copy of the world or only a hint applied when several copies are available, and nobody has shown what happens when the preferred group is thin at a given hour. The practical reading is that language narrows who you are likely to farm beside rather than guaranteeing it, so treat it as one more input into how gold actually gets made and not as a way to pick your competition.
There is one regional split that has been spoken about rather than guessed at: local sharding for Oceanic players is said to be coming at release, so an Oceanic character would normally be placed in a copy of the world held nearby instead of sharing one with North America. Nothing has been published about how many copies that means, which zones it covers, or whether it applies to every ruleset, so the shape of it stays unknown until it is live and somebody checks it.
Two situations are described as pulling an Oceanic character onto a North American copy anyway. The first is grouping with North American players, where the party has to end up somewhere and that somewhere is their side. The second is battlegrounds, which draw from the wider pool rather than from the local one. Both are worth knowing if you gather between queues, because a route planned around a quiet local copy is not the route you come back to after a battleground, and the competition on a node can change without you having moved — which is the same timing problem that runs through how gold actually gets made in the opening weeks.
One consequence of a single world is worth stating plainly, because it is easy to miss until it has already cost you a circuit: North American and European players are drawing on the same pool, and the day and night cycle runs on one schedule for all of them. There is no separate European clock shifting the quiet hours around to suit a second region. What changes with the timezone is not the world but who is awake in it, so a route run during a European evening is shared with a different set of people than the same route run during a North American one.
A separate line of complaint on the forums points the same mechanic in a different direction. The claim is that copies of the world and placement without a realm list make automated gathering harder to notice: there is no fixed server population to recognise names in, the character undercutting your herbs may never be standing in the zone you are standing in, and the usual way players built a mental list of who farms what stops working. Some posts go further and say the arrangement is convenient for whoever runs those routes rather than merely tolerable. None of this has been confirmed by anybody with data, and we have not tested it ourselves, so treat it as a player reading of the system and not as a described behaviour of it.
The second half of the same complaint is about the PvP ruleset, where posters describe being placed into a different copy mid-fight, or an opponent dropping out of view and reappearing elsewhere, and read that as something being used deliberately rather than a placement rule doing its job. What governs placement during combat has not been published, so the difference between an exploit and ordinary behaviour cannot be settled from the outside. For a gatherer the practical part is narrower: if a contested route sometimes empties or fills without explanation, the hour you picked may not be the reason, which is worth allowing for when planning how gold actually gets made on that ruleset.
For gathering that cuts both ways, and which side dominates depends on what you do with the output. The hours when one continent is mostly asleep are the hours with fewer riders on the same spawns, which is the part the gathering professions gain from directly; they are also the hours with fewer people watching listings, which matters if you sell the moment you dismount rather than posting and waiting. The usual handling is to separate the two actions: gather when the field is thin, list when the market is awake. How much that is worth in practice is not something anybody can quote, since nothing has been published about how the population divides between regions or whether launch keeps the world single, so treat it as a shape to test against how gold actually gets made rather than as a rule.
Inside a copy of the world the contest for a spot is settled by a rule that predates all of this: mobs are tagged exclusively, and the first hit claims the kill and its loot. Two players riding into the same camp are not splitting it. Whoever lands the opening attack owns that mob outright, and the other one gets nothing from it, no matter how much damage follows. On a farm built around mob drops — leather, cloth, elemental materials — that turns a crowded spawn into a race measured in the time it takes to get an instant ability off, not into a shared route that two people can run politely side by side.
Two things follow for route planning. First, a contested mob camp is worse than a contested herb field, because a node you lose costs you one pickup while a camp you share can cost you most of a respawn cycle to a faster opener. Second, the practical answer is movement rather than confrontation: when somebody is already working a camp, the cheaper decision is usually to take the next point on the circuit and come back, which is why loops with several stops hold up better than a single rich spot. That is the same logic the gathering professions run on, applied to things that fight back.
Quest mobs are where that rule is felt first, and the complaints from testing are blunt about it. Players describe standing at named or objective spawns with something like 15 others doing the same thing, everybody waiting for the next appearance so they can get an opening ability off. Exclusive tagging does not turn that crowd into a shared kill. One person takes the mob, the rest wait for the respawn, and the queue reforms. A copy of the world is supposed to keep zones from packing, but it does nothing about the fact that everybody levelling at the same pace needs the same few spawns in the same week.
The other half of the complaint is that you do not stay where you planned to be. Testers describe being moved between copies of the world without asking for it and without warning, in the middle of a run, and the objection is not that the move is slow but that it makes a route impossible to plan. You pick a quest chain and a set of contested outdoor spots because the copy you are standing in is thin at that hour; the move resets that assumption, and the circuit you laid out for the next 2 hours is now based on a crowd you have never seen.
What follows immediately after a move is the tag fight. You land at the same coordinates with the same cooldowns, except the camp is already being worked by people who were there before you, and exclusive tagging means the mobs in front of you belong to whoever opens first. The same thing happens in reverse to them. Nobody has published what triggers these moves, how often they happen or whether a player can refuse one, so the only handling available is structural: keep the loop long enough that losing one stop is survivable, and treat any single rich camp as a spot you may be removed from mid-run. That is the conservative way to build a farming route that holds up when the ground under it is not stable.
For a farming route the damage is indirect but real: the hours you spend in a tag queue are hours not spent on a gathering circuit, and the mobs you do land come at a rate set by the crowd rather than by the respawn timer. The usual handling is to treat contested quest spawns as a scheduling problem — clear them when the zone is thin, keep the rest of the session on routes where supply is not rationed by who clicks first, and accept that early zones stay crowded until the levelling wave moves on. Nobody has published how many copies of a zone run at once or whether that number responds to crowding, so how long any particular bottleneck lasts is not something to plan around. What holds is the shape of the fix: fewer contested tags per hour, more time on the parts of how gold actually gets made that nobody has to queue for.
The two outcomes pull prices in opposite directions. If the launch world stays single, every seller in a ruleset feeds one order book, undercutting is continuous, and the only advantages left are timing and supplying something few people bother to gather. If the world is split by region, each region carries its own prices again, the same stack can be worth different amounts in each, and comparing them becomes possible while moving goods between them probably does not — which restores the old habit of reading another market without restoring the profit from it. Either way the raw supply arrives from the same place, so it is worth planning around the gathering professions first and treating the market structure as the part that may change under you.
It is worth being concrete about which habits lose their object when the realm list goes away. A guide written for Classic assumes there is a second market to look at, and that assumption is what does not carry over:
- Comparing the same stack on a busy realm and a quiet one, then listing where it reads higher.
- Buying cheap somewhere thin and paying for a transfer to move the goods to a richer market.
- Running a second account on another realm to hold stock for a market that behaves differently.
- Treating a price database built from many realms as a reference for what your own listing should say.
None of those have a target here, because there is no second auction house to compare against and no transfer to carry anything between two of them. What is left is one order book per ruleset, with every seller in it undercutting the same list, so the questions that still pay are when you list and what you chose to gather rather than where you sell — which is the part of what creates and destroys gold that layering does not touch at all. The open question stays the same one stated above: whether the auction house is shared across copies of the world has not been published, so the single market described here is a market per ruleset as far as anybody can show, and not a claim about the whole game.
For a questing player this is a convenience and nothing more. For anybody making money from the world it is the ground the whole route stands on, because nodes respawn per copy, not per player. A herb that appears every few minutes appears every few minutes for the whole layer, however many gatherers are circling it.
That is the arithmetic nobody puts in a gold guide: your yield per hour is not a property of your route. It is a property of your route divided by everybody else running it in the same copy of the world, and you cannot see how many that is before you set off.
Density and income pull against each other here, and there is no in-game workaround for it. A mob can be tagged and the credit shared; a herb, a vein or a world chest cannot be split between two people who reach it in the same second, and we have found nothing saying Forever changes that. Everything a gathering route is built on is a single-claim object, so the second person to arrive is paid nothing for the travel time. A copy of the world that feels lively is not the same as a copy that pays: population helps whoever is selling into it and costs whoever is picking things up off the ground.
The pressure lands hardest exactly where routes are tightest. High-density spawn clusters and fixed chest spots are the first thing a new gatherer is told to run, which makes them the first thing every other new gatherer is running too, while the thin stretches between them keep behaving normally because nobody bothers with them. The same logic explains a habit that reads as antisocial and is not: on quests that ask for pickups from nodes rather than drops from mobs, invites get declined, because a party member on the same objective is another claim on the same spawns and, by Blizzard's own known issues entry, an invite can also move somebody into a different copy mid-route. If you are choosing what to level on the strength of a busy zone, it is worth weighing which profession pays consistently against how many people are standing on the same spawns as you.
One forum account puts a shape on that. A player describes Westfall at 6 am: around 100 players around Sentinel Hill, and about 10 circling the oat spawns near Ol Blanchey, at an hour that is supposed to be quiet. The complaint attached to it is not about the crowd itself but about the response to it — new copies of the zone are being opened, and the density in front of the poster does not visibly drop. Several replies ask for the same thing: a way to choose a less crowded copy rather than accept whatever placement hands out.
Two things are worth separating there. The count is one player's impression at one hour in one zone, not a measurement, and we have nothing from Blizzard confirming how many people share a copy or how the decision to open another one is made. What the post does show is the gap between the two numbers that matter to a gatherer: how many copies exist, and how many people are standing on the spawns in yours. Only the second one pays, and it is the one nobody can read from the login screen. For the gathering professions that gap is the whole question, and a starter zone at dawn is where it is easiest to see.
The request those replies keep arriving at is a manual one: a list of the copies of a zone and a button to move to the one you pick. The comparison people reach for is Star Wars: The Old Republic, where instances of a planet are named, counted and switchable from the interface, so a crowded one can be left on purpose rather than waited out. The complaints behind the request are social before they are economic — a guild gathering session that ends with half the roster on spawns nobody else can see, a raid group assembling in a city and finding that the people standing at the stone are not all in the same world, a friend invited along as the only way to reach the same copy. Blizzard has published nothing about a copy selector, a named list, or any player-side control over placement, so this is a feature players are asking for and not one that has been described.
The objection raised in the same threads is the one worth keeping if you gather for money. A chosen copy does not stay quiet: the moment placement can be picked, the empty copy is the one everybody picks, and the names circulating in chat as the quiet option are the ones that stop being quiet first. Manual selection moves the pressure rather than removing it, because the nodes in any single copy still pay only the first person to reach them, and a copy that fills up by choice fills up faster than one that fills up by placement. Both sides of that argument are player reasoning about a system that does not exist yet, which is why it changes nothing about which profession pays consistently today and quite a lot about how a route would have to be read if the control ever shipped.
The ceiling behind that has been moved more than once. On 27 September, Holly Longdale said the population limit on the beta worlds had been raised again, following an earlier increase, and that the queue players were meeting when they tried to log back in after a disconnect was a bug rather than a capacity measure. That one has been fixed. Neither statement came with a number attached, so there is nothing in it to convert into players per copy of a zone.
Read from the route side, a higher limit points one way. More accounts admitted to the same ruleset means more characters placed into copies of the same zones, and a node still pays only the first person to reach it, so the count that matters to a gatherer moves up while the supply on the ground does not. Whether more copies are opened at the same time is the part nobody has described, and it is the difference between a busier world and a busier route. That is also why the raise belongs in any reading of what creates and destroys gold rather than in a list of server statistics.
The version of that problem people are already talking about is organised rather than accidental. Large guild networks coordinate their logins so that members land together, and a few hundred players moving as one block can account for most of the active population in a single copy of a zone. From inside, the effect is not subtle: the same names appear at the same spawns on every circuit, the popular veins are taken before the route reaches them, and the quiet corners of the map are the only parts behaving normally. Nothing about that is against the rules — it is what a guild is for — but it turns node competition from a spread of strangers into a schedule somebody else set.
Two things follow for anyone gathering. First, a copy that feels overfarmed at one hour may be ordinary at another, because a block of coordinated players logs off together as well; a route judged once is not a route measured. Second, the pressure is uneven by node type, since a raid roster preparing consumables works through a narrow list of the gathering professions and leaves the rest alone. We have not seen any published figure for how many players from one guild can be placed in the same copy, or whether placement tries to keep them together at all, so the only honest instruction is to check the field rather than assume it.
Two further things push people together in the opening weeks, and neither is accidental. The PvP ruleset is described as keeping the factions in balance, which means the side that is short of players is the side new characters get steered onto, so a large group of people who rolled the same faction on the same day works through the same narrow set of starting zones at the same time. Streamer communities concentrate in a similar way: an audience that follows one person picks the same ruleset, starts on the same day and logs in on roughly the same schedule, which behaves like the coordinated guild logins above but larger and with no roster anybody can read from inside the game.
The consequence for a route is the same in both cases, because a vein or a herb pays only the first rider to reach it. A zone that is ordinary on paper can hold a crowd that arrived as one block, and the crowd thins out together as well, so a circuit judged on one evening says little about the next. The handling is the one already stated: count the field each lap, keep the thin stretches between popular clusters in the loop, and weigh which profession pays consistently against how many people are standing on the spawns it depends on. Blizzard has published nothing on how faction balance is enforced, or on whether placement tries to spread a single community across copies of a zone, so the shape above is what follows from the mechanics people describe rather than a documented outcome.
Language quietly decides who you farm beside
Placement is not only about load. Blizzard's own description of the ruleset system says players can set a language preference and will encounter others who share it. The setting lives in the game menu under Languages and Social, it applies to the whole account, and it can be changed only once every 24 hours.
On the beta that has already had a visible effect. A player from Brazil describes logging in on the first day, knowing that thousands were online, and finding tens: he had been paired with other Portuguese speakers into a copy of the world that was nearly empty. He could not get out of it by changing the setting, and ended up joining a guild through Discord and asking for a party invite to be pulled somewhere populated.
Read that from the money side
An emptier layer is fewer people competing for the same herbs. It is also fewer people buying what you gather, if the market turns out to be tied to the layer at all — and nobody has said whether it is. Two opposite effects, and which one dominates depends on a mechanic that has not been published.
Being moved in the middle of a route
Layers are not permanent. Players report being moved between copies during play, with a warning before it happens, and being pulled into a group-mate's copy when they join a party. On a levelling character that is a curiosity. On a gathering route it is the difference between a circuit you have half-cleared and a circuit somebody else has half-cleared.
The complaint that follows is always the same shape: a player stands in a spot, the world reshuffles, and the thing they were waiting for is either gone or suddenly there. In open-world PvP the same mechanic ends fights by removing half the participants. Neither is an economy problem on its own, and both add noise to any attempt to measure what a route yields.
The part that decides whether a route can be planned at all is how often this happens, and here the reports are more consistent than the rest. Players describe being moved several times in an hour while alone, inside a single zone, with no party involved and no border crossed — a warning, a short pause, and a different set of people standing on the same spawns. Nobody is offered a destination: the copy you land in is handed out, not picked. Blizzard has published no figure for how often placement is reassessed, and the known issues list names grouping as a trigger and nothing else, so the frequency above is what players say they see rather than a documented interval.
That picture moved with the build of 1 October, which carried a note saying layering had been improved and that players would be moved between copies of the world less often. No interval was attached to it, before or after, so there is nothing in it to convert into moves per hour — only a direction. From the route side the direction is useful: if a copy holds for longer, the competition count taken at the start of a circuit stays valid for more of it, and a thin stretch is more likely to mean a gatherer riding ahead of you than a reshuffle behind you.
The complaints arriving alongside that change point the other way. Players describe mob camps in Redridge with several people standing on the same spawns, trading tags and waiting out respawns on quest objectives. Both things can hold at once: fewer moves means the crowd in front of you is the crowd you keep, because a reshuffle is also what used to thin one out without anybody riding away. Nothing has been published about how the change relates to how many players share a copy, so whether the crowding is a side effect of it or a separate matter of population is unknown — and it is felt first by the gathering professions, where a single-claim node pays only the first person to reach it.
The same pressure lands on quest mobs, and it is worth separating from node competition because the mechanic underneath is different. A mob can be tagged, so the contest is over who lands the first hit rather than who reaches the spot, and that is usually settled before a melee character is in range: a hunter or a caster waiting at distance takes the tag while anybody who had to ride in arrives at a mob somebody else already owns. On a camp with several people standing on it, that is the normal result rather than an occasional loss, and the wait grows by however many respawns go to whoever shoots first.
That matters more the further levelling is pushed out of instances and into the open world. Whatever keeps players questing and grinding on the ground rather than queueing for a dungeon keeps them inside the same copy of the zone, and competition in that copy stops being a question about nodes alone: it becomes a question about tags as well. The two contests overlap on the map, because the camps worth grinding sit in the same stretches as the spawn clusters worth riding, and both are decided by who arrives or fires first.
There is a second reason those camps stay full, and it comes from how people are levelling rather than from placement. Players on the beta describe grinding mobs as the quickest way up, faster than working a quest chain through a zone, and they describe doing it alone, because experience is split in a party and a pair rarely kills fast enough to make up the difference. What that produces inside one copy of the world is a crowd of characters who each want a camp to themselves, so the contest stops being about who lands the first hit on a shared pull and becomes a contest over respawn points: who is standing on the patch of ground when it refills.
That lands on the gathering professions as a third kind of competitor along the same loops. Riders on the same nodes, questers waiting out an objective, and now solo grinders parked on spawn points that sit inside the circuit — and the grinder does not move on when a quest is handed in, because the camp is the whole activity rather than a step in one. The handling does not change: count the field each lap, keep the thin stretches between popular clusters in the loop, and judge which profession pays consistently by what your own laps look like rather than by what a zone looks like on paper. Blizzard has published nothing about experience rates from grinding, party experience, or respawn timers in crowded copies, so the shape above is player description from the beta and not documented behaviour.
Read from the income side, a gatherer loses twice over. The ride between clusters gets slower when every patrol along it is already owned by somebody standing at range, and the people who give up on a jammed camp do not leave — they switch to picking things up, which adds riders to the same circuit a lap later. Neither effect shows as a visible crowd on the spawns themselves, so an hour that reads as ordinary can still pay less than the one before it. The handling is the one used elsewhere here: judge which profession pays consistently by what the field looks like on your own laps, and keep the thin stretches in the loop, since that is where the gathering professions keep working while the popular ground is contested. Nothing has been published about how levelling rewards are weighted between open world and instances in Forever, so the direction above is what follows from the mechanics players describe rather than a documented change.
What players report doing about it is the part that reaches the market. Some abandon the objective and move on, some stop questing in the zone altogether and spend the time gathering instead, which shifts the same crowd off the mob camp and onto the herb and ore spawns around it. That is the connection worth holding: crowding on quest objectives does not stay on quest objectives. It arrives shortly afterwards as more competition for the gathering professions in the same copy of the world, and as raw material listed by people who had not planned to sell any — which is one of the quieter inputs into what creates and destroys gold here. Blizzard has published nothing about tagging rules, shared credit on quest mobs, or respawn timers in crowded copies, so this is player description from the beta rather than documented behaviour.
One forum account puts a count on that shape. A player describes a quest camp with more than 30 players standing on 2 or 3 spawn points, everybody watching the same patch of ground and nobody leaving, because the objective has no alternative location. What follows is respawn sniping rather than questing: the mob appears, the first ranged hit lands before anybody on foot has closed, and the rest of the camp waits for the next one. The same account notes that the people who give up and start gathering instead do not leave the copy of the world — they move 2 spawn clusters over and compete there, which is why the gathering professions feel the crowd shortly after a quest camp jams up.
The second half of that complaint is about placement rather than the camp. The same player reports being moved mid-session into a copy that was more crowded than the one left behind, with no choice offered and no way to go back, so the only response available was to log out and try again later. That is the part worth taking into a route plan: a crowded copy is not something you can ride out of, and a reshuffle is as likely to raise the count on your spawns as to lower it. Nothing has been published about how placement weighs population when it reassigns somebody, so the direction of a move is not something anybody can predict — which is one more reason how gold actually gets made here is written as a sequence of steps rather than an hourly figure.
If that order of magnitude holds, a long loop through a zone will cross at least one reshuffle before it closes, which means the competition count taken at the start is out of date by the time the route comes back round. Two habits follow. Build the circuit in short segments that can be judged on their own, so a thin stretch can be read as a changed copy rather than as a farmer riding ahead of you. And treat a sudden drop or jump in available nodes as information about placement first and about demand second, because the gathering professions are the part of the economy where this noise lands hardest.
Three versions of that come up often enough to plan around. A group crossing a zone border can come out of it split, with one member in a different copy and whatever was being chased or contested left behind on the other side of the line. A camp that was empty on the approach is worked by several people on the next circuit, not because anybody rode in but because the copy around you changed. A zeppelin or boat can arrive carrying a different set of passengers than it left with, since the ride ends in whichever copy you are placed into on arrival rather than the one you boarded from.
The common part matters more than the three cases: the number of people standing on your spawns can change without anybody travelling. We have found nothing from Blizzard listing zone borders or transports as triggers, so these are descriptions of what players report seeing, not an account of the mechanic underneath. The habit that costs nothing is to re-count the competition at the start of each circuit rather than once at the start of the session, and to remember that the same reshuffle changes how many sellers are feeding the same market — which is part of what creates and destroys gold in Forever.
There is a social cost underneath the mechanical one, and it is the part players on the beta keep circling back to. Because the pool of people around you changes when you cross a zone line, walk into a city or step off a boat, no stable circle forms: the gatherer you split a zone with yesterday, the buyer who took a stack off you in person, the stranger who kept turning up on the same spawns — none of them are reliably reachable again without an invite. The request that follows is for placement to keep a cluster of players together over a session rather than reassign them at every transition, so that the same faces stay available long enough to trade with twice. Blizzard has published nothing about persistent placement or about keeping any group of players in one copy, so that is a feature being asked for and not one that has been described.
The shape those requests keep arriving at is stickiness rather than selection. Three parts come up together: the copy you are in stays yours after you leave a party instead of handing you back to automatic placement, it survives a zone border so a loop through two zones ends where it started, and a deliberate jump to a friend replaces the invite-and-drop routine people use now. The first two are asked for because of the social cost above; the third is asked for because an invite is currently the only control anybody has, and it needs a second person to be willing.
The part worth noting is that the players proposing the friend jump also propose a cooldown on it, and they are explicit about why. A jump with no wait attached is a copy selector with extra steps: ride a circuit, jump to a friend standing in another copy, and the same veins and herbs are standing again, with rare spawns and world chests behaving the same way. That is the old multi-copy gathering trick rebuilt out of a social feature, and it would land directly on the gathering professions, where a node pays only the first person to reach it. A wait between jumps leaves the feature useful for meeting people and useless as a route, which is the trade the threads settle on. No length is attached to the suggestion, and Blizzard has published nothing about layer persistence, friend jumps or any cooldown on either, so this is what players are asking for rather than behaviour anybody can plan a circuit around.
The complaint that makes the problem concrete is a small one: 2 new accounts started together, in the same ruleset, with the same language preference, and ended up in different copies of the world with no way to correct it from the settings. One of them had to be pulled across by a party invite, which is the same workaround used everywhere else on this topic. For anyone planning to feed one crafter from two gatherers, that is the case to test before building a schedule on it, since the gathering professions only split a zone usefully when both characters are standing in the same copy of it, and how gold actually gets made here assumes a repeat buyer can be found a second time.
The border between two zones is the spot where players notice placement changing most often, and the description is consistent: ride across the line and the names around you are different ones. The part that gets reported loudest is combat. A fight that began on one side ends the moment one participant crosses, because the other is no longer in the same copy of the world — both are left standing where they were, each on a screen the other cannot see. Nothing is resolved, and the only cost is the time already spent on it.
The same property lands on gathering twice over. A contested node near a border can be settled by crossing the line rather than by riding faster, since the rider who was ahead stops existing from your side; by the same token a node you watched somebody take can be standing again once you are across, with no way to tell whether that is a different copy or a respawn. A pursuit along a route that crosses a seam ends the same way for both parties, so a loop drawn over a border is the hardest one to measure. The handling is the one used elsewhere on this page: judge the spawns well inside a zone, keep contested pickups away from the line, and treat the competition count taken on the approach as covering only part of the lap. Blizzard has published nothing naming zone borders as a trigger, so this is player description from the beta rather than documented behaviour, and it is where the gathering professions run into it first.
The words players use on the current beta build have shifted, and the shift is worth noting because it changes what the reshuffle looks like from the ground. Fewer reports describe whole copies of the world; more describe phasing at the borders between zones. A group riding along a seam loses members in the middle of a fight, the ones who disappear are still standing where they were on their own screens, and the party comes back together once everybody is well inside one zone again. That reads closer to retail sharding, where the split is fluid and follows the player, than to the layer boundaries Classic players learned to plan around, where crossing a border was the moment placement was decided rather than a line you could sit on.
For a route the practical difference is who you are competing with along the edge of the map. If the seam itself is unstable, a circuit that follows a zone line spends part of its time in a copy nobody can count, and a competition tally taken on the approach applies to half the loop at best. Spawns near a border are the ones to judge last, and contested pickups are worth doing away from the line rather than on it, since a fight that ends because the other half of the group blinked out is not a result either side can rely on. Blizzard has published nothing describing sharding, phasing at borders, or how any of that relates to ruleset placement, so this is player observation from the beta and not documented behaviour — which is also why the gathering professions are where the effect will be noticed before it is explained.
One trigger for this is documented rather than inferred. Blizzard's list of known issues states that forming a group, or changing who is in one, can move a player into a different copy of the world. It is listed as a known issue that is being worked on, which means the behaviour is acknowledged and may change, not that it is intended as a feature.
For anyone farming in company that is the whole problem in one line. Two gatherers who split a zone between them are relying on being in the same copy: the nodes they leave for each other only exist once. An invite, a swap, or somebody dropping and rejoining can put one of them somewhere else mid-circuit, and the second half of the route is then being cleared by strangers. It is worth planning group sessions so that the party is assembled before anybody starts moving, and treating any reshuffle as a reason to re-check the route rather than push on. The same caution applies to the gathering professions when two accounts are meant to feed one crafter.
Chat and placement do not cover the same ground, and that gap is where most hand-to-hand deals are made. Players report that the general channel reaches across a cluster of copies rather than the one they are standing in, so an advertisement is read by people who cannot be walked to. The buyer answers, and then nothing happens until somebody sends a party invite: the invite is what pulls the other character into the inviter's copy, and a face-to-face trade needs both of them there. Mail and the auction house sidestep the problem entirely, which is the argument for using them on anything that does not have to change hands in person.
The forced moves come with a prompt rather than a jump. Players describe a warning before placement is reassessed, offering the move now or in 5 minutes, which is enough time to finish a node, close an open trade window or ride somewhere the reshuffle costs nothing. Taking the delay by reflex is the safer habit when a deal is half done and the other party is only reachable through an invite. None of this is documented: Blizzard has published nothing on the reach of chat channels across copies or on the timing of that prompt, so it is player observation from the beta, and it is one more reason how gold actually gets made here is written as a sequence rather than a rate.
The prompt is not the usual case, though, and that is the part worth planning around. Players describe the warning appearing only when a copy of the world is opened or closed, and nothing at all in the situations that come up most often on a route: crossing from one zone into the next, joining a party, leaving one, or simply standing in a crowded spot where placement is reassessed around you. In those cases the move arrives first and the explanation second — the names on the spawns change, and no dialogue was offered.
The cost people report is loot rather than time. A mob killed and not yet looted, a node opened mid-cast, a chest being emptied when the reshuffle lands: the account that comes back is the one where the corpse or the object belongs to the copy you just left, and there is nothing to return to. That turns a reshuffle from noise into a direct loss, and it lands hardest on exactly the single-claim objects the gathering professions are built on, since nobody is paid twice for the same pickup. Two habits reduce the exposure without fixing anything: loot before moving on rather than clearing several mobs and collecting afterwards, and keep the contested pickups away from zone borders, where a transition can take the result with it. Blizzard has published nothing about loot surviving a change of copy, so this is player description from the beta and not documented behaviour.
Three variants of that loss come up often enough to name, and all of them are about something already found rather than something missed. A reassessment can land while a character is standing at the node with the cast started, so the herb or vein stays in the copy behind and the time spent reaching it pays nothing. A party that disbands at the end of a shared session can leave its members in different copies, which ends the split-zone arrangement without anybody riding away: the second gatherer is no longer on the same spawns, and getting back next to them means asking for an invite again. And a buff handed out near a zone line can lose its target mid-cast, because the other character is placed elsewhere the moment the border is crossed.
Those are complaints rather than figures. Players writing about placement on the official forum describe the three cases above as things that happened to them, with no count of how often and no statement from Blizzard about whether a cast, a party or a pending buff is meant to survive a change of copy. Treated as a planning input, they point the same way as everything else on this part of the route: finish the pickup before accepting a move prompt, disband in town rather than in the field, and keep anything that needs two characters standing together away from borders, since that is where the gathering professions lose work that was already done.
Because grouping moves people, access to a particular copy of the world has started being sold. On the beta, trade chat carried advertisements offering an invite into a named layer for a flat fee in gold, a few coins per pull, paid by whoever wanted out of the copy they were placed in. The service is nothing more than a party invite and a drop afterwards, which is why the asking price sits at pocket change rather than anything a farmer would think about. It is worth being clear about what is unproven here: we have no confirmation that the invite reliably lands the buyer in the copy that was advertised, and no way to tell one copy from another by name from inside the game, so the buyer is trusting a description they cannot check.
The same players describe the reverse happening for free and without warning. Crossing from one zone into the next can drop a character into a different copy depending on how full the destination is, so a route planned as a loop through two zones can end in a copy with a different set of gatherers on it. That makes paid placement a short-lived thing by nature: whatever is bought at the moment of the invite is only held until the next border, transport or reshuffle. Blizzard has published nothing about placement being sold, priced or intended to be chosen, and nothing about population thresholds behind zone transitions, so both halves of this are player reports from the beta rather than described behaviour — which is the usual footing for anything about how gold actually gets made here.
The status of that entry matters as much as its content. It sits on the known issues list, which is Blizzard saying the behaviour is not what they want and that a fix is coming. No date has been attached to it, so the honest reading is: this is how grouping works for now, and it may stop working this way without any warning that reaches a patch note first. Anything you build around it — a habit of inviting a partner to pull them into your copy, a session that assumes the party will stay together — should be treated as temporary rather than as a rule of the game.
The practical cost lands on the gatherer, not on the party leader. A circuit that has been half-cleared has no value to the person who cleared it and full value to whoever arrives next, so every reshuffle mid-route is work handed to a stranger. Two things reduce the exposure: assemble the group before the first node, and do the swapping in town rather than in the field. Neither is a fix, and we have found nothing describing what happens to a route when the fix lands — whether placement becomes stable for the whole session or simply changes trigger. That uncertainty is part of why the gold plan we publish is written as an order of operations instead of an hourly figure.
The old trick, and whether it still works
In earlier layered versions of Classic, moving between copies was used to gather the same node more than once: farm it here, change copy, find it standing again. It was the single most economically significant thing layering ever did, and it is the reason experienced players watch this system rather than shrug at it.
Whether any of that is possible in Forever is unknown. Placement here looks automatic rather than player-driven, and we have found nothing describing a reliable way to choose a copy on purpose. We are not going to write a method we cannot verify, and we would not write one anyway — but the question is live, and the answer will show up in the price of raw materials before it shows up in a patch note.
A player on the official forum has asked, in passing, whether the game might deliberately put suspected farmers into the same copy. That is speculation by a poster, not a feature anybody has described. We note it because it is the right question, not because it is true.
What nobody has published
This page is unusually short on numbers, and that is not modesty. Almost nothing about layering has been quantified:
- How many players share a copy of a zone, at launch or later.
- How often placement changes, and what triggers it beyond grouping.
- Whether the auction house is shared across copies, or across rulesets at all.
- Whether node respawn rates were tuned for the bigger populations a megaserver implies.
Until those exist, every gold-per-hour figure written about Forever is a figure from a different game. The plan we publish deliberately talks about order of operations rather than rates, and this is one of the reasons.
The fourth item on that list is the one players keep raising on their own. Threads on the beta forum ask whether herb and ore respawn timers will be shortened before launch, on the reasoning that a copy of a starter zone in opening week holds more gatherers than any single realm did, and that a timer tuned for the older population pays only the first few riders on a circuit. No reply from Blizzard appears in those threads, and nothing has been published about respawn rates being retuned for a megaserver, so the timers people are measuring on the beta are the only ones anybody can plan against today.
The expectation behind the question is a launch crush rather than a steady state: everybody starts in the same handful of low-level zones on the same day, and that is exactly where the spawn clusters are tightest. Two readings follow, and both are worth holding. If the timers are left as they are, the first weeks are the worst case for anyone building income from the gathering professions, and the thin stretches between popular clusters are where a route keeps paying. If they are raised, the extra supply lands at the same moment demand is highest, which affects prices as much as yield. Neither has been confirmed, so the honest instruction is to measure the field in the first days rather than carry over a figure from the beta.
The build of 1 October is the only published movement on the second item in that list. Its note says layering was improved and that players are moved between copies of the world less often, which names a direction without naming an interval, before or after. It does not say what still triggers a move, how many copies of a zone run at once, or how many people share one, so nothing above drops off the list because of it.
What changes for a route is small and still worth taking: if a copy holds for longer, the competition count taken at the start of a circuit stays usable for more of it, and a thin stretch is more likely to mean somebody riding ahead of you than a reshuffle behind you. Until the rest is described, the working rule stays the same — count the field each lap, and treat that count as the number most likely to move under the gathering professions.
Our reading: layering is the largest unmeasured variable in Forever's economy. It sits underneath gathering, which sits underneath everything else. The supply side is where it will show up first: if copies are busier than the old realms were, raw materials get scarcer per farmer and prices hold; if placement spreads people thin, the opposite. Both are plausible today.
Questions
What is a layer in WoW Forever?
A copy of the world. Forever has no realms: everybody plays in one space, and the game quietly keeps several copies of each zone running so that no copy is overcrowded. You are placed in one of them, and the players you can see are the players in the same copy.
Does my layer change how much I can farm?
Yes, and it is the most direct effect layering has on money. Herbs and veins respawn per copy of the world, not per player. A copy with more gatherers in it gives each of them less, and you have no way to see how busy yours is before you ride out.
Can I choose my layer?
Not directly. You can set a language preference, which Blizzard says is used to put you with players who share it. It is account-wide and can only be changed once every 24 hours, so it is a lever you pull slowly rather than a switch you flip when a zone feels crowded.
Is the auction house shared between layers?
Nobody has said. It is one of the open questions players are asking on the official forum, and it matters more than it sounds: if the market is shared, your layer decides what you can gather but not what you can sell it for.
Sources
- Rulesets, placement and the language preference with its 24-hour cooldown — Blizzard's own article, Choose Your Ruleset in World of Warcraft: Forever, September 21, 2026.
- The near-empty layer on the first day — one player's account on the official Forever forum, September 2026.
- Node density per copy, and the question about the auction house across rulesets — player discussion on the official Forever forum. Players, not Blizzard.