zigdon
Trigger with own facts *and* alias
Odd little thing with a denizen's quotesfile. "literal[*] nick quotes" resulted in a listing of "Alias to oldnick quotes" plus all factoids for oldnick quotes, and new quotes for [nick] were directed there - but asking Bucket for "Bucket: nick quotes" resulted in one of five factoids every time, and none of them were in the listing. It turned out that the aliased trigger still had some factoids of its own. The resolution:
< barometz> Bucket: delete nick quotes
< Bucket> Okay, barometz, 5 factoids deleted.
< barometz> Bucket: alias nick quotes => oldnick quotes
< Bucket> Okay, barometz.
< barometz> Bucket: nick quotes
< Bucket> [factoid from the new listing]
Right now I'm not sure whether this is an ongoing issue with alias (what is the expected behaviour for existing triggers?) or just some remnants of an old DB mixup. Don't have time for extensive testing at this point, might look into it later.
As I understand it, Bucket: merge oldnick quotes => nick quotes would have solved the issue without deleting any factoids.
