bsaffel / benchmarker

macro trainer | build optimizer | practice tool
10 stars 0 forks source link

Benchmarker

Benchmarker

macro trainer | build optimizer | practice tool

Benchmarker is a starcraft 2 macro and build trainer. This tool aims to help players improve macro mechanics by tracking supply at certain benchmarks during the game. It also includes alerts for common mistakes, and tracks stats for each build.

Features

Reset builds on the fly without having to remake a custom game.

Track personal supply benchmarks by matchup in-game

Practice against "benchmark" build orders to refine and optimize your play

Display customizable alerts designed to help players get into the rhythm of macroing correctly.

Provide performance reports after each build to help you create and refine the perfect build order

In-Game Stats to track your progress in real time

A [WIN] button... because who doesn’t want a win button?

Supports chat commands and hotkeys for accessing menus in game

How To Play

For first time players:

Once you have completed a build you can elect to save it or start over. If you save your build it becomes available to practice against for that matchup next time you play that matchup.

Build Order steps are marked complete when the correct build-order-eligible unit or upgrade is made. They are marked failed when the incorrect build-order-eligible unit or upgrade is made

Recommended Practice Technique

This tool is designed around the idea of perfecting one standard “macro” build for each matchup. It is intended to help you with learning that build order, improving your macro mechanics, and refining your timings all as part of a single practice session. For most players below Master League this single build approach is commonly recommended as a great way to improve both on mechanics and understanding basic timings. So at least until multiple benchmark builds are added (and they almost certainly will be at some point), here are some of my recommended practice techniques:

Standard Macro Practice
  1. Pick a matchup.
  2. Think about what you consider your strongest “standard” macro build in that matchup.
  3. Play through that build a couple of times until you’re warmed up.
  4. Once you have a build run-through that you are happy with, save it as a benchmark build.
  5. For the next 10 - 30 minutes, attempt to refine that build by pushing yourself to exceed the supply benchmarks, and to shave off time from build step timings.
  6. Each time you execute the build more cleanly than the current benchmark save that new build as the benchmark to beat.
  7. After your chosen time is up or when you are satisfied with your current performance, move on to your next matchup and repeat steps 2 - 6 until done with each matchup.
  8. Go on the ladder and collect your wins.
Learning A New Build
  1. Pick a build.
  2. Select the appropriate matchup for the build.
  3. Uncheck practice against build order (if checked), or clear the existing build if desired.
  4. Play through the new build slowly at first. It is more important to get the build steps in the right order than to focus on execution or hitting timings the first time through.
  5. When the correct build order has been achieved (which you can check on the post-build report), save this build as the new benchmark.
  6. Practice against the newly saved benchmark build a couple of times, each time trying to shave a few seconds off the timings, squeezing a few more workers out, or use your resources more efficiently etc…
  7. Feel free to also use the [FORK] option to allow for diverging from the new build to add your own style and variations.
  8. Proceed to ladder.
  9. Slay nerds.

Note - Whenever you are able to exceed one or more of the supply benchmarks during a build, don’t forget update the supply benchmarks to reflect the new record. From there you can tweak them by hand if desired.

More advanced players should ideally be comfortable cycling through different benchmark builds for a matchup since they are already familiar with them. If a large number of users start to ask for multiple different named benchmark builds it could be implemented before the 1.0 release.

Useful Tips