Exploiting layering to 'reset' a boss over & over?

I know a guy, who has a friend, who is definitely not me, and got caught within minutes abusing a glitch (solo’ing BT on a BC server) on a Pserver, no less. I find it hard to believe Blizz doesn’t monitor their servers as well as a Pserver does, but then again… it’s Blundering Blizz we’re talking about.

1 Like

Most likely they already plan to lower the online player cap at the same time as eliminating layers. They probably already have some magic number in mind that they’re aiming for and if the number of players on a given realm doesn’t organically reduce down to that number or close enough to it by phase two then Blizzard flips the layer/cap switch and suddenly there is a queue because they’re not planning to allow so many people online at one time that the remaining single layer world suffers from severe overcrowding.

I play on Atiesh and even though we’ve had nary a queue since the second day of launch I still routinely feel like leveling zones are overcrowded on a daily basis during prime playing hours.

The point being that layering lets more people online. Without layering, less people will be able to get online and then boom, everyone else goes to queue. So yes, layering impacts queues. Even blizzard said that.

Layering having an impact in dungeons is not something that should be possible. It’s not expected like hopping layers to try to get a resource node.

Dungeons and layering shouldn’t have any connection at all. When you’re in a dungeon, you’re not on a layer. You’re not on EK/Kalimdor at all. If the world server for EK/Kalimdor crashes, the people in dungeons on those continents are unaffected because they are in an instance that is not part of those world instances.

My guess is there’s some bug in the code they hacked together to transform sharding into layering that’s causing people to be moved into the new party leaders version of the instance without having to zone out.

I’m curious if once a group breaks if the party leader that’s not in the instance can hit reset dungeon and get an error about there still being players in their dungeon so that they can’t reset. If so, it seems like you could just have two people outside the dungeon to invite and once everyone moves into the new instance, the last one can reset the dungeon and be able to invite after they clear the other person’s and just repeat.

Blizzard,

If you want to have any of my respect again, after implementing this horribly flawed (people mentioned many reasons it would be abused beforehand), you will need to come down with swift and meaningful punishment to the individuals (probably tens of thousands) who have used this very game, economy, ect breaking abuse of the layering system.

This is huge and really a black eye on my whole classic experience now as flask recipes on my server are under 200g each. If you don’t do something meaningful, ban, suspension, removal of ill gotten gains then this will be a cancer that festers within the community of Classic.

Regards,

Extremely concerned Classic lover.

1 Like

Just lol imagine being you now. Multiple proof posted in thread, just lol at you.

3 Likes

Why would dungeons have layers? Each instance is completely independent from the world and instances run on their own servers. How would you change a layer in the middle of an instance??

If you are taking about zoning out and reseting… that has always been a thing.

Agreed, but why would layering be implemented into dungeon instances. It makes zero sense.

It’s likely because layering is more than just one area, so you’re on the same “layer” even in a dungeon. I guess there’s a “layer” in an instanced dungeon, and you can be on the same layer in that…?

Either way it’s horrendous and unimaginable how it made it this far.

well well well…how does it feel to know you were WRONG? Guild did make over 100k together and it’s all facts and proven now…so what do you have to say for yourself? You most likely are one of the exploiters the way you were deflecting…Next time don’t try to act like other people are so stupid when YOU have no clue what you’re even talking about, sir.

It would take 32 days played only doing it to get the 100k gold.
Ironically farming and resetting SM with a gorup of 5 60 mages is far more rentable and can get the same 100k in 10 days played.

Since ques don’t exist, and never have, of course layering won’t affect them.

But does that affect queues?

And this has what to do with layering ?
Here is how raids should work in Classic (and did originally)
Player #1 goes into MC and kills a boss gets Raid ID 12345
Player #2 goes into MC and kills a boss gets Raid ID 12346
Player #2 invites Player #1 but can’t see them as they are in different raids.
Player #1 gets invited to a fresh MC and all players are given Raid ID 12345 with the same bosses dead.

By trying to fearmonger and blame layering you are instead taking away from the actual bug where player #1 when invited to a new raid is getting a new raid ID. This has 0 to do with layering.

ummmm you are JUST responding to someone who commented on a video where ALL bosses were back up.

I also responded that this is how it SHOULD work and if it’s not that it’s a RAID ID issue not a layering issue.

Raid ID’s appear to work perfectly fine in Retail
Raid IDs appear to work fine in past versions of WoW

hmmmm introduce a new variable - layering which is a Frankenstein monster built upon the roots of sharding and CRZ and suddenly you can layer to reset entire Raids.

But yes lets blame the Raid IDs

2 Likes

Yea there was.
More servers with less max population,
Increase population limit as needed per realm activity.

Any problems in the future with crowded areas? Oh well, deal with it in your own way. Done is done.