These exports should provide a much more robust dataset to work with.
SC2 REPLAY PLAYER PATCH
Future versions of sc2reader will provide support for game data exports from the World Editor (introduced in patch 2.0.10). Basic cost, build time, and race information has been packaged. Player Team Workers Resource Collection Avg Unspent Resources Spending Quotient Workers Killed Resources Lost. Hero Units Global Replays Reporting Challenges. In the prompt window, select a capture mode from the Mode drop-down list. A Create/Select Source window will pop up, hit OK. Sc2reader has attempted to mitigate this serious deficiency by packaging its own game data files. A unique custom stats replay hosting site. Under the Sources section on the home screen, click the + button > Game Capture. When tells you it is “Fetching Files”, it can often be referring to dependencies like this. These dependencies might look like this:Īs part of the replay pre-load process, each of these dependencies is fetched and all of their associated data is loaded into memory. The other important aspect of this is that instead of completely describing all of the game data (unit data, ability data, map info, etc), replays maintain a list of dependencies. StarCraft enables the player to record a game and save it as a replay, which can then be viewed with any other copy. Fortunately since 2.0.4 tracker events now record some of this information prior to that patch we had to run our own simulations to guess at most of the data. Information that you are super interested in probably is not directly recorded.
That means no player resource counts, colleciton rates, supply values, vision, unit positions, unit deaths, etc. Game state is not recorded because the game engine can recreate it based off the other information. Replays are specifically designed to only include data essential to recreate the game.
0 kommentar(er)
