<Prof. Farnsworth> Good news, everyone! </>

After arduous two days of banging my head against the proverbial wall,
the eqset command and the back-end have received some improvements.

However, the stored data format had to be changed to accommodate for
the new features, and thus the next time you use 'eqset', you will
be notified about it, and to proceed you need to 'eqset convert'.

Just to make it clear, 'eqset convert' will NOT cause any harm to
your eqs, and it should NOT destroy your eqset data. It MAY cause
it to look a bit weird BEFORE the first time you use 'eqset view'
WITH the eqs in your inventory that belong to that specific set.


The main new features are:

- The short desc of the items is now stored, thus you can actually
view the set contents with 'eqset view' even when you are not
carrying all the items that belong to the set.

- The 'eqset validate' will now tell (if possible) what items were
removed from the validated set.

- The 'eqset foreach' command has been reworked and a special <item>
tag has been added. You can now do, for example, following:

> eqset foreach spr put <item> in chest

or even this:

> eqset foreach spr get <item> from chest

The possibilities are numerous, as you can make command aliases like

> command chest eqset foreach $1 put <item> in $2

HOWEVER .. there are certain issues with this functionality ..
if you have multiple items with the same longest handle (in practice
this means the shortdesc), then wrong items MAY be handled. There
is no 100% good way around this .. (yes, I know what other wizards
may think now, but unique ids as handles are not a pretty solution,
though we may move to those if the consensus becomes such.)


These changes will become effective at next boot.

Thanks go to Heidel, Darol and Durand. Bug reports and whines to me.

--
Ggr the Bunny of Magical Bunny Land