Help

1. What are "Failed Replays"?

   Failed replays are replays that were not able to be converted to the new format on database upgrade. There are any number of reasons this might occur, but in general it is because of some unexpected content or format of the data. If you have several failed replays, upload them to dropcanvas and create an issue that includes the link.

2. Why does it take so long to render replays?

   See information on rendering and why it takes so long here.

3. Why can't I upload more than x replays at a time?

   A single replay has a lot of information. The storage, retrieval, and usage of information for a handful of replays isn't taxing, but problems could occur during extension upgrade if limits were not put in place. Doing a partial upgrade of the replay database would be prone to error, so a full upgrade is required and the Chrome process that does the writing of the extension storage is in danger of running out of memory if tasked with processing too much data at once.

4. Why can't I upload any more replays? I'm nowhere near the limit!

   Restricting replay length and player count keeps replays to a predictable size while being straightforward for users to understand, but the real underlying issue is the total size the replays take up. The size of the database that holds the replays is a more accurate indicator of likely crash on upgrade, and is used as one of the restrictions. If you are hitting this limit before hitting the replay limit, you may have some large replays. Try saving your replay data and seeing which replays are the largest.

5. Why can't I set my FPS higher than 60?

   For the same reason as other constraints, this gives a typical number that will work for most people and can be tested against. FPS impacts the amount of time spent saving data in-game and also the size of the replay in the extension and when downloaded.

6. What is "debug mode"?

   Debug mode is a planned setting that allows users to bypass some of the restrictions on replay size, length, player number, FPS, and so on. This is available to allow users to view/recover old replays that may exceed some of these restrictions, but which are normally not permitted in the extension. These restrictions are in place because they give a foundation on which to test, but the extension may be useful for more than those meeting the specific needs. However, replays recorded in debug mode may cause issues, up to and including complete loss of all extension data, and users use this setting at their own peril. If you need to reset the FPS of some specific replays or cut replays down to size, the best thing to do is download all of your replays, enable debug mode, process the replays you need to process and download the fixed replay data (once they meet all requirements). Once that's done, uninstall the extension and re-install it. Make sure debug mode is not enabled after re-install. This ensures that your replays are safe and you are working within the tested capabilities of the extension.

7. Why should I download my replays? Can't the extension keep them for me?

   The extension can definitely keep track of your replays, but it's safer to download your replay data. Storing data in the browser is risky for two reasons. The first is if your Chrome profile becomes corrupted (or you need to remove it to troubleshoot some issue) then you have to go in and copy over the files. The second is that if your hard drive close to full Chrome, like other browsers, will clear out storage (possibly to include the database that holds your replays). When the extension storage is cleared there's no way to recover unless you have a backup of your chrome user folder. See here for more information: IndexedDB and limits