Dota Replay Manager User Manual

Table of contents

Installation

Simply unpack the ZIP archive to any folder and you're good to go. When upgrading from a previous version, unpack on top of it to keep the old settings.

Settings

General options
  • Warcraft III Folder: the path to your WC3 installation. It is used to extract data from map files.
  • Replay folder: the root path for all your replays. Normally it will be a folder named 'Replay' in your WC3 directory.
  • Hide empty folders: folders containing no replays will not be displayed in the tree view.
  • View replays in windowed mode: launch WC3 in windowed mode to view replays.
  • Automatically open new replays: display game information when a new replay is detected.
  • Automatically copy new replays: when a new replay is detected, copy it to the path specified below (click 'Help' to see the list of tags allowed).
  • Select columns: choose which columns will be displayed when viewing a folder with replays.
  • Minimize to system tray: application will hide to tray when minimized.
  • Enable URL in path bar: when a path starting with 'http://' is specified, it will be downloaded to a temporary folder for viewing.
  • Automatically check for updates: the program will check for updates online once a day (kinda pointless considering I don't plan to update it anymore, and its using an old nonexistent webside to check).
  • Automatically load missing map data: when a new Dota map is used in a replay, the program will look for it in the WC3 folder and parse it.
  • Set this program as default for opening replays: check to open .w3g files with Dota Replay Manager, uncheck to open with WC3.
Replay options
  • Your name(s) in replays: used for some statistics. (Currently not implemented)
  • Repeated action delay for skills/items (ms): ignore repeated skill/item clicks when determining skill/item build.
  • Timeline mode: determines which elements will be displayed in timeline tab (note that wards might not be accurate when other ground target items are used such as blink dagger).
  • Show skill levels in build view: display skill level next to skill name.
  • Smoother gold timeline: gold graph will be less spiky when somebody buys multiple items in quick succession.
  • Time relative to creep spawn: time will start when the creeps spawn, as opposed to from the beginning of the replay.
  • Show empty slots: display empty item slots in item builds.
  • Show assembled items in itembuild: determine which items were combined (might not be 100% accurate).
  • Show hero names in chat: show heroes next to player names in chat.
  • Show assists in chat: show assists after kills in chat.
  • Chat colors: choose text font, player colors and chat background (by clicking on the sample bar).
  • Log actions to log.txt: dump replay actions into log.txt for use with another tool. This can slow down replay parsing.
Clicking Cache all replays at the bottom will cause the program to parse all files in the replay folder and cache the results for searching.

Search

This menu allows searching for all replays in the specified folder matching certain criteria.
  • File name: matches the name of the replay file.
  • Game length between: typo: matches game date.
  • Game name: matches game name.
  • Game mode: matches game mode.
  • Number of players: min/max total number of players in the game.
  • Map version: min/max map version.
  • Patch version: min/max WC3 version.
  • Game length between: matches match length.
  • Players: specify up to 5 players's names and/or heroes (looks for a game with all of them).
The program will check all replays in the folder, using cached results when possible.

Presentation tab

Exporting replay data to text format is now done via this interface. Clicking "Generate" button in top right will generate a simple preset based on selected options. The syntax of the script is fairly simple:
  • Comments start with $$ and last until the end of the line.
  • All text not contained in curly braces is copied directly to output (including line breaks).
  • All replay data is accessed through a hierarchy of variables, addressed as {item.subitem.subitem} etc.
  • All variables are of string type.
  • Some variables contain a list of values, such as a list of all players - those can be iterated through with {for} block: {for p in game.players}{p.name}{endfor} would print the names of all players (with no spaces in between).
  • Conditions are added with {if} blocks: {if player.name == "Riv"}(myself){else}{player.name}{endif} A condition is either a variable (which is true unless it doesn't exist, is empty, or equals false), or a case-insensitive comparison, or a logical expression consisting of other conditions.
Two sample scripts are included. I'm not listing all the variables because they can easily be viewed in the editor by pressing Ctrl+Space.

Command line interface

Starting with 3.02d, a separate tool is provided for users that need a way to quickly generate log files for replays.
It can be run from the command line with the following arguments: qlog [options] <file name>
  • <file name> - full or relative path to replay file
  • -d --detail <detail> - detail mode, simple or full (default: simple)
  • -o --output <file_name> - path to output file (default: log.txt)

Other features

Most of the interface should be fairly intuitive, here are some random notes:
  • Folder view: right clicking file(s) and selecting "Backup" will copy them to the path specified in "Copy to file" option in settings.
  • Hero chart: find games based on a hero; only checks for games in cache and can display the same game multiple times if the replay has been copied.
  • Action log tab: shows a full list of actions that occured in the replay, for advanced users. This requires the original map file and works with any map (not just Dota).

RivSoft.net by Riv (riv@rivsoft.net) - All rights reserved