PQR - Rotation Bot

[jjlanp]

the frame is more for trying out settings. if more people follow the example i set for them in how to set it up, there's going to be a giant table that you setup and that will have all the values you are changing anyways. so you can just go into that and set the perfect values for yourself there after you've done all of your tests with the frame on the fly. This isn't supposed to be a magical way to save people from ever going into the PQR ability and rotation editor again.... it's just supposed to make it a 100 times easier than entering into those things each time you want to try some different value out, or if you just want to disable a single spell for a fight (like turn off cleaves for a certain boss fight, change your CD keys to see which one feels better to you, etc)

Of course. Totally agree. Sorry if I came off rude. Definitely appreciate the effort.

[deadpanstiffy]

Are you using the default Interrupt profile that Xelper releases?

If so here's something in the "-- Variables: Interrupt --" ability you should know about.

--This is the percentage of the cast to wait before interrupting
PQR_InterruptPercent = 0

If the class profile itself has a built-in interrupt then you shouldn't use any Interrupt profiles. Since your interrupt is on cool-down, techniquely the class profile that has a built-in interrupt just gets ignored.
However if the class profile doesn't have a built-in interrupt then I might suggest using Team Nova's Interrupt profile.

Same location, sort of looks like the default Interrupt profile Xelper gives out except notice the difference.

--This is the percentage of the cast to wait before interrupting
PQR_InterruptPercent = math.random(30, 80)

Instead of going off at 0% it goes off of those two random percentages, 30% and 80%.

So the point of this post is don't use an Interrupt profile if the current class profile you are using doesn't already have it built-in.

Hope this helps you, larrybyrdy.

if PQR_InterruptStarted then
   PQR_InterruptStarted = false

    --This is the delay before interrupting in seconds.
    PQR_InterruptDelay = 0.5
    
    --This is the percentage of the cast to wait before interrupting
    PQR_InterruptPercent = 0
end

As soon as the interrupt has started it will use the same value for PQR_InterruptPercent until the global PQR_InterruptStarted is set back to true. If you want random interrupts all the time, you'll need to not use the global, PQR_InterruptStarted.

[imdasandman]

the frame is more for trying out settings. if more people follow the example i set for them in how to set it up, there's going to be a giant table that you setup and that will have all the values you are changing anyways. so you can just go into that and set the perfect values for yourself there after you've done all of your tests with the frame on the fly. This isn't supposed to be a magical way to save people from ever going into the PQR ability and rotation editor again.... it's just supposed to make it a 100 times easier than entering into those things each time you want to try some different value out, or if you just want to disable a single spell for a fight (like turn off cleaves for a certain boss fight, change your CD keys to see which one feels better to you, etc)

I can see how powerful the table will be on healing profiles as you can change spell priorities on the fly as the fight goes on or even from encounter to encounter

Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

[bu_ba_911]

if PQR_InterruptStarted then
   PQR_InterruptStarted = false

    --This is the delay before interrupting in seconds.
    PQR_InterruptDelay = 0.5
    
    --This is the percentage of the cast to wait before interrupting
    PQR_InterruptPercent = 0
end

As soon as the interrupt has started it will use the same value for PQR_InterruptPercent until the global PQR_InterruptStarted is set back to true. If you want random interrupts all the time, you'll need to not use the global, PQR_InterruptStarted.

or just move the global outside of that closed check

[Ninjaderp]

Is it possible to add Asphyxiate/Strangulate and Arcane Torrent blood elf-racial as interrupts if Mind Freeze is on cooldown? Talking Nova's modded interrupt-profile.

[Rubim]

Is it possible to add Asphyxiate/Strangulate and Arcane Torrent blood elf-racial as interrupts if Mind Freeze is on cooldown? Talking Nova's modded interrupt-profile.

Yep, do a CD check.

Sstart, Sduration, Senabled = GetSpellCooldown(MindFreezeID)
Scooldown = (Sstart + Sduration - GetTime())

if Scooldown > 1
then
...

Asphyxiate need resources you will probably need some way to have the bot save resources.

[cassrgs]

@Ninjaderp
try to change in the initalize ability

if playerClass == "DEATHKNIGHT" then
    return 47528 

for

if playerClass == "DEATHKNIGHT" then
    if PQR_SpellAvailable(47528) then --mind freeze
        return 47528
    else
        if PQR_SpellAvailable(108194) then --asphyxiate
            return 108194
        elseif PQR_SpellAvailable(28730) then --arcante torrent
            return 28730
        end
    end 

Try it and say what happens. I have no ideia if it will work XD

[Rubim]

@Ninjaderp
try to change in the initalize ability

if playerClass == "DEATHKNIGHT" then
    return 47528 

for

if playerClass == "DEATHKNIGHT" then
    if PQR_SpellAvailable(47528) then --mind freeze
        return 47528
    else
        if PQR_SpellAvailable(108194) then --asphyxiate
            return 108194
        elseif PQR_SpellAvailable(28730) then --arcante torrent
            return 28730
        end
    end 

Try it and say what happens. I have no ideia if it will work XD

The interrupt profile is not constantly checking your CLASS, you could change that, dunno how much that will hit on the performance side.

Make a tabbled list of spells that interrupt?
if playerClass == "DEATHKNIGHT" then
return PQ_InterrruptSpells = {47528,28730}

That wont work out of box you will have to change almost everything point to this function.

==

My bad, it is >.>

local interruptSpell = PQR_InterruptSpell()

Yeah your solution should work.

[Ninjaderp]

thanks both of you rubim, cassgrs, I will try it in a heroic!

As rubim said, I got severe fps-lag with that coded in. I got no problem using shift (stoprotation in rubims blood dk) and using it manually until there is a way of it working without fps suffering.

[geroth22]

Any chance of getting pqr to work with the ptr tonight? Got some raid testing to do.

[cassrgs]

thanks both of you rubim, cassgrs, I will try it in a heroic!

As rubim said, I got severe fps-lag with that coded in. I got no problem using shift (stoprotation in rubims blood dk) and using it manually until there is a way of it working without fps suffering.

Another thing that i realized its that maybe Arcane torrent wont work all the time as interrupt in those times you have a target but its not in melee range since dont seem to have a distance check (if youre away from target casting howling blast or something)

[Ninjaderp]

^ Yeah thats true as well, I may try remove the arcane torrent-portion and try it again but for now its sleepytime here. Take care!

[larrybyrdy]

Are you using the default Interrupt profile that Xelper releases?

If so here's something in the "-- Variables: Interrupt --" ability you should know about.

--This is the percentage of the cast to wait before interrupting
PQR_InterruptPercent = 0

If the class profile itself has a built-in interrupt then you shouldn't use any Interrupt profiles. Since your interrupt is on cool-down, techniquely the class profile that has a built-in interrupt just gets ignored.
However if the class profile doesn't have a built-in interrupt then I might suggest using Team Nova's Interrupt profile.

Same location, sort of looks like the default Interrupt profile Xelper gives out except notice the difference.

--This is the percentage of the cast to wait before interrupting
PQR_InterruptPercent = math.random(30, 80)

Instead of going off at 0% it goes off of those two random percentages, 30% and 80%.

So the point of this post is don't use an Interrupt profile if the current class profile you are using doesn't already have it built-in.

Hope this helps you, larrybyrdy.

Fantastic, thanks man. Basically what I was doing was this. I was running Nova's Arms single target profile. Then I'd alt+c to activate interrupts set to everything so it'd interrupt on cooldown (glyphed pummel for dmg). I assume then that I was using the default interrupt built into PQR. If so, I can just go find that code and change the percentage like you listed. Either way, I have a decent idea of where to start hunting so thank you.

[WWF]

Hi, PQR doesn't work on test realm, current build is 16467, do you can tell me how make a new offsets?

[lostinthewoodslol]

Hi, PQR doesn't work on test realm, current build is 16467, do you can tell me how make a new offsets?

im sure Xelper will get it as soon as he can.