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!

[Release] RebornBuddy Version 1.0.461

Is the bot supposed to return to the zone we were in upon death? mine just seems to sit there on death.
 
Thanks for your work mastahg fate bot running now on my low level ain't ran into any other problems, using Level requirements and when to engage 'Boss' fates no problems.
 
Sorry, is there fate grinding for the bot now? I just saw someone mention Fatebot, and I want a piece of that action, hah.

I have version 1.0.133.0
 
mastahg said:
Beta 3

Code: 
Settings menu added for fate bot:
Blacklisting
Level requirments
Fate Types
When to engage 'Boss' fates.

Meshs have been tweaked, I knew there would be issues but I wanted to start them as relaxed as possible and tighten them as needed.

Fixed NPE with orderbot and fatebot.
Click to expand...

I too am getting a hang on death.

View attachment 8160 2014-05-29 08.16.txt

Level requirements and fate types settings are working well so far. I have noticed that the boss fate engagement setting only triggers when getting close to the fate. If i have it set to 10% and manually approach a boss fate, it won't path trigger to engage until i can see the health onscreen. I'm not sure if there is any indication of the fate progress for boss fates (though they are adding that in 2.28) but maybe the bot needs to path towards the boss fates to trigger the information for that setting.
 
onyxial said:
I too am getting a hang on death.

View attachment 131527

Level requirements and fate types settings are working well so far. I have noticed that the boss fate engagement setting only triggers when getting close to the fate. If i have it set to 10% and manually approach a boss fate, it won't path trigger to engage until i can see the health onscreen. I'm not sure if there is any indication of the fate progress for boss fates (though they are adding that in 2.28) but maybe the bot needs to path towards the boss fates to trigger the information for that setting.
Click to expand...

Did the character release and it was standing in town or was it just sittin in the corpse. As for the progress that data is already in the client. I'll investigate why it might not be updating properly.
 
mastahg said:
Did the character release and it was standing in town or was it just sittin in the corpse. As for the progress that data is already in the client. I'll investigate why it might not be updating properly.
Click to expand...

The character was sitting in it's corpse with the return prompt onscreen.
 
Problems in western La noscea, when it runs between fates it is running back and forth real fast. It does it durning escort fate also.
 

Attachments

Last edited:
Beta4
Code: 
Tweaked all meshes, using a slightly larger radius.

Api:
PullRange for ICombatRoutine is now a float

Kupo:
Now uses the hitbox of mobs instead of stopping a flat distance away from them.

Navigation:
Tweaked navigation code to use target destination instead of the last hop returned.

Fatebot:
If we get out of range of a fate, move back inside the radius and do nothing else until we do.

Fatebot/Orderbot:
Fix issue where bot would not revive.

Known Issues:
The way we update fate progress is unreliable at the moment, 2.28 will be out in a few days until then it will remain only semifunctional.

http://www.thebuddyforum.com/reborn...ornbuddy-version-1-0-133-a-6.html#post1533560
 
mastahg said:
Beta4
Code: 
Tweaked all meshes, using a slightly larger radius.

Api:
PullRange for ICombatRoutine is now a float

Kupo:
Now uses the hitbox of mobs instead of stopping a flat distance away from them.

Navigation:
Tweaked navigation code to use target destination instead of the last hop returned.

Fatebot:
If we get out of range of a fate, move back inside the radius and do nothing else until we do.

Fatebot/Orderbot:
Fix issue where bot would not revive.

Known Issues:
The way we update fate progress is unreliable at the moment, 2.28 will be out in a few days until then it will remain only semifunctional.

http://www.thebuddyforum.com/reborn...ornbuddy-version-1-0-133-a-6.html#post1533560
Click to expand...

Does this redirect to the right post? It's linking me to:
mastahg said:
if the item is not unique then that has nothing todo with this.
Click to expand...
 
mastahg said:
Nope, its right. Checked using both firefox and chrome.
Click to expand...

Strange, I was able to manually look for it, though, so thanks!

Also, that does seem to be the right post number but my browser directed me to a different one everytime I clicked on it. Derp. Verified the post ID
 
When I load the bot it does not allow me to put in my key, it opens up an update is available and bot crashes.
 
mastahg said:
Code: 
Tweaked all meshes, using a slightly larger radius.

Api:
PullRange for ICombatRoutine is now a float

Kupo:
Now uses the hitbox of mobs instead of stopping a flat distance away from them.

Navigation:
Tweaked navigation code to use target destination instead of the last hop returned.

Fatebot:
If we get out of range of a fate, move back inside the radius and do nothing else until we do.

Fatebot/Orderbot:
Fix issue where bot would not revive.

Known Issues:
The way we update fate progress is unreliable at the moment, 2.28 will be out in a few days until then it will remain only semifunctional.
Click to expand...


With this build, the fatebot is refusing to do fates, even if I begin them manually. I adjust the bot settings and click start and it lets fates that meet the criteria go without recognizing them. It also fails to move in the Orderbot, but I'm still working on that so I'll post a log later.

Thanks for all the work on this bot. I know it's gonna be great.

View attachment 8336 2014-05-30 23.02.txt
 
crazybuz said:
When I load the bot it does not allow me to put in my key, it opens up an update is available and bot crashes.
Click to expand...

Going to need a log file.

onyxial said:
With this build, the fatebot is refusing to do fates, even if I begin them manually. I adjust the bot settings and click start and it lets fates that meet the criteria go without recognizing them. It also fails to move in the Orderbot, but I'm still working on that so I'll post a log later.

Thanks for all the work on this bot. I know it's gonna be great.

View attachment 131639
Click to expand...


There was a problem with the nav service please try now.
 
It does not create a log file to send after I start as admin it opens the download update and crashes.

Fatebeta4ss.webp
fatebeta4ss2.webp
 
You must log in or register to reply here.
Back
Top