Suggestion: Allow option for "any lore"

[GavJenks]

Currently, you can set it to only accept items with no lore, or to only accept items of a specific lore. But you can't set it to accept any items with or without any lore.

Similar to how you can do "any enchantment."

The reason this came up was for a casino idea, for use in getting an unpredictable value of chip (printing press security notes) from an exchange, which you can go cash in for diamonds.

[ttk2]

the option of having unpredictable lore would require some way to do parsing in the config.

[WildWeazel]

I'm not sure how this fits your use case. Wouldn't you want different rules for specific lore so that you can match chips to a diamond value? If an input rule accepted any lore you'd get the same number of diamonds for each.

[GavJenks]

Why parsing? All it has to do is completely ignore lore to do this. Right now, it ALWAYS pays attention to lore -- either an exact match or the explicit lack of any. It would be another command and putting an if statement around the part that checks lore at all.

Wildweazel -- that would just be a regular shop then, if I charged different amounts appropriate to the object. It's supposed to be gambling. You put in one diamond no matter what, and sometimes you get something worth less than a diamond, sometimes you get more, that's the point to always put in the same amount. Like always putting a nickel into a slot machine.

It would also be useful for other minor things. Like a fun grab bag for a shop if you want to sell off randomly assorted authored books.

[WildWeazel]

Oh I see, you want to SELL an item with arbitrary lore. In that case I'm not sure how inventory selection works, would it grab from the first slot that matches? I thought you were trying to set up a change dispenser with different denominations of coins.

[GavJenks]

Uh I dunno, whatever it already does with "any enchantment" amongst many options. I didn't think about random slot selection. Probably more trouble than it's worth then, I guess.

[ProgrammerDan]

I might look into this, if I understand the issue. Might be implementable as a flag on the exchange rule, indicating unconstrained output and a random selection from chest contents (not including any output rule item matches and not including any rule buttons.)

[rourke750]

@ProgrammerDan Want to be assigned this?

[ProgrammerDan]

Sure, sounds good
On May 25, 2015 4:59 PM, "rourke750" notifications@github.com wrote:

@ProgrammerDan https://github.com/ProgrammerDan Want to be assigned
this?

—
Reply to this email directly or view it on GitHub
#11 (comment)
.