Combat issues with Elegon boss

[muffmann]

Was just wondering if anyone else was having issues with the bot attacking Elegon when you enter the phase barrier or w.e it's called, it will cast pestilence, but it wont use any abilities. I'm using lazy raider, If any of you guys have had the same trouble, could you tell me how you were able to fix the situation, or if it's just an error with the HB bot.

Thanks in advance.

 

[chinajade]

Was just wondering if anyone else was having issues with the bot attacking Elegon when you enter the phase barrier or w.e it's called, it will cast pestilence, but it wont use any abilities. I'm using lazy raider, If any of you guys have had the same trouble, could you tell me how you were able to fix the situation, or if it's just an error with the HB bot.

Hi, Muffman,

You must attach a full log for us to help you with this type of problem.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

[muffmann]

Sorry china, the logs are too big, and not sure how to downsize it for you.

 

[xsilverdicex]

Sorry china, the logs are too big, and not sure how to downsize it for you.

You can zip them using winzip or winrar. WinZip for Windows, Mac and Mobile - Zip Files, Unzip Files

On topic though the Honorbuddy devs are aware of the issue with elegon, my understanding is there are two problems one being because the floor vanishes the bot is endlessly trying to calculate distance to target, another being Elegons extremely large hitbox mess's with hb for example if you are within melee range the bot detects you as being around 30 yards away. CC devs can make a work around in there cc's however it is a HB core issue.

 

[CodenameG]

you dont have to, just zip the log and upload it.

 

[muffmann]

Ahhh..ok thank you all, didn't know how to compress the files. lol sorry, but you guys told me the issue, was just seeing if it was something I was doing wrong. I will still post log if you guys want me too(hopefully its the right one though). Again thanks for the info.

 

[Stormchasing]

On topic though the Honorbuddy devs are aware of the issue with elegon, my understanding is there are two problems one being because the floor vanishes the bot is endlessly trying to calculate distance to target, another being Elegons extremely large hitbox mess's with hb for example if you are within melee range the bot detects you as being around 30 yards away. CC devs can make a work around in there cc's however it is a HB core issue.

- calculating distance - wrong
- large hitbox - wrong

both can be done without workarounds
Workarounds were needed while cata was up, but atm we (as i speak as part of the CC devs) don't need these workarounds anymore.

A Simple answer to the problem could be given if we had a log.
For example:
- Singular is by default paused on Transporters ... the platform is a transporter
- PureRotation is not checking range, transporters or something else, it is "stupidly" executing the rotation and hopes that CanCast from HB returns correct values (which it does in Elegon-Fight for melees, ranges,healers, tanks)
- CLU is checking range with workarounds (this is related to cata, CLU already existed there, and no one removed the not necessary checks), not checking Transporters, thousands of CanCast overrides, and so on

So ... Singular should stop working in this fight, CLU & PureRotation should be executed.
The behavior of Singular is working as intended, cause it is not meant for raiding , but to find the real issue and the reall solution ... attach a log

 

[CodenameG]

well then dont worry about if that was in fact the case, theres nothing we're going to be able to trouble shoot, gotta wait for the devs or the Combat Routine developers to work on it.

 

[Stormchasing]

Ahhh..ok thank you all, didn't know how to compress the files. lol sorry, but you guys told me the issue, was just seeing if it was something I was doing wrong. I will still post log if you guys want me too(hopefully its the right one though). Again thanks for the info.

Wrong log, this is from the first 3 bosses (Guardians, Feng, Garaj), not elegon

 

[chinajade]

Ahhh..ok thank you all, didn't know how to compress the files. lol sorry, but you guys told me the issue, was just seeing if it was something I was doing wrong. I will still post log if you guys want me too(hopefully its the right one though). Again thanks for the info.

Hi, Muffmann, and thanks for the log.

The TuanHADK Combat Routine is throwing a lot of exceptions. This is why you are not using any abilities.

You might try a different Combat Routine and see if you fare any better.

Also, Stormchasing has a lot of good points about this particular encounter--it just might not be doable given the current state of things.

cheers,
chinajade

 

[xsilverdicex]

- calculating distance - wrong
- large hitbox - wrong

both can be done without workarounds
Workarounds were needed while cata was up, but atm we (as i speak as part of the CC devs) don't need these workarounds anymore.

A Simple answer to the problem could be given if we had a log.
For example:
- Singular is by default paused on Transporters ... the platform is a transporter
- PureRotation is not checking range, transporters or something else, it is "stupidly" executing the rotation and hopes that CanCast from HB returns correct values (which it does in Elegon-Fight for melees, ranges,healers, tanks)
- CLU is checking range with workarounds (this is related to cata, CLU already existed there, and no one removed the not necessary checks), not checking Transporters, thousands of CanCast overrides, and so on

So ... Singular should stop working in this fight, CLU & PureRotation should be executed.
The behavior of Singular is working as intended, cause it is not meant for raiding , but to find the real issue and the reall solution ... attach a log

thanks for validating all that, it appears i was still partially correct though, Pure rotation is not checking for ranges (it's not required but still kind of a work around)
CLU is using work around to check distance.

not wrong

 

[muffmann]

Sorry about that, was in a LFR and didn't have a lot of time to find the right log. added the new one, also China, Ive tried tuanadk and purerotation routine, with the bot too on elegon lfr but it didn't work in either normal raid or lfr. It's worked fine with every other boss besides that one, so don't know if it would be the routine interfering with it (not sure im not the expert here.) Thank you all though for the info.

 

[muffmann]

I will also try singular on the elegon fight to see if it works, even though it is mehhhhhhhh, haha but if it gets the job done with out my raid leader yelling at me then I will praise you. Also does it matter if I use lazyraider when testing singular or just use it with combat bot?

 

[xsilverdicex]

I will also try singular on the elegon fight to see if it works, even though it is mehhhhhhhh, haha but if it gets the job done with out my raid leader yelling at me then I will praise you. Also does it matter if I use lazyraider when testing singular or just use it with combat bot?

Singular will not work for it.

 

[muffmann]

Oh damnit, hmm read a previous post wrong then. So just wait for HB to fix it?

 

[xsilverdicex]

Tuanha DK and pure rotation should both be working for it, they have both be designed to work on that fight, make sure you are using the latest version of tuanha DK

 

[muffmann]

copy that, will check and make sure. Thanks

 

[CodenameG]

let us know how that works for you.

 

[muffmann]

It is working flawlessly again, ty all for the info/input.

 

[tuanha]

Fixing Elegon is such a pain for dev :|

I can't remember how many try Join LFR to fix that stupid boss.

If you stand under the boss, HB will report:
- In melee range: No
- Range: 23 yard
- Facing: No
- Hitbox Radius: only 1 yard rolf
... A lot other fail API

So to fix this boss, I have to make a special code to make routine work.

Because my CR made to other thing than just raiding, I just can't remove the check and an special code part only reduce the whole CR.

I really wish HB take a look and fix that few boss, that make the whole existing CR instantly work without modification.