I really hope they dont do what they did to thousand needles with Ungoro...Ungoro is one of my most favorite zones.
I really hope they dont do what they did to thousand needles with Ungoro...Ungoro is one of my most favorite zones.
That's actually the most credible explanation.
Because Un'goro is below sea level.
Blizzard copy+pasted the silithus map segment into the scenario and then either layed in a basic water level to cover the borders of silithus and didn't bother with un'goro, as no one would see it, or the copy+pasted segment of the map came with water and they didn't bother to cut the water out of un'goro.
You can see a similar thing if you get to the shore of sholazar in isle of conquest. The water level of the ocean continues right on into sholazar basin and fills it up.
Exploring around outside map boundaries turns up things like this quite often. most of the time maps will have no water outside of where you're supposed to go.
Ergo, there's no lore reason. It's just a time-saving maneuver from Blizzard.
“Do not lose time on daily trivialities. Do not dwell on petty detail. For all of these things melt away and drift apart within the obscure traffic of time. Live well and live broadly. You are alive and living now. Now is the envy of all of the dead.” ~ Emily3, World of Tomorrow
Words to live by.
No, no it is now
A. why does the water spill into silithus?
also that area on the map is not water on the live client...
- - - Updated - - -
this does seem possible as the water area in uldum is dry because it is above sea level
but it doesent explain why the water goes so high up into silithus
They didn't edit it. That's why it's under water.
Like I explained: to make the scenario, Blizzard needs to take part of the map and drop it into a blank map. So they copy a huge square chunk of silithus and drop it into a new map. WITHIN that giant copied chunk of silithus is part of un'goro, part of uldum, and part of the ocean bordering silithus on the western side. This wasn't intentional or meaningful, it just got caught up in the ctrl+copy.
Silithus has an ocean around it. So Blizzard dropped in a flat sea level to comprise that ocean within the scenario. But BECAUSE un'goro is BELOW sea level normally, the sea level they dropped in covers it.
But because Un'goro isn't to be seen in the scenario, they didn't bother removing the water from it in the scenario map.
Because that ramp up into silithus is below sea level and very likely will not be reachable in the scenario.
That's all that matters here. It's literally a copy paste of silithus and a little bit of un'goro that got caught in the copy paste.
“Do not lose time on daily trivialities. Do not dwell on petty detail. For all of these things melt away and drift apart within the obscure traffic of time. Live well and live broadly. You are alive and living now. Now is the envy of all of the dead.” ~ Emily3, World of Tomorrow
Words to live by.
Last edited by Velerios; 2017-10-20 at 10:13 AM.
Considering that the location was only used for a scenario, it might simply have been easier to remove that portion of the map than to try and load in a bunch of extra assets. Also this is just the minimap texture, which means anything not meant to be seen by players didn't really need to be included in the render.