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

Beta 0.1.2551.879 Bugs

A

Anjin

Member
Joined
Sep 23, 2012
Messages
39
Reaction score
3
1. Bot does not open containers and loot at combat and can go away. To much back track.
2. Some time flip-flop. Then bot can't open container it's start flip-flip on one place.
3. If bot main executable file renemaed, bot dosn't work with error (Start] Please configure the ExampleRoutine.cs file before starting!). Most easy way to ban acc it is get process list and ban.
4. Town runs not work, at all. ([GrindTask] Now stopping the bot because we are in a currently unsupported area.)
5. Used only one spell. One of my characters (which) have a bunch of spells.
 
Last edited:
- i can confirm the already reported huge backtracking EB does to get loot that dropped like at the start of the run, this needs to be fixed asap.

- very smooth and seems very light to run EB.

- i get like 0,5 secs client freezes, i believe it happens when EB calculates the path from char to monster to attack. Will further watch for this to track even further down what could be causing this.

edit,

it has been told here ( https://www.thebuddyforum.com/exilebuddy-forum/174957-exilebuddybeta-forsaken-masters-guide.html ) that town run still isnt in, so it aint a bug.
 
Flip-flop, just part of log
Code: 
2014-08-27 10:56:06,373 [31] INFO  GrindTask (null) - [HandleDoors] Now attempting to highlight the chest (13186).
2014-08-27 10:56:06,407 [31] INFO  GrindTask (null) - [HandleChests] Now interacting with the chest (13186).
2014-08-27 10:56:06,890 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 30.02776 away.
2014-08-27 10:56:06,940 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 29.02939 away.
2014-08-27 10:56:06,973 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 28.03122 away.
2014-08-27 10:56:07,057 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 26.03567 away.
2014-08-27 10:56:07,124 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 23 away.
2014-08-27 10:56:07,157 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 22 away.
2014-08-27 10:56:07,225 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 21 away.
2014-08-27 10:56:07,257 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 20 away.
2014-08-27 10:56:07,341 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:07,374 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 25.81139 away.
2014-08-27 10:56:07,440 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 25.81139 away.
2014-08-27 10:56:07,474 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:07,540 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,573 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,657 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,724 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,758 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:07,824 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:07,857 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,924 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:07,957 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:08,040 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 26.81139 away.
2014-08-27 10:56:08,107 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 26.81139 away.
2014-08-27 10:56:08,140 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 25.81139 away.
2014-08-27 10:56:08,207 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:08,240 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:08,308 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 16 away.
2014-08-27 10:56:08,340 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:08,407 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:08,425 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 25.81139 away.
2014-08-27 10:56:08,507 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 24.81139 away.
2014-08-27 10:56:08,590 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 17 away.
2014-08-27 10:56:08,657 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 16 away.
2014-08-27 10:56:08,675 [31] INFO  GrindTask (null) - [HandleChests] Now moving towards the chest 551 because it is 16 away.
 
The current bot implementation will not open Strongboxes by design. It also skips breakable chests unless they are really close by.

You can rename the Exilebuddy process just fine. The actual error you see was from not setting up the CR first.

The current bot implementation does not do town runs, this is known, as I didn't want to rush it into the release last night.

The only bug is the back and forth movement, which should not be happening at all. Based on the log, it looks like a pathfinding issue and a path being generated that was switching between two possible routes. What are were you in and did you happen to take a screenshot of what was going on?
 
Flip-flop was in docks, bot is try to flip the rock (boulder) which is very close to ladder. And character run up-down all the time. I'm try to get screenshot but the game is stop generate what place.
 
I'm getting the half-second freezes as well, with the added downside of the bot doing nothing after the freeze, while getting attacked. I have to take over and attack something for it to start going again.

This is always the last line in the log when it freezes:
Code: 
[Logic] Now moving towards the monster False because [canSee: False][pathDistance: 61.04989][blockedByDoor: False]
 
Last edited:
Anjin said:
1. Bot does not open containers and loot at combat and can go away. To much back track.
2. Some time flip-flop. Then bot can't open container it's start flip-flip on one place.
3. If bot main executable file renemaed, bot dosn't work with error (Start] Please configure the ExampleRoutine.cs file before starting!). Most easy way to ban acc it is get process list and ban.
4. Town runs not work, at all. ([GrindTask] Now stopping the bot because we are in a currently unsupported area.)
5. Used only one spell. One of my characters (which) have a bunch of spells.
Click to expand...


Number 4 and number 5 are CLEARLY outlined in the beta thread.

https://www.thebuddyforum.com/exilebuddy-forum/174957-exilebuddybeta-forsaken-masters-guide.html
 
For the people with freezes, can you check if #880 fixed the issue or not? I moved some extra calcs outside of the framelock so it shouldn't execute inside anymore.

If it is still happening, I'll do some more searching.

Also, an easy fix for the backtracking is to just limit the combat targets in the routine itself: Private Paste - Pastie

This will be changing in the next version, but it was by design to make sure as much area coverage was done as possible.
 
pushedx said:
For the people with freezes, can you check if #880 fixed the issue or not? I moved some extra calcs outside of the framelock so it shouldn't execute inside anymore.

If it is still happening, I'll do some more searching.

Also, an easy fix for the backtracking is to just limit the combat targets in the routine itself: Private Paste - Pastie

This will be changing in the next version, but it was by design to make sure as much area coverage was done as possible.
Click to expand...
I can't tell b/c I can't get it to run anymore. It keeps saying "please configure" the routine, but I've gone into the new settings file you added and specified my melee slot as 1. The error logic says it only occurs if both ranged and melee slots are set to -1, so I don't know what's going on.
 
imdivesmaintank said:
I can't tell b/c I can't get it to run anymore. It keeps saying "please configure" the routine, but I've gone into the new settings file you added and specified my melee slot as 1. The error logic says it only occurs if both ranged and melee slots are set to -1, so I don't know what's going on.
Click to expand...

Please download clean copy of the bot, and then go to the Settings tab to configure the bot and routine.

You should be fine as long as one of the slots is not set to -1 (I just re-tested on a clean download.)
 
I downloaded a clean copy and modified it and I'm still getting the issue. To be clear what I am doing, I modified ExampleRoutineSettings.cs, not ExampleRoutine.cs, because I didn't see any setting for meleeSlot in ExampleRoutine.cs anymore, despite the error message pointing me to it. I changed:
private int _meleeSlot;
to
private int _meleeSlot = 1;

That being said, I have no idea what the "slots" maps to as far as the keys go. is the top left one (default LMB) 1? i.e. is it:
first row: 1,2,3
second row: 4,5,6,7,8?

I also set combatrange to 35, in case that is relevant.
 
Last edited:
Ok sorry, let me re-explain.

The initial version required you to change the CS file, because there was not enough time to tie everything into the GUI.

The previous release fixed that, by exposing all the options you need to change in the actual Settings tab in the bot itself. If you go to "Settings" in the GUI, and then either "BasicGrindBot" or "ExampleRoutine", you'll be able modify the bot/CR settings without ever having to touch the CS files themselves.

That is where you want to change your skill slots. Skill slots are just 1 - 8, and correspond to the actual skillbar slot. So your LMB is Slot 1, and your T key is Slot 8. Since slot keys can be rebinded, the CR uses the actual slot # and looks up the keybind for you, so you don't have to worry about that.

Hopefully that clears it up!
 
pushedx said:
Ok sorry, let me re-explain.

The initial version required you to change the CS file, because there was not enough time to tie everything into the GUI.

The previous release fixed that, by exposing all the options you need to change in the actual Settings tab in the bot itself. If you go to "Settings" in the GUI, and then either "BasicGrindBot" or "ExampleRoutine", you'll be able modify the bot/CR settings without ever having to touch the CS files themselves.

That is where you want to change your skill slots. Skill slots are just 1 - 8, and correspond to the actual skillbar slot. So your LMB is Slot 1, and your T key is Slot 8. Since slot keys can be rebinded, the CR uses the actual slot # and looks up the keybind for you, so you don't have to worry about that.

Hopefully that clears it up!
Click to expand...
ah that clears it up. thanks. the error message confused me I guess. :)
 
pushedx said:
Are you using a VM or a normal PC? Can you make a short video and PM me so I can see exactly what is happening, having F1 on will help.
Click to expand...
Normal PC. I don't have any video recording software readily available to do that. If it really becomes necessary, I can look at installing something.

I did run it with F1 on for a bit until it happened and saw frame time (ms) spiked big time. nothing else showed any major change.
 
There seems to be a problem - no priority targeting.
So npc's that resurrects, summons skeletons, or gives undead buff to others makes bot get stuck and kill same useless mobs.
 
Buratinas said:
There seems to be a problem - no priority targeting.
So npc's that resurrects, summons skeletons, or gives undead buff to others makes bot get stuck and kill same useless mobs.
Click to expand...

Yes, this is by design. The CR provided is really basic and doesn't have targeting priority logic added to it yet. I'll get some basic examples added for people to customize later on, but all you have to do is change how the best target is selected.

Right now, that's just:
var bestTarget = monsters.First();

Before that, if you order by buffs, or if it's a necro type, that mob would be at the front of the list of monsters instead.

All combat stuff is handled though the CR, which is done that way so users can customize what needs to be attacked.

In places where necros are an issue, simply taking necros first brings about the problem when there's more than one, and you have a mobs blocking your character so you can't LoS attack the necro. Or, the necro is on the high ground, ressing low ground units along a wall / narrow pathway, so you can't get by it. These are really specific cases that users would have to code around, as the logic we provide would not handle it (because, it requires having specific types of skills, and making sure you actually use those skills at the right time). The same is true with allies cannot die.
 
imdivesmaintank said:
Normal PC. I don't have any video recording software readily available to do that. If it really becomes necessary, I can look at installing something.

I did run it with F1 on for a bit until it happened and saw frame time (ms) spiked big time. nothing else showed any major change.
Click to expand...

For now, I'll just have to see if anyone else reports similar, and figure out if there's any common denominator with hardware or software.

So far, almost all the feedback is that it's running smoother than before (although we don't currently have nearly as many users as pre 1.2 due to things still being worked on), which it should because of some changes made with things that used to lag the client, and I've tested in a VM and of course my main PC.

I know you have used EB before, and the core methods we use for working with acquiring the DX frame and reading memory are the exact same. Is that the same PC you used to use?
 
You must log in or register to reply here.
Back
Top