• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 19:34
CEST 01:34
KST 08:34
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
[ASL22] Ro16 Preview: Holy Diver4[ASL22] Ro16 Preview: Rough Waters10[ASL22] Ro24 Preview: Siren's Call8[ASL22] Ro24 Preview: Summer's End9Serral wins HomeStory Cup 2915
Community News
StarCraft open world shooter announced at BlizzCon97Weekly Cups (Aug 30-Sep 7): herO thrives amid growing schism10Official StarCraft website teases new content ahead of BlizzCon?175Stellar Fest TWO the Moon (Dec 16-20)9Weekly Cups (August 24-30): Patches' balance mod takes over3
StarCraft 2
General
StarCraft open world shooter announced at BlizzCon How do you feel about the StarCraft shooter announcement at BlizzCon 2026? Balance hotfix patch 5.0.16b (July 16) Blizzard Classic Cup @ BlizzCon 2026 - $100k prize pool Team Liquid Map Contest #22: Results and Winners
Tourneys
RSL Revival: Season 6 - Qualifiers and Main Event RSL goes to London! 2026 Offline Finals Nov 21-22 SC2 AI Tournament 2026 Fall Sparkling Tuna Cup - Weekly Open Tournament KSL Week #92
Strategy
[G] Having the right mentality to improve
Custom Maps
Nexus Wars 2021 GUIDE [M] (2) Industrial Park
External Content
Mutation # 543 Enhanced Defenses The PondCast: SC2 News & Results Mutation # 542 The Ascended Mutation # 541 Binary Choice
Brood War
General
New 3v3 BGH Ladder (and more) on ShieldBattery! Official StarCraft website teases new content ahead of BlizzCon? [D] Brainstorming a balance patch for Brood war Making an Online Broodwar Manager Game [ASL22] Ro16 Preview: Holy Diver
Tourneys
[Megathread] Daily Proleagues [ASL22] Ro16 Group C [ASL22] Ro16 Group B [ASL22] Ro16 Group A
Strategy
Replay Review Process - What do you do? Simple Questions, Simple Answers Odyssey Mineral Stack Saturation Game Theory for Starcraft
Other Games
General Games
Nintendo Switch Thread EVE Corporation Stormgate/Frost Giant Megathread Diablo IV [Maplestory Hardcore] Let's Play~!!
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
[TL LoL EUW IHs] Teemo shall perish
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Community Thread
Community
General
US Politics Mega-thread Artificial Intelligence Thread Russo-Ukrainian War Thread UK Politics Mega-thread Things Aren’t Peaceful in Palestine
Fan Clubs
MarineLorD Fan Club The Creator Fan Club The ShoWTimE Fan Club
Media & Entertainment
[Manga] One Piece Movie Discussion! Diablo Animated Series on Netflix
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023 MLB/Baseball 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Northern Ireland Global Starcraft
Blogs
Virtual Romance, Real-Life C…
TrAiDoS
Regacy Esports:Our Goa…
regacyesports
Dreaming of BW patches (mod…
c3rberUs
LOCKPICKING NOOB
LUCKY_NOOB
Customize Sidebar...

Website Feedback

Closed Threads



Active: 6279 users

[M](2) Havens Lagoon - Page 3

Forum Index > SC2 Maps & Custom Games
Post a Reply
Prev 1 2 3 4 Next All
Modernist
Profile Joined March 2011
United States89 Posts
Last Edited: 2012-04-08 00:59:32
November 13 2011 09:19 GMT
#41
Timetwister22
Profile Joined March 2011
United States538 Posts
November 13 2011 09:55 GMT
#42
On November 13 2011 18:19 Modernist wrote:
Great map!

One complaint: sooooooo much air space around the edges!


If you're judging by the picture, it lies. In game, its much better. If you're judging from in game, then not sure what to say. I think its perfectly fine, though I appreciate the feedback
Former ESV Mapmaker | @Timetwister22
IronManSC
Profile Blog Joined November 2010
United States2119 Posts
November 14 2011 08:01 GMT
#43
@modernist:

Do not be deceived by the map borders. That is actually one of the pinpoints, and most crucial elements of map-making. The map borders are not actually that wide while playing in-game because the playable bounds are near the bases themselves. The extended map borders (with aesthetics) are only there to prevent black borders from showing up in-game which look terribly sloppy.
SC2 Mapmaker || twitter: @ironmansc || Ohana & Mech Depot || 3x TLMC finalist || www.twitch.tv/sc2mapstream
Timetwister22
Profile Joined March 2011
United States538 Posts
Last Edited: 2011-11-14 22:32:45
November 14 2011 22:30 GMT
#44
Been messing around with the aesthetics, mostly with the water. Here is what I've come up with.
Variation 1
+ Show Spoiler +
[image loading]

Variation 2
+ Show Spoiler +
[image loading]


If you have other ideas, let me know.
Former ESV Mapmaker | @Timetwister22
EatThePath
Profile Blog Joined September 2009
United States3943 Posts
Last Edited: 2011-11-14 22:36:25
November 14 2011 22:35 GMT
#45
I'm partial to multi-level water which is severely lacking in maps out there, so I vote for 2. If you do that, you should also add a falls at the upper lake, the spring where the water comes out of the ground and starts the flow to the ocean. Otherwise you have a random lake uphill from the flow. And who doesn't like more waterfalls? ^^
Comprehensive strategic intention: DNE
Timetwister22
Profile Joined March 2011
United States538 Posts
November 17 2011 04:31 GMT
#46
Got analyzer working and posted analyzer pictures.
Former ESV Mapmaker | @Timetwister22
Timetwister22
Profile Joined March 2011
United States538 Posts
November 17 2011 07:32 GMT
#47
Just updated for 1.5 which was an aesthetics update. Only physical map change was the removal of the experimental curtain on the extended land mass that wraps around the main.
Former ESV Mapmaker | @Timetwister22
jsemmens
Profile Blog Joined June 2011
United States439 Posts
November 17 2011 13:10 GMT
#48
The only part of this map that I find difficult strategically is the late-game with the single xel'naga tower in the center. Once someone holds that position (especially a terran w/ siege tanks), it seems that defending the forward 4th base is difficult since the opposing forces will have to split up to defend the two ramps (note that the tower is *very* close to the minerals at the fourths). Additionally, since the low-ground counter attack path is on the low ground, it is especially easy to shut down counter attacks with siege tank fire from the high ground. Also, with *HUGE* margin space around the edge of the maps, and relatively close-by-air mains, I would expect alot of drop play on this map.

I think a possible solution could be to simply remove the xel'naga watchtower, not every map has to have one, even though it is the trend, or two watchtowers, one on each side of the map.

Picture included for your viewing pleasure! (I love to draw )
+ Show Spoiler +
[image loading]
Check out the Flash Fanclub! http://www.teamliquid.net/forum/viewmessage.php?topic_id=336995
The_Templar
Profile Blog Joined January 2011
your Country52798 Posts
November 17 2011 13:33 GMT
#49
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.
ModeratorI am still alive, somehow
TL+ Member
RumbleBadger
Profile Joined July 2011
322 Posts
November 17 2011 14:56 GMT
#50
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.
Games before dames.
The_Templar
Profile Blog Joined January 2011
your Country52798 Posts
November 17 2011 15:26 GMT
#51
On November 17 2011 23:56 RumbleBadger wrote:
Show nested quote +
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.
ModeratorI am still alive, somehow
TL+ Member
Phried
Profile Joined June 2011
Canada147 Posts
Last Edited: 2011-11-17 15:31:39
November 17 2011 15:29 GMT
#52
On November 18 2011 00:26 TehTemplar wrote:
Show nested quote +
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.

What's the actual distance?
NullCurrent
Profile Joined November 2010
Sweden245 Posts
November 17 2011 16:19 GMT
#53
On November 18 2011 00:29 Phried wrote:
Show nested quote +
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.
The Planetary Workshop - TPW - Mapmaking Team
The_Templar
Profile Blog Joined January 2011
your Country52798 Posts
November 17 2011 17:38 GMT
#54
On November 18 2011 00:29 Phried wrote:


What's the actual distance?

139
ModeratorI am still alive, somehow
TL+ Member
The_Templar
Profile Blog Joined January 2011
your Country52798 Posts
November 17 2011 17:39 GMT
#55
On November 18 2011 01:19 NullCurrent wrote:
Show nested quote +
On November 18 2011 00:29 Phried wrote:
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.

Main to nat+nat to nat=main to main.
ModeratorI am still alive, somehow
TL+ Member
Sea_Food
Profile Blog Joined May 2011
Finland1612 Posts
November 17 2011 19:03 GMT
#56
On November 18 2011 02:39 TehTemplar wrote:
Show nested quote +
On November 18 2011 01:19 NullCurrent wrote:
On November 18 2011 00:29 Phried wrote:
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.

Main to nat+nat to nat=main to main.


Not actually true at all.
Phried
Profile Joined June 2011
Canada147 Posts
Last Edited: 2011-11-17 19:40:15
November 17 2011 19:23 GMT
#57
On November 18 2011 04:03 Sea_Food wrote:
Show nested quote +
On November 18 2011 02:39 TehTemplar wrote:
On November 18 2011 01:19 NullCurrent wrote:
On November 18 2011 00:29 Phried wrote:
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.

Main to nat+nat to nat=main to main.


Not actually true at all.


I think he means (2 *(mainToPersonalNat) + natToNat) or (2*(main2nat) - nat2nat).

He IS right that the two are directly related. Main2Nat(opponent) is correlated to what the main2main is (obviously). main2main and nat2nat are just different ways of measuring the same information.

139 is very short as well. If I'm not mistaken, Steppes of War is only 138(?). It would be a good idea to try and bump that up to 150 or so.

edit: Never mind, wasn't thinking straight
Sea_Food
Profile Blog Joined May 2011
Finland1612 Posts
Last Edited: 2011-11-17 19:32:42
November 17 2011 19:32 GMT
#58
On November 18 2011 04:23 Phried wrote:
Show nested quote +
On November 18 2011 04:03 Sea_Food wrote:
On November 18 2011 02:39 TehTemplar wrote:
On November 18 2011 01:19 NullCurrent wrote:
On November 18 2011 00:29 Phried wrote:
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.

Main to nat+nat to nat=main to main.


Not actually true at all.


I think he means (2 *(mainToPersonalNat) + natToNat) or (2*(main2nat) - nat2nat).

He IS right that the two are directly related. Main2Nat(opponent) is correlated to what the main2main is (obviously). main2main and nat2nat are just different ways of measuring the same information.

139 is very short as well. If I'm not mistaken, Steppes of War is only 138(?). It would be a good idea to try and bump that up to 150 or so.


If you looked at an analyzer picture (example in this OP), you would see that all main to main paths dont go trough the natural bases.
Phried
Profile Joined June 2011
Canada147 Posts
Last Edited: 2011-11-17 19:42:30
November 17 2011 19:39 GMT
#59
On November 18 2011 04:32 Sea_Food wrote:
Show nested quote +
On November 18 2011 04:23 Phried wrote:
On November 18 2011 04:03 Sea_Food wrote:
On November 18 2011 02:39 TehTemplar wrote:
On November 18 2011 01:19 NullCurrent wrote:
On November 18 2011 00:29 Phried wrote:
On November 18 2011 00:26 TehTemplar wrote:
On November 17 2011 23:56 RumbleBadger wrote:
On November 17 2011 22:33 TehTemplar wrote:
Rush distance is too short.
Also, the third seems very hard to take because the entire left side is incredibly open. The average openness of 4.04 is misleading because you have a lot of small, narrow passageways on the right.

The rush distance isn't too short. It's well over 100, and really a map maker is just trying to avoid the fiasco that is close positions metal or shattered (around 60 rush iirc?).
As for the openness, it's just part of the dynamic of the map. A zerg player will be able to expand well into the more open areas late game so a terran or toss will want to pressure early to deny bases. For P and T the extra expansions can be very helpful but require lots of resources to hold, forcing them to be very careful with their timings and such.

100 is a short nat-to-nat distance.
I suggest having at least 150 as a main to main distance.


I think the rule of thumb is generally 145-175. I'm pretty sure that hits the extremes on each end of acceptable. Generally you want 150-165 I think.


Personally I don't think main to main distance really matters, as long as it is not a map where you have a backdoor expo like in Crevasse or so. The important thing is that it is not too long from the main to the natural, so you can easily creep your way there (and also have a somewhat short distance to the walloff for the main/nat choke).

Then you have the natural to natural distance. This will determine how easy it will be to prepare to defend an attack you see coming and will also help define if the map favors rushes or not. Longer distance = easier to hold the natural, that is why steppes of war was so horrible; very short natural to natural distance resulted in almost no time to prepare when you see your opponent moving out.
What I think is acceptable here is everything over 115 Analyzer units (~35 sec, iirc), and not too large for the map as that will make it too hard to scout your opponent.

So main to main distance is not really important at all.

Main to nat+nat to nat=main to main.


Not actually true at all.


I think he means (2 *(mainToPersonalNat) + natToNat) or (2*(main2nat) - nat2nat).

He IS right that the two are directly related. Main2Nat(opponent) is correlated to what the main2main is (obviously). main2main and nat2nat are just different ways of measuring the same information.

139 is very short as well. If I'm not mistaken, Steppes of War is only 138(?). It would be a good idea to try and bump that up to 150 or so.


If you looked at an analyzer picture (example in this OP), you would see that all main to main paths dont go trough the natural bases.


Touche.

I guess I overlooked the fact that the natural isn't necessarily (or even generally) on the main2main path. In any case, the main2main is still pretty short and should be extended. It's called rush distance for a reason.
Timetwister22
Profile Joined March 2011
United States538 Posts
November 17 2011 19:48 GMT
#60
139 is very short as well. If I'm not mistaken, Steppes of War is only 138(?). It would be a good idea to try and bump that up to 150 or so.


Where 139 is short, keep in mind that the analyzer is judging that by going through the narrow entrance to the natural with the high ground of the main beside it. Sticking a marine or stalker on the high ground can deny any scout coming through, and the small entrance plus the high ground gives the defender an advantage when engaging there. The other entrance which is further also isn't very open, and the defender can utilize the narrow entrance for flanks. Thus, Havens is much different than Steppes of War since the natural is easier to defend.

Former ESV Mapmaker | @Timetwister22
Prev 1 2 3 4 Next All
Please log in or register to reply.
Live Events Refresh
Next event in 10h 26m
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
JuggernautJason69
StarCraft: Brood War
910 33
soO 17
Dota 2
monkeys_forever598
NeuroSwarm198
League of Legends
JimRising 504
Super Smash Bros
hungrybox172
PPMD65
Other Games
summit1g11110
shahzam560
PiGStarcraft237
ToD181
Organizations
Other Games
gamesdonequick2165
[ Show 12 non-featured ]
StarCraft 2
• Hupsaiya 83
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• masondota22146
Other Games
• imaqtpie774
• Shiphtur146
Upcoming Events
Afreeca Starleague
10h 26m
Snow vs Shinee
Shine vs EffOrt
GSL
11h 26m
PiGosaur Cup
1d
The PondCast
1d 10h
Kung Fu Cup
1d 11h
Replay Cast
2 days
KCM Race Survival
2 days
IntoTheTV X SOOP
2 days
Replay Cast
3 days
IntoTheTV X SOOP
3 days
[ Show More ]
Replay Cast
4 days
GSL
4 days
Replay Cast
5 days
GSL
5 days
Shopify Rebellion Sundays
5 days
Spirit vs Mixu
Replay Cast
6 days
WardiTV Weekly
6 days
Liquipedia Results

Completed

Blizzard Classic Cup 2026
Blizzard Classic Cup 2026
Big Dog Cup 2026 Div 1

Ongoing

KCM Race Survival 2026 Season 3
K-JUNGMAN
ASL Season 22
Super Anchor Qualifying S3
CSL 2026 AUTUMN (S22)
Acropolis #5
Proleague 2026-09-14
Calamity Invitational
FISSURE Playground #3
BLAST Open Fall 2026
Esports World Cup 2026
BLAST Bounty Summer 2026
BLAST Bounty Summer Qual
Stake Ranked Episode 3
XSE Pro League 2026

Upcoming

Acropolis #5 - GSA
Acropolis #5 - GSB
Acropolis #5 - GSC
SC4ALL II: Brood War
HSC XXX
Stellar Fest 2: Lunar Cup
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
Copium Cup
PGL Major Singapore 2026
Stake Ranked Episode 6
BLAST Rivals Fall 2026
IEM Beijing 2026
Stake Ranked Episode 5
PGL Masters Bucharest 2026
1win Private Club #2
Thunderpick World Champ. '26
ESL Pro League Season 24
Stake Ranked Episode 4
1win Private Club #1
Logitech G Play Connect 2026
SL StarSeries Fall 2026
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2026 TLnet. All Rights Reserved.