Macroing Blacksmithing with Razor Problem

[Edie Brickell]

So I'm trying to use a fairly simple macro to make short spears with Razor and raise my blacksmithing skill and I'm running into a frustrating problem. The macro is pretty straightforward...dbl click hammer, target ingots, pick appropriate spots on the menu, wait 4 seconds, rinse and repeat.

The problem I have is that when the macro runs it leaves the menus on the screen and they sort of "pile up" on top of each other instead of disappearing when the choice is picked from the menu as would happen manually. What happens then is that as the macro runs I begin to experience lag as the piling up of the menu somehow slows my functions down. The end result is thato ver time the gumps start to missfire and I start mass producing the wrong items.

Is there any way to set the macro so that when the choices are made the menus disappear thus preventing the lag I'm experiencing???

[Derrick]

I've heard of this problem before but I'm not sure what's causing it, it doesn't seem to happen when crafting normally. I'd suggest adding a pause and make sure you've recorded "wait for menu".

[Edie Brickell]

I've got a .5 second pause between all my commands jsut to account for spikes of lag and random events. None of this changes the fact that the menus don't disappear and their multiple appearances seems to be what causes lag and ultimately causes my macros to misfire. Nice to know I'm nto the only one iwth the problem. Then again if I had some decent RAM it might not matter in the long run anyway. Thanks Derrick, you'[re still my favorite staff member...

[kurai shinzou]

I have the same problem when I macro craft anything. I noticed a significant reduction of the pileup when I put in full 1 second pauses, but they do still stack.

[Kaivan]

A possible solution might be appending a close menu to the end of your macro. Don't hold me to it, but that's my two cents.

[Edie Brickell]

A possible solution might be appending a close menu to the end of your macro. Don't hold me to it, but that's my two cents.

I don't know why I didn't think of this myself, but it could save a lot of troble. Not to mention ingots...whenever my macro begins to deteriorate I end up making heater shileds...no gains and awful waste of ingots....

[johttenn]

I have this same problem.

When I am connected directly to my router I have no pauses inserted in my crafting macros and do not see the menus.

But, when I am on wireless and must have pauses to prevent lag from messing up the macros, the menus stack up.

[Edie Brickell]

I have this same problem.

When I am connected directly to my router I have no pauses inserted in my crafting macros and do not see the menus.

But, when I am on wireless and must have pauses to prevent lag from messing up the macros, the menus stack up.

How long are oyur pauses then? I have .5 seconds and still run into trouble...

[johttenn]

I switch from .5 to 1 sec and have the same issue. Only when I go with no pauses at all does the problem go away...but I can't do that to often because I'm on a really laggy connection

[BlackFoot]

i had this problem before but only when i had a bunch of different ocloured ingots in my pack,

[Prurk]

I never had hang up problems unless I was too close to colored ingots as well. I removed the target by type and began manually re-targeting the ingots when I ran out. this solved that problem.
I find adding too many .5 pauses can cause this as well. Unless your macro is super complicated I'd recommend rerecording it.

The macros I used for smithy only had two pauses. One 2 second pause after I made the item, and one 2 second pause after I smelted the item. Here is what my "make katana and smelt it" macro looks like.

[eyesdearth]

I have not had this problem with tailoring, and haven't tested it in blacksmithing. Maybe it's client-specific. I'm using the 5083 torrent. Are people who are having this problem using a different client version? The download page links to three different ones.

[johttenn]

That may be it, my client is from default install and has never been updated...

Maybe I should do that...