I just experienced the most peculiar bug where I and everyone else that was on could not get past these invisible barriers that prevented access to the area where the world boss was going to spawn. I’ve never experienced this bug before but apparently there are reports of this happening going as far back as the Beta! WTH is this even???
This is a problem with the servers. Usually it only happens when the servers go down and the clients are still running because spaghetti code game. But it does happen from time to time when the servers are chugging. I really was excited for diablo’s free open world in this game but these kind of issues absolutely kill it. It’s just like sometimes when chests spawn and your character struggles to get away from the chest, or when you ride a horse and it just moves at a snail pace because the game is struggling to load.
It’s really awful and makes me miss the way diablo 3 and diablo 2 did things
1 Like
but they wanna sell cosmetics at ridic prices!!!
Every time my horse stutters it makes me want to throw my computer out the window but then I remember it’s got nothing to do with things on my end and it makes me want to sue Blizzard instead coz surely using a vaunted IP as cover for this 
show of a game has got to be illegal!
I know it’s not the same people that created D2 who work at Blizzard anymore but, my god, did they really not retain even an ounce of institutional knowledge? It’s beyond amateur hour over at 16215 Alton Pkwy, Irvine, CA!
Why does the horse stutter from zone to zone? it’s really weird.
Because they had the bright idea to make transitions between different zones “seamless” aka without a loading screen. However, it seems that their technology isn’t capable of handling it so instead of a loading screen we get to bear witness to the glorious stuttering while everything loads. In short it’s because hubris met incompetence.
So when my horse is running at full clip then starts running on the stop I’m getting a loading screen anyways?
1 Like
its not invisible wall. its lag once the horse move from one map to another.
7 months and blizzard still didn’t fix this annoying issue.
The zones are handled by many different servers and when you move between zones you may connect to another server. The stutter is caused by switching servers.
That’s why you may experience extreme lag in one zone, but be completely fine in another. If a certain zone’s server goes down or is unresponsive, then you get blocked outside the zone like what happened to OP.
2 Likes
Its because you don’t load any other zones until you get there, and the game has to load the phase that you’re in which means any other players that are currently in that phase, the monsters, the loot thats dropping for YOU from things THEY are killing. All while you’re trying to run Mach 10 on your horse
the multiplayer aspect of the open world is what causes a lot of problems.
Just what Zolmation and others have said.
Just this morning going to the World Boss - Dry Steppes actually - I was in a rather uncommonly large group riding to it.
I wasn’t partied, just happened to be in the presence of 5 other Players heading the same way.
When I “Transitioned” into the World Boss Zone - I was alone.
No sign of those 5 other players and the only Yellow dots I saw were Players arriving behind me.
I was the “first” to arrive at the WB.
I think what must be happening is that whatever their architecture is for ‘Instances’ - It’s trying to, erroneously, place Players into a Full Instance.
It’s like the ones encountering the error have been flagged for X instance - but it’s FULL - and the server isn’t reassigning them to Y or Z instance like it should.
Basically. It’s more complex than that but essentially that’s what it comes down too. I don’t know of any game any that has the infrastructure to handle truly seamless loading, idk why Blizzard thought they could do it but they clearly can’t.
This is an ongoing issue for the last week. I had it in the past 3 or 4 days and i posted about it.
well you can click to buy or NOT click to buy. yer choice.?