Page 1 of 3
Possibly something wrong
Posted: September 21st, 2007, 3:24 am
by strabomeeks
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, 9:42 am
by 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, 6:04 pm
by stupidhead64
working fine on other computer
Posted: September 21st, 2007, 8:28 pm
by strabomeeks
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, 6:33 am
by strabomeeks
im still getting a lot of jibberish for retruns on this value, any word on this Wyv?
Posted: September 24th, 2007, 11:50 am
by Tault_admin
that if VG patched, it VGExtreme may need a patch
Posted: September 29th, 2007, 1:57 pm
by 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, 3:12 pm
by wolfstar
BUMP
Any word on a fix Wyv????
Posted: October 31st, 2007, 2:33 pm
by 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, 4:30 pm
by wyvernx
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.
Posted: November 1st, 2007, 12:51 pm
by 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, 10:31 pm
by marandor
Also wrong:
Roughhew
Treatment
Posted: November 5th, 2007, 7:50 am
by wyvernx
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.
Posted: November 5th, 2007, 7:26 pm
by 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, 9:24 pm
by wyvernx
Whoops, I forgot to include a file.
SHould be working now. Repatch.