Beastlord coding suggestions needed!

[Kannkor]

EDIT: Apparently the below wasn't clear enough. Do not post about your group setup, your dps, your thoughts on the class. Start a new thread. This thread is specific to what needs to be coded. I'm not going to go through 10s of posts to find the 1 that contains information I need. Keep on topic or I'll keep deleting posts or just close down this thread.

First, READ THIS ENTIRE POST BEFORE POSTING.

1. I have never "played" the Beastlord class.
2. I don't know the Beastlord class.
3. I don't know the Beastlord AAs.
4. I don't know the Beastlord abilities.
5. I won't spend time researching the class for you.
6. My beastlord has 2 warders. Aquatic and Feline. If I need another one, specifically tell me which one, and where to get it. Telling me "Any dog" will probably not get the response you are looking for.

Keep the above list in mind before you suggest anything.

For suggestions, this is what you need to do. You have to be VERY specific with everything. Example:
Beastlord ability abc doesn't work when placed in tab def. The bot gets stuck on this ability and it says ____ (in the console/eq2 chat window).
You get ability abc from leveling warder type ____. To obtain this warder you ____.

If you are also like me, and don't know the Beastlord class well, feel free to read this thread, but please don't post stupid suggestions, let the people with experience post.

 

[Kannkor]

Suggestions/things to fix/code

• Allow primals to be used in tabs other than Beastlord tab
• primal Stealth attacks no longer work (Because of IsReady, need to see if stealth is required and skip the check).

 

[larrydoyle]

Don't claim to be an expert on this class .. but just raided on BL for first time, and had following thought to max DPS:

Could you make the level at which Primals fire off to be set based on ranges of a mob's health?

For instance, instead of setting the level (1-6) for an ability to be the same, create 5 ranges: targeted mob health % 100-80, 79-60, 69-40, 39-20, 19-0
Or, at least 3: 100-80, 79-20, 19-0
If you could have these options for named vs. non-named, that would be even better.

When I set my savagery thresholds real low (like 1-3), I lose DPS on those big hits versus waiting until savagery is higher (5-6), mostly on named. On non-named, you actually will rarely have time to get savagery levels up, unless there is a better method developed to manage savagery freeze within Ogre.

But sometimes, especially in long fights towards end, I might be sitting on 2-3 savagery level waiting on more stuff to refresh to build more (cause my levels are set to 4-5), but the toon is not doing much while it is waiting, although I could have every Primal up and available to add to my DPS. But they won't cast since they are waiting to hit the savagery level. On non-named, you actually do better just firing off Primals almost as soon as you can. Keep in mind (after reviewing ACT), primals are going to do a disproportional amount of your damage in raid situations.

So, ideally, it seems like I would set up a high-DPS ability for named (If I had 3 levels of mob health available) like this:

100-80 level 3
79-20 level 5
19-0 level 2

For non-named, I probably would set them like:

100-80 level 1
79-20 level 2
19-0 level 1

Or something like that. I tried this strategy manually playing the BL in the raid, and my parse improved significantly.

Savagery freeze is also a big deal .. but there was another post on that so I won't repeat. But intelligent management of savagery based on that ability would be very useful.

Thanks for listening

 

[Orwak]

Don't claim to be an expert on this class .. but just raided on BL for first time, and had following thought to max DPS:

Could you make the level at which Primals fire off to be set based on ranges of a mob's health?

For instance, instead of setting the level (1-6) for an ability to be the same, create 5 ranges: targeted mob health % 100-80, 79-60, 69-40, 39-20, 19-0
Or, at least 3: 100-80, 79-20, 19-0
If you could have these options for named vs. non-named, that would be even better.

When I set my savagery thresholds real low (like 1-3), I lose DPS on those big hits versus waiting until savagery is higher (5-6), mostly on named. On non-named, you actually will rarely have time to get savagery levels up, unless there is a better method developed to manage savagery freeze within Ogre.

But sometimes, especially in long fights towards end, I might be sitting on 2-3 savagery level waiting on more stuff to refresh to build more (cause my levels are set to 4-5), but the toon is not doing much while it is waiting, although I could have every Primal up and available to add to my DPS. But they won't cast since they are waiting to hit the savagery level. On non-named, you actually do better just firing off Primals almost as soon as you can. Keep in mind (after reviewing ACT), primals are going to do a disproportional amount of your damage in raid situations.

So, ideally, it seems like I would set up a high-DPS ability for named (If I had 3 levels of mob health available) like this:

100-80 level 3
79-20 level 5
19-0 level 2

For non-named, I probably would set them like:

100-80 level 1
79-20 level 2
19-0 level 1

Sounds like quite a horrible idea I'd say. At least as long as it would replace the current system.

What I would like to see is this:
The possibility to prioritize advantages in a good way, this of course can already be solved with assigning them to named CAs and Force CA, so it's not a high priority I guess.

I have a few other things as well, but as I was about to write them down, I came up with ideas to possibly solve them within the current system, so I'll take a look at that tonight and return if it doesn't work.

 

[battleaxe]

Can you make the cap on the Savagery slider equal to your toon's savagery cap? That threw me off for 10-20 lvls.. no primals were triggering because I only could get to 3 (300) savagery at the time and they primals were set to 5 be default.

If no, whatever, just would help folks not catching the savagery cap on their toon as they lvl..

 

[Orwak]

The possibility of binding chain 1-3 to a savagery level would be awesome.

 

[larrydoyle]

Sounds like quite a horrible idea I'd say. At least as long as it would replace the current system.

What I would like to see is this:
The possibility to prioritize advantages in a good way, this of course can already be solved with assigning them to named CAs and Force CA, so it's not a high priority I guess.

I have a few other things as well, but as I was about to write them down, I came up with ideas to possibly solve them within the current system, so I'll take a look at that tonight and return if it doesn't work.

The idea enhances the current capability in the BL section (i.e., only being able to set a primal to trigger on a single value). If you wanted to set all the options to the same level, you still could and it would not change what you can currently do. Why is the idea bad?

 

[Orwak]

The idea enhances the current capability in the BL section (i.e., only being able to set a primal to trigger on a single value). If you wanted to set all the options to the same level, you still could and it would not change what you can currently do. Why is the idea bad?

Reply in OT thread

 

[battleaxe]

Caught this while researching optimizations for my BL and thought it might be worth mentioning here. Instead of going with Savage Freeze to lock in high savagery, some folks saving the aa's and using ca's and advantages inbetween to keep up the savagery..

I usually use at least 4 of 6 primals at rank 6, depends on advantage procs. First and last are always with 6 savagery though.

So yes. Primal, ca, ca, primal, ca, ca, primal, ca, ca, primal, ca, ca, primal, ca, ca, primal.

Was from Buffrat on the eq2flames site. He was inferring the use of ca/adv when he writes ca, but none the less.. I'm not sure how one would be able to get something like this working within ogre. The Primals could have a limiter to make sure x number of ca/adv from the priority list hit between each primal, but that'd be annoying to code.

 

[Ali]

From what I've seen, it already does a fairly good job at that. If you set all the primals to just be cast at 6 (or 5 if don't have the aa), it will alternate between casting primals and ca's/advantages. Sorry Kannkor if this is too far offtopic!

 

[Kannkor]

From what I've seen, it already does a fairly good job at that. If you set all the primals to just be cast at 6 (or 5 if don't have the aa), it will alternate between casting primals and ca's/advantages. Sorry Kannkor if this is too far offtopic!

Not off topic at all.

I would agree with you though. Set all your primals at 6, and the bot will cast any primal when you are at 6, and CAs in between. There's no "for sure" it's only going to cast 2, but it'll cast enough to get you back to 6, which is what we're really after.

 

[Ali]

Would it be possible to add chain tabs to being able to be used off a savagery level in beastlord tab?

 

[Kannkor]

Patch 133 (not released of me typing this, but will be in a day or 2).
BL primals can now be cast directly off the CA/Named CA tabs. Note: You NEED TO RUN A NEW SPELL EXPORT FIRST
primals require level 1 or higher of savagery to cast for now. May look for a better fix in the future.
Technically any ability can be marked to only cast at a savagery level.
If you want to specify a required Savagery level for a chain tab you can do that also by setting the Sav level on the "Chain#Tab" entry in the CA tab.
Stealth primal abilities now work HOWEVER - I do not have a method of seeing if you have actually selected the stealth ability on the beastlord ability window selector thing. This falls onto YOU the user to determine. Simply put, if you tell the bot to cast a stealth ability, but not give YOU the ability to cast it, the bot will get stuck.