MoP Paladin

[wanton lark]

today during raid it felt like it only recommended HoW when the spell was already off CD, i.e. it you use HoW > use another spell > it shows a 3rd spell instead of HoW, even though it will be ready by the time GCD ends.

after raid I even tried or (NAG:AuraIsActive(31884) and (NAG:SpellTimeToReady(24275) <= 1.5)) and NAG:Cast(24275) so a hard 1.5s window (ik it's dumb but for testing purposes). it showed HoW properly as every other spell most of the time, but from time to time it would still recommed something irrelevant, although HoW will 100% be ready. no idea why that happens tbh.

anyway sorry for wallspam, I don't mean to pressure or bug you, cause you already do so much for the community, I just had some free time and found it interesting. 😁

[sick flame]

OK i got my new keyboard and I'm looking at the APL now and inputting my tweaks

maybe I misunderstood you. What I mean is, your HOW CD needs to be short enough when hasted to do HOW every 2 casts instead of every 3 casts.

at least to my knowledge, because we had someone whose HoW was not ready because they were missing some haste and then when they got more haste they were suddenly able to cast HoW every 2 casts

the way it functions is that HoW should be recommended if it will be ready when GCD expires or in less than 200ms from when GCD expires

I'm not aware of the nuance of if GCD/CD scale linearly with haste from sanctity of battle

but I would assume that there may be some desync due to how sanctified wrath works

by cutting the base CD down to 3s

[sick flame]

what am I missing something? isn't the APL already supposed to work and recommend DS at 3hp with holy avenger up?

oh I guess it was if you had wings but NOT holy avenger

okay so this line is further down

or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(31884) and NAG:AuraIsActive(144595)) and NAG:Cast(53385)

and this line is higher up

or (((NAG:NumberTargets() >= 2) and ((NAG:CurrentGenericResource() == 5) or (NAG:AuraIsKnown(105809) and NAG:AuraIsActive(105809) and (NAG:CurrentGenericResource() >= 3)))) or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) and NAG:Cast(53385)

so there already is a line for if wings is active but it might just need some tweaking and moved up

no wait this further down line is JUST for t16

or (((NAG:NumberTargets() >= 2) and ((NAG:CurrentGenericResource() == 5) or (NAG:AuraIsActive(105809) and NAG:CurrentGenericResource() >= 3) or (NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3))) or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) and NAG:Cast(53385)

so i think this is the fixed line

actually needs a lil tweaking

okay there i think this should work

its just spaced out for me to read it easier

are you around to test an APL for me?

this seems to work just fine for me

all I did so far was the change for DS to work under 3HP during CDs

i didnt test if it was broken before but

this is very explicit and does work for me

havent found any issues with it

now im gonna add some of my other tweaks i had in the chamber

next tweak I am adding is for the APL to not go blank when everything is on CD but inquisition will be cast before anything becomes ready

or ((NAG:RemainingTime(84963) < NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(20271)) and NAG:CurrentGenericResource() < 3) and NAG:Cast(84963, 4.5)

woops used wrong variable

or ((NAG:AuraRemainingTime(84963) <= NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(20271)) and NAG:CurrentGenericResource() < 3) and NAG:Cast(84963, 4.5)

import string with both fixes

[sick flame]

so the only reason I can think for this is that somehow the prediction engine that allows "slack time" aka the numbers at the very end like 4.5 in this example above is not working due to some recent version

because in the HoW line it has slack time for 0.2s which means if HoW is going to be ready when gcd expires or within 0.2s of gcd expiring

maybe something changed in a recent version?

but it seems to be working just fine for me right now on live

[sick flame]

hmm this doesnt work in some scenarios

also for some reason GOAK is in the center instead of the right side

when I loaded this up stock (beta19)

GOAK should be on the left

the "pre-set" seems to be middle though

import string with all the tweaks so far

- no longer recommends judge over CS when the CDs are nearly the same but Judge is very slightly 0.01 shorter
- now recommends DS more explicitly when HP >= 3 and CDs are active instead of pooling to 5
- should now properly recommend Inquisition immediately when everything is on CD and Inquisition needs to be refreshed before other spells become active```

if anyone wants to help me test this out, new APL

@hallow canopy new APL that I am testing right now but seems to work good from my end with these fixes @scenic tusk

but also I need Guardian of Ancient Kings "pre-set" moved from middle to LEFT

for some reason it made its way back to middle again

[hallow crater]

@sick flame "now recommends DS more explicitly when HP <= 3 and CDs are active instead of pooling to 5"--> Shoulnt be >=3?

[sick flame]

Yes just a typo

Give it a shot

Test er out

[hallow crater]

Yeah sure. I’ll test in some celestials

[hallow canopy]

making this the new default!

[wanton lark]

yeah, with the haste formula applying the same way (ik it's not linear, but gcd can never go below 0.75s - but up until that point it should be the same formula, in theory). anyway, the testing I did was with baseline haste, and then with hero + wrath haste pot. in both situations HoW cd was always double gcd, and the bug happened regardless.

looking at the code for your rotation it all seemed logical to me, that's what was confusing. I'll be able to also test the new rota in a couple of hours, then I'll report back. thanks so much for looking into this.

[wanton lark]

there's still significant problems with the rotation. I recorded myself blindly following the addon display during AW, you can see HP to the left above mana bar, gcd below.

• at 12s you can see it recommends HoW then changes to CS for no reason mid-gcd, there's no situation where CS would ever be prioritised over HoW afaik, assuming they're both ready for next cast. note how it changes back to HoW the moment HoW is ready (instead of recommending it before it's off cd).
• immediately after, at 13s, it recommends judge (good), then CS (should be HoW) instead. then it changes HoW for the last few frames.
• then I use CS which brings me up to 3HP -> DS is recommended, but HoW is still ready to cast. spender should not be prioritised over HoW when at 3HP, instead it should be HoW to get to 4HP, then spender, then HoW again. I think your change to dump HP at 3 is fine but needs an exception for HoW.

a huge part of why Sanctified Wrath is so powerful is because of the ability to use HoW for every other cast. following the addon here I lost 3 cds where I could've cast HoW. you said you didn't have this problem on your end, I'm not sure what's different with my setup, as it happens with a fresh reset as well.

[hallow crater]

same position but only TV suggeste uring wings

after wings, it starts suggesting DS

DS>TV with 2+ targets right?

[hallow canopy]

time to death was bugged, which made dummies rotations bug out.

i just sent another beta please try again

[hallow crater]

beta 20?

[hallow canopy]

yes

[hallow crater]

now it looks OK guys

im sening new recoring in ummies

I nee a new keyboar too

[hallow crater]

@wanton lark how you see it?

[wanton lark]

in beta20, both the default rotation and the rota surv posted earlier still have the same issue. both on dummies and enemies. no idea why it looks different on my end.. I tried fiddling with random talents and NAG settings, nothing seems to change it. :/

[sick flame]

Dont forget to move preset GOAK to left!

[sick flame]

Might be an addon issue, on beta19 i cant replicate this

But i haven't updated to beta20

I wonder why Ramicie's is working but Beanlord's is not

Ramicie's wings rotation is literally perfect

[sick flame]

Delete NAG folder and reinstall? Or did you reset NAG?

All i can think of

And thanks yeah looking at the rotation logic it all looks okay-A to me

[hallow crater]

The mystery of the never shown synapse springs guys

It shows for other classes except retri!

[wanton lark]

I know, on his screen it's flawless! on mine it's the same even after a full reset. 😭 I'll try deleting and reinstalling the actual folder, perhaps that will work.

[hallow canopy]

is this the correct version?
for the sake of testing, try this one

also try the /nag reset all

[hallow canopy]

just did! will be live later todayu

[wanton lark]

mine was beta20 from curseforge, I tried your zip too but same bug. I tried /nag reset all multiple times, I even deleted by savedVariables .lua file, completely resetting the addon (had to enter a new license key and all). the addon is as tabula rasa as can be, but I'm afraid the bug happens no matter what.

the only things at this point that I suspect is some weird interaction with other addon (unlikely), or some weird character specific thing. @hallow crater do you mind posting your talent + glyph combo? also, do you have t16? if yes, can you unequip it and see if the rotation is still fine?

[wanton lark]

my guess is that the rotation simply needs to have NAG:Cast(126734) and 126734 under -- Tracked IDs for optimization. this is the correct ID for synapse springs, all the other class .lua files have it.

[sick flame]

Wait why doesn't paladin have it lmao

Is this why we havent had synapse this whole time

Smh

[sick flame]

It almost seems like your look-ahead isnt working

Its updating at the last second

Does your rotation have look-ahead values at the end of some lines?

Like NAG:Cast(20271, 0.2) means 0.2s of lookahead

Maybe there is a setting somewhere breaking it idk

I would assume so since you imported the string

[sick flame]

@scenic tusk @hallow canopy

[wanton lark]

yeah it has that, I'm always testing with the default rotation that the addon comes with and the one you posted earlier. I have a custom lag tolerance (aka input window) cVar, I'll try fiddling with it tomorrow after work. right now I'm out of ideas. 😅

[hallow crater]

Or SW+ES

[hallow crater]

Fiiiinally!!! That was weird!

@wanton lark

[hallow canopy]

@hallow crater @sick flame @wanton lark plz try this one (check for gloves)

[haughty relic]

Gloves working

[hallow canopy]

thanks!!

[hallow canopy]

bean, I faced a similar bug recently that i only managed to fix by deleting all saved variables related to the nag in the WTF folder. please open the WTF folder and do a control F, look for NAG

you have to CLOSE the game first

or else the game just restores them

so close it, delete all WTF files with NAG in their names, open again

[wanton lark]

I did that with just the NAG.lua in the savedVariables folder (renamed the backup too). I wasn't aware there were multiple files in the WTF folder! I'll try it when I'm back home later today, thanks mate

[wanton lark]

ok I quickly tested it before going to work - with all the files deleted, using your latest .zip file, still bugged, even if NAG is the only addon enabled. :/ even tried Ramicie's talent / glyph setup. super weird

[wanton lark]

also, spender at 3HP is still being recommended over HoW. instead, it should prioritise putting HoW on CD above everything else, ever, except inquisition, and then casting spenders at 4HP.

gloves are working fine though.

[haughty relic]

mine works fine now

im just having problem with keybinds not showing, but cba

[lucid pasture]

how can i fix gloves not showing on Nag?

[hallow crater]

@lucid pasture

[hallow canopy]

Will be another beta soon

[hallow crater]

o you think will be up for tomorrow mate?

you just inclue the synapse stuff right?

[winter creek]

is there anyway to remove arcane torrent from the rotation?

[hallow crater]

go to spell locations an change it to ignore

[hallow canopy]

yes, another beta will be out today

and hopefully that beta will be a release

[hallow crater]

Crossing fingers

[winter creek]

Thanks legend

[sick flame]

𝕵𝖊𝖘𝖚𝖘 𝕮𝖍𝖗𝖎𝖘𝖙 𝖇𝖊 𝖕𝖗𝖆𝖎𝖘𝖊𝖉

[sick flame]

It should already prio HoW above spender, iirc HoW is higher in the prio

But ill double check

[hallow crater]

Why you say casting spenders at 4hp?

[wanton lark]

because if HoW is ready when you have 3HP, you will want to cast HoW, which brings you to 4HP, then you spend so you can HoW on the next GCD.

[wanton lark]

I appreciate it. although at this point this could be caused by the same thing as my other HoW problem. i.e. I'm the only one who experiences it for some reason lol. so if it looks fine on your end and for others, then don't worry about it. I'll keep looking into it I guess.

[sick flame]

ES causes this

when you ES at 3HP it means afterwards you can spender or HoW is now ready again

its ideal to HoW before going back to spender though the diff is marginal over a fight length

so this would cause you to go to 4HP then spender to 1HP and repeat the cycle, spending at 4HP

because keeping HoW on CD is big, every 2 casts

well its not that big tbh but it does give an improvement

ive been considering rewriting my rotation guide to cover this explicitly in some way, like moving how to the top for sanctified wrath or something

but its pretty complicated due to how many diff scenarios you could be in

[hallow crater]

Yes true. I forgot ES

Then there is something I should improve

During wings

Normally ES is suggested at 2HP in my case

So I first how into ES into how so spender at 4hp yes yes

[sick flame]

so regardless it should recommend HoW after ES

and in my experience it has been

but ill have to dig into it a bit more

[hallow crater]

This works like you say in my case

[hallow crater]

Just checked my recording again and it’s like this

[wanton lark]

on my end it happens even if specced out of ES, or if ES already on CD. looking at the rotation code it makes sense - these are lines 14 & 15 (I added some comments). note that the HoW line comes after these 2 lines.

--LINE14 (DS)
    or (((NAG:NumberTargets() >= 2) and ((NAG:CurrentGenericResource() == 5) --[[C1: 2+ targets AND 5 HP ]] or (NAG:AuraIsActive(105809) and NAG:CurrentGenericResource() >= 3) --[[C2: holy avenger active AND 3+ HP]] or (NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3))) --[[C3: wings active AND 3+ HP]] or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) --[[C4: T16 proc AND 5 HP]] and NAG:Cast(53385) --DS
--LINE15 (TV)
    or ((NAG:CurrentGenericResource() == 5) --[[C1: 5 HP]] or (NAG:AuraIsKnown(105809) and NAG:AuraIsActive(105809) and (NAG:CurrentGenericResource() >= 3)) --[[C2: holy avenger active AND 3+ HP]] or (NAG:AuraIsKnown(90174) and NAG:AuraIsActive(90174) and (NAG:AuraRemainingTime(90174) < 4.0))) --[[C3: DP proc AND duration < 4s]] and NAG:Cast(85256) --TV

TV line (15) is fine, all 3 conditions justify using TV over HoW (if 5 HP / if avenger active / if DP proc about to run out).
the problem is in DS line, where you have NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3 condition, which does not justify using DS when HoW is available, as I understand it. (maybe a check for Sanctified Wrath is needed here, cause this would be irrelevant for people like Ramicie who are running Avenger)

    or (((NAG:NumberTargets() >= 2) and ((NAG:CurrentGenericResource() == 5) --[[C1: 2+ targets AND 5 HP ]] or (NAG:AuraIsActive(105809) and NAG:CurrentGenericResource() >= 3) --[[C2: holy avenger active AND 3+ HP]] )) or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) --[[C4: T16 proc AND 5 HP]] and NAG:Cast(53385) --DS
    or ((NAG:CurrentGenericResource() == 5) --[[C1: 5 HP]] or (NAG:AuraIsKnown(105809) and NAG:AuraIsActive(105809) and (NAG:CurrentGenericResource() >= 3)) --[[C2: holy avenger active AND 3+ HP]] or (NAG:AuraIsKnown(90174) and NAG:AuraIsActive(90174) and (NAG:AuraRemainingTime(90174) < 4.0))) --[[C3: DP proc AND duration < 4s]] and NAG:Cast(85256) --TV
    or (NAG:IsExecutePhase(20) --[[C1: execute phase]] or NAG:AuraIsActive(31884)) --[[C2: wings]] and NAG:Cast(24275, 0.2) --HoW
    or (NAG:NumberTargets() >=2) and (NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3) and NAG:Cast(53385) --DS C3: wings active AND 3+ HP, moved after HoW check

what I did here was move the condition out of line 14 and put it in a new line for DS so that this condition comes after HoW but the rest remain as they were. seems to work fine on my end after a quick test.

[sick flame]

how do you color the code like that

i've never known how to do that

but it looks so crisp

i would've had a much better time reading the rotation code if I had it colored like that

@scenic tusk @hallow canopy would be a fantastic fucking feature in-game

[scenic tusk]

ya, i was bonna ask it to do that earlier 🤣 i'd made a enhanced one but it wasn't that enhanced. was gonna add tab completion etc

[sick flame]

let me look at the rotation I used as the foundation

in the MoP sim

so Hammer of Wrath is indeed above everything here, unless it's 5HP

[scenic tusk]

the AuraSet shit should be working now for trinkets if paladin uses them, test em out

[sick flame]

so if HoW is properly at the top in my rotation on wowsims, which I parsed

above 3HP finishers

why is it not at the top in yours though

or how did it get moved down

cause this is literally the rotation I parsed originally

and I don't think I've ever reordered anything

maybe we are getting to the root of beanlord's issue

where his rotation is seemingly different than everyone's

in multiple ways

let me log into game

and check my end

okay maybe not

it's true, HoW is lower, but I'm not sure HOW it got moved down

maybe I fucked that up at some point but idk how i've never reordered anything to my knowledge

I can push an APL update right now

oh I know what happened

[scenic tusk]

more i fuck with this more i dunno htf to get it to lay out nicely 😛

[sick flame]

there is separate actions for 5HP and 3HP in the sim, at some point they got combined, probably when I did these DS changes recently

[scenic tusk]

not sure if that or text would be easier haha

anyways, gn 😛

[sick flame]

that's the crux of the issue

but I have no memory of it

so I just need to separate them again

and move HoW above

but leave it below the 5HP

okay I'll fix rq

[sick flame]

I have an APL update for next version

but you can do it in the morning or whatever

[scenic tusk]

ping fonsas, he's doing apl updates mainly

he just woke up

figure easier if one person does it so we don't step on each other toes

i think i removed jiw's cause i thought it was from cata.. we relaized last week lol

oops 😛

[sick flame]

@hallow canopy

[scenic tusk]

@hallow canopy

😛

GN gonsas

fonsas

lol

i'm gonsas

[austere meteor]

I'll help yall out he'll think nag on fire @hallow canopy (don't hurt me lord fonsas)

[sick flame]

so apparently I introduced this bug with the most recent APL update

so it's only been there for a few days and it's very marginal

since it's just one specific moment during wings where you are doing spender where you should do HOW

its pretty damn marginal

but I have a fix in a sec

just separating 5HP from 3HP spenders once again

-- 5HP DIVINE STORM
        or (NAG:NumberTargets() >= 2) and (NAG:CurrentGenericResource() == 5) and NAG:Cast(53385) 
-- 5HP TEMPLAR VERDICT
        or (NAG:CurrentGenericResource() == 5) and NAG:Cast(85256) 
-- HAMMER OF WRATH, 0.2s SLACK
        or (NAG:IsExecutePhase(20) or NAG:AuraIsActive(31884)) and NAG:Cast(24275, 0.2) 
-- 3-4HP DIVINE STORM
        or (((NAG:NumberTargets() >= 2) and ((NAG:AuraIsActive(105809) and NAG:CurrentGenericResource() >= 3) or (NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3))) or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) and NAG:Cast(53385) 
-- 3-4HP TEMPLAR VERDICT
        or ((NAG:AuraIsKnown(105809) and NAG:AuraIsActive(105809) and (NAG:CurrentGenericResource() >= 3)) or (NAG:AuraIsKnown(90174) and NAG:AuraIsActive(90174) and (NAG:AuraRemainingTime(90174) < 4.0))) and NAG:Cast(85256)```

updated lines

idk how to color it all fancy

but that's my fix

APL UPDATE - RETRIBUTION MOP

extremely marginal bugfix:
-- should fix a bug introduced with the last APL that causes 3-4HP spenders to be recommended before Hammer of Wrath```

testing this APL, but @hallow canopy we also need synapse spring fix in the class lua file if you didnt already post that to beta21

the APL seems to work properly on my end, just tested with sanctified wrath

it recommends HoW over 3-4HP spenders.

thanks to @wanton lark for bringing this bug to my attention

he's done wonders in the past few days finding little mistakes here and there

still waiting for him to tell me how to change the color of text in a codebox on discord 😛

oh I see

you just invoke that it's lua code at the top of the codebox?

or NAG:Cast(53385)```

omg it WORKS

how did I never know this

-- 5HP DIVINE STORM
        or (NAG:NumberTargets() >= 2) and (NAG:CurrentGenericResource() == 5) and NAG:Cast(53385) 
-- 5HP TEMPLAR VERDICT
        or (NAG:CurrentGenericResource() == 5) and NAG:Cast(85256) 
-- HAMMER OF WRATH, 0.2s SLACK
        or (NAG:IsExecutePhase(20) or NAG:AuraIsActive(31884)) and NAG:Cast(24275, 0.2) 
-- 3-4HP DIVINE STORM
        or (((NAG:NumberTargets() >= 2) and ((NAG:AuraIsActive(105809) and NAG:CurrentGenericResource() >= 3) or (NAG:AuraIsActive(31884) and NAG:CurrentGenericResource() >= 3))) or (NAG:AuraIsKnown(144593) and NAG:AuraIsActive(144595) and (NAG:CurrentGenericResource() == 5))) and NAG:Cast(53385) 
-- 3-4HP TEMPLAR VERDICT
        or ((NAG:AuraIsKnown(105809) and NAG:AuraIsActive(105809) and (NAG:CurrentGenericResource() >= 3)) or (NAG:AuraIsKnown(90174) and NAG:AuraIsActive(90174) and (NAG:AuraRemainingTime(90174) < 4.0))) and NAG:Cast(85256)```

so the lines look like this now

it seems fine to me right now, but it's late, so maybe I am missing something

it works ingame for me too

I just for some reason combined the 3-4HP spenders and 5HP spenders at some point and somehow have no memory of it

not sure why

oh wait I have one more small tweak to make

no wait

the t16 is fine the way it is

no need to tweak

i think

or at least we can cross that bridge when we get there

[hallow crater]

Thank you guys. I’ll test this in raid today

[hallow canopy]

I panicked a bit

wtf hapening

hahah

[hallow canopy]

i did it already yesterday!

should be there on the latest beta

[hallow canopy]

making this be default!

[hallow crater]

just seen beta 22, is that one mate?

[hallow canopy]

not yet

im sending it now, should be live in 15 min

[hallow crater]

ah ok ok

ty!!!

[sick flame]

Thanks babe 💋

[sick flame]

Just an APL update. Also I found out how to make my code block syntax colorful, by telling Discord it is Lua code

Also would be great if a feature like that was added to ingame rotation editor

So much easier to read

[wanton lark]

haha sorry, I went to bed after that, yeah you just add the programming languange at the top of the code block and it will highlight syntax accordingly. 😁 I can't read the in-game editor at all, I just copy and paste the code into my JetBrains IDE, but those cost money. try visual studio code, it's free, good, and highlights lua.
a BiS feature for the in-game editor would be the ability to see spell names next to IDs or sth similar. now I just have a .txt with all the IDs that I have to ctrl+F. x)

also, beta23 works like a dream, well done and thanks for the update.

I also found a (sort of) workaround for my previous rotation bug, where HoW would show up only at the last nanosecond before it's usable, instead of displaying as the next action properly.

I cranked up the input delay setting from 0.1 (default) all the way to 1. and now HoW seems to appear a lot earlier. it's still a bit glitchy, but this gives me more time than before, so the add-on is finally not trying to trick me to judge or crusader strike above HoW all the time. 😁

not sure why this helps, or what exactly this setting does, the tooltip isn't very specific, but it made the rotation feel a lot more fluid, without the icon jumping from one choice to another last second like it can't make up its mind.

[hallow canopy]

so you just want to wait on HoW for longer than 0.2 secS?

you dont have to tweak that

i think that will hurt more than help

[hallow crater]

Let me test beta 23

[hallow canopy]

or (NAG:IsExecutePhase(20) or NAG:AuraIsActive(31884)) and NAG:Cast(24275, 0.2)

that is HoW

0.2 says it adds a tolerance/wait of up to 0.2

change that

it will get stuck on HoW much earlier, making you wait for it

[hallow crater]

That is my feeling as well

[hallow canopy]

you mean, that it should get stuck on it much earlier?

Sims and surv wanted it to wait just up to 0.2

[hallow crater]

I dont think so

But he just mentioned it worked for him, based on the issues he had right?

The rest I think we didn’t have that issue

[sick flame]

yeah idk why I never thought of just copy pasting it into Vistual Studio Code

[sick flame]

I am very, very, VERY happy to hear that all the issues on your end are finally gone, and that the APL is up to spec

I can relax for the rest of Phase 1 now (:

thank YOU for the wonderful insight that has helped us fix these issues.

it is truly appreciated because I have been so ridiculously busy with work this past month I have barely even played the game, let alone work on the NAG

and I have been so damn tired that I thought I could just combine 5HP spender line with 3-4HP spender line apparently with no ramifications, and have no memory of it

so my mistake definitely shining through there

luckily it was a very, VERY marginal bug

@NAG Retribution users - Mists of Pandaria

Please update to Beta28 or newer, it is our best version yet!

The most optimized rotation so far, with some improvements even the simulator doesn't have, along with Synapse Springs fixed, and numerous other bugfixes + optimizations! It currently has no known issues, at least, on the rotation side of things.
This is likely to be the final Retribution update until Phase 2, excluding any bugfixes that present themselves as being necessary in the coming weeks.

I can't actually tag them

I don't have the permissions

[sick flame]

it currently has no known issues! at least, on the rotation side of things

[hallow crater]

thank you guys for all the work

much appreciate it

thats the way!!!

[sick flame]

#1347562002306043977 message

CHANGELOG

[sick flame]

thanks for subscribing to NAG premium!!!

you guys paid for it, so we put in the hours

https://www.curseforge.com/wow/addons/nag/files/6906676

I am finally comfortable enough to do another big advertising post in Light Club

I will get some good footage, if anyone wants their footage to be in the NAG promo for Light Club, post your footage using the new NAG version here!

[sick flame]

right

[hallow crater]

aghhhhh synapse is not visible to me even in beta 24

🙁

[sick flame]

Looks like we are beta27 already

but everything beta23 or newer should be good

I doubt anything else has changed for Paladin in those newer versions

[sick flame]

go to 27

link above

its working for me

is the spellid in your .lua file? for paladin

paladin.lua or whatever

[hallow crater]

where can fin this?

[sick flame]

C:\Program Files (x86)\World of Warcraft\_classic_\Interface\AddOns\NAG\Mists\Classes\Paladin.lua

You should have 126734 spellID listed here

that was the recent fix

you can see it is the last one here

https://www.wowhead.com/mop-classic/spell=126734/synapse-springs

that's the synapse spellID

[hallow crater]

I o

[sick flame]

let me double check the APL

maybe I'll add a duplicated line with old spellid and new spellid

in the rotation

so higher prio is the new spellid

[hallow canopy]

it doesnt show right at the start, keep sending the rotation

[sick flame]

lower prio is the old spellid

just in case anyone has the old spellid

yeah synapse can show at a lot of different places

[hallow crater]

it never shows

[sick flame]

depending on your talents etc

[hallow canopy]

https://tenor.com/view/curse-gif-21856580

let me check that again

[hallow canopy]

did you do a reset all? dont run any old rotations, get back to default

[sick flame]

@hallow canopy something I've noticed

the rotation editor is super buggy for 16:10 resolutions

I am frequently in 2304x1440 or 1728x1080 which are 16:10

because my Steam Deck is 16:10 and I often stream to my steam deck

just something I've noticed

[sick flame]

trying to copy paste is like impossible on 16:10

[hallow crater]

I also remove NAG lua files

[onyx wolf]

You need to either alt click or open the /nag options and drag it around from there.
If you need further assistance, contact a mod/dev.

[hallow canopy]

we suck handling UI, sorry. never been our forte

we try hahah

[sick flame]

    ((not NAG:AuraIsActive(31801)) and (NAG:NumberTargets() <= 3)) and NAG:Cast(31801)
        or ((not NAG:AuraIsActive(20154)) and (NAG:NumberTargets() >= 4)) and NAG:Cast(20154)
        or ((not NAG:AuraIsActive(20154)) and (not NAG:AuraIsActive(31801))) and NAG:Cast(31801)
        or (NAG:AuraIsActiveWithReactionTime(2825) or (NAG:RemainingTime() <= 40.0) or (NAG:AuraIsActive(86700) and NAG:AuraIsActive(31884))) and NAG:Cast(76095)
        or (((not NAG:AuraIsActive(84963)) or (NAG:AuraRemainingTime(84963) <= 2.0)) and ((NAG:CurrentGenericResource() >= 3) or (NAG:RemainingTime() < (NAG:CurrentGenericResource() * 20)))) and NAG:Cast(84963)
        or NAG:AuraIsActive(84963) and NAG:Cast(31884)
        or NAG:AuraIsActive(31884) and NAG:Cast(86698)
        or (NAG:AuraIsActive(84963) and (NAG:CurrentGenericResource() <= 2) and NAG:SpellIsKnown(105809)) and NAG:Cast(105809)
        or (NAG:AuraIsActive(84963) and ((not NAG:AuraIsActive(86700)) or (NAG:AuraNumStacks(86700) == 12))) and NAG:Cast(82174)
        or NAG:AutocastOtherCooldowns()```

this is the current APL

[wanton lark]

line 9 has the old synapse springs ID, probably safe to remove since nobody is gonna use the Cata version?

[sick flame]

it still uses the old spellid 82174

but @hallow canopy

you told me

that the ID gets translated into the name anyway

so it shouldnt matter whether its the old id or the new id

right? you said this to me before

last time I inquired about this

but I can just duplicate the line 1 line up

and add the new spellid

[hallow canopy]

it does, but who knows this one in particular is buggy i guess

[sick flame]

so I will do this

I will add this line

[hallow canopy]

change that for ramizie

@hallow crater change the line

[sick flame]

        or (NAG:AuraIsActive(84963) and ((not NAG:AuraIsActive(86700)) or (NAG:AuraNumStacks(86700) == 12))) and NAG:Cast(126734)```

[hallow canopy]

that!

[sick flame]

I will add this line, right above the OG synapse (old id)

so it should work

for both

newer = higher prio

[hallow canopy]

yeah good call

❤️

[sick flame]

now if only I could edit the damn rotation

on my resolution lol

im telling you its broken af

on 16:10

wherever you click, it goes somewhere else

same for copy paste

its like misaligned

[hallow canopy]

what is it you see?

[sick flame]

when I click a line to copy paste

it actually copies a diff line

when I click to put my cursor somewhere in the rotation and start typing

it goes to the wrong place

its an aspect ratio issue

[hallow canopy]

thats wild HAHAH @scenic tusk was touching that yesterday. Rak HELLP

[sick flame]

and/or resolution issue

it's been like this for a long time

tbh

idk how many people play in 16:10, it's not that common, but it's not uncommon either

and I'm using a custom resolution for 1080p/1440p resolutions in 16:10

[hallow canopy]

OHHHHH YEAH i see that on other addons too!

[sick flame]

so I'm using 2304x1440

and 1728x1080

[hallow canopy]

true true true

[hallow crater]

how? sorry im so noob for this, I only unerstan SAP LOL

[sick flame]

these are custom resolutions

to get the full amount of vertical rows on 16:10

instead of stretching

[hallow canopy]

i use chat copy/paste addon a lot and i see invisible lines a lot

[sick flame]

for 1080p/1440p

so if you try to edit rotation in 16:10

you have to switch to 16:9 and reboot game

[hallow canopy]

maybe something we could tweak with ace

[sick flame]

to get it to work

you just need some sort of UI scaling support

for this aspect ratio

[wanton lark]

no, that is not what I'm talking about. I showed in the video already what happens - 2 spells like CS and HoW will be ready for the next gcd, but CS is shown for the entire GCD swirl animation, and changes to HoW only when it's ready. it should pre-display HoW since it will be ready at the same time.

anyway it seems like I'm the only one getting this bug despite installing NAG completely fresh with everything reset.

[sick flame]

it's a UI scaling thing

actually you know what

[hallow canopy]

yeah that should never happen. let me look for this

[sick flame]

its bugging even on 16:9

it's not unique to 16:10

no wait

im stupid

ignore

i forget to change res lol

2304x1440 is damn near the same as 2560x1440

[hallow canopy]

https://tenor.com/view/homer-simpson-gif-18107776837214963761

[sick flame]

hard to tell sometimes

[cunning lance]

after my second aw ends it still show HOW to be casted when it cannot be casted in the latest version

[sick flame]

on my 27 inch

[sick flame]

beta27?

[cunning lance]

yes

[wanton lark]

I posted a video earlier to show exactly what happens, but it only seems to happen to me and not others, so idk how to even investigate at this point.

[hallow canopy]

try on real mobs

[sick flame]

yeah try on a real mob

not a dummy

[hallow canopy]

nag is simulating a fight for you

[sick flame]

its prob the dummy isExecute thing

[cunning lance]

haha was using a dummy ok

[sick flame]

bugging out on the dummy

[cunning lance]

ic ok

[hallow canopy]

it was enough info. i will check now

[sick flame]

        or (NAG:AuraIsActive(84963) and ((not NAG:AuraIsActive(86700)) or (NAG:AuraNumStacks(86700) == 12))) and NAG:Cast(126734)
        or (NAG:AuraIsActive(84963) and ((not NAG:AuraIsActive(86700)) or (NAG:AuraNumStacks(86700) == 12))) and NAG:Cast(82174)
        or NAG:AutocastOtherCooldowns()```

the new line added for synapse ids

[hallow crater]

can I import this one mate'

[sick flame]

if you have mark 2 synapse (which I actually do not have yet)

(i know, laugh at me)

then please import and test synapse

[hallow canopy]

is this the video?

[sick flame]

well he said it was fixed on beta23

earlier

im not sure why its broken again for bean

[hallow canopy]

@hallow crater

[hallow crater]

shall I reset all after importing?

even the belt slot is not working

[sick flame]

tbh i am still having issues with it on 16:9

you can work around it

you just gotta figure out how misaligned you are

or copy extra text, hoping to get the part you want

and just do the editing outside of the NAG ingame

but it is very annoying

maybe you could fix that while you add the Lua syntax color-coding (:

[sick flame]

im not sure honestly

you can try it

as long as you have the rotation imported

[hallow canopy]

no, use the one you imported

[sick flame]

you can also try deleting the NAG folder

and reinstalling newest beta

then import and go again from there

that rarely fixes random bugs for me

a "clean install" so to speak

[hallow canopy]

he should be fine, he imported a new rotation and its active

@hallow crater test gloves brothaaa

[sick flame]

but yeah i am a major slacker

dont have mark 2 synapse springs yet

i havent even raided yetr

[hallow crater]

not working

also the exo bin was lost

[hallow crater]

with this I mean

[hallow canopy]

what bin?

whats bin

[hallow crater]

bind

[hallow canopy]

what is an exo bin

[hallow crater]

exorcism

[hallow canopy]

oh yeah it needs reload

[hallow crater]

ok that is solve

also I ont see GOAK suggeste anywhere off Cd

[hallow canopy]

it will pop to the right

[hallow crater]

I see it efault on left

[hallow canopy]

have you got the old WA?

[hallow crater]

but oes not appear

[hallow canopy]

plz post a full video. I just debugged all functions, they all behave as expected

like record your whole screen and pin point when it happens

so i can check all conditions/state

[hallow crater]

lemme try clean install first

[hallow canopy]

RAMI RAMI

dont drive me crazy rami

let me try again on another toon

1 sec

importing the rotation again

[hallow crater]

sure sure

I have remove the NAG foler but I still see it as installe in curse??

[onyx wolf]

You need to either alt click or open the /nag options and drag it around from there.
If you need further assistance, contact a mod/dev.

[hallow canopy]

waiting forever

again rami

@hallow crater

[hallow crater]

again what sorry?

[hallow canopy]

it showed again

just had to burst

[sick flame]

if you're using the curse app, i have no idea how it works

but I install my addons manually

just delete the NAG folder and reinstall it manually

extract the folder to interface/addons

[hallow canopy]

OHHHHHH Curse app take a day to update!

[sick flame]

that solves it

[hallow canopy]

install manually

[hallow crater]

hmmmmmm

shall I clean install again?

[hallow crater]

in curse?

[hallow canopy]

from the link in #🌟｜nag-updates

[hallow canopy]

that ddidnt have the double gloves line

i added it

here

[sick flame]

thats my export

looks to be the same?

[hallow canopy]

yes, i might have clicked the wrong on ethen

yeah theres no double gloves here, right?

[sick flame]

wait

why isnt it exporting the double gloves line

[hallow canopy]

idk HAHAHAHAH maybe your buged out UI

mine had it

[hallow crater]

I have manually installe beta 27

nothing ifferent

[sick flame]

oh i didnt hit save

lol

[hallow canopy]

now you improt the string

[hallow crater]

which one?

[sick flame]

this string

[hallow crater]

ok this one

lemme try

[sick flame]

i forgot to hit save lol

when i added the double gloves line

[hallow crater]

hahaha

[sick flame]

@hallow canopy that might be a problem for latest release

check it has the line

let me check actually

oh there is no newer release

than beta27 still

it hasnt come out yet

ok

beta28 will have it tho

as long as you use this string fonsas

[hallow canopy]

ok ill send another one

[sick flame]

right there

[hallow canopy]

confirmed gloves on your end? my ret is boosted, no engineering

[sick flame]

i onlyhave mark 1

they work

i dont have the new version

@hallow crater will have to test this string

[hallow canopy]

https://tenor.com/view/sussa-gif-5432297967573209335

[cunning lance]

if i am using beta27 do i still need to manually import or i can use default paladin rotation

thought it was updated

[hallow canopy]

Imagine ramicie telling us he forgot to enchant his gloves

[hallow canopy]

we are just updating the update

[cunning lance]

thanks sir. so i should import for now yeh

[hallow canopy]

ty!

[hallow crater]

guys, all G

[hallow crater]

noooooooooooooo hahahaa

[hallow canopy]

https://tenor.com/view/nacho-jack-black-awkward-gif-4691467854324958416

[hallow crater]

[hallow canopy]

@sick flame sending it

[sick flame]

ty ty ty

thanks @hallow crater

and @wanton lark

please update to beta28 at your earliest convenience

it has the new synapse springs line in the APL

should work mark 1 and mark 2

thats the only change

[hallow canopy]

bot decided to name it 25 again

[hallow crater]

but why GOAK oes not show on the left?

WTFFFFFFF

[hallow canopy]

mine show as soon as i wings

[hallow crater]

I have a macro

wings + goak

so first wings it pops

[hallow canopy]

then it will never show, Gok waits for wings

in the APL

a macro works

[hallow crater]

in secon wings GOAK is still on cd

but it does not shows up while wings is on cd an GOAK is off cd

[hallow crater]

that means its not recommen to cast GOAK without wings then?

there is 1 min Cd ifference

[hallow canopy]

that you ask surv my friendo

nag shows as he intended

[hallow crater]

yes yes its ok

I will ownloa beta 28 an ill manually install it!!

so the efault shoul be ok

ty bro

[hallow canopy]

its actually called 25 now

555-25

[sick flame]

bro this bot is killing us

lol

[hallow crater]

hhaha

[sick flame]

you gotta tame that bitch

[hallow canopy]

it did correct hahaha

[sick flame]

I just edited all my advertisements about the new version to say beta28

what am i supposed to do now

[hallow canopy]

i can rename it

HAHHAAH

let me rename it

[sick flame]

"please install the new version of NAG, beta25, not the bottom one though, make sure its the top one, the new one, there's two 25s"

just make it an official release

at this point

[hallow crater]

🤣

[sick flame]

5.5.5

whys it still beta

anyways

28 betas is enough bro

SEND IT!

[hallow canopy]

hahahah thats true

[sick flame]

also, just a side note but, we gotta chill w/ these constant updates

[hallow canopy]

will send it

[sick flame]

there has been like 7 this morning

I mean I know I have gotten slightly exhausted keeping up with it, troubleshooting people who are all using 10 diff versions from the last 7 days

maybe just slow it down now for a bit

if there's an APL update, just let people import the string for a few days

[hallow canopy]

hahaha thats the idea, but we still have to fix some other classes

[sick flame]

until there's something good to publish etc

[hallow canopy]

makes sense

[sick flame]

word well I'm hoping sometime soon yall can sit back and relax until phase 2

yall been going ham as fuck

paladin should be done now

until phase 2

[hallow canopy]

❤️

hell yeah

[sick flame]

unless some new issue crops up

set it and forget it, we ride until phase 2

honestly we might not even need to update the APL for phase 2 at all

the APL is already setup as far as t16

the only reason might be to hardcode some active trinket on-uses if they dont get popped with wings

[wanton lark]

I will find more bugs for you Surv, don't worry. 🙂

also, guys, I had beta25 and everything was working fine, but then I updated to beta25 and my exo disappeared, wtf? hopefully it's fixed when you release beta25, cause I don't want to revert to beta25 again.

[wanton lark]

I posted a video earlier, but I'll do a new video a bit later on the latest beta and the APL monitor open, if that helps.

[cunning lance]

beta 28 is showing no options

[hallow canopy]

you most likely have a lua error somewhere, try /nag reset all
then enable lua errors via using this command:

/console scriptErrors 1

Once you're done reporting a problem, and no longer wish to see error messages, feel free to disable them with this command:

/console scriptErrors 0

[cunning lance]

still showing the same thing after reset sigh

can i report the lua errors somewhere?

[hallow canopy]

im sending another one

[sick flame]

Beta28

[hallow canopy]

im sending another 28 in a few

[sick flame]

Kk

Smh you make one post in paladin classic discord, a place you've contributed for years

Telling NAG users to update

And this is the thanks you get!

[hallow canopy]

sent again, free of bugs

will be live in 3 min

[hallow canopy]

new 28 now live, should be visible in 1-2 min

[wanton lark]

advertise hekili to balance it out. 🤣

[harsh kraken]

Don't listen to them. You get a weed every now and then saying either that or that they don't trust the sims. Every time I see those kind of comments I just cringe.

Some people just don't respect the time and effort others put to make the class and the experience better.

[hallow crater]

shall we remove 555 beta 25?

[hallow canopy]

I removed the old one

[hallow crater]

this is what it downloads from 554 beta 28

[hallow canopy]

Aw fuck me

Let me edit again

Just rename it NAG

wait im not crazy

[hallow canopy]

https://www.curseforge.com/wow/addons/nag/files/6907157

[hallow canopy]

Tell them I didnt pay. Your advertising just bcs its good hahah

[sick flame]

Lol

He sells WAs too...

[harsh kraken]

Here is something more like a want, rather than a need.

The weakaura on AOE is showing CS while on CD and switching back to HoR as soon as it comes off CD

Also, is it possible to add the GCD to the Light's Hammer/Execution Sentence Icon in the NAG? I think this is the only Icon that pops up without it

[wanton lark]

OMG I'm not crazy! someone else is having the exact same issue as me! this has been driving me nuts and nobody else reported this problem until now. do you have the same issue with other spells, like HoW during AW? @hallow canopy

[harsh kraken]

The issue where it prioritizes CS or Judgment over HoW during AW? Yes

I’m just noticed in the first dungeon I did after the update. I think I didn’t have that issue before

But I’ll do some more testing to confirm

[wanton lark]

yeah that was my main issue, I didn't even notice the HoR problem until you mentioned. tested it and yea, happens to me in the same way as your video shows.

[harsh kraken]

How did you know? It is just a 2sec video 😂

[wanton lark]

bro I've been trying to debug this for 2 days now 😭 haha just the general behaviour of 2 spells being usable in next gcd, but display shows the correct one only after it's ready to use. i.e. it doesn't seem to know that HoW / HoR will be usable soon, so recommends the next best thing.

[harsh kraken]

Do you know how to open up the window to see the logic while in combat?

Where it highlights the logic that is using for the next cast?

I think they changed the options menu and now I can’t find it

Found it

[wanton lark]

@hallow canopy here's the video I promised mate, would appreciate if you had a look when you have a moment.

• at 0:12 recommends CS after using DS. HoW will be ready for next cast. then changes to correct recommendation (HoW) only after GCD and HoW CD is done. seems like it's exact moment, not 0.2s, or gcd+0.2s before it's usable.
• same situation at 0:18.
• at 0:23 it recommends judge after DS, changes to correct recommendation at the last second.

I hope this is helpful, let me know if you need anything else.

@harsh kraken btw if you want a "band-aid" fix for now, try cranking this up to max on the main settings screen. for me it feels a bit better that way.

[harsh kraken]

Same thing is happening to me in 0:20, 0:25 and 0:31

also, can you make the APL monitor shorter by default? I couldn't find the bottom on my screen to adjust the size

[scenic tusk]

man your AI smokes crack dude 😛 htf it find 5.5.5 out of nowhere 🤣 😛

[hallow canopy]

It was technically your ai hahah

[hallow canopy]

Will check this when im home!!

Tyty!

[scenic tusk]

my AI shares it's crack with me though so it's ok!

[hallow canopy]

Mine is just tired bcs of his kids, then hahahah

[austere meteor]

#6.6.6 version next from bot the devil update where the nag ai takes over

[copper rune]

more of a headache, installed the newest beta 28, did a /nag reset all, and synapse springs still doesn't show

after changing the settings to show it

[vague elm]

It doesn't shows for me either, even after clean reinstall/etc

[hallow crater]

Have you tried to install manually?

This solved the issue in my case

[jaunty jay]

anyone know why NAG doesnt suggest synapse OR execution sentance?

[hallow crater]

Which version you have installed?

[jaunty jay]

how do I check?

checked curse and it says latest version is v5.5.3

[hallow crater]

Download the file manually

And do a clean install

[hallow crater]

Seems like you are in an old version

[haughty relic]

i really wanna have the option to remove synapse

with the new updates its not possible

even when im trying to go swap it a few times like before

[copper rune]

have done all the things and no dice on synapse springs, even going back to beta 24 that was supposed to fix it, tried manually installing and every time after a reload did a /nag reset all for good measure

[hallow crater]

Can you please check something?

[copper rune]

sure

[hallow crater]

Go dummy and do the following: CS-judg-exo-inq-wings

Wings without macro

And let me know if gloves shows up on the left

After pressing wings

Synapse on pala does not show in the same way as other classes

[copper rune]

no dice

forgot to check the tings in class and going to try again with them cheked in a minute

no dice with it checked

so I've noticed ES gets suggested when dancing steel procs also, which makes sense because it's a str proc

could that be interacting poorly with synapse?
I have another wep without dancing steel I can check

[hallow crater]

no

ES starts suggesting at GOAK 12 stack

[copper rune]

correct, it goes away after I pop GOAK until it hits 12 stacks

but on pull it'll show up if dancing steel procs, which it almost always does

[harsh kraken]

Not a bad update

[sick flame]

okay this is an easy fix

at the bottom there are "look-ahead" lines

I just need to add one for hammer of the righteous

I'll post the APL shortly.

The lines at the bottom compare the CDs of various abilities against each other to determine what your next spell is going to be when everything is on cooldown.

There is a CS line, so it predicts up to 4.5 seconds out.

But there is no HotR line, easily fixed.

Give me 5-minutes and I'll post you an import string

@wanton lark

okay so there is a HotR line already but it has no target count check

ill add one and see if that fixes it

-- HOTR look-ahead
        or (((NAG:NumberTargets() >= 4) and (NAG:SpellTimeToReady(53595) <= NAG:SpellTimeToReady(20271) and NAG:SpellTimeToReady(879))) and NAG:CurrentGenericResource() < 5) and NAG:Cast(53595, 4.5)
-- CS look-ahead
        or (((NAG:SpellTimeToReady(35395) <= NAG:SpellTimeToReady(20271) and NAG:SpellTimeToReady(879)) and (NAG:NumberTargets() <= 3)) and NAG:CurrentGenericResource() < 5) and NAG:Cast(35395, 4.4)
-- Judge look-ahead
        or ((NAG:SpellTimeToReady(20271) < NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(879)) and NAG:CurrentGenericResource() < 3) and NAG:Cast(20271, 4.3)
-- Exo look-ahead
        or ((NAG:SpellTimeToReady(879) < NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(20271)) and NAG:CurrentGenericResource() < 3) and NAG:Cast(879, 4.5)
-- Inquisition look-ahead
        or ((NAG:AuraRemainingTime(84963) <= NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(20271)) and NAG:CurrentGenericResource() < 3) and NAG:Cast(84963, 4.5)```

wait it already has one

maybe it just needs moved up

the condition that is

I will also change the HP check to 5 for these

that might also be something causing this

Try this @wanton lark @harsh kraken

see if that fixes the HotR issues

[hallow crater]

Yesterday I had raid and I was paying attention to this issue on first boss. This didn’t happen to me. No CS was suggested at all but hotr

[wanton lark]

yes, we've established that it doesn't happen to everyone for some reason, we just don't know why.

[hallow canopy]

maybe surv should remove this like from the APL
or NAG:PlayerName == 'Beanlord' and NAG:BreakRotation()

im into this now

[hallow canopy]

for the sake of me i cant replicate this

i will prob send you a version with a shit ton of prints so you can copy the log and send me when it hapens

[hallow canopy]

can you check something for me.. plz remove the tolerance from your HoW casts

no bug brothas!!!! i think this is exactly as intended with the 0.2 delay

you see, the GCD is being ready BEFORE the spell is ready. it changes to HoW becaus only then the 0.2 tolerance made sense..

you guys probably have slightly faster haste than everyone else

and are triggering this effect

lets make it like that

let me do some APL magic

@harsh kraken @wanton lark plz try this one

all i did was change this line from 0.2 to 0.35 so you guys can spam the spell
or (NAG:IsExecutePhase(20) or NAG:AuraIsActive(31884)) and NAG:Cast(24275, 0.35)

maybe you could go for even more

as you can queue the spells earlier

another possible fix would be to make sure this hardcoded time/tolerance is haste effective

i mean, if we make haste change the tolerance so that it now fits what the difference would be so that you wait for HoW every 4 GCDs, so to say

in my tests i cant replicate this bcs my HoW has REALLY CLOSE CD so that it will be ready/shown in every 4 GCDs i cast

my gcd is 1.432

this is lower than 0.2

then ill be prompt HoW

what i mean is.. 4 GCDs for me are 5,728 secs

plust the 0.2 added as tolerance, would be 5.9.. im safe

makes sense?

i mean. i can make 0.2 be a variable not a constant there. so that it covers your difference and you have important spells prompted bcs now they have a sligtly higher tolerance

@sick flame if this is true, this MIGHT also reflect to a better simmed values in wowsims

for instance, if you compare a piece of gear that puts you bellow the haste threshold, even thought the piece is actually better it would perform worse just because it missed HoW by not waiting an extra 0.1 secs for it

@wanton lark that also explains why you were able to fix by increasing your imput delay

[wanton lark]

how are you calculating your GCD? afaik /dump GetSpellCooldown(<ID>) would show the remaining cooldown for a spell, not the total.

[hallow canopy]

it always show the start time and the total. second argument it the total

i reforged haste to make a test

maybe its not haste related

something to do with server ping maybe?

haste changed to 1.338

HoW is still roughly 4 GCDs

[wanton lark]

I see, thanks! let me just run my own numbers to see what they look like on my end

[hallow canopy]

something in your end is making your GCD be ready BEFORE HoW is

let me create a quick WA to print stuff on your end

[wanton lark]

no need, I got it 😄

[hallow canopy]

OK! i managed to replicate it!!!

i had to send spells REALLLLLLYYYYYY fast

[hallow canopy]

making sure i queued 4 spells in a row

[wanton lark]

oh

OH

[hallow canopy]

then the 4th spell woundt be HoW

[wanton lark]

well, I have a confession to make. I fire spells approximately every 0.1s as per my rate of fire variable on my autoHotkey script..

[hallow canopy]

hahaha delete that!

i got it!

[wanton lark]

I use an AHK script to automate button mashing so I only have to hold the key instead of spamming my keyboard.

[wanton lark]

I can't, I have a disease that makes my fingers numb so I need this script or my hands hurt after the 2nd boss pull 😄

I could decrease the rate of fire to 5Hz instead of 10Hz. see if that helps.

[hallow canopy]

dont decrese!

i mean

i was managed to queue 4 spells

anyone can

the way blizzard works to normalize the lag and user input is that it accepts keypresses before GCD is ready

its called queueing.. that way whatever you queued in that window is instantly send and processed by the server, leading to zero downtime

i queued 4 spells perfectly, the 5th wasnt HoW, thats what i saw

let me send you a WA so you can make a log during wings

and we see if thats actually the case

[wanton lark]

yeah, I'm sure @harsh kraken doesn't use any AHK scripts or anything and it happens to him. he might just be a pro gamer. 😎

I have manually set this CVar btw, could it be an issue? (the default feels horrible)

I kept 100ms because that guarantees that my AHK script outputs are always able to queue spells.

[hallow canopy]

ok so try this

!WA:2!fw1YUTTrx44OcKcUOWwn1abilecqBKDBCZVrDcq2jklz7czjxk6y3vYd5CO4utnd7md1LSlEvw7hbTTDLEeCX)EcHI(aKf9bWpb9mdLuCcqr1cIZ9BZ57O1AwEqzAz67QoLfk4DfzYq4X3toUtuKc0RnJq)LmLgOhtgF)pWW43xozLj8WyH8ebJRdQ3OTFdV5HcrcvmI3DelfU4MLSnO9HyxtIU4kTK1VpivFX3ixq(xPRl4NMsjAWpwk06e4KspFN)3SqmPIb90tsHaLMOZutPqqwuKpkrEyJwN080wEWqalGdbsIo(9QSal)jsiIn2R7jnA1YnJZ0bPjKjG0JtgakNGIqN(hrz8qntWRULtQeBKQp9G67xzijjdEvLNUZov0cfwM8(vBx7GxH68zdGxBuxDRT(iF0Oc06ksGqN8V7RVWZyWD9(zpRYHIZ(pdWD9E3Fy3xUNjeaNUQN7Itg24z9QxRRFVU(1889cJHWldYSZ2RuPqsYruLJRzIM)OLZ3ygf8mzNEDgFXBIt6geCWme8l4pwqHF)E3I1li5KKxJpG4u73U9sasRHbou7rW5y81eoBGHI)cp8jtQBEdquqxTe491XpiVIlxWH50mP1k7JRub4QbvDLXuZBB(2UdimEZ8TqhY3o)BZ)U8NLVDqeJZuXFQyCPqHlhyaH4P4WWd6Jrw9QnZRmhzdiHx2xkY4039W0YAySUNkMGRLNVyro9rwH2prcjw(9uliY3(6v6EYxRsx)oUxxKiK)4ARTwP3xifsISGb3AN63j9lTcjz4eg70WZyuDSBnK92IeXgduRW3oVai9ZlkNBS6naow0K8hmfregKbk0TDN2nYRiXMYyZuRHH2YOe(76fDaxNUEtj7nv(PmcfNkKk((FuJVmtZTYgjK0ZKK0RoBbrrbmKPybjiiUO66LAAT0noQD7gE9C74735yVJo4q)5RYAx2BGhTOzo)JsHrRfZ25u)wh1UXFpVFIyutj8RzapCYjF2Z3z39kAmJIBmF2FXgsPRmCgVNhKP1cENHGeXYtnIBz3Q(Qzg6LD11gM6RMk3KPGdwkj2A5QIZg5yw4LCqPkzDSBijbk5AiJTcAXqLByZMloGazCqmW6hRFRBIGqBgOrh46n9gKLOzoUgWWM5x44fMqukdLRchmgI01XAP2IBP2tRXFQigpEQ0U)AXboEKK0ysPDZy0zheE4LHb8xYFXbZy8Ifu0qN3Nkf9LyhuCfF7hFV7lj2RAQxKx1j)7DCrCJ2X9ncXG18(WcZuTiCybs(Z))7)eg1RnmQYEZIK4rseYIRoLslJfy9f3XXRaimhUWBKDX92I36MgZnLBq36EnA0oabZrS(o4Llt0H40hU8pcmBX7ZueCXIgphbhO7DsTLQZuZnawb9vlD4IRxbRYFqzvWE7SlURuE4FE()a

with this

record a few HoWs during wings, send it, try to replicate

@wanton lark

im managing to replicate it now, over and over

you guys are just being supa fast bois

ill find a way to fix it

got it on screen

[wanton lark]

here you go boss, the bug happened multiple times during the log

ctrl+F "HoW time to ready: 0." - 69 matches found (nice)

even got a negative float (whatever that means)

 GCD value: 1.239 
 GCD time to ready: 0.023999999999887 
 -- HoW time to ready: -0.0080000000002656 

[hallow canopy]

i got it several times too! am creating more debugs to see whats going on

but will have to pause for a while

[hallow crater]

guys, then is haste-related stuff?

I have around 8500 haste atm

[hallow canopy]

Not haste

A queue

I'm on it

[wanton lark]

I'm a bit sceptical about it being a haste issue. no matter the haste, 1x HoW CD should always be ~4x GCDs, or ~2x GCDs during AW with sanctified wrath. we can see from Fonsas' testing that there's usually a slight difference between this theoretical ratio and the reality (as reported by WoW API), but the difference at least to me looks negligible. it sure as hell isn't 200ms which is the allowance supposed to be given. I also tried increasing the 0.2 number to 0.4, 4.5, even removing it, and nothing changed

[hallow canopy]

Identified and now I can replicate constantly

[hallow crater]

awesome

[sick flame]

I won't be around much today, I have a lot going on, but I am catching up on the discussion

Did my APL fix the HOTR issue?

[sick flame]

I am not sure what this means

The value is 0.2s because according to the simulator, you can "wait" up to 0.2s for HoW cooldown and still gain DPS.

[harsh kraken]

I'll try it in a dungeon today... let me see if I can figure out how to upload it

[sick flame]

Just copy the string, open rotation manager, click import, and paste - then switch your enabled rotation to the new one.

Just like you would import a weak aura

[harsh kraken]

got it

[sick flame]

All I did was tweak the conditions for the "look-ahead" HotR action at the bottom of the APL

The bottom four actions check cooldowns of your spells against each other to determine what spell will be the first to come off cooldown, when nothing is available to currently cast.

And I believe the HotR only showing at the last second is related to that line

If it were working right, it should recommend HotR if the conditions are met (will be ready before other spells) up to 4.5 sec into the future

So that is my workaround for adding "predictiveness", same trick used in Cata

[harsh kraken]

Done

Lets kill some GOATS

to test it out

[sick flame]

I await your results

I will not be available most of the day today and Saturday, but hopefully the HotR thing is fixed at least.

Beanlord's NAG is another issue entirely.

[harsh kraken]

Reviewing it as it gets uploaded

I "felt" it was inconsistent but let me review it and summarize my findings

[sick flame]

I spent a few hours last night double checking the APL and I don't see anything wrong with it on my end, but I may have missed something

[harsh kraken]

Check out the video between 0:15-0:20

[sick flame]

Wait

We made progress

[harsh kraken]

While it is on CD, it goes from HoW to CS

Yes

we did

[sick flame]

It is predicting HotR ahead of time

[harsh kraken]

but it is switching back to CS

[sick flame]

Its just bouncing back to CS briefly for some reason

[harsh kraken]

yup

but it has been inconsistent

[sick flame]

The only way I can think of is two possibilities

[harsh kraken]

I have seen other instances where it stays on how

Between 0:45-0:52 it is fine

[sick flame]

• CS action higher up is being activated
• HotR condition are briefly not being met, could be the target count tracker briefly dropping below 4

I have an idea

If I hardcode target count into the CS action

This will narrow it down

[harsh kraken]

1:18 - 1:22 it goes to CS and switches back to HoW when it coes off CD

[sick flame]

Let me see if I can fix this rq before I leave for the day

[sick flame]

Hmm

I could fix that by extending the HoW look-ahead timer at the bottom

I dont want to touch the slack timer 0.2s for the HoW action

[harsh kraken]

Do you want me to test it with the monitor up?

[sick flame]

That's been dialed in

For the footage it would help yeah

[harsh kraken]

Ok, sec

[sick flame]

I will extend HoW look ahead from 4.3 to 6

[harsh kraken]

The FPS comes drastically down with the APL Monitor open

but here it is

It does the thing towards the end

[sick flame]

        or ((NAG:SpellTimeToReady(24275) < NAG:SpellTimeToReady(35395) and NAG:SpellTimeToReady(20271)) and NAG:CurrentGenericResource() < 5) and NAG:Cast(24275, 6)```

new HoW look-ahead line, predicting up to 6 seconds ahead

it will go right below 5HP spender look-aheads

[harsh kraken]

got it

send me the whole thing to upload it and test it

[sick flame]

the other thing I will do is

hardcode target count into CS

just to rule that out

[harsh kraken]

<=3?

[sick flame]

oh wait

hold on

i need to remove this condition

[harsh kraken]

k

[sick flame]

see if this fixes the HoW thing specifically

I'll work on the HotR part now

HoW actually didn't have a look-ahead line before

cause it didn't really seem necessary before now

[harsh kraken]

I dont have to reset the nag, do I?

[sick flame]

no

just import and switch rotation to new

you might want to reload after

but i dont think it matters

Here is my attempted solution for HotR

hardcoding target count into CS action

it now requires <4 targets

[harsh kraken]

It is a lot better

[sick flame]

so this most recent import string here attempts two fixes:

• CS now hard-coded to require < 4 targets, hopefully stabilizing HotR vs. CS recommendations
• HoW now has a look-ahead action at the bottom that will recommend HoW if it will be the first available cast in the next 6 seconds

[harsh kraken]

a lot better

[sick flame]

still not perfect?

[harsh kraken]

It is perfect

lol

[sick flame]

I do see a brief CS recommend but that can easily be explained by, one of the mobs fell outside of range briefly

@MoP Paladin please import this new rotation string APL

[harsh kraken]

I kept testing it and it seems perfect

[sick flame]

awesome

[harsh kraken]

It also seems good on single target

[sick flame]

thanks for your quick responses

and input

and footage

[harsh kraken]

ty

[sick flame]

@wanton lark try this new APL whenever you get a chance

@hallow crater you too

I have also adjusted the look-ahead timer of Judgement to 4.49 seconds

it was originally 4.5 seconds like the other spells but

if you Judge then CS, you can often end up in a situation where

the CD is almost the same but they are very very slightly different

for both Judge and CS

and if they are both 4.5s look-ahead, it will recommend Judge

so it is set to 4.49 so that CS will be recommended under this circumstance

I had it at 4.3 before for the same reason and it seemed to work well

so I am hoping it keeps working well

but i will test rq before I leave

yep it works, if you Judge -> CS and both go on cooldown, CS will recommend instead of Judge because they are both going to be the first spells ready at nearly the same time, but CS is better ofc, which is correct

so that still works thankfully

but hopefully changing it from 4.3s to 4.49s gets rid of any brief recommendation errors or "blank"ing

CS also has 0.2s slack

which also helps prevent these bugs

and by "slack value" I mean, it is okay to wait up to 0.2s for CS cooldown

instead of casting a weaker spell like Judge or Exo (outside of Wings, where Judge > CS)

@hallow canopy when are you going to give me the role/permission I need to tag @mop paladin broooooo

i swear ive asked like ten times and still dont have it after over a year :p

@hallow canopy @scenic tusk whenever you get a chance please push this to a new version for stock paladin ret rotation

[hallow crater]

I’ll check this out guys

Thank you for all the time spent and effort

Also looking forward to hearing from @wanton lark feedback too!

[sick flame]

using the lua syntax to color code the changelog, looks dope

[sick flame]

thx 4 subscribing

YET ANOTHER Retribution Paladin APL update for MoP!

This update seeks to fix the following issues:
CHANGELOG

- "CRUSADER STRIKE" now hard-coded to require < 4 targets. -- This will hopefully stabilize HAMMER OF THE RIGHTEOUS vs. CRUSADER STRIKE recommendations and prevent any flip-flopping.

- and "HAMMER OF WRATH" now has a "look-ahead" action at the bottom of the APL with a 6-second time variable. -- HAMMER OF WRATH should now be accurately predicted up to 6 seconds ahead of time, if it will be the next action.

- and "JUDGEMENT" has had its "look-ahead" value changed from 4.3s to 4.49s to hopefully prevent any extremely brief recommendation errors or "blanking". -- (NAG briefly goes blank)

-- "Look-ahead" actions are the actions at the very bottom that calculate the first spell that will become ready when everything is on cooldown. 

-- The reason the time variable for Judgement is 4.49s instead of the typical 4.5s value is so that when you:
- ("JUDGEMENT") first -> followed by ("CS/HOTR") 
-- and both have very similar cooldown lengths remaining, CS/HOTR will be recommended instead of JUDGEMENT; which is the correct and intended behavior.```
Please let me know if you have any issues or questions, though I will be out most of the day today and Saturday, I will still try to stay caught up with any discussion of the new APL.

***Malakawa*** has already tested this APL for me and it does appear to be working perfectly so far - he concurs.

# IMPORT STRING BELOW

small tweak

@harsh kraken import again

I moved HoW "look-ahead" above CS/HOTR, it was mistakenly below them

it is now the highest priority "look-ahead" action

[wanton lark]

well, still bugged for me regarding the HoW issue. also, debug console unusable as you can see.

I'll test HotR as well.

I'm happy to report that HotR seems to be perfect now. 🙂

[sick flame]

Alright I have an idea for HoW that I will test when I get home again later tonight

I think I know what is happening and how to fix it

[hallow canopy]

its not an APL issue

its me

let me send another

I FOUND IT BOYS

[harsh kraken]

we knew that

🤣

[hallow canopy]

i told it was me ages ago ahahhaha

fixed it

https://tenor.com/view/mic-drop-obama-barack-gif-13411519

[hallow crater]

Send send!!!

[hallow canopy]

@hallow crater @wanton lark @harsh kraken

it does NOT have surv latest APL

I will add surv new APL when i send the beta

[hallow canopy]

DONE

I didnt manage to replicate the bug anymore BOIS

4 hours of testing

to change 2 lines of code

but I believe now its gooooone

https://tenor.com/view/zenrepublic-bug-vr-zenfighters-thomukas1-gif-25704478

[hallow crater]

clean install bro?

[hallow canopy]

toss it on top of what you have

react super fast when you wings. spam the next spells before they are ready so you queue them

we want HoW to be the 4th spell every time

HoW - 3 spells - HoW

[hallow crater]

so just replace NAG foler?

[hallow canopy]

yes

and import surv's new apl

[hallow crater]

just teste a bit

there is something elseeeee