me, @chad and @mindme as we dig into medivac transport logic, stuck unit detection, and map debugging quirks. The session also showcased experiments with Protoss wall-offs and building placement tools. Themes included debugging mechanics, smarter micro, and balancing automation vs. manual map setups.
Key Takeaways:
-
Use medivacâs unload attargeting the transport itself to allow smooth drop-while-moving behavior. -
Detecting stuck units can be done by pathing them toward distant minersâworkers are guaranteed pathable. -
Debugging load/unload requires careful tracking: drop ships chasing units vs. units moving into transports behave differently. -
Protoss walling can be automated with map analysis, but SC2âs grid system snaps buildings to 0.0 (even sizes) or 0.5 (odd sizes), making manual editor placement often faster. -
Dynamic calculation vs. hard-coding: worth prototyping, but for only 5â6 ladder maps, manual coordinates may be the pragmatic choice. -
Bugs like missing Battlecruiser damage values can cascade into faulty combat simulationsâdebug across maps to isolate whether itâs code or map data. -
Balance time spent on automation with practical shortcuts; sometimes manual fixes unblock progress faster than over-engineering.