cactbot VS xivanalysis

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 ?).

Finally, if you're able to (and want to), you may want to considering getting ACT and setting up your character on FFLogs. You can set all your logs to Unlisted to keep them private, but the main reason I recommend logging is so you can put your logs into XIVAnalysis after uploading - it will give you a breakdown of what you did during the fight and offer advice on what you can do better. Even if you don't care that much about parse numbers the tips XIVA can be really helpful in terms of playing most effectively and seeing where you need to practice - and all of this will help even in casual content!

If you know where one of your logs are posted https://xivanalysis.com will tell you some basic things you might miss.

People running ACT often upload logs of fights they were in as publically searchable there, so it is relatively likely if you've run the Abyssos raids a bunch that if you search your character there'll be logs with you in on the site. Damage is obviously effected by gear score and many people will have 630 ilvl and materia melds, but if you want stat agnostic feedback on how you're doing your rotation you can paste log URLs into https://xivanalysis.com/ to get some useful info.

https://xivanalysis.com/ very useful website

Pick a row, click on any number on the first 6 columns to access the log for that particular fight. You can then copy/paste the URL for that log into the box when you load up xivanalysis.com. If the URL doesn't work, you're looking for the string after "/reports/" for a random example: bN6nfqaYZkrcL8VW would be adequate to paste in the box.

If you have logs of your fights, you can plug them into XIVAnalysis to give you specific feedback on your raiding gameplay.

If you are unwilling to show us some logs, the best thing you can do is plug your logs into this website and see what it says. If you can fix any things it points out and consistently play at that level, then you can fire back at anyone that singles you out for dps reasons.

you could try plugging one of your parses into https://xivanalysis.com/ to get a better idea of where you need improvement.

take your logs, stick them into xivanalysis.com, and see what it spits out