Approved tool by the Warframe Speedrunning community!
https://www.speedrun.com/wf/resources
This tool analyzes Profit-Taker runs from based on Warframe's log file, EE.log.
It marks the time spent on each phase and the time spent on the parts that make up said phase.
For the total time, there are two timing methods. The first timing method starts when you leave the elevator, and ends when the final blow is dealt to Profit-Taker. This is accurate up to a frame or two with the speedrun RTA timing.
Another timing method is called fight duration. This timing method starts when you approach Profit-Taker and it first becomes vulnerable. This reduces the difference between the different spawning locations and better reflects your performance in casual runs where you leave the elevator earlier than in speedruns.
Example output:
Downloading:
- You can download the latest version by downloading the executable file here.
Usage:
- Either run the program to follow the game's log files and have your runs analyzed live.
- Or drag a specific log file onto the .exe file.
EE.log can be found in %LOCALAPPDATA%/Warframe (EE.log is reset on startup)
Linux users will have to export the folder that contains /Warframe/EE.log as LOCALAPPDATA to get follow mode to work.
Features:
- Analyzes specific log files by dragging one onto the .exe file.
- Follows the game's log file analyze your runs live (survives game restarts!)
- Displays the first shield element as soon as Profit-Taker spawns in follow mode.
- Marks the best run and displays timestamps and phase durations.
- Supports multiple Profit-Taker runs per EE.log
- Detects the leg regen bug and marks the extra legs in red.
- Detects bugs that lead to incomplete logs and indicates what information is missing.
- Automatically checks for newer versions.
Limitations:
- The tool can only detect runs where you are the host.
- The tool can only detect shield changes, not the cause of it. This means it cannot differentiate between it being destroyed and it getting reset by an Amp or the time limit.
- The tool won't show stats runs that are affected by the pylon stacking bug or other bugs that mess with the logs.
Feel free to contact me on Discord about this tool: Iterniam#5829