VG Advanced Crafting Bot v2.0 : VGExtreme Programs

[sagatious]

I see there was a significant patch a couple days ago. Is the bot broken (or is anyone still using it)?

It's a little broken... not getting crafting level, etc.
I havent had a chance to run through it yet though to pick up the new offests, may get to it tonight... we'll see.

Ok, here's the updated offsets...

Crafting Level = 0x4962C0
Base Crafting Skill = 0x4961E4
auto setup = 0x496D70

[beergeek]

Thanks again, update posted.

[Tault_admin]

sagatious 500 points to you. Keep up the good work.

[dxwarlock]

any update on this, is it dead?
it works fine it seems other than finding my level..so it always using option 1 on every stage.

or was a new bot released that works that Im missing?

[lorddread]

wouldn't mind knowing if this is working as well still?

[tourertt]

Hi! Bot is working fine (except for level recognise) on one of my computers. However, when i try to run it on another computer, bot pauses every time it targets something (taskmasters, stations, utility/repair merchants). What is the problem? I have tried many different things... Please help

[beergeek]

Now that Vanguard is free to play, I may tinker around with the bot again. That is, if I can get it successfully loaded into VS12. If I can get it going, I can fix the broken level offsets and just maybe update it to allow full automation of crafting above level 50. Don't expect anything quick; it's been a long time since I've even looked at the code.

[beergeek]

@beergeek

Do you have any News for us waiting folks

[Tault_admin]

Do you need anything else beergeek to help you. I can ask the viper guys for some stuff if needed.

[beergeek]

Tault_admin, Yes, if you can find out from wyvernx exactly what dlls are loaded in the course of running vgextremeservice.exe, I may have better luck being able to find the culprit. Unfortunately, I believe the code which encrypts and protects the service is also preventing me from being able to figure out what dll is causing the program to crash each time I run it.

As it stands, not only can I not run the service, but I cannot reference the service in visual basic to expose the methods to my app. It's been that way for a few years now, ever since I ran a particular batch of windows updates. I'm somewhat confident the problem is in a windows dll that's been updated which doesn't play nice with the service, but that is truly a needle in a haystack to guess and try older files.