Source (David Sifry), resized

Torn API Reader (TAPIR) by Bobogoobo [2618206]

Designed primarily to parse and analyze your activity log for interesting statistics, but also capable of any other API stat tracking.

For any suggestions, questions, or issues, please mail me in game (not chat) or message me on Discord (I'm verified in the Torn server). No item is too insignificant, and feedback is appreciated!
If you do something cool using this, feel free to send me a link! (Credit would be appreciated.) More interest in the project means I can spend more time improving it.
The program's repository is here - please see the readme for guidelines.

Your API key will not be stored except in temporary browser memory only while the program is running, unless you choose otherwise. It will not be transmitted except to the Torn API, over a secure connection.

The information exposed by this tool can be very sensitive in terms of Torn gameplay. Always think and look it over before sharing! Never share your API key with players you don't trust!

Disclaimer: this tool is in beta and will be updated frequently. Customized log formats are subject to change. You accept responsibility for any damages incurred as a result of using this tool.
Logs may not be complete or totally accurate due to not always being tracked by the game or bugs that were not fixed retroactively.

Last updated: 2022-08-07 - tech demo release.

Don't play Torn? Check it out here.

Log Information Parser (TAPIR LIP)

Instructions

1. Enter an API key. To read your log it must be Full Access. Your browser may allow you to save it as a password for quick use on this page.
2. Set options. Most selections are not required. On your first full run, I recommend storing logs and leaving other settings alone, but you can also do a limited run to try it out.
3. Start the program.
   • For your first full run:
     1. Enable the option to store logs, then click "Run From Torn API". It may take a very long time to run depending on how long and how frequently you've been playing.
     2. When it is done, the Torn Logs field will populate. Click "Copy to Clipboard", open up Notepad or equivalent, paste, and save somewhere convenient.
   • For subsequent runs:
     1. Click the file selection button next to "Choose saved log file" and select the log file you previously saved.
     2. Click the Submit button to load the log data into the program.
     3. Choose routines to run by clicking the "Show list of routines" button (this is optional).
     4. Click "Run From Stored Data".
   • Note: you can also run from stored data after doing a full run without needing a file, if you chose to save the logs and haven't refreshed the page.
   • Any errors or potential issues the program encounters will be logged in the "Program Logs" area.
4. If you refresh the page, you will need to follow these steps again. Your browser may save your selections for you, but the file will always need to be submitted again.

Routines

Known Issues / Planned Features

When reporting a bug, please include any errors in the browser console (F12) and how to reproduce it.

Many more ideas for features and routines are already noted, but feel free to suggest specific ideas (requests help prioritize development).

• Output of routines should have some nice formatting and they should be easier to navigate. Page needs to be more visually appealing in general.
• Mobile support and keyboard interfacing should be added.
• Progress indicators do not take limits into account. Limits are not always followed correctly. Limiting to 0 logs does not terminate properly.
• Analyze Log fails with console error if run without first doing something else to call the API.
• API error codes are not specifically checked and may result in program errors.
• Re-running without refreshing the page may not always work as expected.
• Log file should be easier to update.
• Some API inconsistencies have not yet been accounted for and not all issues have been found. Additional non-API data is still to be added.
• Program start/end time should be tracked in ms.
• Racing routine does not work without license acquisition being in the read logs.

Log Versions

If the version in your log file does not match the most recent version (listed first), data may not be read properly by the program.
To update to a more recent version, you will need to adjust the data manually. This may be automated in the future.

• v0.1.0 - 2022-08-07
  • Initial limited test release. Many changes to API data to make it more concise, consistent, and program readable.

Thanks for visiting!