Post Reply Home » Forums » Vanguard » VGExtreme General Discussion

Possibly something wrong : VGExtreme General Discussion

Posted: September 21st, 2007
Total Posts:266 Joined:2007
I am starting to get jibberish on some of the returns for

Crafting_StepName

Where before I would get something like:

Heat Metal
Work
Stitch
Frame

Now I am getting this:
??ri?t
?ly?eet
bu?1po?

VGExtreme might need an update?? not sure, but this started happening this morning.
Posted: September 21st, 2007
stupidhead64
Thats where my script just stops totally when it gets to Crafting_StepName, even though im using the exact one you use..Might just be a VBE prob
Posted: September 21st, 2007
stupidhead64
working fine on other computer
Posted: September 21st, 2007
Total Posts:266 Joined:2007
yeah, I knew that the problem you were having is computer specific because it is working for everyone else and it is working on the 3 computers I can test it from.

Just like VGBuddy will not work on one of my computers for some reason no one can determine, but it works on the other two just fine.
Posted: September 23rd, 2007
Total Posts:266 Joined:2007
im still getting a lot of jibberish for retruns on this value, any word on this Wyv?
Posted: September 24th, 2007
User avatar
administrator
Total Posts:29918 Joined:2002
that if VG patched, it VGExtreme may need a patch
Posted: September 29th, 2007
wolfstar
I've also come across this problem and it needs fixing ASAP, this is a bot breaker. I don't seem to see anything being done by the creator, there's API's being waited on and this issue and he's not even posting about them!
Posted: October 6th, 2007
wolfstar
BUMP
Any word on a fix Wyv????
Posted: October 31st, 2007
wolfstar
Is this just a too hard to fix problem so you're ignoring it Wyv and anyone who asks about it?
Posted: October 31st, 2007
User avatar
Premium
Total Posts:6718 Joined:2004
I will take a look at this. Be SURE that when you call craft-name API you have alraedy called a /selectcraftingstep xxx or else it will return gibberish. Ie you have to have a step selected before you can get the name from it I beleive.

That said...

I am sorry, for some reason I miss threads. Thanks whoever send me the PM and linked me in. If I can reproduce the error, I'll get out a patch tonight. Give me about 2 hours to get it out.

_________________
Use Search first, ask questions later!
Posted: November 1st, 2007
wolfstar
I'm positive the scripting is correct with the stepname being called.
The main culprits I've found have the following step names;
Softener
Alter
Arrange Material
Ornament
Decorate
TableSaw
Embroider
Adjust Heat
Manipulate
Heat Metal

There are probably more I haven't found yet but hopefully these will help steer you in the right direction, if you need any other info just ask.
Posted: November 2nd, 2007
Total Posts:7 Joined:2007
Also wrong:
Roughhew
Treatment
Posted: November 5th, 2007
User avatar
Premium
Total Posts:6718 Joined:2004
I just did another test of this, and whenI run this:

DebugLog VG.Crafting.StepName(1)
DebugLog VG.Crafting.StepName(2)
DebugLog VG.Crafting.StepName(3)
DebugLog VG.Crafting.StepName(4)

While crafting, it shows correctly the names of the steps.


Now, I also tested this:
DebugLog VG.Crafting.Actionname(1)

And it will ONLY work once you have selected /craftingselectstep XX

After I select a step, it shows me every time the name of the possible counters I can cast.

I added RemedyName : DebugLog VG.Crafting.RemedyName(1)
but again, you MUST click on the remedy base icon to have it populate the sub-action events else you cannot get the names out.

I am still workign on adding Complicationname(step) to get the base complication name that is outputted in the log. But since it is output in the log I'm gonna go ahead and post this update.

If you still have problems after updating, please try the DebugLog things like I did and make sure it is returning correct values.

_________________
Use Search first, ask questions later!
Posted: November 5th, 2007
stuarcl
Well ever since this update I get a "VGExtreme has encountered a problem and needs to close. We are sorry for the inconvenience." error. Anyone else getting this? I can still run exhume fine, but not vgextreme.
Posted: November 5th, 2007
User avatar
Premium
Total Posts:6718 Joined:2004
Whoops, I forgot to include a file.

SHould be working now. Repatch.

_________________
Use Search first, ask questions later!
Ready to join the community? Click here and see all of the benefits!
blue large dotWho is online
Users browsing this forum: No registered users and 12 guests
Post Reply