Page 1 of 1

Request: 'pack 8' == enviro - update - 'pack e'

Posted: Fri Aug 08, 2003 2:20 am
by GoatFoot
I've been playing around with tradeskill macro's and have found the syntax differences between enviro and inv containers to be a bit awkward.

currently, to left click slot 0 in an enviro container, we must:

Code: Select all

/click left enviro 0
while for an inv container its:

Code: Select all

/click left pack # 0
'#' being the inventory slot of the pack, 0 - 7.

I'd very much like:

Code: Select all

/click left pack e 0
to be the same as

Code: Select all

/click left enviro 0

Awkward?

Posted: Fri Aug 08, 2003 3:22 am
by wassup
How is it awkward?

Pack = container in your inventory, 2nd # = which pack, 3rd #= slot in the pack. You can always use /finditem with all your packs open, and it's much easier.

enviro = external container, such as a Forge or Brew Barrel, 2nd # = slot in that container.

Seems fairly straightforward to me

Posted: Fri Aug 08, 2003 4:05 am
by GoatFoot
Because the syntax required to address a slot in a combiner is different based on whether the combiner is in your inventory or not.

This means that when you can't write a generalised macro with out doing some sort of hack like:

Code: Select all



/call something

| hack to set combiner

/varset COMBINER enviro
/if n $return<8 /varset COMBINER "pack $return"

/click left $COMBINER <slot>


sub something
.
.
    /for l0 0 to 7
       /if "$pack($l0,combine)"~~"<tradeskill>" /return $l0
   /next l0
/return $l0

I believe that it would be simpler if "pack 8" always pointed to enviro.

yes, it just saves a couple lines, but it should be a trivial mod.

not 'pack 8', but 'pack e' or something.

Posted: Fri Aug 08, 2003 5:26 am
by GoatFoot
On further thought, 'pack 8' probably isn't the way to go. Who knows what inventory changes may take place. Instead something like 'pack e' may be better.

I'll edit my original post.