Dupliate entries in build order in almost every replay

[GoogleCodeExporter]

Run the upload_file.php demo on the attached replay file.
Pretty much every replay yields these same results, though :(

18 sec  trains a Probe (090E00)  
18 sec  trains a Probe (090E00)  

320 sec     lifts off (Factory) (080500)
320 sec     lifts off (Factory) (080500)

348 sec     researches Cloaking field (090600)
348 sec     researches Cloaking field (090600)

514 sec     lifts off (Factory)
514 sec     lifts off (Factory)
515 sec     lands (Factory)
(just one of the "two" factories landing after the factory/starport swap)

I presume this has to do with some structure not getting reset correctly, or 
maybe some offset repeating itself, or being misaligned when parsing the replay 
file? 

Got any good ideas? :)

Original issue reported on code.google.com by talon...@gmail.com on 30 Aug 2010 at 10:44

Attachments:

• (P)DuckloadRavs(T)roxkisBratOK_LT_2010-08-01_1198.sc2replay

[GoogleCodeExporter]

ahum *blushes*

"The event system is innately married to the game engine. What this means is 
that for example unit deaths, hit points and resources can't be directly 
parsed. A similar limitation exists for interpreting build orders. As a simple 
example, let's assume at game start that a player clicks the "Build SCV" button 
3 times. Even though two of the three clicks will fail because of lack of 
resources, all 3 will get registered as "builds an SCV" in this file. In order 
to distinguish between failed build orders, one would have to implement at 
least a part of the game engine to keep track of different resources. This is, 
however, completely unfeasible and thus any build order lists will always 
contain errors."

This is quite well layed out in your Wiki. Sorry about that. Please close down 
this ticket.

Original comment by talon...@gmail.com on 30 Aug 2010 at 10:52

[GoogleCodeExporter]

Original comment by zsol.z...@gmail.com on 31 Aug 2010 at 12:41

• Changed state: Invalid