Weaponsmith Archive
Thread: anyone know crafting macro
Page 1 of 1
Manbush
Mon Oct 17, 2005 6:00 pm
#1
been playing on 2 years, never used a macro so call me macro noob, just wondering if anyone has a good crafting macro, my wrists are killing me:/
StarNick
Mon Oct 17, 2005 6:25 pm
#3
For grinding or just churning out generic-named components/items?
If the latter, you could use:
nextcraftingstage;
nextcraftingstage;
nextcraftingstage;
createPrototype;
createPrototype;
Then assign a UI toolbar button to a key, and whenever you've finished putting in resources, just hit the button and bam. Of course you cannot name nor experiment if you do this, but you can use this during any crafting stage.
For grinding, you could modify this to:
nextcraftingstage;
nextcraftingstage;
nextcraftingstage;
createPrototype practice no name;
createPrototype practice no name;
And it won't produce an actual item, rather using the practice feature to get the extra few xp from the item.
Now, if you want a more complex macro...one that runs multiple tools, those are tricky and really need some fine-tuning on your part.
This is an example of a 4-part macro that ran quite a few tools when I was grinding weaponsmith:
/ui action toolbarSlot00;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot01;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .75;
/ui action toolbarSlot02;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot03;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot04;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/macro grindcraft2;
You can of course modify the pauses to what suits you best, and have the macro repeat itself rather than go onto another macro...
If the latter, you could use:
nextcraftingstage;
nextcraftingstage;
nextcraftingstage;
createPrototype;
createPrototype;
Then assign a UI toolbar button to a key, and whenever you've finished putting in resources, just hit the button and bam. Of course you cannot name nor experiment if you do this, but you can use this during any crafting stage.
For grinding, you could modify this to:
nextcraftingstage;
nextcraftingstage;
nextcraftingstage;
createPrototype practice no name;
createPrototype practice no name;
And it won't produce an actual item, rather using the practice feature to get the extra few xp from the item.
Now, if you want a more complex macro...one that runs multiple tools, those are tricky and really need some fine-tuning on your part.
This is an example of a 4-part macro that ran quite a few tools when I was grinding weaponsmith:
/ui action toolbarSlot00;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot01;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .75;
/ui action toolbarSlot02;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot03;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/ui action toolbarSlot04;
/pause 1.5;
/ui action defaultButton;
/pause 5.5;
/next;
/next;
/next;
/createPrototype practice no item;
/createPrototype practice no item;
/pause .5;
/macro grindcraft2;
You can of course modify the pauses to what suits you best, and have the macro repeat itself rather than go onto another macro...
Page 1 of 1