What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Apsalar - heavy duty Rogue CustomClass

Status
Not open for further replies.
Nope still broken with 99. Don't know how you're the only one who can get it to work but it's not doing anything anymore besides stealthing while idling
 

Attachments

projektt said:
Nope still broken with 99. Don't know how you're the only one who can get it to work but it's not doing anything anymore besides stealthing while idling
Click to expand...
it is still 97 not 99

EDIT: it's same log from before
 
Last edited:
It's still broken tho. I'm not at home so i can't post any logs but it's not doing anything like before
 
v99

Tried combat against single targets (LazyRaider): Works so far, could be a bit faster using the available energy (especially when adrenaline rush is activated).

Subtlety:
x Fore behind target
[] Disable movement
[] Disable targeting

Tried with Lazyraider (and Combat bot to test any movment): Log is for Lazyraider

Doesn't do much, no Hemorrhage at all, Recuperate should be used far earlier (Energetic Recovery). Tries to backstab targets while in front of them (probably because of the IsBehind checking doesn't work (HB's broken as usual)). Just as a few observations...
 

Attachments

PHP: 
WoWMathHelper.IsBehind(WoWPoint me, WoWPoint target, float targetFacingRadians, float arcRadians = 3.14159f)
arcRadians: The arc to test against in radians. PI is the default value.

Who would suspect that it's arc defining what is "front" in IsBehind function.
So when i narrowed arc thinking it would increase accuarcy of behind, it actually did exactly opposite and considered quite wide area in front of target being behind.

Now that i know that, hopefully next release will fix Backstabbing issues.


EDIT: So nobody having any issues anymore?
 
For now i honestly have no idea why it's moving with 0.7.3, but not with newer ones.

Maybe i will rewrite it yet another time ;(
 
just throwing it out there i just used this for rag and it wasnt throwing up rupture at all im using lazy raider disabled movement and targeting just letting u know
 
I drop support for Apsalar until i merge it with Singular.
New thread will be created when i'm done.

For more details read first post.
 
Singular is just framework for customclasses, the things being bad right now are sub-customclasses it uses.

To make it easier to understand:
* Singular is set of tools and parts you can build your CC with,
* till now i had to craft those tools and parts before actually using them,
* it took hell lot of time and most of these tools and parts weren't built as supposed to and needed lots of fixes,

In short, i won't have so much fun coding, but result will be exactly the same, releases will be more frequent and less buggy.
 
Last edited:
I'm sure you will do your job right!
Take it on :)

greetz

Weischbier
 
i know u said u wont throw anymore support out there but im curious with ur lazyrogue cc how come it out performs this one with lazy raider. did u right a new code and forget about it? for with ur mut in this cc its terrible is there a way(even in the singular merge) you could incorperate ur lazyrogue code into it for the mut pve side of things?
 
First of all LazyRougue is written with simple functions and specialized for Raid DPS, while Apsalar is written with Behavior Tree so totally different concept and for 3 different environments (PvP, PvE and Boss), i try to move those rotations as close as possible.

Also Apsalar uses simple PvE, not the raid dps rotation for Training Dummies.
Think i will add option to manually choose which rotation should it use for Training Dummies in Singular.

To end with in current state of r100 i have no idea how good every single rotation work as there are total of 9 of which i could test just 2 (PvE on Sub & Assa) on training dummies.
 
Last edited:
Status
Not open for further replies.
Back
Top