no matter how many times Blizzard says that there will be no layering past Phase 1, we still get nonsense threads like this.
That is my entire point. If we are having layering until phase 2, why would you bother saying that they will layer “if large groups of players cluster in an area” . If they are already layering entire continents due to overall server population, why redundantly state that they will layer if people cluster in one area?
I’m not sure. I only figured they meant for the launch surge. I’ll take a look at the question again.
Here is the entire comment from the AMA (which I think you may be over-analyzing here)
“We’re not releasing specific numbers, that will likely change dramatically. Based on the response we got from name reservations, we’re anticipating large player populations for some realms initially. This may change as players switch to lower population realms. We’ll use layers to help improve performance in the short-term if large groups of players cluster in an area. We hope to reduce the use of layering over time as people spread out in each realm.”
Considering they are talking about initial high pops, and reducing it as people spread out, it is probably that they will implement a lot of layers at first to aid the starting zones and then those will be less necessary as people move to other zones. Makes sense and seems to be in line with everything they have said about layering thus far.
Here, I found a much larger explanation on layering that included this, which just reaffirms what I was saying:
"We’ve seen some confusion about layering, both about how it helps support our launch, and how it’s supposed to behave while its active, so I’d like to both speak to it and clear up some misconceptions about it.
First, we’re absolutely committed to reducing to one layer per realm before our second content phase goes live, and the sooner we can get there, the better. The reason we can’t do that initially is that on launch day, everybody will be clustered in the starting zones, and having players so close together causes an exponential drain on server resources. In fact, the same number of players cause more server problems crammed into Northshire than they do spread across all of Elwynn Forest. We expect that even after the first couple of days, we’ll need fewer layers than we need for the initial hours of launch, and our stress tests have confirmed that expectation." - Pazoraxm AMA r/classicwow
And for those curious, here is the entire comment:
"I’m so glad you asked this question.
We’ve seen some confusion about layering, both about how it helps support our launch, and how it’s supposed to behave while its active, so I’d like to both speak to it and clear up some misconceptions about it.
First, we’re absolutely committed to reducing to one layer per realm before our second content phase goes live, and the sooner we can get there, the better. The reason we can’t do that initially is that on launch day, everybody will be clustered in the starting zones, and having players so close together causes an exponential drain on server resources. In fact, the same number of players cause more server problems crammed into Northshire than they do spread across all of Elwynn Forest. We expect that even after the first couple of days, we’ll need fewer layers than we need for the initial hours of launch, and our stress tests have confirmed that expectation.
A related concern that was raised during our pre-launch test was that capital cities felt empty, but that only occurred because we left the pre-launch test running two days past its original end date, and we didn’t reduce the number of layers at all during that test. During our launch week, as the players spread out across the world, we’ll monitor activity and reduce layers as necessary, so the world continues to feel full.
Some players have suggested using sharding in low level zones to address launch demand, both because we talked about that at Blizzcon, and because it’s what they’re used to from our modern expansions. Unfortunately, while modern WoW has content designed to work with sharding, WoW Classic does not. The most obvious example of incompatible content is Rexxar’s famously long patrol path, but there are lots of other examples throughout WoW Classic. Since we want all that content to work as it was originally designed, we’ve made sure that every layer is a copy of the entire world, so you can kite Anachronos all the way to Orgrimmar, and you can ride the boat from Ratchet to Booty Bay with the same people alongside you the whole way.
Some players have asked us to use realm caps and login queues to handle the demand, and while those are tools we have at our disposal, we don’t want to rely on them exclusively, because they keep people from playing the game.
One of the most frequently reported problems during our tests was players transferring to a layer for what seemed like no reason. There were several bugs that caused this, and we’re confident we’ve fixed them. At this point, the only thing that should cause you to change layers is accepting an invite from a player on another layer. Additionally, it should always transfer the player who was invited to the layer of the player who invited them.
Nonetheless, after accepting an invite, the layer transfer doesn’t always happen immediately, because we don’t want to transfer you in the middle of combat, or before you get a chance to loot. During our pre-launch test, we saw a few reports of what seemed like random layer transfers, but when we investigated, we realized this was due to us making that transfer delay too long. The delay was so long that players could unintentionally chain one delay into another by starting combat immediately after looting. Because of those reports, we’ve fixed the transfer delay to give you enough time to loot, without being so long that you’re left wondering why you can’t join your friend. We’ll keep an eye on that, and we may decide to reduce it further.
We’ve also seen reports of people transferring suddenly at the entrances to capital cities, which was related to the transfer delays. If you’re waiting to transfer to your friend’s layer, and you enter a capital city, we ignore the delay and transfer you immediately. The long delays were making it more likely that you’d enter a capital with a transfer pending, and now that we’ve reduced the transfer delay, it will be a bit more clear that your transfer was the result of accepting a group invitation.
Regarding PvP, we saw many posts from players wondering if getting invited to a party is a good way to escape from PvP combat. I’m pleased to say there’s actually a separate, longer transfer delay following any PvP combat. We know a lot of world PvP enthusiasts are excited for WoW Classic, and we don’t want the additional layers to feel like they’re robbing you of your kills. When the time comes to withdraw from the fight, you’ll have to escape from your enemies and get to a safe place before you’re able to join your friends on another layer.
I’d also like to clarify how multiple layers work with logout. Early in our stress testing, players reported that logging out and back in would let you hop to a new layer to farm the same mineral or herb node on different layers. That was a bug, and we’ve fixed it. Your layer assignment now persists for a few minutes between logouts, long enough that by the time the game would choose a new layer for you, that node would have respawned on its own anyway.
I hope that all makes things a bit more clear."
Knowledge is power friend. Please read the rest of the AMA
essentially its mostly for places where a mass amount of characters play.
Because there were multiple people answering the AMA. There’s bound to be some redundancy. In fact, I noticed it a few times when I was reading through it.
It is 100% sharding. Blizzard was never going to budge on sharding. We are all fooling ourselves if we think it is going away, completely, when phase 2 starts. Just saying…
1 Like
Don’t get your hopes up. Just because they turn off general layering starting with Phase 2 doesn’t mean that they won’t turn it on again as needed. If an area starts becoming unplayable due to many players swarming then it will make sense to turn on layering to better manage the stability of the game. Playability trumps all.
did you even read the entire layering essay?
[Q: My understanding is that layering is mainly a tool to alleviate the playing experience in overcrowded zones, not to fill up servers “infinitely” to avoid queues. Could you reiterate and clarify this and your current intentions and plans with layering, server caps and handling population at launch and in the future now that you’ve had the chance to study and tweak it during the stress test?
A: I’m so glad you asked this question.
We’ve seen some confusion about layering, both about how it helps support our launch, and how it’s supposed to behave while its active, so I’d like to both speak to it and clear up some misconceptions about it.
First, we’re absolutely committed to reducing to one layer per realm before our second content phase goes live, and the sooner we can get there, the better. The reason we can’t do that initially is that on launch day, everybody will be clustered in the starting zones, and having players so close together causes an exponential drain on server resources. In fact, the same number of players cause more server problems crammed into Northshire than they do spread across all of Elwynn Forest. We expect that even after the first couple of days, we’ll need fewer layers than we need for the initial hours of launch, and our stress tests have confirmed that expectation.
A related concern that was raised during our pre-launch test was that capital cities felt empty, but that only occurred because we left the pre-launch test running two days past its original end date, and we didn’t reduce the number of layers at all during that test. During our launch week, as the players spread out across the world, we’ll monitor activity and reduce layers as necessary, so the world continues to feel full.
Some players have suggested using sharding in low level zones to address launch demand, both because we talked about that at Blizzcon, and because it’s what they’re used to from our modern expansions. Unfortunately, while modern WoW has content designed to work with sharding, WoW Classic does not. The most obvious example of incompatible content is Rexxar’s famously long patrol path, but there are lots of other examples throughout WoW Classic. Since we want all that content to work as it was originally designed, we’ve made sure that every layer is a copy of the entire world, so you can kite Anachronos all the way to Orgrimmar, and you can ride the boat from Ratchet to Booty Bay with the same people alongside you the whole way.
Some players have asked us to use realm caps and login queues to handle the demand, and while those are tools we have at our disposal, we don’t want to rely on them exclusively, because they keep people from playing the game.
One of the most frequently reported problems during our tests was players transferring to a layer for what seemed like no reason. There were several bugs that caused this, and we’re confident we’ve fixed them. At this point, the only thing that should cause you to change layers is accepting an invite from a player on another layer. Additionally, it should always transfer the player who was invited to the layer of the player who invited them.
Nonetheless, after accepting an invite, the layer transfer doesn’t always happen immediately, because we don’t want to transfer you in the middle of combat, or before you get a chance to loot. During our pre-launch test, we saw a few reports of what seemed like random layer transfers, but when we investigated, we realized this was due to us making that transfer delay too long. The delay was so long that players could unintentionally chain one delay into another by starting combat immediately after looting. Because of those reports, we’ve fixed the transfer delay to give you enough time to loot, without being so long that you’re left wondering why you can’t join your friend. We’ll keep an eye on that, and we may decide to reduce it further.
We’ve also seen reports of people transferring suddenly at the entrances to capital cities, which was related to the transfer delays. If you’re waiting to transfer to your friend’s layer, and you enter a capital city, we ignore the delay and transfer you immediately. The long delays were making it more likely that you’d enter a capital with a transfer pending, and now that we’ve reduced the transfer delay, it will be a bit more clear that your transfer was the result of accepting a group invitation.
Regarding PvP, we saw many posts from players wondering if getting invited to a party is a good way to escape from PvP combat. I’m pleased to say there’s actually a separate, longer transfer delay following any PvP combat. We know a lot of world PvP enthusiasts are excited for WoW Classic, and we don’t want the additional layers to feel like they’re robbing you of your kills. When the time comes to withdraw from the fight, you’ll have to escape from your enemies and get to a safe place before you’re able to join your friends on another layer.
I’d also like to clarify how multiple layers work with logout. Early in our stress testing, players reported that logging out and back in would let you hop to a new layer to farm the same mineral or herb node on different layers. That was a bug, and we’ve fixed it. Your layer assignment now persists for a few minutes between logouts, long enough that by the time the game would choose a new layer for you, that node would have respawned on its own anyway.
I hope that all makes things a bit more clear.
AQ opening of the gates !!!
I called it. Where’s my pony ?
That is the same response they gave on retail to the RP community.
It’s off until it’s on and is used for crowd control.
They probably did, they just fundamentally believe Blizz lies all of the time. That sounds like a horrible state of mind to be in, and probably says more about them than Blizzard.
2 Likes
Actually it would be “turned off” not “gone”.
But if they automate it with a threshold then you will get phased just like on retail.
And nothing Blizz has said implies that that will be the case. Now you’re just looking for something to complain about.
Ikr
absolutely committed
Thats the way the said it. All servers must be balanced and have no layers before phase 2.
Ie long phase 1
Is it westfall chickens?
The AMA made it pretty clear that they intend to remove it by phase 2 and really do expect it to only be a short-term thing. They stated they are ready and able to launch new servers to spread out the population if/when necessary.
This isn’t scary at all, let’s not cherry pick and fearmonger.
There are many things in this world that are scary.
Short-term layering technology in a nearly 15 year old game isn’t exactly among the top contenders.
1 Like
How did you interpret that to be “complaining” ?
No where did they say they would use layering during the opening of AQ. Stop spreading your conspiracies and read the AMA