VSOH - Advanced Crafting Bot v1.1 : VGExtreme Programs

kronfu wrote:Loaded the program on another computer and all the other problems i had went away. The only issue i am having now is getting workorders. I use the default UI for crafting. When getting work orders it only displays 10. IF none of the first 10 work orders meet the criteria i set then the script runs around. How do i ge the script to scroll down and display the next 10? Thanks.

It does scroll down; you're the first I've heard having this problem. It sends mousewheel I/O commands to scroll.

Try this... manually open the work order window, select any of the work orders on the available page, and use your mousewheel to scroll up and down the list. If it does not work, then there is likely a problem other than the bot, although theoretically, the mousewheel commands should work even if you have no mousewheel.

beergeek wrote: Make sure the refining and finishing skills in the userdata file are set to your BASE skill values. These would be your station/tool/utility skills without gear, modifications or guild trophy buffs.

The script uses your base skill levels to determine how many (and what) complication remedies you have available. If the skill numbers are too high, it will think you have more remedies available than you really do and end up clicking as you described.

EDIT: if you are a blacksmith, that could be related. I don't have bs code fully in yet, although it will be in next release.

I don't think that's it. I am a 20th lvl Tailor and I got it even with default skill settings which are lower than mine.
It's not that it's trying to click on the counter action that is not there. Its trying to click on the complication that's not there.
For example: we have 3 slots for complications. If I get complication 1 and don't address it, I might get a complication 2 on top of it and then 3. Well what happens is--I get complication 1, but it starts clicking on complication 2 which is not there.
I have not caught it in time yet, but I am guessing that in some cases, if I don't have tools or regs to fix complication 1, it assumes that I got a complication 2 and tries to resolve it.

railshot wrote:I don't think that's it. I am a 20th lvl Tailor and I got it even with default skill settings which are lower than mine.
It's not that it's trying to click on the counter action that is not there. Its trying to click on the complication that's not there.
For example: we have 3 slots for complications. If I get complication 1 and don't address it, I might get a complication 2 on top of it and then 3. Well what happens is--I get complication 1, but it starts clicking on complication 2 which is not there.
I have not caught it in time yet, but I am guessing that in some cases, if I don't have tools or regs to fix complication 1, it assumes that I got a complication 2 and tries to resolve it.

Ahh, I know what you're talking about now. This is a bug where a complication comes on the heels of another, but the comp that disappears provides no chatlog text that the comp has gone away. Therefore, the script thinks the new comp is the second, not the first.

I have fixed this in the version I am running, which will be released once I work on a couple things. Fortunately, this shouldn't be a common occurrence, so when it happens in the meantime, just click through it and move on.

Scrolling works wonderful now. Down to two issues for me:

1. Buying from vendor - if i have this enabled, my crafter always goes to the vendor and purchses all the items listed in the script, even if i already have the quantity in my inventory.

2. When i run out of Action Points, The bot just keeps trying to hit the same key, and i get the 'You do not have enough action points' spam.

kronfu wrote:Scrolling works wonderful now. Down to two issues for me:

1. Buying from vendor - if i have this enabled, my crafter always goes to the vendor and purchses all the items listed in the script, even if i already have the quantity in my inventory.

2. When i run out of Action Points, The bot just keeps trying to hit the same key, and i get the 'You do not have enough action points' spam.

1: Make sure the name of your default chat tab is 4 letters, that timestamp display in your chat is turned off and that you are not filtering the chat type that displays the results of the /inventory command.

The timestamp or tab name bugs have been addressed for the next release.

2: If you run out of AP, it should only try a final action then cancel automatically and start the next recipe. If it is hanging here, then it is probably not recognizing the chat text. Again, follow the recommendations for #1

kronfu: strangely, I had the same problem you had in #1. Adding the following line in Sub Init() in acbinit.vbs solved it for me. Not sure why it was working before and not now, though...

VG.Log.EnableLiveChatLog()

Just an FYI: GU3.2 is preventing the navigation part of the script from working, but the crafting works fine. This means you will need to manually turn in work orders and buy utilities until wyvernx gets the updated vgservice out.

The easiest way to force the script to stop after completing your work orders is the following:

Open the acbinclude.vbs tab and scroll all the way to the bottom

The last subroutine is called Start_Crafting. In there, there's the following line:
After that, insert the following two lines:

I just found out about the patch. I'm looking into it and should have a patch out today.

What does error

'Error:Line 839, Char:4::Input past end of file


Line 839 is:

strSearchString = objFile.ReadAll


Thanks.

Never seen it before. Is it happening regularly, or just a one-time thing?

Beergeek,

I have having an issue with refining. The Bot is stalling on me. Below is where it is stalling

Refining
Stage 2
Treatment and it shows 2 available actions.

I am currently level 40 crafiting and have the following base stats..

Outfitting

const refStat = 234
const refUtil = 372
const refTool = 305

Here is a short copy of the log files that is produced when it stalls.



2007-12-14 15:14:24 Clearing Log
2007-12-14 15:14:24
2007-12-14 15:14:24 craft: skipCraft = False
2007-12-14 15:14:24 step name = 'Treatment'
2007-12-14 15:14:24 Util2 action family identified
2007-12-14 15:14:24 sub idUtil2 args: 1
2007-12-14 15:14:24 sub pressHotkey args: 1
2007-12-14 15:14:27 Util2 HK2
2007-12-14 15:14:27 sub Craft
2007-12-14 15:14:27 Crafting Step = 3
2007-12-14 15:14:27 sub checkLog
2007-12-14 15:14:27 Clearing Log


2007-12-14 15:14:27 Clearing Log
2007-12-14 15:14:27
2007-12-14 15:14:27 craft: skipCraft = False
2007-12-14 15:14:27 step name = 'Treatment'
2007-12-14 15:14:27 Util2 action family identified
2007-12-14 15:14:27 sub idUtil2 args: 1
2007-12-14 15:14:28 sub pressHotkey args: 1
2007-12-14 15:14:30 Util2 HK2
2007-12-14 15:14:31 sub Craft
2007-12-14 15:14:31 Crafting Step = 3
2007-12-14 15:14:31 sub checkLog
2007-12-14 15:14:31 Clearing Log


2007-12-14 15:14:31 Clearing Log
2007-12-14 15:14:31
2007-12-14 15:14:31 craft: skipCraft = False
2007-12-14 15:14:31 step name = 'Treatment'
2007-12-14 15:14:31 Util2 action family identified
2007-12-14 15:14:31 sub idUtil2 args: 1
2007-12-14 15:14:31 sub pressHotkey args: 1
2007-12-14 15:14:34 Util2 HK2
2007-12-14 15:14:34 sub Craft
2007-12-14 15:14:34 Crafting Step = 3
2007-12-14 15:14:34 sub checkLog
2007-12-14 15:14:34 Clearing Log


2007-12-14 15:14:34 Clearing Log
2007-12-14 15:14:34
2007-12-14 15:14:34 craft: skipCraft = False
2007-12-14 15:14:34 step name = 'Treatment'
2007-12-14 15:14:34 Util2 action family identified
2007-12-14 15:14:34 sub idUtil2 args: 1
2007-12-14 15:14:35 sub pressHotkey args: 1
2007-12-14 15:14:38 Util2 HK2
2007-12-14 15:14:39 sub Craft
2007-12-14 15:14:39 Crafting Step = 3
2007-12-14 15:14:39 sub checkLog
2007-12-14 15:14:39 Clearing Log


2007-12-14 15:14:39 Clearing Log
2007-12-14 15:14:39
2007-12-14 15:14:39 craft: skipCraft = False
2007-12-14 15:14:39 step name = 'Treatment'
2007-12-14 15:14:39 Util2 action family identified
2007-12-14 15:14:39 sub idUtil2 args: 1
2007-12-14 15:14:39 sub pressHotkey args: 1
2007-12-14 15:14:41 Util2 HK2
2007-12-14 15:14:42 sub Craft
2007-12-14 15:14:42 Crafting Step = 3
2007-12-14 15:14:42 sub checkLog
2007-12-14 15:14:42 Clearing Log


2007-12-14 15:14:42 Clearing Log
2007-12-14 15:14:42
2007-12-14 15:14:42 craft: skipCraft = False
2007-12-14 15:14:42 step name = 'Treatment'
2007-12-14 15:14:42 Util2 action family identified
2007-12-14 15:14:42 sub idUtil2 args: 1
2007-12-14 15:14:42 sub pressHotkey args: 1

officers: an fyi, where it says Util2 HK2 is just a display bug where I fat-fingered a debugLog statement where it's telling HK2 for HK1 and vice versa.

The important line is "sub pressHotkey args: 1" which is telling me the next action is VGsendKeys HK1. I have no idea why it would be looping here unless there is some kind of external influence.

Does this happen every time?

beergeek wrote:officers: an fyi, where it says Util2 HK2 is just a display bug where I fat-fingered a debugLog statement where it's telling HK2 for HK1 and vice versa.

The important line is "sub pressHotkey args: 1" which is telling me the next action is VGsendKeys HK1. I have no idea why it would be looping here unless there is some kind of external influence.

Does this happen every time?

Yes, it happens everytime on this particular work order in exactly the same spot. Finishing work orders work great. It's just the refining.

I will PM you a complete log file that includes this work order from start to whe it hangs. I deleted the old log file so this one will be just this work order.

Hiya, where in the script does it list the location for the Complication buttons. Right now when it clicks it misses the second complication. Thanks.

kronfu wrote:Hiya, where in the script does it list the location for the Complication buttons. Right now when it clicks it misses the second complication. Thanks.

I think it is based off of the follwoing button...

'HotKey To Cancel Crafting - this is the cancel button when you are actually crafting. SET POINT TO CENTER OF BUTTON.

The problem I think your describing is probably a bug in the script. I have the same thing that happens to me occasionally.