Help Ultra Rare bug?!?!

the_tom77

New member
Ok so mafia showed this in the CLI
http://s53.photobucket.com/albums/g46/the_tom777/?action=view&current=Talismanscare.jpg
http://s53.photobucket.com/albums/g46/the_tom777/?action=view&current=Talismanscare2.jpg

I totally freaked out and I was all like "OMFG what are the chances"
I went and checked the session results and there it was.

http://s53.photobucket.com/albums/g46/the_tom777/?action=view&current=Talismanscare3.jpg
http://s53.photobucket.com/albums/g46/the_tom777/?action=view&current=Talismanscare4.jpg

But I looked in my inventory in the relay browser no Talisman of Baio
So I right clicked it in Session Results to put in Display Case.

The CLI showed it was put but couldn't see in relay browser.
Please fix bug if it is a bug.
Or tell me where my Ultra Rare is.
 

lostcalpolydude

Developer
Staff member
Someone has a mall store called "You acquire an item: Talisman of Baio" that shows up on the front page of the mall, probably for the sole purpose of screwing with people that use mafia. The problem will fix itself when the advertising budget drops.
 

the_tom77

New member
That still doesn't account for why the Talisman of Baio item appeared in my session results or why it happened in the middle of adventuring. Also I had the effect teleportitis active if that counts for anything.
 
The line before the line you are focusing on is where it's at. It says "insufficient health..." which triggered a restoration. In the process of restoration, kolmafia needed an item, and did a mall search for it. in the mall search Kolmafia encountered the store name and mis-took it for the results text, and therefore assumed you had acquired the item, and logged it.

This is in fact a bug because now that it is known, people can intentionally cause everyone's log's to go haywire.
 

lostcalpolydude

Developer
Staff member
This isn't the first time someone has done a stunt like this. Due to the expense of having a mall store on the front page, it wasn't something that people did all the time.

Thanks to the update in build 6167: "Ignore "search" pages when parsing for item/effect results", this shouldn't be a problem ever again.
 
Top