Hey, so I've had problems with two things :
In Raid / ST : The combustion rotation is off because the bot keeps casting fireball, while it should cast Scorch (because scorch has no travel time and a short cast time, so it can maximize Hot Streak procs). Also Meteor should never be used during Combustion but right before it (and with the Ring Of Power buff)
Here is the actual rotation it should do (all coming from https://www.altered-time.com/ and the mage discord)
Rotation with no Blaster Master buff :
Now about Blaster Master (which everyone is stacking usually) : Optimizing the uptime of Blaster Master procs (gained after using Fire Blast) is quite important, that's why the casts of Fire Blast are purposely delayed by Scorch. (FB>Pyro1>Scorch>Pyro2>FB>Pyro3>Scorch>Pyro4)
(Combustion must have priority over using the Hot Streak proc for a Pyro, because we want the FIRST spell used during Combustion to be ideally a Pyroblast)
Here is how a Blaster Master optimized rotation should look like :
Right now the bot is doing this, which is all wrong. casting fireball, meteor after combust, not starting combust with at least half a hot streak proc... :
Also it could be epic if you added the two most important Fire Mage items and incorpore them in the rotation (Lucid Dream essence as well as Hyperthreading Wrists from Mechagon), almost every mages play with them in raid now and it will likely still be used in the next patch, same for Lucid Dream (must be paired with combustion phases). Those abilities are now core part of the rotation and I think it's a must to add them if you want to make the bot competitive.
Here is how the rotation look with those two new buttons :
Anyway, Fireball should NEVER be used during combustion, only Scorch.
Now in M+ : Is there a way to make the bot knows that Flame Patch is picked as a talent (like a check box). The normal priority in AoE with Flame Patch is to hardcast Flamestrike and spend the hot streak procs into Flamestrike, not Pyroblast (at 2 or 3+ targets). I found out that the bot was barely casting Flamestrike below 7~ targets in combat. The idea of adding a check box would be to prevent the bot to cast Flamestrike in raiding environment (when passive Cleave happens). Otherwise there should be no Flamestrike during a Combustion window (whenever the buff is tracked).
Thanks for reading and hope you'll be able to help !
Try this version please - http://www.bimsbot.ru/maxtests/Wusukuzataxofuh.zip
I do not have Lucid Dream essence, Hyperthreading Wrists from Mechagon and Blaster Master essence therefore I cann't test they work. If you have them and program will work incorrect - record short video with problem and send it to me pls.
I do not have Lucid Dream essence, Hyperthreading Wrists from Mechagon and Blaster Master essence therefore I cann't test they work. If you have them and program will work incorrect - record short video with problem and send it to me pls.
- Штрейхбрекер
- Posts: 58
- Joined: Mon Jun 18, 2018 9:57 am
Also the bot is casting fire blast after the rune when it should cast it before it and sometimes it doesn't cast meteor. I tried removing scorch and it's almost perfect at the beginning, but the bot is recasting the rune too early, and should never cast rune during combustion as it's a gcd loss.
I think how to fix it would be : Never cast SCORCH if WRISTS are available, never cast RUNE if COMBUSTION is up, always prioritize FIRE BLAST over RUNE (to maximize pyroblast & BM under rune buff).

I think how to fix it would be : Never cast SCORCH if WRISTS are available, never cast RUNE if COMBUSTION is up, always prioritize FIRE BLAST over RUNE (to maximize pyroblast & BM under rune buff).

Your first screenshot was taken outside the combust phase - in this case, if we do not have fire blast charges, then we use scorch - it should be so. Also on this screenshot Hyperthread Wristwraps is used outside the combust phase, so you use it yourself. Try testing the program using Hyperthread Wristwraps automatically.
