Zugg Software :: View topic

Posted: Thu Sep 01, 2005 5:21 pm

Been thru loads of posts here, and unless i am looking the wrong way, i'm missing what I am looking for

Trying out a new mud that has an assemble command.

ex:
assemble crystal strap 2.strap

success msg:
You assemble a small crystalline dagger!

if you try to asssemble items that wont make anything:

assemble crystal strap

Fail msg:
You fiddle with your inventory, but fail to assemble anything useful.

#BUTTON 1 {Assembler} {askass}
#alias askass {
#var ItemTypeAsk {}
#var ItemCountAsk {}
#PR ItemTypeAsk "What item would you like to use?"
#ADDITEM Assembly.ItemType @ItemTypeAsk
#PR ItemCountAsk "How many of them are you going to use?"
#ADDITEM Assembly.ItemCount @ItemCountAsk
#YESNO {"Are there any more Items in this?"} {*Yes:askass} {No:doass} {Cancel:#Echo %cr%ansi( bright, red)Assembly Cancelled.}
}
#alias doass {all the looping stuff here}
#TRIGGER {^(You assemble (%*))~!$} {#SUBSTITUTE {%ansi( bright, red)"%1" utilizing (whatever the count and item type was)}}
#VAR ItemCountAsk {} {}
#VAR ItemTypeAsk {} {}
#VAR Assembly {} {}

I am very sure I havn't done askass correctly for this.
I enter that I have 2 leather & 2 obsidian
It stores it as
#VAR Assembly {ItemTypeleather|obsidianItemCount2}

Which is kinda correct, except that the 2 only appears once, and if I am using 3+ items of some same and some diff # then it wouldnt know which is which.

When I run it again with diff items:
4 leather & 2 bamboo
#VAR ItemCount {2|4} {}
#VAR ItemType {leather|obsidian|bamboo} {}

The obsidian is still there but I'm assuming somewhere in the doass it will clear it after a success or the FINAL fail with a #VAR ItemCount {} {};#VAR ItemType {} {}

As for doass what I would like it to do is run thru this:

assemble 1.leather 1.obsidian
assemble 1.leather 1.obsidian 2.obsidian
assemble 1.leather 1.leather 1.obsidian
assemble 1.leather 1.leather 1.obsidian 2.obsidian

Of course it would have to loop thru as many times as the highest # of items

After each assemble if it sees:
You fiddle with your inventory, but fail to assemble anything useful.
it goes to the next step

assemble 1.leather 1.obsidian
You fiddle with your inventory, but fail to assemble anything useful.
assemble 1.leather 1.obsidian 2.obsidian

And if sees the success it stops
assemble 1.leather 1.obsidian
You fiddle with your inventory, but fail to assemble anything useful.
...etc etc...
assemble 1.leather 1.obsidian 2.obsidian 2.leather
You assemble a primitive chisel utilizing 2 leather 2 obsidian

btw:
Any combination as long as the # is there works so the exact order that it does it is not a concern:

assemble 1.leather 2.obsidian 1.obsidian 2.leather
You assemble a primitive chisel!

Any help would as always make me worship you.

SubAdmin Joined: 18 Nov 2001 Posts: 5187

First question is does assembling 3.leather and 3.obsidian also make a primitive chisel?

Next does failing an attempt to assemble eat items in your inventory?

Do you have a complete and current inventory list stored in a variable? If so format (like mine is a record fields of name values of 'total bag qty bag qty')?

Do you have a list of likely 'assembly' objects?

Posted: Fri Sep 02, 2005 2:00 am

well, 1. and 2. and 3. and 4. and anyother #. is not due to addition. It's the 2nd, 3rd, 4th item of the type.
So 3.leather and 3.obsidian is just 1 of each. Thought that was common on all muds so i didn't point that out. sorry.

Inventory is not eaten on a fail.

If i had a complete and current inventory list in a variable then I could just have an alias that would do the specific assembly needed, i think.

As for a list of assembly objects, see what i just said about the alias :-)

What i think would be the hardest thing about all this is the knowing which # is highest since i might not enter them in order. of course i don't even know if that will matter. This makes my head swim

SubAdmin Joined: 18 Nov 2001 Posts: 5187

Lets start with inventory capture and logging. I will simply post what I use, and you can modify it for yourself to get it working.

Posted: Fri Sep 02, 2005 6:18 pm

ummmm....sorry, but no clue how this will work.
i just want to type an alias, that will then allow me to enter items and thier quantity and have them loop thru in an assemle.
Neck, finger, wrist, all this is not needed.
i have 3 leathers and 2 obsidians in my inv.
i type askass, then item #1 and qty, item #2 and qty, and if that's it, then start all the combinations possible.
There's nothing in what you posted that resembles even being able to do that....

Posted: Sun Sep 04, 2005 2:33 pm

Posted: Thu Sep 08, 2005 4:21 am

Well, found a post about %additem that got me thinking and I got this so far
#CLASS {AssemblerV3}
#ALIAS askass3 {
#var ItemTypeAsk {}
#var ItemCountAsk {}
#PR ItemTypeAsk "What item would you like to use?"
#var Assembly.ItemType %additem( @ItemTypeAsk, @Assembly.ItemType)
#PR ItemCountAsk "How many of them are you going to use?"
#var Assembly.ItemCount %additem( @ItemCountAsk, @Assembly.ItemCount)
#YESNO {"Are there any more Items in this?"} {*Yes:askass3} {No:doass} {Cancel:#SAY %ansi( bright, red)Assembly Cancelled.}
}
#ALIAS doass {#echo all the good looping here}
#VAR Assembly {} {}
#VAR ItemCountAsk {} {}
#VAR ItemTypeAsk {} {}
#TRIGGER {^(You assemble (%*))~!$} {#SUBSTITUTE {%ansi( bright, red)"%1" utilizing (whatever the count and item type was)}}
#BUTTON 3 {Assembler3} {
#var Assembly {}
askass3
} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} "" {} {} {}
#CLASS 0

the result is happily
#VAR Assembly {ItemTypeleather|Obsidian|BambooItemCount2|2|3} {}

duplicate items are not a prob for me anymore.
I just still have the output prob.
Is that I would like just NOT possible at all?
I have 3 items, and i'd like to combine them in all possible ways based on the qty i have of each. Or is my approach wrong?

starting from:
assemble 1.leather 1.obsidian 1.bamboo
all the way to:
assemble 1.leather 1.obsidian 1.bamboo 2.leather 2.obsidian 2.bamboo 2.leather 2.obsidian 3.bamboo

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

here is a start to the massive nested loop that needs to follow:

the variable:

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

after the code in the above alias, ive added the following, but i cant for the life of me get the loops straight but hopefully someone can work with it:

Posted: Thu Sep 08, 2005 11:07 pm

looking at it and not getting it :(
need to go from 1. of how ever many objects to n. of how ever many objects.

assemble 1.leather 1.obsidian
assemble 1.leather 1.obsidian 2.obsidian
assemble 1.leather 2.leather 1.obsidian
assemble 1.leather 2.leather 1.obsidian 2.obsidian

the order has no bearing in the creation.
1.itema 2.itema 1.itemb
is the same as
1.itemb 2.itema 1.itema

besides, considering 15 straps, and any extra items would amount to more than the 18 or so that comes up.
if there are 15 of one and 10 of another then the end result would be from
1.strap 1.obsidian

all the way to

1.strap ....15.strap 1.obsidian ... 10.obsidian
the possible combinations there are a LOT more than 18, and that's just with 2 items.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

for that last output... the variable contained:

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

ok,,, try this script....

Posted: Fri Sep 09, 2005 12:36 pm

Don't think it will work...unless i dont know what the heck yer doing and how to make it do more than what it does
I need more than just
assemble 1.a 1.b
assemble 2.a 2.b

It's
assemble 1.a 1.b 2.a 2.b

and more.

one particular assembly uses like 4 diff items of different amounts:

a bamboo fishing pole
> a bamboo pole
> a bamboo pole
> a giant crab claw
> a small length of rope
> a small length of rope
> a small length of rope
> a length of leather
> a length of leather
> a length of leather

so to make a bamboo fishing pole i have to type out:
assemble 1.bamboo 2.bamboo 1.claw 1.rope 2.rope 3.rope 1.leather 2.leather 3.leather

here's the thing, bamboo poles aren't findable, they have to be made, but i don't have that in the file so i have to figure out how to make it.
that's where i got the idea for an assemble script.
I'll assume a bamboo pole uses bamboo, and either leather or rope.
so i'd just gather a load of bamboo, leather and rope, and run 3 things.
1) bamboo & leather combo
failing that
2) bamboo & rope combo
failing that
3) bamboo, leather & rope combo
failing that
4) throw computer out window

I dont need the script to send all three possibilities out, i can do that myself on a one by one basis.
but what I need it to do is when i have entrered all 4 components and qtys, run:
assemble 1.bamboo 1.claw 1.rope 1.leather
assemble 1.bamboo 1.claw 1.rope 1.leather 2.leather
assemble 1.bamboo 1.claw 1.rope 1.leather 2.leather 3.leather
assemble 1.bamboo 1.claw 1.rope 2.rope 1.leather
assemble 1.bamboo 1.claw 1.rope 2.rope 1.leather 2.leather
assemble 1.bamboo 1.claw 1.rope 2.rope 1.leather 2.leather 3.leather
until the final combo of:
assemble 1.bamboo 2.bamboo 1.claw 1.rope 2.rope 3.rope 1.leather 2.leather 3.leather

It does the 1st, and then based on the msg of success or failure it either does the next or stops and reports what was made and how.

Order is NO matter.
2.bamboo 1.claw 3. leather is the same as 1.claw 2.bamboo 3. leather
But all the components have to be there for a success.

Of course, the FUN part (as if all this wasn't already fun) is that it needs to SKIP known items...like PRETEND that
1.bamboo 1.claw 1.rope 2.rope 1.leather 2.leather 3.leather
made something, but I already know that, I need it to SKIP this particular combo and goto the next one because since i know it, and don't NEED that item it's a wasted trip.
Like in brewing a potion
you have 2 acids and 1 blood
brew 1.acid 1.blood
That explodes in your face.
You don't want that, so you have it stored that NEVER run that combo. it will only do
brew 1.acid 2.acid 1.blood

(note: this is not part (that i know of) the mud that i am trying to do this whole assembly stuff for. it's just another example)

I was planning on storing the created items components in a variable and have it check on a %ismember thing to tell it to skip it.

Really starting to think that this isnt going to work at all. *sigh*
Seems simple enuf, but damned if i know how to explain it better.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

ok... let's say you want to try your 1st thing... leather and bamboo...

cleraitems alias 1st....
Adding 2 leather
Adding 2 leather
Adding 3 bamboo

Assembling with 3 items
assemble 1.leather 2.leather 1.bamboo
assemble 1.leather 2.leather 2.bamboo
assemble 1.leather 2.leather 3.bamboo
assemble 2.leather 1.leather 1.bamboo
assemble 2.leather 1.leather 2.bamboo
assemble 2.leather 1.leather 3.bamboo
All Done.

there are 2 sets of 3 there.... 123 and 456, i know 123 is the same as 456.... but what should it be doing differently?

Posted: Fri Sep 09, 2005 2:39 pm

k, getting me all confused.
I look at my inventory and see
2 leather
3 bamboo

So, i enter
additems 2 leather
additems 3 bamboo

and the result that I get from your script is

Assembling with 2 items
assemble 1.leather 1.bamboo
assemble 1.leather 2.bamboo
assemble 1.leather 3.bamboo
assemble 2.leather 1.bamboo
assemble 2.leather 2.bamboo
assemble 2.leather 3.bamboo
All Done.

ALL the possible combos *I* need start with
assemble 1.leather 1.bamboo
and end with
assemble 1.leather 2.leather 1.bamboo 2.bamboo 3.bamboo

That is WAY different from what yours does. THAT is what I was trying to explain to you
as I posted several times already, i NEED ALL the components listed for it to work.
Assemble 1.leather 1.bamboo
is the same as
Assemble 2.leather 2.bamboo

But it is NOT the same as
Assemble 1.leather 1.bamboo 2.leather 2.bamboo

#.item is just a place holder...like
look bag
look 2.bag
look 3.bag

If i use the 1st piece of leather or the 100th it makes no difference.
But if i need *3* pieces of leather i need to put
Assemble 1.leather 2.leather 3.leather

Posted: Fri Sep 09, 2005 2:51 pm

BTW:
Changed your doassemble code:

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

make the doassemble do loopit2, loopit3, loopit4, etc for they total numbet of items in the recipe.....
for: assemble 1.leather 2.leather 1.bamboo 2.bamboo 3.bamboo

run1:

Posted: Sat Sep 10, 2005 12:30 am