<deleted>

Kaitain · Post by **Kaitain** » Wed Nov 26, 2003 6:48 am

NewUser_24 · Post by **NewUser_24** » Fri Nov 28, 2003 9:26 am

Is there a change in the way MQ2 reads or accesses ini files? Reason I ask is because I have successfully used this macro with MQ1 but when I tried using it today I received the infamous "could not find : <container not found>" problem. I was using a new recipe so to check that I hadn't inadvertantly mistyped I tried using a recipe that I know 100% worked pre patch, pre MQ2.
Yes I am using a custom UI, no it does not have custom bags, and I was able to use this macro successfully for several days so I know the UI, bag positions, and recipes are fine. Only thing that has changed is using MQ2.
/shrug I'd love to debug and troubleshoot this but I am extremely out of practice and there isn't any documentation on MQ2 out yet (didn't look today but there wasn't any as of nov 25).
If anyone knows anything about how MQ2 reads ini files and can give me a hint I can try to figure this out :)

UNREGISTERED · Post by **UNREGISTERED** » Fri Nov 28, 2003 2:09 pm

I just upgraded to MQ2 and loaded the tradescript and it is working fine. I got the no container error but changed the path for the INI file to the full directory path in the new Macro folder and it works very smooth.

Thanks to all who developed it, one question though, I am using a tool and my results are set to destroy on success, and it is destroying the tools as well as the successes.

I think the container not found error could be improved with a step to check that the file is present. That way error reporting wouldn't be as confusing. I will look at it this evening and if I can sort it out will post the code.

Thanks again to the dev dudes.

New_User_24 · Post by **New_User_24** » Sat Nov 29, 2003 4:14 am

Yep that did it. Had the path set relative to macro folder, not absolute. Worked fine for MQ1 but wasn't for MQ2 /shrug. With absolute path it works perfect. Thanks.

Kaitain · Post by **Kaitain** » Sat Nov 29, 2003 7:52 am

New_User_24 · Post by **New_User_24** » Sat Nov 29, 2003 1:55 pm

Just woke up so this might not be the best suggestions but:

So far all the recipes in the ini don't use tools, what about adding a tool part to check for in the recipe?
[NeatRecipe]
Cont=enviro
comp0=some item
.
.
tool=

Adding additional parameter to check for when calling the macro:

/macro TS destroy=1 keep="shaving razor".....

/shrug Not that I'm a wiz at macroing, but I figure different recipes return different number of items on fails and combines so listing the tool you want to keep might be easier on ya. (I just woke up so I can't rember at this point if the tool is always the first item, the last item or in the middle when you are done combining)

UNREGISTERED · Post by **UNREGISTERED** » Sat Nov 29, 2003 8:20 pm

it may be easier to just add an optional result array pointer; so (Cont, Comp0, Comp1, Comp2, CompX, Makes)...that way if Makes is specified it can be set for destroy if it appears on the pointer and if it isn't specified it doesn't destroy, could even array it for multiple results (Makes0, Makes1, etc). I think this would be easier to implement and has the least impact on the recipie format, but I may be wrong. I printed out the files to go over, but my kids are sick and it just hasn't been quiet yet. If I can get some peace I will try and play with it again. Sorry I am not more productive. Again thanks for the dev dudes who put this together, I was in danger of Tradeskill induced carpal tunnel syndrome.

Kaitain · Post by **Kaitain** » Sun Nov 30, 2003 7:04 pm

Rassilon · Post by **Rassilon** » Wed Dec 03, 2003 2:18 am

Nothing but frustration in trying this macro. Here are the steps I do for brewing, for example:

1. stand in front of the brew barrel
2. open my inventory
3. open my last right slot bag that has my brewing supplies
4. open the brew barrel
5. make sure none of the windows overlap or touch each other
6. close brew barrel, bag and inventory window
7. reopen brew barrel, bag, inventory window
8. /macro khits frostessence (for example)

I've tried step 7 with the windows opened and closed. I've used Infinities custUI and defaultUI. All that happens is that the macro picks up one item and puts into the barrel but never completes the macro. It loops and loops and loops. I can't seem to even stop it or even type /endmacro. I have to /q to get it to stop. I am using MQ2.

Thanks,

Rass

Kaitain · Post by **Kaitain** » Thu Dec 04, 2003 9:08 am

dont_know_at_all · Post by **dont_know_at_all** » Thu Dec 04, 2003 1:27 pm

If you rewrite this please do the following:

1. Add a step to open and close all the bags.
2. Better error messages (that refer to the user by name: idiot :-)
3. Debug messages on by default. And lots of them.
4. Confirmation that correct item is picked up by /finditem
5. Dump the usage on any and every error
6. Basically, idiot-proof it because we know no one reads the directions.

UNREGISTERED · Post by **UNREGISTERED** » Thu Dec 04, 2003 2:59 pm

For those who want to stop the macro if you hit F1 to self target it will pause everything. You have to hit it a few times to get the macro to notice, but essentially at the point between completing one combine and beginning the next it looks around real quick.

Rass, can you insert the recipie you are working from? I use this script for pottery and it works fine. I open all bags, not just component one though (I have components in all bags actually). The script tries to take the next component available in inventory. So if you need a Flask of Water and your 8th bag is open with a stack in it but there is a stack in your second bag as well, it will be trying to pull from the second bag and never notice the 8th one.

Rassilon · Post by **Rassilon** » Thu Dec 04, 2003 11:37 pm

Code: Select all

[FrostEssence]
Cont=Enviro
Comp0=Frost Turnip
Comp1=Water Flask

This is just one I've tried but I've tried 4 tradeskills and each one does the same thing.

Thanks,

Rass

Guest · Post by **Guest** » Fri Dec 05, 2003 1:32 am

Try using Cont=#Enviro

That should solve your combine problem.
[/quote]

Amadeus · Post by **Amadeus** » Fri Dec 05, 2003 2:12 am

I think this is misprint in the macro

Code: Select all

    /echo -- Syntax: destroy=1|0 
    /echo -- Example: destroy=1 
    /echo -- Tells the macro wether end-result is destroyed or kept. 
[b]    /echo -- Set to 1 for destroying end-result, 1 to keep end-result. [/b]

<deleted>

Change with MQ2?

Check INI location

ini file

keeping tool

maybe simpler?

Quick stop