Subjunctive Games

The main story continues! Find out what happens after your close encounter with AVA.

All new story content in this version is completely linear, and there’s no reason to play the game from start to finish to experience it — just use the link in the game’s changelog.

Version 0.0.7 (to be released in +- 2 weeks) will conclude this linear transition between Prologue and Chapter 1, leaving you in another open section.

Changelog:

• Added Panacea Clinic as a new location.
• Added a main story mission: hospital visit.
• Added a photosensitivity warning.
• Notifications change color based on their number (1 = yellow, 2 = orange, 3+ = red).
• Improved email client design to make read and unread emails more distinct.
• Added the ability to change the first name, last name, and nickname in the Extra Options menu.
• Added the option to enable “Skip Minigame” buttons in the Extra Options menu.

---

Archived release announcement. The current version of MindWare is always available at playmindware.com and on the downloads page.

This version introduces a new location: EroSphere.

The main story is still where it was in version 0.0.4, but I’ve made significant behind-the-scenes progress to create the foundation for AVA’s influence on the player. The next version will provide the first glimpse of it.

Changelog:

• Adjusted coding minigame reward.
• Adjusted starting money.
• Added a rent mechanic.
• Added a Hive Properties website.
• Added a Hive Properties email.
• Added expenses tracking.
• Added a bug report form.
• Fixed a bunch of typos.
• Fixed the Download Wiper Tool / Save Target button order issue.
• Fixed the long black tunnel animation delay by implementing a preload function and optimizing the animation itself.
• Added EroSphere location.
• Added EroSphere pole dancing.
• Added EroSphere dishwashing minigame.
• Added quick access buttons tooltips.
• Adjusted Project XX text.
• Improved Prologue pacing.

---

Archived release announcement. The current version of MindWare is always available at playmindware.com and on the downloads page.

I’m excited to announce that MindWare is now officially listed on TFGames.Site – Interactive Game Database (IGDB)!

To everyone who has taken the time to play MindWare, from the bottom of my heart, thank you 🙏. Your engagement, your reviews, and every piece of feedback have been an enormous source of motivation for me.

Extra special thanks to those who have gone above and beyond by supporting me on Patreon or joining my Discord channel. You are the true rockstars! I genuinely appreciate your belief in this project.

As a promise to all of you, I’m dedicating as much time as possible to the continued development of MindWare. We’re at the very beginning, and the road ahead is long, but I can’t wait to bring my ideas to life.

Thank you again,

Subjunctive

With MindWare’s prologue section mostly finished, I needed to create a good-looking chapter header. Given the game’s cyberpunk theme, a neon flickering text effect seemed like a good fit. Here’s what I came up with:

To display notifications in MindWare, I have created an alternative version of ChapelR’s excellent Notify macro. The new macro differs from the original in two important ways:

1. Close button: In my version, notifications don’t close automatically. Instead, the user has to click a close button. This is to prevent situations where the player doesn’t have enough time to read the information in the notification, especially in cases where the content is crucial to the gameplay or story.
2. Multiple notifications: Unlike the original macro, which replaces the existing notification with a new one, my macro supports the display of multiple notifications at once. All displayed notifications can then be dismissed with just one click on the close button.

Here’s an example of the notification macro being used in MindWare (version 0.0.2):

You’re using Twine 2 with the SugarCube story format for your interactive fiction story, but JavaScript is throwing curveballs your way. Functions that work like a charm elsewhere mysteriously trigger cryptic error messages. The culprit? JavaScript scope.

Let Your Functions Mingle

The Story JavaScript area, any JavaScript file in the compile path of a Twee notation project, or code written within SugarCube’s <<script>> tags operates in a “Private Scope.”

Imagine a private scope in JavaScript like a private room in a house. It’s a space where everything you put inside (your functions and variables) is only available to those who are inside the room. This privacy sounds great for security, but not so much when you want your code to mingle with other parts of your Twine story.