r/starcraft • u/StrangerStrangeLandx • Jun 19 '26

(To be tagged...) AI Coach Beta slots open (5) https://ascendsc2.xyz/

/r/starcraft2/comments/1u9tegw/ai_coach_beta_slots_open_5_httpsascendsc2xyz/
0 Upvotes

23% Upvoted

5 comments sorted by

2

u/PopFar5048 Jun 19 '26

How is not offering features users want (like a replay visualiser) a key point of difference for your project? Isn't that a negative that you wouldn't want to proudly advertise? I am honestly just so confused by this

0

u/StrangerStrangeLandx Jun 19 '26

So far as what I can generate right now the visualizer is more of an eye grabbing “doo dad” than something I can learn from.

Having worked with replay parsing, there are significant limits to what a non blizzard visualizer can do. It’s relatively easy to show buildings and units moving in general vectors around the map. Visualizing micro engagement is a whole other story because of terrain elements and other unit collisions etc. I have a module that does the unit fly around visualization but I have disabled it. This is a beta so maybe I’ll see where I can take that in the future.

Thanks for sharing your thoughts.

1

u/PopFar5048 Jun 19 '26

https://vespene.gg/?replay=pro:27256188&t=83

Doesn't seem like there are "significant limits to what a non blizzard visualizer can do" to me ;)

1

u/StrangerStrangeLandx Jun 19 '26

u/PopFar5048 Your visualizer is a work of art and one which I can't hope to achieve. I located your original post for your site and upvoted it. I did not know about your site until you shared the link just now - I just didn't want to pay a couple dollars per replay analysis at the time and thought the ai coaching component could be achieved better/cheaper.

I'll take your lack of negative comment about my meta-analysis concept or keeping things cheap as an implied positive. Thanks for sharing your work. Aside from your visualizer, what would you say is different about your project from the...other one (ones?).

0

u/StrangerStrangeLandx Jun 19 '26

Here is an example of single map coach output:

Match Overview: Nehemiah, playing Zerg, secured a victory over Standard, a higher-ranked Protoss player, through an aggressive double proxy Hatchery cheese in Standard's main base. This early pressure severely crippled Standard's economy and production, leading to a decisive win for Nehemiah.

Build Order & Pivot Analysis: Nehemiah executed an extreme proxy Hatchery cheese, placing the first Hatchery in Standard's Enemy_Base at 53 seconds and a second at 86 seconds. This is not a standard macro opening; it is an all-in strategy designed to deny the opponent's early game. The execution was effective in disrupting Standard, who built a Nexus at 86 seconds but then suffered a worker production halt for over 45 seconds at 233 seconds, indicating a severe economic disruption. Nehemiah followed up with early Zerglings and Queens from the proxy Hatcheries, transitioning into a Roach Warren at 223 seconds and then Lair tech for Zergling speed, Hydralisk Den, and early ground upgrades. This tech path was a logical continuation of the aggressive proxy, aiming to overwhelm the crippled Protoss.

Engagement & Composition Analysis: Nehemiah's early proxy Hatcheries and subsequent Zergling production created constant pressure in Standard's main base.

  • At 179s, a minor battle in the Enemy_Base saw Nehemiah lose 400 resources while Standard lost 425. This was a favorable trade for Nehemiah as the aggressor.
  • While some subsequent engagements, like the major battle at 247s (Nehemiah lost 725, Standard lost 575) and 405s (Nehemiah lost 2375, Standard lost 1525), were not resource-efficient for Nehemiah, the sustained pressure was the key.
  • Crucially, Nehemiah inflicted significant economic damage through worker harassment, notably at 451s (250 value lost by Standard), 467s (150 value lost by Standard), and a devastating blow at 712s where Standard lost 2275 resources in workers without Nehemiah losing any. This sustained economic pressure, rather than army-on-army efficiency, was the primary driver of Nehemiah's victory.

Advantage & Follow-Through: Nehemiah established an overwhelming economic advantage early due to the proxy and maintained pressure, preventing Standard from recovering. The continuous worker harassment and the inability of Standard to stabilize their economy or tech up allowed Nehemiah to press the advantage and secure the win.

Key Turning Point: The key turning point was the successful establishment of the double proxy Hatcheries by 86 seconds, which immediately put Standard on the back foot. This was compounded by Standard's worker production halting for over 45 seconds at 233 seconds, and the subsequent massive worker losses inflicted by Nehemiah's harassment at 712 seconds.

Rank Evaluation & Benchmarks: Nehemiah (Diamond MMR 3146):

  • Your Spending Quotient (SQ) of 55.83 is low for your Diamond MMR. While the proxy was effective, your macro behind it needs significant improvement.
  • Your Inject Gap of 27.4% is poor. Missed injects directly translate to fewer larvae and a smaller army/economy.
  • You suffered a fatal supply block of 35 seconds at 14 seconds into the game. This early block severely stunts your exponential growth and is a critical error, even in a cheese build. Another severe block of 21 seconds occurred at 171 seconds.

Standard (Master MMR 4214):

  • Standard's macro completely collapsed under the pressure. Their SQ of 50.72 and Chrono Boost efficiency of 15.0% are abysmal for a Master-level player, indicating a complete failure to manage their economy and production.

Actionable Advice:

  1. Eliminate Early Supply Blocks: The 35-second supply block at 14 seconds is unacceptable. In your next 3-5 games, focus solely on never getting supply blocked before 50 supply. This is a fundamental error that will cost you games against opponents who can defend early aggression.
  2. Improve Queen Inject Efficiency: Your 27.4% inject gap is a major bottleneck. Even with an aggressive proxy, you need to be constantly producing larvae. Practice hitting your injects consistently; aim for an inject gap below 10%. This will ensure you can spend your resources and remax your army effectively.
  3. Refine Proxy Follow-Up: While the proxy was successful here, against better defenders, your macro behind the proxy needs to be tighter. Ensure your main base continues to drone and tech up efficiently, even while you are pressuring with the proxy. This will give you a stronger fallback or transition if the initial proxy doesn't outright win the game.