Weaponsmith Archive
Thread: nextCraftingStage--from broken to worse?
I raised my Medic character by hand through the Medic, Combat Medic and finally Doctor crafting trees since I could never get the /nextCraftingStage (in any variation) to work. /selectDraft works, /pause works, just not /nextCraft..
The ongoing message thread in this forum made me try it with my Weaponsmith and lo and behold, /nextCraft is actually WORSE now.. Before it would just do nothing, now it eats my resources.
I open my Weapon crafting tool, type "/selectDraft 98" (for my Projectile Rifle Barrel), double click my ingredients and type /nextCraft and it looks like nothing happens. When I try to manually click Assemble it gives me a message saying that my schematic isn't ready since it is missing ingredients. The ingredient list shows as 31/31 and 15/15 (meaning all requirements are met). If I try to drag the 31 and 15 units back out into my resource selection screen on the leftit gives me a message "Cannot add ingredient: not in crafting stage". The only thing I can do is click Back or close the screen and I lose my resources..
I've tried what the "//" command lists (/nextCraftingStage), I've tried different variations like /next, /nextCr, /nextCrafting, etc all with the same results. I'm in the middle of BFE nowhere so there are no crafting stations within 2000m. I've tried it next to a crafting station even. I've tried it next to my droid with a crafting station in it..I even tried turning my Crafting Confirmation option back on under Options. I have always seen about half the people in every macro thread say it works while the other half says they have never gotten it to work but I've never seen or experienced it where even testing the command eats your resources.
Has anyone else noticed this too? (In case you're wondering why I'd be typing the /commands out by hand.. I'm trying to test Anger's macro to make my Weaponsmith's life so much easier. I've found it to be incredibly useful for finding syntax errors, spelling errors, etc. I'm also REALLY hoping to get /nextCraftingStage to work instead of having my macro just start the tool, pick the schematic and pause while I select my resources and pound ENTER a few times..
this may sound dumb, but when i tried manually typing in the commands when crafting, it didn't seem to work properly ever.
However, when i put them all in a macro, it worked like a champ.
Greets ...
I am not at home ... but I beleive you have to put both 2 each /nextCraftingStage on the same line ... and you have to turn "crafting confirmations" on.
Something like:
/select 58;
/pause 5;
/nextCraftingStage;/nextCraftingStage;
/xxxxxxxx practice no item; /xxxxxxx practice no item;
Can't recall what goes into the xxxxx's off hand :-)
Hero_DarkJedi wrote:
Greets ...
I am not at home ... but I beleive you have to put both 2 each /nextCraftingStage on the same line ... and you have to turn "crafting confirmations" on.
Something like:
/select 58;
/pause 5;
/nextCraftingStage;/nextCraftingStage;
/xxxxxxxx practice no item; /xxxxxxx practice no item;
Can't recall what goes into the xxxxx's off hand :-)
/createprototype practice no item;
/createprototype practice no item;
my macro does this: launch one of my tools>load the scheme>pause for 3 seconds to load resources> then the /nextCraft; /nextCraft;/create... create.../ pause for 1 second - then /ui action toolbarSlot01 to call itself again and again until I type /dump in the command bar. all I have to do is double click on steel every 3 or 4 seconds.
I get no critical failures and I can make an average of 3 runs every 10 seconds. Sometimes you have to change the length of the pauses depending on lag. sometimes the loop will get ahead of itself and you'll get an error if the the loop calls /nextCrafting before the resources are completely loaded (due to lag)
if you do run into an error quickly hit Esc untill all screens are closed and the macro will start up again on the next loop. If you still have problem, /dump and restart the macro
Nasents wrote:
/createprototype practice no item;
/createprototype practice no item;
Yea ... that's the ticket ...
And you are correct ... you have to account for lag ... mine was set to 5 seconds to account for the lag and sometimes missed doubleclicks :-)