|
![[image loading]](http://i.imgur.com/RJhl95H.jpg)
Through the 3.10.1 patch, Cactus Valley has been modified. But there are some problems. First, look at the gif picture comparing the previous version to the current version of Cactus Valley.
+ Show Spoiler +
Picture 1 : + Show Spoiler +
The width of the paths are different from the other because of the changed the position of expansions. In this case, the position of 3, 6, 9, 12 o'clock may be disadvantageous in fighting troops because of the narrow path. I think it would be more effective if it is changed the terrain behind the resources.
Picture 2 : + Show Spoiler +
The places where the textures are modified are too awkward. Texture work in the Cactus Valley is not symmetric, but it seems to have occurred by modifying the texture with symmetry.
The reason I write this is because I was very disappointed with a few things. If dev team modifies the ladder maps used by people around the world, I think it should be more complete.
Of course, it's good to be quick to deal with the Liberator issues in the Cactus Valley, but it's disappointing that simply moving the expansion location.
I hope to make a more appropriate revision.
|
Oh wow.
Looking at the new base positions, there's going to be absolutely zero room to move once a base is down, and those textures are absolutely atrocious. I wonder how they look in game.
|
That, plus the fps lock/drops issues, it really feels like blizzard want to rush their patches and don't care that much ...
Not sure if I'm the only one feeling that way
|
here we go again, all aboard the drama train
|
The textures are really not a problem. The space behind the expansions helps to defend against liberators (if it is not a cliff).
The path is really not an issue, there is enough space and you can attack from three sides. Also it helps protoss and terran build a wall or cover the space.
It would be nice for a change, if we play some games on the new map before we complain. If problems occur, blizzard will fix it as usual.
|
Blizzard never had any quality control for maps and never will get some.
The new base location makes holding this base close to impossible if your opponent spawns counter clockwise or opposite. If the base is placed, your opponent only need to hold the two very small choke-points close to his base while hes harassing the base. two liberators can easily prevent any army movement along this route. Or three(?) force fields. It is really awkward.
|
On February 01 2017 21:40 Meavis wrote:
here we go again, all aboard the drama train
Waah no one should ever criticize Blizzard for any of their shortcomings Waaah
|
On February 03 2017 00:15 Turi wrote:
Blizzard never had any quality control for maps and never will get some.
The new base location makes holding this base close to impossible if your opponent spawns counter clockwise or opposite. If the base is placed, your opponent only need to hold the two very small choke-points close to his base while hes harassing the base. two liberators can easily prevent any army movement along this route. Or three(?) force fields. It is really awkward.
I tried making a stink when they did the same thing to my map Galactic Process, hoping they would see what my problem was with how they handled it, and try to improve their methods, for future instances of changing a community map. The response I got was very reasonable, and in the end promised more communication between Blizzard and the mapmakers going forward. A change like what was done here looks like something they did quickly in response to a problem, which is fine, but I think it should still be followed up by having the mapmaker, Ferisii, go over it and refine the map to both his and Blizzard's liking.
If they leave the map as-is without cleaning it up and making it more presentable, that would tell me they're not listening. And the change they made to the expansion addresses one problem, but introduces another, the attacker's advantage on that expansion is just too big now, that shouldn't have made it through. It introduces what's probably an even bigger imbalance in close spawn positions.
|
|
|
those random texture circles xD
|
It really does feel as if the map department at Blizzard is just one guy who doesn't actually care.
|
Elentos
55594 Posts
I don't get... like... It's one thing to fix the map to account for liberators. But what's with those texture changes?
|
On February 03 2017 06:45 Elentos wrote:
I don't get... like... It's one thing to fix the map to account for liberators. But what's with those texture changes?
Looks like a 12 year old who made their first map and is so excited to share it they don't realize it's shit
|
Thanks for the work Jacky, hopefully they fix it in time
|
lol those random circles. It's like some dude went to photoshop and randomly dabbed some colours with the brush tool.
Blizzard are never good with maps, hardly a surprise.
|
|
|
Those random removed texture circles. Looks awful. Makes me wonder why the mapmaker did it. But judging from the atrocious state of blizzard mapmaking and blizzard's complete lack of care about their maps since forever, it's probably some exploited intern.
|
|
|
Those droplets all over the map happened to me when trying to rush remaking a map I lost after a hard drive failure. I don't know exactly why the texture spattering (random dots/circles everywhere) happened but it was at some point between re-texturing the map after changing the symmetry and moving geysers and mineral lines with symmetry, but in my case it looked far worse than it does here. If it's from a similar bug I'd guess they went back over most of the textures but missed the dots still there? I ended up painting my map over completely several times and still missed some spots before discarding the whole thing but never really asked about it, I figured I just clicked a wrong setting and mussed it all up myself.
|
That was quick... I wonder what made them make those changes in the first place.
|
|
|
|
|
|
EPT![[image loading]](http://i.imgur.com/huTb2IV.gif)
![[image loading]](http://i.imgur.com/7AtS1Dl.gif)
![[image loading]](http://i.imgur.com/pdclekQ.gif)
