Cheeseypickle
New member
I was running garbo today, when I noticed that the preference shockingLickCharges doesn't change, even though I used the skill. I copied the relevant part from the log here:
This is the 2nd time this has happened. The above log was specifically taken from version r27380. Any chance I could get some insight on this?
[191] Thugnderdome
Preference lastEncounter changed from Adjust your Parka to Gnomester Blomester
Encounter: Gnomester Blomester
Preference _lastCombatStarted changed from 20230530222000 to 20230530222004
Round 0: CheeseyPickle wins initiative!
Preference cosmicBowlingBallReturnCombats changed from 11 to 10
Round 0: CheeseyPickle casts SHOCKING LICK!
Round 1: Your toy train moves ahead to the Coal Hopper. Your train takes on coal to power the next stop.
Preference trainsetPosition changed from 91 to 92
Round 1: Aesh tosses you some sleazy nuggets. You respond with some sleazy nuggets of wisdom, most of which involve the judicious use of prophylactics while making spreadsheets.
You acquire an item: sleaze nuggets
Round 1: CheeseyPickle wins the fight!
After Battle: Aesh surveys the scene from atop the throne, and gains 1 Experience.
After Battle: Black Magic does the nanobot. Which is a dance like the robot, but smaller and harder to see.
You acquire an item: cog
You acquire an item: spring
You acquire an item: flange
After Battle: Black Magic wobbles a little bit and then ejects a little bolus of mass, which spontaneously reassembles itself into a bottle of booze.
You acquire an item: bottle of gin
After Battle: You gain 6 Strengthliness
After Battle: You gain 14 Wizardliness
After Battle: You gain 7 Roguishness
After Battle: You gain 1 Strengthliness
Preference _juneCleaverFightsLeft changed from 5 to 4
Preference _juneCleaverCold changed from 4 to 5
Preference sweat changed from 32 to 35
Preference lastCopyableMonster changed from Knob Goblin Embezzler to Gnomester Blomester
This combat did not cost a turn
Preference familiarSweat changed from 150 to 151
This is the 2nd time this has happened. The above log was specifically taken from version r27380. Any chance I could get some insight on this?