new v0.19 bugs...post the details here dudes!

[pronoooob 42]

I'll start..first off Thanks to Alk for the quick releases and continued development .

-> Heard peoples guy is attacking the air sometimes...
-> Piety also, I've heard its buggy

 

list more !

[Allexiel 0]

- Looting a lot of crap

- XP/H still not showing for higher levels

[Druzil 0]

Bot stops working after trying to pickup loot and doesnt find it.

after it circled around the item without finding it just stops doing anything

 

it also picks up a lot more crap with the new loor routine. (my stashes where full of white and yellow crap after like 3 hours botting (what naever happened before))

[bbones 3]

- Looting a lot of crap

it also picks up a lot more crap with the new loor routine. (my stashes where full of white and yellow crap after like 3 hours botting (what naever happened before))

 

1. I confirm this!

 

2. Sometimes the bot seems to get stuck in some kind of a loop while picking up loot. Doesn't seem to do anything at all, while the pathfinding log shows something like this (endless identical entries):

 

2014-05-29 17:20:56 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:56 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 0 ms, cost: 159.000000

2014-05-29 17:20:56 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:56 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:56 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:56 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:56 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 31 ms, cost: 159.000000

2014-05-29 17:20:56 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:56 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:56 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:56 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:56 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Set explored nodes took: 0 ms

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 16 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 16 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 31 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 0 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 15 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(181, 896)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(181, 896) took: 16 ms, cost: 159.000000

2014-05-29 17:20:57 [pathfinding] -> Computing A* path from P(186, 969)->Pos(202, 948)

2014-05-29 17:20:57 [pathfinding] -> A* from P(186, 969)->Pos(202, 948) took: 0 ms, cost: 24.000000

2014-05-29 17:20:57 [pathfinding] -> Raycast took 0 ms, wall found.

 

3. After about 15sec to half a minute of using the new hold mouse when attacking function the bot just stands next to monsters doing nothing. As soon as I disable it, everything is fine again.

[drmaboul 3]

inventory full of blue/white item

[metaxer 7]

New Pickup system SUCKS, bot dont pick items on the ground. Bot is trying to find item via moving cursor by the radius and stuck. 

Exiled Bot Beta v0.19 RC was working just Fine - is there any reasonable point to put in Live ver. New Untested Feature? 

 

About Blue\white Items in Bank - system.cfg

; Set here the delay in ms to wait before looting an item (to ensure that the item is really the one we want)

pickup_delay=70 >>> 200  

Its all about Ping - Devs think we're boting with ping 10-40 or so i think 

Edited May 29, 2014 by metaxer

[Rooroosh 1]

Same issue with the new looting, when there's a big pile of loot it sometimes just starts making huge circles around the item that needs picking up, never actually getting to it. I feel like overall the chances of looting things in a big pile have improved with the more randomized cursor movement but it still takes a long time due to the bot not choosing the X-axis correctly.

[Jermanius 0]

Lag/Desynching seem to be the culprits for picking up non specified items, I know my one had problems accessing stairs in Scepter of God, neither the bot or trying it manually worked, had to log back into the game.

[metaxer 7]

Circles are pointless at X,Y PoE reality - all what we want - aside step on Left Then Check this zone by Y and step to the Right side and check this zone by Y -  And new command *How far gonna be this Step (Left\Right)* 

[ExVault 3]

Circles are pointless at X,Y PoE reality - all what we want - aside step on Left Then Check this zone by Y and step to the Right side and check this zone by Y -  And new command *How far gonna be this Step (Left\Right)* 

Anyway new system is better than old. Now bot does not stuck on every big loot pile until idle loguot.

pickup_delay=70 is not quite enought indeed, I've set it to old 200 as you suggested.

[ExVault 3]

Aaaaand pickup_delay=200 does not seem to work, bot still picks up shitload of white items. At least he is not stucking...

[metaxer 7]

Anyway new system is better than old. Now bot does not stuck on every big loot pile until idle loguot.

pickup_delay=70 is not quite enought indeed, I've set it to old 200 as you suggested.

how new system is better if its not work? =\  

[ExVault 3]

how new system is better if its not work? =\  

I've written it already.... bot does not stuck in infinite loop trying to pick up item in huge pile.

[ExVault 3]

Tried pickup_delay=500, seems working, bot stopped picking up trash.

[metaxer 7]

Just hapend with 1x Item  no white or blues around, Bot ignored item and didnt pick it up just moved Cursor above twice. 

[bonebox 36]

Bot sometimes follows mob instead of attacking if click and hold attack is set on a left mouse mouse button skill. Think i know what's happening: at the point the attack is initiated, the mouse isn't over the mob perfectly, either through it moving or desyc or whatever, so it clicks and holds but it's going to do movement instead of attack. But as it thinks it started with an attack it doesn't release the button and hence follows mob around, maintaining movement rather than attack. Solution: don;t set any skills on left mouse you want to do a hold attack with.

[alkpone 1000000]

Yeah, as bonebox said don't set any skills you don't want to hold attack with.

RC should pick a lot less thrash, feel free to test and give your feedback.

[RubyTuesday 3]

Bot skips scroll of wisdoms sometimes. My bot has no more scrolls... Then i stop restart and it starts working again

[Apache 0]

Using EB 0.19b on Garena,

 

- On inventory full, portal to town. EB doesn't return back to same map to collect rares & uniques.

[johnco00 0]

^ Agreed, not working in garena