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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

BuddyWing 1.0.1310.898 (March release) discussion

use 891 version is working perfect with stealth and rest till this version is fixed for grinders
if you want to make your bot to heal nonstop use last version and let bot go under some % health and then he will cast rest or heal spell non stop but this is only for grind profile
must something like this for infiltration i don't know
problem is most like level sync with max health
 
Sweet I can resume testing of the new targeting too once that's in. Had some odd issues with dps. AOE heals were broke compared to normal default combat so that I do have to fix.
 
Is maxhealthunscaled for general backend or do we need to change something in default combat?
 
wired203 said:
Is maxhealthunscaled for general backend or do we need to change something in default combat?
Click to expand...

There's no real point in using it other than for determining by how much health is scaled down (and if it's scaled). You shouldn't need to change anything for the routine to work.
 
So I was trying my modified code and was getting a ton of hitching running a dps grind test. Every spell my game would freeze for a half second or do. So I reverted to the shipped Default Combat to compare and received the same results. Log doesn't show anything but the casting of the spells but it pauses a heck of a lot even with shipped default combat.
 
So latest version re-broke healing, same kind of issues as before where it locks onto one player and goes to town. Would be health percentage goofed up again. Testing on 898 has healing back to working great.
 
wired203 said:
So latest version re-broke healing, same kind of issues as before where it locks onto one player and goes to town. Would be health percentage goofed up again. Testing on 898 has healing back to working great.
Click to expand...

What I've discovered during my last adventures is that the maximum health differs greatly for the various types of objects. For local player and its companion, it's not the same function as it is for another player and their companion, for instance. While mobs and companions are both NPCs, it's not the same function to get their maximum health, either. It's not very pretty.

To make things worse, they've introduced the level scaling, which affects maximum health. Except that it does affect players, and companions (remember a companion being an NPC?), but it doesn't affect mobs (which are NPCs as well). See the issue there? The scaled health and the maximum health aren't being kept in the same store in the game's engine, and vary across different objects of the same type.

The previously release focused on getting the core of the bot - i.e. killing stuff - working. We can move towards getting a method of determining the max health and therefore the health percentage working across the board, including for healing routines, but for that, we'd need specific reproducible cases of where the bot gives us the wrong values, for instance, does it return the wrong value for friendly players' companions, enemy's companions, enemy players, friendly NPCs, hostile mobs, etc, etc. Once we have that down, we can work on a solution for healing routines and other stuff as well.
 
Companion and self have always seemed to return correctly, It's other players within a group. I could give you the logging I have used in the cast routine if you would like. 898 was on the money as far as healing goes but if a player was dead we got a few hundred HP's left, and yeah broke lots of other stuff. I would assume isfriendly could be a good place to focus but only problem in 898 I had was when another player in group had died their points never went to 0.
 
Last edited:
wired203 said:
Companion and self have always seemed to return correctly, It's other players within a group. I could give you the logging I have used in the cast routine if you would like. 898 was on the money as far as healing goes but if a player was dead we got a few hundred HP's left, and yeah broke lots of other stuff. I would assume isfriendly could be a good place to focus but only problem in 898 I had was when another player in group had died their points never went to 0.
Click to expand...
Its a game problem. It has an issue at death and around death, not registering the correct value.
Maybe we need better logic with the following points:
- HP value
- HP percentage value
- UI Change. When dead, well they grey out.
On Death the values of energie / mana / action points change to 0.
 
I was thinking if Aevitas can't fix it perhaps just doing a if me.healcandate.health >= 1% add to list etc. Then it wouldn't add 1% or lower to the heal candidates list. Would prefer if buddywing could give a proper value if possible but I could work around it if we had to.
 
Already had a isdead check and wasn't working when they never went to no HP's

Code: 
                            if (p.HealthPercent <= MaxHealth && !p.IsDead)

That's the heal target list creator. We had dead on our lists that caused people to heal non stop to a dead person showing 432 hps left even though they were dead as a doornail.
 
I'm sure the isdead was associated to the character still showing HPs.
 
Put in a beast of a pull request on GitHub, there's a lot of changes I made not just to healing as well as others (Cyrogenesis, Alltrueist) which were in the test edition. I updated all headers to the new year as you had a few days ago. Everything has been tested pretty heavily and once the MaxHealth can be nailed down buddywing will be a beast of a healer as it has been in the tests.
 
You must log in or register to reply here.
Back
Top