Beta bug fixes
Added 2018-03-05 21:13:40 +0000 UTCToday I fixed a bunch of bugs reported in the Beta version. The serious one still outstanding is that loads from saves can't progress through the backstage stripping scene at Oceana – I'm still working on this, as well as a couple of minor errors (like dialogue/decision links appearing twice in the options lists).
This release, however, fixes the following bugs reported since Friday:
- Fixed a bug where the game couldn’t progress past Max’s balcony. (Cause: the PC’s “position” not being reset after the previous sex scene.)
- Fixed 2 bugs where an NPC’s name was displayed as $male1.firstname in a link. (Cause: incorrect formatting of the link text.)
- Fixed a bug where answering the question on-stage about whether the PC has done anal displayed all four possible answers at once. (Cause: missing <</if>> tag.)
- Fixed a bug where towards the end of the wet t-shirt contest, all options were available to all agents regardless of their traits. (Cause: missing conditional logic.)
- Fixed a bug where a non-Promiscuous agent could pick the Promiscuous option at dinner with Max in Dubai. (Cause: missing conditional logic.)
- Fixed a bug where attempting to break off sex with a partner in Scotland jumped the agent forward to the sex scene in Dubai. (Cause: misdirected link.)
- Fixed a bug that displayed a "Invalid or unexpected token" error describing the aftermath of a sex scene in Scotland. (Cause: incorrectly named variable in code.)
- Fixed a bug that displayed "Cannot read property 'from' of undefined" during dance floor flirtations. (Cause: incorrectly named variable in code.)
- Fixed a bug that caused the error message "Invalid or unexpected token" during sex with an NPC. (Cause: accidental use of typographic quotation marks instead of plain text ones in one line of code.)
- Fixed a bug where a male taking (or pushing) the PC onto a bed wouldn't display any text to report that. (Cause: missing line of code in the relevant macro.)
- Fixed a bug where a male attempting to finger the PC would generate the error message "Error: <<set>>: bad evaluation: State". (Cause: logic error in code.)
Special thanks to Hyneman who spotted and reported nearly all of these bugs, with assistance from Zachary Spear and Goblin Steve. Thanks guys!
If you encounter any more bugs, please message me directly here, or post them in the Discord bug channel: https://discord.gg/UFh5euh
Update: the linked file is now 1.3.2 B, with further bug fixes.
Comments
Fixed in 1.3.2 B
Crushstation
2018-03-08 11:00:53 +0000 UTCFixed in 1.3.2 B
Crushstation
2018-03-08 11:00:36 +0000 UTCFixed in version 1.3.2 B
Crushstation
2018-03-08 11:00:17 +0000 UTCCat, I gave the beta a runthrough myself. I currently can't find a workaround. However you're largely at the end of the new content. There is just the last sex engine sequence for Oceana, a debriefing and then to Dubai. However, if you like you can message me; I still have the original copy of the first beta which should allow you to advance. You'll need to use a brand new Agent though. Or alternatively, the general release with the bug fixes and all the additional content Dissosant Soundtrack, myself and Dracis3D have contributed will be available by this Sunday.
esclavage
2018-03-08 00:30:56 +0000 UTCCat
2018-03-07 23:55:59 +0000 UTCHum, seems as though no matter what trait/s I have, it always fails to progress beyond the end of third night in glasgow (lots of red errors in the proceeding few screens too)
S Pore
2018-03-06 19:43:44 +0000 UTCThanks, guys, I'll fix that.
Crushstation
2018-03-06 18:18:29 +0000 UTCYep, getting that same bug on the third glasgow date myself
S Pore
2018-03-06 13:04:35 +0000 UTCof the third night in glasgow
Zachary Spear
2018-03-06 03:23:02 +0000 UTCthere is a bug where if you choose the promisuous/exhibitionist in the car the next part show up as red macro text with no options to go forward
Zachary Spear
2018-03-06 03:22:50 +0000 UTC
