Editing .echoreplay File Format

From Echopedia

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
[[Category:API]]
[[Category:API]]
The <code>.echoreplay</code> file format is a container for nearly raw API data from EchoVR. It is designed to be as simple as possible while retaining all information provided by the API.  
The <code>.echoreplay</code> file format is a container for nearly raw API data from EchoVR. It is designed to be as simple as possible while retaining all information provided by the API.  


Line 11: Line 12:
| [[Spark]] || Records <code>.echoreplay</code> files from game data.
| [[Spark]] || Records <code>.echoreplay</code> files from game data.
|}
|}
To record <code>.echoreplay</code> files without writing your own software, you can use the [[Spark]], but the format is designed to be simple enough to let people read and write their own replay files.
To record <code>.echoreplay</code> files without writing your own software, you can use the [[Spark]], but the format is designed to be simple enough to let people read and write their own replay files.


Line 18: Line 20:
* One line per API request.
* One line per API request.
* Each line contains the a timestamp, the ''tab'' character, and the full JSON data from the game's API
* Each line contains the a timestamp, the ''tab'' character, and the full JSON data from the game's API
* Optionally, the JSON data for player bone data is included at the end of the line, separated by another tab character.
 
Due to the high efficiency of zip compression, binary formats such as <code>.milk</code> (once modified to include all the data necessary for replays) provide only marginal or no benefits over the compressed <code>.echoreplay</code>. These formats also require modification for every API change from the game, unlike <code>.echoreplay</code>.
Due to the high efficiency of zip compression, binary formats such as <code>.milk</code> (once modified to include all the data necessary for replays) provide only marginal or no benefits over the compressed <code>.echoreplay</code>. These formats also require modification for every API change from the game, unlike <code>.echoreplay</code>.
Please note that all contributions to Echopedia may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Echopedia:Copyrights for details). Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)