Fixed [0.9.139-PUBLIC-ELECTRON#6354] Bizzy's Porn Studio Quest Bug

Issue is marked as fixed.

Kromarty

New Member
May 16, 2023
3
6
35
I encountered following bug with Bizzy's quest:
At stage 4 of the quest (flat-chest route) [Save1], after she's given 200,000 credits, a field appears to enter a name for her studio. If you enter a name that's too long, a warning appears stating that the name can't exceed 16 characters.
Then, if you shorten the name and continue the dialogue (by selecting any options), the quest is irreversibly broken:
Immediately after leaving her apartment, the player receives a letter from Bizzy informing them that they will now receive royalties:
scr1.png

However, we've already received this letter in one of the previous stages! The letter mentions "busty kaithrit" instead of "mosquito-bitten kaithrit," meaning the quest jumps from the flat-chest route to the busty route:
scr2.png

Bizzy herself remains flat-chested, although "Encounters" journal entry now states she has a J-cup, and the quest has advanced to stage 5. Also, the dialogue in her apartment gets stuck in a dead loop, allowing the player to endlessly transfer 200K to her over and over again [Save 2].

This bug, however, ONLY and EXCLUSIVELY occurs if the studio name length warning was triggered. If the name was entered correctly, the quest will advance to stage 5 without any issues. [Save 3]
 

Attachments

  • Save1.json
    871.5 KB · Views: 2
  • Save2.json
    872.7 KB · Views: 1
  • Save3.json
    871.9 KB · Views: 1

Jacques00

Administrator
Moderator
Aug 26, 2015
5,234
1,329
Hopefully fixed for the next release (not the currently released patch, but the next one), but things like the e-mail message, due to how the data is saved, might not be retroactive. However, the functional parts should be corrected now. So the chest flatness should now be checked before sending out the proper e-mail, and the renaming of the studio should reroute to the correct passage if there was an error in naming (it was routing to the busty variation and might have crashed out if the function wasn't nested properly). Also, her encounter log should also properly check for flatness now.