[Beta] QuestBot

Are you talking about the built in one or AIF? The few simple rules I've setup seem to work with QuestBot such as save all rare accessories and don't ID them.

 

the built in filter. as an example: i want to vendor unidentified magic rings -> bot id's them first. i set up sell all rares & keep rare accessories -> bot sells all accessories. If I'm using OldGrindBot the filters work fine.

 

Dunno if this is the right place to report it, (yes I know its in beta, hence I want to help out and report any issues =D) But there seems to be a pathhing issue in "the city of sarn" when it tries to path to the sarn encampment, mine was doing a little dance for quite a while (even with the stuck plugin enabled)

And I've noticed that the bot is extremely confused when you die in merveil, it spawns him outside of merveils chamber but then doesn't know how to path to merveil because of the transition.

Keep up the good work! =]

 

ID, sell and moveitem actions are too fast. Should be more human-like like in OGB

 

Problem: Infinity loop(i think?) Failed to open chest and stuck.
Quest: A1_Q3_DirtyJob
SS: http://i.imgur.com/ZRWC5kJ.png
Log: View attachment QB_dirtjobstuck.txt

@edit
Same thing happen in Flooded Depth. Even if i have StuckDecetion enabled it will relog and go to the same instance and stuck again.
http://i.imgur.com/zYmMyVg.jpg

 

Because tin foil hats users like you we get less eficiency, never ever GGG will track and ban shit like this, imagine all the false positives, take off the hat a little bit.

 

Update: Protip to everyone: Take mana potions out of your flask slots if you go blood magic.

You need to register and have one post to see spoilers!
You need to register and have one post to see spoilers!

 

ID and sell are no faster than humans. Are you comparing it to clicking and dragging each time? Because most experienced players will shift click to ID or ctrl click to sell. Item movement as well, I can put a stash full of currency in my tab faster than the bot just by ctrl clicking.

And if you want to get super legit, it's more likely that someone with 20 hours of playtime knows these things and is faster moving items. Would look a bit suspicious for someone playing that long every day to still be manually dragging each item slowly.

 

So a human can ID 7-8 rares AND stash them within 1-1.5 seconds? I know shift+click is fast but I doubt it's that fast.

 

An update to my earlier report, if the bot dies on dominus it gets even more confused, it failed to even path when I manually put it back inside the "dominus room"
Don't die on bossfights pretty much =P

 

Also this QuestProgress.txt file should be saved in settings folder so its possible to level 2+ chars with 1 bot instance.

 

Please post logs when these issues happen so ExVault has something to go off of. Aside from the log a detailed description of the problem and a way of reproducing it helps find a fix faster for developers. If they're unable to reproduce it they're probably never going to find a fix as they would have no way of confirming what they changed worked.

 

Will be hyped when this is complete

 

If bot would used shift-click it would be ok but it clicks on scrol, click on item, clicks on scrol, click on item, clicks on scrol, click on item ... It x2 clicks than normal player with the same (if same) ID speed.

 

same on Kaom fight
my char died and refuse to come back and just stop.

Code:

[WalkablePosition] "King Kaom" at {1860, 422} (distance: 996) is unwalkable.

When i move him manualy inside kaom's boss room he continue to run just fine.

 

The Grand Arena bot stop
SS: http://i.imgur.com/gLAkawV.jpg
You need to register and have one post to see spoilers!
@edit
when i start bot again in new grand arena instance same error:

Code:

[FindAll] Found total 3 tgt(s) with name "colosseum_wall_door_v0?_0?_c3r2.tgt".
[FindFirstWalkablePosition] Now trying to find walkable position for {575, 1173} (distance: 688)
[FindFirstWalkablePosition] Walkable position for {575, 1173} (distance: 688) has not been found.
[FindFirstWalkablePosition] Now trying to find walkable position for {391, 2277} (distance: 1803)
[FindFirstWalkablePosition] Walkable position for {391, 2277} (distance: 1803) has not been found.
[FindFirstWalkablePosition] Now trying to find walkable position for {1679, 2415} (distance: 2212)
[FindFirstWalkablePosition] Walkable position for {1679, 2415} (distance: 2212) has not been found.
[TgtPosition] Fail to find position for "colosseum_wall_door_v0?_0?_c3r2.tgt". Type: Closest.
[CRITICAL ERROR] Now requesting bot to stop.
[Stop] Now requesting the BotThread to stop.

I had to place bot in daresso boss room to make him progress again.

 

ahhh will do, next time I run into an issue I'll be sure to get the logs so I can report things properly! =]
I'll ttry my best to give a proper 'bug' report next time. sorry about that!

 

Also bot seems to cast auras too late in some boss fight. For example malachai 2nd phase, he cast aura after he goes down so bot cast auras and mobs kill you in meantime.

 

Thank you for all the reports, especially ones with logs
It seems pathfinding bugs to boss/bossroom after death are the most common ones. I am currently working on it.
There was some conflict between QuestBot and DefaultPlayerMover which caused movement errors in act 3. Its was fixed, if you are still getting it - you might be using a custom player mover.

Please ensure that you created the QuestProgress.txt in \3rdParty\QuestBot\ directory, not \3rdParty\_CONFIGS_\Default\QuestBot\
And IDs are set properly, for your case, if you have just arrived to act 2, you should set the bot to A2_Q1_SharpAndCruel, which should be 8,0 in QuestProgress.txt

Thanks for the report, currently bot indeed perform identification on everything, ignoring the filter rules. Thats gonna be fixed.
But vendoring is working fine for me. Bot sells items only marked for sell in item filter and stashes everything else. Also, nobody else reported such issue. Please check your item filter setup.

Good catch. This is controlled by "public const bool GlobalUseReactionWait" in \EXtensions\EXtensions.cs\
It should be set to "true", so bot is human-like by default, but users who wanna be as speedy as it possible could set it to false. Bot I forgot about that and now is false by default. Will fix in next version.

According to your log, you did not stuck. There were too many invisible monsters or something and bot was trying to kill them, in log you can see TrackMobTask spammed kill attempts, but nobody was around. Next time this happens, please open the ObjectExplorer plugin and navigate to Monsters. It will open a list of all nearby monsters sorted by distance to you. Copy information about first 2-3 alive monsters and send it to me. Also, it seems like a general Cadiro chest problem and does not relate to QuestBot in particular.
You next stuck near shrine is a different one, bot makes only few attempts to take a shrine and if it fails bot will ignore it and move forward. I don't know why you got stuck near it, provide a log please.

Movement logic is general and not tied to a particular bot. It seems many users have such problems, please look at this thread.
For identification speed: check the "public const bool GlobalUseReactionWait" in \EXtensions\EXtensions.cs\. It should be false for max speed.

Will be fixed in next version.

 

Thank you! Any new version ETA?