cactbot VS ZeffUI

In many cases the triggers tell you more than just mechanic X will come. That includes where the mechanic is gonna hit (for some randomized mechanics) as well as telling you some time before the actual visual indicator! Let me run you through an example. The very first mechanic of Titan in UWU without a trigger would be: 1. run to titan, 2. turn the camera behind you so you see where the boulder drops. 3. Take around ~1 sec to move to either a little left or right dependant on 2. (you are still looking behind you btw) With trigger: 1. run to titan 2. Take ~3 sec to adjust left or right dependant on bot callout. (no camera movement needed) The bot calls it out BEFORE the actual boulder drops giving you roughly thrice the time. That stuff is freaking advanced you can take a look yourselve: https://github.com/quisquous/cactbot/blob/ebc00d32b37c1803def106667dd5c3149c3166d3/ui/raidboss/data/04-sb/ultimate/ultima_weapon_ultimate.ts

Yes/No. I am aware for in TEA it has a "Wormhole Cactbot Strategy" which I assume will handle everything for you (based on the encounter text file found at https://github.com/quisquous/cactbot/blob/main/ui/raidboss/data/05-shb/ultimate/the_epic_of_alexander.ts, around like ~1600) and call out when to soak, when to move in as taken from the file:

It's called Cactbot. Why the fuck do you all call it cactpot

Cactbot - Gives you DBM/BigWigs style warnings and timer bars in raid content. Also has other useful plugins such as cause of death and Eureka plugin trackers. Will start an argument in The Balance whenever you bring it up. https://github.com/quisquous/cactbot

I haven’t found a nice visual timeline yet, so https://github.com/quisquous/cactbot/blob/main/ui/raidboss/data/05-shb/trial/diamond_weapon-ex.txt is the best ur gonna get. P1 ends at 170s so should be plenty of time to get off 3rd req phase and skip goring blade and instead royal authority and atone.

I then wrote a Python script to very crudely parse all of my logs that are in the folder. It tracks start of pull and end of pull, for a given fight (here TEA, but it should hande any fight if I have the fight's ID), giving me a pull duration. To do so I used this documentation that was enough for my needs. I won't share the code here because the goal is not to showcase how ugly a mere 150 lines of code can be, the idea is just to match the regex corresponding to start of figth, end of fight and using the info in the lines, extract timestamps. Then standard Python ploting. Someday I may make it a bit fancier and customizable, might share then (during UCoB maybe ?).

Nothing wrong with being used to a different HUD layout. He does however, still have cactbot installed because it is required for ZeffUI to work. You can read the installation process in the bottom here. You, as well as many others, probably aren't aware that cactbot is just an overlay, that several "modules" uses. One of those are ZeffUI, another is RaidBoss, the module with the callouts and timelines. He only has ZeffUI installed, not RaidBoss.

I'd also recommend ZeffUI which is actually Cactbot preset now. If you have Cactbot installed then all you need to do is create a new Overlay and select ZeffUI as a preset. I use it to track my raid buffs and it's really just a not clunky as shit version of SpecialSpellTimer/HojoRing for viewing how long raid buffs will last for and when they'll come off cooldown. Here's an example of what it looks like it from the github page. Super easy to set up and use.

Using ZeffUI just to track mit/swift cooldowns in party.

You can try out https://github.com/Zeffuro/ZeffUI :)