The Incident of the Mysterious Melting Icium! (Patreon)

Published:

2021-11-23 10:36:21

Imported:

2026-06

Content

a puzzle most perplexing has this evening plagued our poor and otherwise unsuspecting dev team! a plot, perhaps, the perpetrator positioned in pause perchance to purport their pernicious purpose!

the victim-- one so-called "cass". part time community admin, engine developer and game tester, full time cutie pie. but don't tell her i said that.

the crime-- during testing, against a potentially problematic pair of opponents, she sought to use her Z-Move, Subzero Slammer, from the Icium Crystal. but lo! vanished! it had just been equipped to her weaville, sure as the sun doth shine, but now the weavile remained empty handed and prepared to pickpocket!

the scenario is as such:

before the battle, we confirmed that weavile was indeed holding the icium!
she fought hard. but alas, a loss. important, though, to test that whiting out works well.
she fought again, only to notice that icium was gone!
reset!
no icium before the battle.
we add the icium! she is prepared to strike! fight!
turn one! weavile poison jabs the opponent! the opponent's eject button activate! it flees without making a move!
turn two! a dire foe appears-- we must strike fast and hard! z-move, go!
weavile does not have the icium. it cannot z move.
the battle falls apart quickly.
thousands dead,
many more missing.
somewhere in the chaos it seems like the eject button activates twice.
i cry and note down two bugs.
we try again, several more iterations! does it disappear after a loss? after a use? after the round. none truly know for sure.
i suggest that, ah, just yesterday perry did something with z-moves hadn't he? perhaps one of his changes broke something for z-items in doubles.
cass considers this carefully, and then decides to confront the so-called culprit in a rational and reasonable way

let us now observe the situation as it unfolds. we go to the headquarters and scene of the confrontation, a certain discord channel: #deez-nuts-inc. gifs will be inserted as posted by our participants.

cass's opening argument:

perry, on the scene quicker than we expected, is quick to answer in kind in a perfectly reasonable way that promotes no suspicion or blame whatsoever:

cass offers this logical counter argument:

acknowledging an illustriously-made point, perry provides this response in mutual respect:

but cass, still a victim of a crime most foul, would not be convinced.

at this point in the conversation, i 'oh no' because despite what i just said, we were still testing on the side of things and cass went into battle fully prepared for her icium to be disappeared from the outset...
only to find that it was still quite there.

i've already basically info-dumped that that's not quite the case in the exposition at the start of the post but uhhh don't worry about that, don't worry about the timeline, just here look violence !!

suddenly, evidence!
and then!
perry chimes in with this piece of code, for the eject button!

the problem is made clear!
user.pbDisposeItem--
sure, the holder of the Eject Button is the user of the item
but here, in this code, user refers to the user of the attack that triggers it! eject button activates, and deletes the attacker's item instead of consuming itself. That's why it activated twice earlier!

the kicker, we know...
cass was the one who refactored the pbDisposeItem function into existence!
it was her who did it all along!

the conversation, of course, proceeds in a reasonable manner.