Some matchups builds go way longer than that, especially pvz where tech choices aren't decided until after 30 supply frequently. I would love if the game was capable of just extracting the build order of a replay just straight into a text file.

Lampan

Sweden43 Posts

February 06 2010 14:09 GMT

#106

Thanks man this looks amazing will try it out right away.

]343[

United States10328 Posts

February 06 2010 14:39 GMT

#107

LOL I'm glad you thought of this... pure genius

tofucake

Hyrule19213 Posts

February 06 2010 14:49 GMT

#108

On February 06 2010 23:07 Nevuk wrote:

Show nested quote +

Definitely. Many Terran BO's go into the 40's, and there are a couple up to the 50's. The BO thinger should definitely go past 26.

RaptorX

Germany646 Posts

February 06 2010 14:52 GMT

#109

HOLY RAPTOR JESUS....!!

Dude this shit is amazing! now as somebody else asked, is there a way to choose which player to follow when you have a mirror match up?

As you mentioned, it will follow the biggest blob of units... but what if I dont want to follow that particular player?

I think it would be better to make it work like:

/follow [unit] [player number]
where player number would be a number between 1-8.

/follow lurker 1 would follow the lurkers of player 1

Leoj

United States396 Posts

February 06 2010 14:54 GMT

#110

This is absolutely amazing, it's certainly a great tool for me as a new player. Watching replays normally I usually don't say the following:

"oh hey my opponent has 2x the workers on only one more base, why?"
"oh hey I'm attacking and I have 5+ idle production facilties, why?"
"oh hey I'm queueing units but not building more production, why?"
"oh sweet my build order was very good"

Thanks, this'll make catching all those types of mistakes millions of times easier.

Toads

Canada1795 Posts

February 06 2010 14:54 GMT

#111

I've try to find any bug in this program for anyone get fuck by this. And i found one, you can't go on battlenet thay say you have a problem and go contact his support

Nevuk

United States16280 Posts

February 06 2010 14:56 GMT

#112

I just saw the thing about a request for a good formula... not certain if I'm capable of coming up with one, because it's totally different for each race and it's been a while since I did math.

I do have a replay of tempest where he gets a maxxed out army in 11:30 in pvt, it's pretty sick and you might be able to extrapolate a bit from it. By the current thing at that point he has an avg of 17000/18000 (somewhere in between there) and later on peaks in 23000s for overall. One thing to note is that you shouldn't count having idle nexus' against the player after a certain number of probes/expansions. He had 60 probes on 3 bases with only one geyser, so it wouldn't really be beneficial to him to make more.

For protoss it's a combination of never queueing, keeping money <500 for the first 10 or so minute, and never ever missing a pylon. After hitting 200/200 all bets are off. Terran is similar except it's a bit more acceptable to queue mnm. There's also the caveat that it's ok to get supply blocked if there are no idle buildings (ie, they're all producing and the next pylon/depot will be done before the next round of production). It's easiest to measure for zerg because it's just all about how many idle larva they have compared to their resource count. This may do funny things like giving 5 poolers perfect macro, but whatever.

edit : On a different note, how do you change the game speed when watching with this? It's a bit annoying to have to watch it on fast in single player and also to not be able to go faster than fastest online.

yh8c4

108 Posts

February 06 2010 14:57 GMT

#113

really great tool.

here's what i think would be a nice addition:

create an output file which contains information not found in replays (e.g. unit/building creation/destruction). with such a file one could create an advanced version of bwchart with tons of more information than what is inferable from a replay (e.g. graphical representation of army compositions, kill statistics for single units/unit types, etc).

iirc rwas (replays with audio) somehow included the audio into the replay file, so i guess it would be possible that after you watch some replay 'replay.rep" a file "replay_extended.rep" which contains the extra information, but is still usable for programs which require vanilla replay files.

i know this is possibly a huge task (determining the relevant events to store, finding an efficient encoding, creating a parser, etc), but i think it would be a really nice addition.

RaGe

Belgium9950 Posts

February 06 2010 15:03 GMT

#114

btw, since hotkeys are stored in replays, can't you make a /follow # command that follows a certain hotkey group?

This would mean you could basically just /follow 1 and watch the replay without even touching your mouse