Asynchronous Art Update (Patreon)

One of the issues that many erotic games have is dealing with complexity in their mechanics. Whether it's Inform7, Twine, or a number of other engines, detailed mechanics lead to increasingly bogged-down games. It's actually become so commonplace, that people start to assume that complex games can't be built by indie developers without suffering from slowdown that impacts game play. Thankfully this isn't necessarily the case.

So what are the solutions?

The most common way for small games to handle complexity successfully is processing things only as they are interacted with, and keeping most things separate to avoid complex interaction. Another common method is giving the appearance of complexity, but having most things "hard coded". Some great games work this way, but it isn't viable for highly-interactive environments or interdependent mechanics. Many use a combination of these approaches.

Games that are truly complex suffer from slowdowns, because the above solutions aren't feasible. (without exactly naming names, FC and TQ are examples of complexity resulting in slowdown.)

I believe that part of the solution can be found in the form of asynchronous programming methods. These are used in more advanced games, and in game engines built around 3d play. To put it simply, in Twine and some other IF engines, processing occurs in a "single line", often in-between the points of player interaction. This is the biggest reason why AW is using the 'day system' for periods of sleep, and the 'week planner' at the start of each week. 

Having these points in AW, where play is constrained, allows for asynchronous functions to be viable. The problem with slowdown in the previously mentioned games isn't that it takes 15 or 30 seconds to process everything, it's that this processing takes place while the player is waiting to do something. My plan is to take advantage of JavaScript's async functions to process the changes to all the NPCs populating the world while the player is busy with other aspects of game play, like planning social events or choosing which outfits to wear on which day.

As far as I know, this is a first for a twine game. (With exception of the Sugarcube "timed" macro, which is a rather limited implementation with a specific purpose.) Unfortunately, trailblazing means that the useful help available online is limited. It's going to be interesting!

All of this starts in Stage 2, but I'm discussing it now because the refrain "this isn't possible, just look at X, and it only does Y!" does start to get a bit old. ;)

Finally, the Art Part: 

A peak at AlexW95's line art. He's got a few variations he's working on (with different facial expressions), that are pretty cool.

Arteria's work in color. Main issue is that it's the wrong time of day, but it's a great start.

Complete images have been posted on Discord, if you want to take a look. (In the announcements channel.)