Coda 1.0 138x144 Published on NA , EU WCS SEASON 2 LADDER MAP
Didnt realise the map thread for Coda was missing. Oh well here you go. This is actually one of my more standard maps , if not THE MOST standard. Many people said the map resembles Muspelheim by Jacky , while i can agree on the third layout , the map plays out almost entirely different. So shut up and enjoy the pretty pictures i guess , lol.
-Korhal City Dirt Dark -Korhal City Tiles Small -Phaeton Rock rough -Phaeton Rock Cracked -Phaeton Dirt Light -Phaeton Sand Dark -Phaeton Dunes -Phaeton Sand Light
Hm, maybe it seems standart in the starting-bases-layout department, but the overall flow is interesting, there are attack paths that are pretty "disconnected" (depending on rock state) - meaning that it takes a lot of time to get between them. That makes for a good backstab/runby opportunity, but if you play any slow composition (mech/SH), it can be really punishing (which may be seen as a good thing).
One thing: I don't see many places where I would like to engage toss with roach/hydra (being not a SH map, this is the likely fighting composition) - while the map offers plenty routes for harass and flank, the actual fight may be hard to set up, there is no "treacherous" area the toss should be afraid to cross.
On February 26 2015 05:46 opisska wrote: I don't see many places where I would like to engage toss with roach/hydra (being not a SH map, this is the likely fighting composition
On February 26 2015 05:46 opisska wrote: I don't see many places where I would like to engage toss with roach/hydra (being not a SH map, this is the likely fighting composition
Looks like a good muta map to me, actually.
That's actually one thing I never know how to guess from these overviews (and I don't have access to SC2 at my laptop) - how far goes the "flyable" space from the mineral lines at the edge of the map?
If you do that change, taking the forward 3rd as a 4th base is too easy and powerful. You have it as a staging area for attacks MUCH closer to all of their new bases, and the walk distance to cover your old 3base is the closest possible of the choices of 4th. With e.g. a terran wall at the 3rd this is like the easiest way to establish or retake a winning position. You can even build the CC in the main and fly it ezpz. It's important that the ramp to mid be large so that holding that pod is a full time job. Which is unfortunate because it just underscores the lack of any strategic forward positions on this map.
On March 26 2015 11:14 EatThePath wrote: If you do that change, taking the forward 3rd as a 4th base is too easy and powerful. You have it as a staging area for attacks MUCH closer to all of their new bases, and the walk distance to cover your old 3base is the closest possible of the choices of 4th. With e.g. a terran wall at the 3rd this is like the easiest way to establish or retake a winning position. You can even build the CC in the main and fly it ezpz. It's important that the ramp to mid be large so that holding that pod is a full time job. Which is unfortunate because it just underscores the lack of any strategic forward positions on this map.
Your 'issue' with a 'too strong forward fourth' already exists on this map with the central pod fourths. Don't let the large diagonal rocks fool you into thinking they make the base harder to take, as a 3 base army will destroy them in seconds. Once the rocks are down, you are left with essentially the 'problem' you just described. You'd have a fourth that makes for a super close staging point that covers your third, and you can even build the CC at the third and float it to the fourth ezpz. Just saying, the current forward fourth is exactly what you just described.
What this change would do is create a choice in the fourth base, making for more dynamic play. Each fourth would be viable, and each one exposes or defends different paths. Thus, making the map less boring and stuff.
As a side note, I would not consider that base a 'forward third' either. Maybe that was just a misnomer you used to describe the base, but even with Super's idea, the base could not be a reliable third.
I was considering removing the rocks on the center highground, along with the changes superouman suggested. Would make even more interesting the attacker pathways. Do you agree?
Honestly it doesn't even matter, I doubt if it's possible to convince blizz to use a different map file at this point. The current version is almost certainly what's going to be played in every case.
But I do agree with Superouman/Timetwister's suggestions.
On March 26 2015 11:14 EatThePath wrote: If you do that change, taking the forward 3rd as a 4th base is too easy and powerful. You have it as a staging area for attacks MUCH closer to all of their new bases, and the walk distance to cover your old 3base is the closest possible of the choices of 4th. With e.g. a terran wall at the 3rd this is like the easiest way to establish or retake a winning position. You can even build the CC in the main and fly it ezpz. It's important that the ramp to mid be large so that holding that pod is a full time job. Which is unfortunate because it just underscores the lack of any strategic forward positions on this map.
Your 'issue' with a 'too strong forward fourth' already exists on this map with the central pod fourths. Don't let the large diagonal rocks fool you into thinking they make the base harder to take, as a 3 base army will destroy them in seconds. Once the rocks are down, you are left with essentially the 'problem' you just described. You'd have a fourth that makes for a super close staging point that covers your third, and you can even build the CC at the third and float it to the fourth ezpz. Just saying, the current forward fourth is exactly what you just described.
It's not exactly the same at all, lol? And what's with the 'tude, bro?
What this change would do is create a choice in the fourth base, making for more dynamic play. Each fourth would be viable, and each one exposes or defends different paths. Thus, making the map less boring and stuff.
It could definitely use some changes so it's less boring, which is why I actually would rather see a version with your change. However, my observation was to point out that it leads to an imba map imo.
As a side note, I would not consider that base a 'forward third' either. Maybe that was just a misnomer you used to describe the base, but even with Super's idea, the base could not be a reliable third.
Well obv. Just a way of naming it.
To your actual point though, there is a world of difference between the two forward 4th locations. The game would have to be in an already lopsided state for the farther pod to be an "easy" 4th. Once there, it's good for attacking the enemy maincliff base and general center/XNT presence but it's strictly not as good as your own maincliff for attacking the other enemy expansion sites, due to distances. (This is immediately clear from the overview.) It also makes you more vulnerable by stringing you out instead of clumping you up. Moreover, the ground distance to guard your entrances is sooo much longer than if you're at the maincliff 4th.
I like choices of expos though and aggressive expanding and the map needs something to spice it up, so I'd rather have the change than not because I'm not a fan of the map anyway. It's an okay map and all, it's just a mildly improved Daybreak evolution with similar 5th base problems. Conventionally this is a bit anti zerg in a passive macro game but we have SH/spores now instead of BL/spines so mise.
I have already noticed it. If you look at my version , I used a custom cliff which worked flawlessly.I cant believe how much the blizzard "mapmakers" have fucked up. They're just incompetent , I have no faith in them anymore.
On April 07 2015 04:41 IeZaeL wrote: Afaik Echo uses custom textures for the terrain , mine was just a changed cliff texture ( from grey to a orange tint ).
Are you refering to the golden Castanar small tiles? Uvantak told me these are official but hidden textures like nilfheim
I just realized you didn't use space cliffs in the first place. That means some blizz guy intentionally switched them. wat
On April 07 2015 04:35 IeZaeL wrote: I have already noticed it. If you look at my version , I used a custom cliff which worked flawlessly.I cant believe how much the blizzard "mapmakers" have fucked up. They're just incompetent , I have no faith in them anymore.
Did you mail them about that ? Are we going to play Coda and Echo with blatant graphics issues ?
On April 07 2015 05:08 -NegativeZero- wrote: At least the coda cliff problem is only in the LotV version and not the version that's going on ladder soon - hopefully it stays that way...
What kind of twisted pleasure does a mapmaker feel when he creates a map with only 2 closer mineral patches ? You're STARVING on that map, just like on Expedition Lost or Vaani. Seriously, make maps with 3 closer patches at least.
coming in late with this, but i really wanted to say how much i adore the rocks on this map. almost every single time i play i find myself moving my army and wanting the rocks down at some point as well as having to strategically second guess the decision to open them, which imo is perfect rocks function
On June 18 2015 05:10 brickrd wrote: coming in late with this, but i really wanted to say how much i adore the rocks on this map. almost every single time i play i find myself moving my army and wanting the rocks down at some point as well as having to strategically second guess the decision to open them, which imo is perfect rocks function
I agree. And we should relish one of the last solid maps standing in this chaos of a map pool.
EPT![[image loading]](http://i.imgur.com/9SxRDyJ.png)
![[image loading]](http://i.imgur.com/hUpyXix.png)
![[image loading]](http://i.imgur.com/RNuel8l.jpg)
![[image loading]](http://i.imgur.com/b8qvX33.jpg)
![[image loading]](http://i.imgur.com/iX7wptL.jpg)
![[image loading]](http://i.imgur.com/EIbBC0b.jpg)
![[image loading]](http://i.imgur.com/RwTe3ey.jpg)
![[image loading]](http://i.imgur.com/UwJ2Mem.jpg)
![[image loading]](http://i.imgur.com/gPBAh9F.jpg)
![[image loading]](http://i.imgur.com/opSOmmW.jpg)
![[image loading]](http://i.imgur.com/WIsL8nY.jpg)
![[image loading]](http://i.imgur.com/ImJSou8.jpg)
![[image loading]](http://i.imgur.com/pg10LiL.jpg)
