Womble

Here is a condensed part of my profile showing neither of these working.

Infact, it doesn't cast either slice or rupture at all.

Hmm.

SUB TEST 4.xml

Hey, I must have been wrong about Slice and Dice yesterday.

Testing both and neither are working.

My slice code: -

local nameSpell = GetSpellInfo(5171);
local name, rank, icon, count, debuffType, duration, expirationTime, unitCaster, isStealable, shouldConsolidate, spellId = UnitBuff("player", nameSpell);
local expireTimeLeft = expirationTime-GetTime();
ret = 0;
if expireTimeLeft <= 6 then ret = 1 end

return value research: 1

return value var: ret

and my rupture code: -

ret = 0;
local nameSpell = GetSpellInfo(1943); 
if (not nameSpell) then return; end
local name, rank, icon, count, debuffType, duration, expirationTime, unitCaster, isStealable, shouldConsolidate, spellId = UnitDebuff("target", nameSpell);
if (not expirationTime) then return; end
local expireTimeLeft = expirationTime-GetTime();
if expireTimeLeft <= 6 then ret = 1 end 

return value research: 1

return value var: ret

Thank you - that works for Slice and Dice.

I tried the same for Rupture: -

local nameSpell = GetSpellInfo(1943);
local name, rank, icon, count, debuffType, duration, expirationTime, unitCaster, isStealable, shouldConsolidate, spellId = UnitBuff("target", nameSpell);
local expireTimeLeft = expirationTime-GetTime();
ret = 0;
if expireTimeLeft <= 2 then ret = 1 end

Changing 5171 to 1943 for the spell and UnitBuff("player", nameSpell) to UnitBuff("target", nameSpell) but rupture won't work.

Any ideas what I'm doing wrong?

Could you use a similar script to check for duration of spells?

i.e.

local nameSpell = GetSpellInfo(*INSERT SLICE AND DICE HERE*);
local name, rank, icon, count, debuffType, duration, expirationTime, unitCaster, isStealable, shouldConsolidate, spellId = UnitBuff("player", nameSpell);
ret = 0;
if duration <= 3 then ret = 1 end

Would this refresh slice and dice if under 3 seconds?

I don't quite understand what you mean with the second c# code or what it does but I'll try them out later. If you could try to explain what they do again that would be great.

I've put your print code into my profile just now to watch it alongside my rotation, and it's only refusing to use backstab when the print says either 'no back' or 'no back and facing' otherwise it works, basically like the screenshots but I wanted to confirm it.

The only other important thing I noticed is sometimes when moving from the front of my target to the back it takes 5/10 seconds 'sometimes' to update to 'back and facing' from 'no back' or 'no back and facing' - which is another key problem.

I have to head out for now but I'll check back later.

Thanks for your patience - just trying to create the absolute best profile I can.

Sent you a PM.

-test-

Hey. Testing that rotation now.

It shows the problem clearly to me: I get crazy results, I've taken a few screenshot examples. I'll send them you in a moment.

I've also tried to remove hemo entirely and the same issue, it just stops using backstab. It's got to be the position of the '0.35f' that is wrong somehow.

Update 2: I've found somewhat of a fix...

Basically I recreated the exact same spell as 'Hemorrhage', called it 'Sinister Strike' and set the 'Check if know spell, is usable and good distance' to true from false.

However we still need better detection whether we are behind or infront of the boss because at certain points / angles behind the boss it thinks you aren't behind which causes random hemorrhages.

So like I said above, what would be brilliant is a 180 check behind the boss whether its the above code, lua, c+ or a new condition. I just don't know the calculation or math to work that out sadly.

And vice versa a 180 check infront so that hemo will go off the instant you slightly go ahead of the boss by mistake, or too far to the side.

Also see:  - which is now more relevant than this thread, but I'll keep this open so you know the issues at hand.

Important Update: I had created my profile on a lower level raiding dummy. I decided to try and replicate the issue by using my profile on the raiding dummy of level '??'.

Guess what happens? None of my ambush or backstab abilities work. 

As soon as I attack one of the nearby lower level dummys my rotation starts to use backstab and ambush.

Thing is I don't have any 'target level' checks on these abilities...

Sigh.

Okay I think it is to do with the hit box of the target being tempremental.

Back on a dummy after the raid, the rotation is flawless, backstab works.

HOWEVER... if I stand to the back and the side (but still behind as far as the game is concerned) it starts using hemo - either side, left or right.

At a guess "C Sharp Code: (System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f)" needs to account for 180 degrees behind the boss.

Any thoughts Droidz?

Apparently using my rotation on actual bosses / trash is a whole new thing. Finding more issues by the hour...

So, my Backstab condition works on target dummy's but refuses to work in a raid.

The ability is as follows: -

Conditions:

C Sharp Code: (System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f)

Buff: Shadow Dance > False

Buff: Stealth > False

Buff: Vanish > False

Is Spell Usable: Shadow Dance > False

Target Buff Casted By Me: Hemorrhage > True

I changed 'Check if know spell, is usable and good distance' to false in hopes it would work in a raid but it still won't.

All of the above conditions are met when it refuses to work - it literally doesn't cast a single backstab during fights.

I'm looking for a similar version of this: -

(System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f)

that will check if you are infront.

It is strange, on a target dummy my rotation is perfect and yet when on an actual boss or trash target it stops back stabbing and resorts to something at the bottom of my priority list which is hemo spam, even when 100% behind targets.

So I'm looking for perhaps a version of the above code that has the angle for being infront? I've Googled Radians and such but I can't find any straight forward answer that will give me the number i.e. "<0.35f" that I am looking for.

This way I can attach it to the hemorrhage in question and solve this issue.

Alright excellent. That works well, is there anyway to modify that to say 'less than' or 'more than' similar to combo point condition?

I attempted < 5 and a few others but to no avail.

I'll try when I get home later, thanks for the assistance.

I tried to use Hostile Unit Near Targets (which in theory should still work shouldn't it?) but changed to Hostile Unit Near which fixed it.

Thanks!

Hi again.

I'm all but ready to release my subtlety profile but for one MAJOR problem. Banging my head into a wall atm.

I've attached a watered down / test profile with only a few abilities. The ones with the issue.

The abilities are simple with a couple of conditions.

I don't and can't use a Combo Point alternative to fix this due to the nature of my actual profile, so please bare that in mind.

The idea is it will hemo until 5 anticipation buff stacks (condition = smaller than 5) and then it should apply a 5 anticipation buff stacks slice and dice > 5 anticipation stacks rupture and if both of these are up it will use 5 anticipation stack eviscerates.

I have literally no idea why this isn't working.

I had it working yesterday and managed to overwrite the profile after about 3 hours work and since then I just can't fix it.

Would love any help. Profile is attached.

It is important to test it on a dummy for at least 2/3 minutes. Sometimes and it is rare but sometimes it will actually apply some finishers but then just stop and resort to spamming hemorrhage.

SUB FRONT TEST.xml

Straight forward this time... can't get any form of AOE to work. Iv'e read the AOE conditions and tries various amounts of targets / radius upto 25 yards and even when I run around on trash with 10/15 mobs, Fan of Knives won't work - Crimson  Tempest / Blade Flurry.

Is there a specific way to do this that I'm missing because my profile just needs AOE implemented now to be released.

Resolved it myself. My profile has a crazy amount of conditions and abilities to best simulate the optimal rotation - so I just had to wrap my head around it. It's crazy!

Almost ready to release.

Hey, alright - following on from this thread: 

My entire rotation is basically either really good or broken / doesn't work.

Bosses and trash mobs always spin around, and the second anything turns my way - the rotation breaks.

I need to be able to replace backstab with hemorrhage when infront of an enemy. No other spell, just hemorrhage.

This part of my priority list looks like this: -

Hemorrhage > This has a lot of conditions, but essentially just refreshes the bleed on the target when it runs out.

Backstab > My main CP builder, again with quite a few conditions.

I tried to have another Hemo below Backstab without any conditions = didn't work.

I've had Hemo with a variety of conditions = didn't work.

My backstab has this condition built in: (System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f)

Ideally I need to somehow make a version of Hemo that will go off once my character can no longer backstab (is infront of my target).

Once I fix this I can basically release my sub profile, which is as close to perfect as you'll get with this bot. There are issues with timings but the bot can't handle that or work out pooling, so there is some forced pooling but this creates other issues which I've worked around by making vanish manual (I'll explain this in more depth on the description when I release the profile).

Much appreciate any help / fixes to this.

I've attached a version of the profile so you can see it in action yourself. Remember for Sub you'll need 2 daggers.

Wayne - Sub With Vanish.xml

 

Hello,

 

WRobot before launch spell it faces target, this condition is not required.

 

But wait next update I'll add this condition (IsFacing).

 

Yeah, we have a misunderstanding. I think your condition is just checking if your character faces your target, correct?

What I need is if an ability can only hit from behind, that if I am infront of a target it uses another ability. That's why I placed '(System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f)' on backstab.

OR perhaps tell me how to edit: (System.Math.Abs(ObjectManager.Me.Rotation - ObjectManager.Target.Rotation) < 0.35f) to being infront of a target?

Hey.

Ambush is behind and in stealth only and garrote isn't right either.

The ability I'd want it to use is hemorrhage since that can be used infront and also grants Combo Points, it just isn't as powerful as backstab. BUT it is a decent substitute if you aren't behind an enemy.

I'd love to know how to do this though. Not sure if the condition Droidz mentioned will fix this?

Also, is there any chance you could add a condition something like 'buff duration' so you type the name i.e. 'rupture' - time left '3' or 3000 if done in miliseconds and it refreshes it? Would simplify things a lot for more complex rotations.