Live analyzer for Eidolon hunters

YATE's watershield definition is a bit different from idalon; the watershield displayed does not include the spawn delay in the calculation, which means it is the exact time from the eidolon spawn to the limb break. idalon adds the spawn delay to the watershield time. So what you will see is in the format x (+y = z) where x is the watershield as it is defined within the tool, y is the spawn delay, z is the watershield by the definition of idalon..

Starting from v0.5.0, there is a lock button next to the overlay window that locks the window in place and prevents any further interaction till closed.

Host's logs are the only usable logs, however starting from YATE 1.0.0 you can connect to the host's YATE and see the updates directly on your client.

YATE is based on the game's log, so it depends on how fast the game updates the logs.

YATE only parses the EE.log file, so it shouldn't violate Terms of Service, but use at your own risk.

There is an option called Streamer Mode that help solve these types of issues.

You can reset the window position from the Settings window.

Anti-viruses work in various ways; YATE's source code is publicly available and there is not any sort of security risk when using the tool.

Unfortunately, there is no way to do that, fullscreen means that the operating system allocates the display and most of the computational resources to the game, so nothing can be on top of it, so you have to use Borderless Fullscreen to see the YATE overlay.

There are several reasons that can cause that, some solutions to try:

• Double check that a Discord instance is running before starting YATE.
• Sometimes the firewall hinders the communication between YATE and Discord, this can be solved by adding an exception rule for YATE in the firewall.
• If you run Discord/Warframe as admin, then you need to run YATE as admin too, otherwise YATE cannot access Discord/Warframe logs.
• You may try going to Discord Settings > Privacy & Safety > Choose “Do not scan”, or “My friends are nice” if your squad is on your Discord firend list.
• If none of these solutions work, DM me on Discord to run the debugging version and trace the issue.

Sometimes there is a small misalignment between YATE's capshot calculation and idalon's, probably due to a rounding error in one of the tools or a minor difference in the calculation method, but shouldn't be a huge difference.

This is not a bug, the spawn delay is the time from the last shard insertion till the eidolon spawn. However, sometimes the shard insertion is registered in the log AFTER the spawn, which results in a negative spawn delay.