Garzahd: Mage-types tend to get the "weak" version of pseudo-ID, which labels things as {good} and {cursed} but not as anything else.

However, if I set autosquelch to destroy "good" items in a certain type (but not excellent), then they are nuked immediately after the pseudo-ID system labels them as {good}. I have no idea whether these were actually "good" or "excellent" items.

This would seem to imply that one of two things is wrong:

  1. An "excellent" item might be autosquelched that I didn't ask for;
  2. I'm receiving more information about item quality than I deserve given my skill point arrangement.

RedNaga: confirmed. i just picked up a princess quest reward with a mage and not identified it immediately. Lately, not finding it, i discovered from the message history that it has been pseudo-id'ed as 'good' and got destroyed.

Now i have added a rule to any problematic item that tell the automatizer to not destroy it unless i have Combat skill high enough to get strong pseudo-id, but this essentially make the automatizer useless for mage-types, since that rule will keep it from destroying even fully identified items.

I can think of two possible solution to this problem:

  1. Adding a new rule to the automatizer that return true only if the item has been properly identified (via scroll, spell or whatever). This would make rules handling a little more complicate but would allow to build safer rules, or...
  2. Change the internal automatizer functions to assume a pseudo id'ed object is 'exceptional' if the character has only weak pseudo-id. Thus it would destroy a good object (assuming all other clauses are met) if the character has strong pseudo-id, otherwise it would assume it is exceptional and wait for it to be fully identified). In other words, the automatizer should never destroy a good item if the character has only weak pseudo-id.

BugReport286 (last edited 2004-11-30 23:56:24 by RedNaga)