Bug - Fixed ash create(int, item) fails with "[¶item#] has no matches"

ereinion

ereinion

Member
Using ash create(int, item) fails with "[¶item#] has no matches" (as shown in the attached image). Happened somewhere between r16340 and r16350.

 
Ok, clearly ItemFilter doesn't do what it sounds like it should. When you filter by an item type, it ignores the filter if there is only one match. The question becomes, why? And why when this is a creatable, and a creatable is specified as the filter, this gets filtered out.
 
I do have a fix for this, but will release later after more testing. Basically having identified the item, it then adds the fuzzy search, not the item to the item list, and then filters it, and the filter fails.
 
In r16352:
Code: 
> ash create(1, $item[milk of magnesium])

[¶1650] has no matches.
Returned: false
As a workaround, the CLI equivalent can be used:
Code: 
> create 1 milk of magnesium

Verifying ingredients for milk of magnesium (1)...
Searching for "glass of goat's milk"...
Search complete.
Purchasing glass of goat's milk (1 @ 2,455)...
Purchases complete.
Creating milk of magnesium (1)...
You acquire milk of magnesium (3)
Successfully created milk of magnesium (3)
 
r16354 seems to fix this. Checks for mixing method by item number, not item name which can be a numeric which isn't handled right.
 
You must log in or register to reply here.
Back
Top