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

I finally got 1.53 to load.
I added Magitek to routine folder and chose it for the routine and it started right up.
I exited the bot and chose kupo as routine and it would not start.
Even though I was able to actually get to the bot settings when I clicked run nothing happened. I am including the log
View attachment 9564 2014-08-02 15.26.txt
I am working on getting you another log with Arcanist with Pet out as you asked. Give me a min or 2.
 
I think I found the issue. Forgot to upload a code change for kupo.

Can you open Spell.cs

Look for line 108
Code: 
return Cast(name);

and replace it with

Code: 
return Cast(name,onUnit => Core.Target);
 
Just encountered this problem. bot crashes as soon as I pressed start.

Was trying to Fate bot at Hawthorne Hut.
 
Last edited:
Yes. I am working on the beta nav server so expect some issues.
 
Cameronaut said:
View attachment 137302 I can't get past log in. I just bought it and am trying it out for the first time so I'm sure it's something small I'm doing wrong.
Click to expand...

This error indicates you failed to extract all the files properly.


NavServer is down for a few minutes as I am currently running a quick memtest on the machine.
 
Hi mast, some of the regular navmesh routes seem to be no longer available even on the non-beta navmesh. Specifically, I can't get to FATEs in the Sahagin Stronghold from the Aetheryte in Aleport when it worked just fine yesterday. It ends up blacklisting fates from the beastmen stronghold but seems to be able to navigate to the area and FATEs right outside of Aleport and Swiftperch. It can also navigate to the Sahagin Stronghold FATEs as long as you aren't in the big walls of Aleport anymore. Here's the log.

View attachment 5864 2014-08-03 11.42.txt
 
Last edited:
Klacid said:
Hi mast, some of the regular navmesh routes seem to be no longer available even on the non-beta navmesh. Specifically, I can't get to FATEs in the Sahagin Stronghold from the Aetheryte in Aleport when it worked just fine yesterday. It ends up blacklisting fates from the beastmen stronghold but seems to be able to navigate to the area and FATEs right outside of Aleport and Swiftperch. It can also navigate to the Sahagin Stronghold FATEs as long as you aren't in the big walls of Aleport anymore. Here's the log.

View attachment 137316
Click to expand...
Your log doesn't show anything being blacklisted.
 
mastahg said:
Your log doesn't show anything being blacklisted.
Click to expand...

Might have gotten the wrong log since I actually had it a few hours before, might have sent you one after trying from outside the gates. >_<

I'll try to recreate it when I get back home.
 
Mastahg, I have a request to add to the long list of things you're working on.

For the FATE bot, specifically for Escort type FATEs, can you adjust how the bot keeps within the range of the FATE?

Currently, as the escort subject walks along, the bot will stop-start-stop-start to keep just within the range of the FATE. Could you adjust it to run to the centre of the FATE, then wait until the FATE moves out of range before running back to the centre? The current stop-start way of just barely keeping within range of the escort target makes the bot look very ... botish.
 
i just started getting this error '[23:52:47.915 V] Blacklisting 116 for 00:20:00 [Type: Node] - Reason : Could not navigate to NeoGaia.ConnectionHandler.CanFullyNavigateResult' when fating in costa del sol

it won't go to any fates for some reason
 

Attachments

exaccuss said:
i just started getting this error '[23:52:47.915 V] Blacklisting 116 for 00:20:00 [Type: Node] - Reason : Could not navigate to NeoGaia.ConnectionHandler.CanFullyNavigateResult' when fating in costa del sol

it won't go to any fates for some reason
Click to expand...


Yea some of the meshes got corrupted. I'm rebuilding them now and prepping a new beta.
 
Beta 154
Code: 
Kupo:
Fixed recursion issue that wasnt pushed before the last beta.

Gathertag:
Will now buff Truth of Mountains/Forests
Fixed issue blacklisting targets that could not be navigated to.


TeleportTag:
Will now dismount before teleporting

Orderbot:
Will now propely dispose of network connection on botstop
 

Attachments

the problem seems to have started again.

[01:17:28.962 V] Blacklisting 118 for 00:20:00 [Type: Node] - Reason : Could not navigate to NeoGaia.ConnectionHandler.CanFullyNavigateResult
 

Attachments

papatoast said:
Mastahg, I have a request to add to the long list of things you're working on.

For the FATE bot, specifically for Escort type FATEs, can you adjust how the bot keeps within the range of the FATE?

Currently, as the escort subject walks along, the bot will stop-start-stop-start to keep just within the range of the FATE. Could you adjust it to run to the centre of the FATE, then wait until the FATE moves out of range before running back to the centre? The current stop-start way of just barely keeping within range of the escort target makes the bot look very ... botish.
Click to expand...


This, just some way to make it walk smoother i don't care how you do it.
 
You must log in or register to reply here.
Back
Top