HTML Ready to Reform [v1.010] [Midnoblu]

[Marylyn326]

Dude, money is trouble. I have only 2AP every day, and my hard work only worth 8$ per day??? I guess that's a fair price in prison, maybe, but in a game, which I need to repeat 5min just to buy something to push forward, that is a bit noisy.
Anyway, the new update is good, though there is some typo mistake. Hope to see next update soon.

 

[ibizadalton]

Dude, money is trouble. I have only 2AP every day, and my hard work only worth 8$ per day??? I guess that's a fair price in prison, maybe, but in a game, which I need to repeat 5min just to buy something to push forward, that is a bit noisy.
Anyway, the new update is good, though there is some typo mistake. Hope to see next update soon.

money increases when you move forward a little in the story

 

[TheFamilyDog]

That $8 dollars a day is for hard labor (cracking rocks, road crews, or cleaning-up swamps), and even then most of the prisoners are there just so they have something to do. Most money in prison comes from outside sources, family or scamming women who think they found their soulmate. If not those, then the prisoner is running some sort of business or services in prison (like cook, beautician, porn acquirer). And those dollars you get from the work crews goes on your inmate card, actually paying another prisoners usually involves stamps or ramen.

At least to the varies youtube vids and podcast I've listen to.

 

[fitgirlbestgirl]

I feel it's too early to review this so I will dump some thoughts here. The writing is good, usually sissification games annoy me by the MC being too eager or too forced, this strikes an interesting balance where the MC is kind of forced but also kind of wants it but is conflicted. The psychological treat system is cool and it kind of reminds me of Nothing Is Forever where the different aspects of your personality comment on your shit. I also like that you have a girlfriend and get to have the cuckold angle, which is also too rare in these types of games. Overall this pushes a lot of my buttons and I like it.

 

[Vypress]

I went the most fleshed out route (the sissified MC) going for the more feminine touch bi/straight-leaning route rather than full on sissy gang slut. Really enjoying it so far, though do have some hopes. In the non sissy slut but still feminine answers I get kind of Egg (Slang term for someone who is trans but doesn't know it yet) vibes and hoping it kind of goes that way. Also very curious about whether the storyline with the prisoner you gave the photos of your GF too and who got released will go anywhere. Though going to have to wait until more GF phonecalls & visit content is added potentially.

Just wondering but in the new update is the feminine touch/trans route still accessible or is the focus solely on the submissive sissy slut style route.

 

[HairyJerry]

Dunno what to do in here, feels like sandbox with deadline going in negative(bug). My notes say I have to meet Javier and swap USB but there's no way to do it.

 

[hf1024]

The game can be played online

You must be registered to see the links

.

Not being able to go back in history is clearly a bummer for me. I don't understand why authors think it can be a good thing to force players this way

The story is well written, but I'm really waiting for the other paths to be developed (not really interested by the eagerly submissive sissy path).

 

[riadhloch]

I too dislike the lack of a back button, but I can see the rationale for a couple possible reasons:

1. The dev employs persistent variables with several downstream triggers based on that variable state, that then get effed-up when players go backwards. The persistent variable state must be backed-out, as well as any variables reliant, and if fault tolerance isn't rigorous that can cause a lot of cascading errors. Depending on how much spaghetti there is in the code, that could be simply too difficult to debug.​

​

2. The dev wants to force replays to see all the content, increasing the perceived value of the game based on the investment of time.​

I hope it's #1 over #2, because frankly #2 is an antiquated notion and a lazy, arrogant way to increase the investment of time. If a game is the sole option in a genre or immensely popular for various reasons, then the player has no other choice how to spend their time. Replay value, however artificial in design, makes a difference. But if there's plenty of competition in the genre (just look at everything on offer on F95zone for example), then forced replays merely encourage the player to uninstall and play something else.

 

[dopefish]

1. The dev employs persistent variables with several downstream triggers based on that variable state, that then get effed-up when players go backwards. The persistent variable state must be backed out, as well as any variables reliant, and if fault tolerance isn't rigorous that can cause a lot of cascading errors. Depending on how much spaghetti there is in the code, that could be simply too difficult to debug.​

Twine (at least Sugarcube) reverts variables to their previous state when you go back in history. There are a few exceptions to this, but none of them are particularly common to use, nor best-practice. I'm pretty sure it's almost always reason #2, or for whatever artistic reason ("the purity of the playthrough" or whateever) the author might have.

 

[hf1024]

Yeah, the game uses no persistent variables for now, so this is option 2 unfortunately. The buttons can be added back by modifying the HTML file or using GM scripts, but that's cumbersome

 

[riadhloch]

Twine (at least Sugarcube) reverts variables to their previous state when you go back in history. There are a few exceptions to this, but none of them are particularly common to use, nor best-practice. I'm pretty sure it's almost always reason #2, or for whatever artistic reason ("the purity of the playthrough" or whateever) the author might have.

I respect that Twine Sugarcube is supposed to revert variables gracefully, but I've seen plenty of Sugarcube games break on back button use or window refresh. It's code -- there's always some way to invoke a beautiful disaster, haha.

Ironically, isn't the back button available by default in Twine Sugarcube? Wouldn't the Dev have to go out of their way to remove it? So, removing it actually already introduces new points of failure?

I'm not sure if Twine Harlowe also defaults to a back button.

 

[dopefish]

I respect that Twine Sugarcube is supposed to revert variables gracefully, but I've seen plenty of Sugarcube games break on back button use or window refresh. It's code -- there's always some way to invoke a beautiful disaster, haha.

Ironically, isn't the back button available by default in Twine Sugarcube? Wouldn't the Dev have to go out of their way to remove it? So, removing it actually already introduces new points of failure?

I'm not sure if Twine Harlowe also defaults to a back button.

In Sugarcube, it's a config variable you can set to true or false.

 

[hf1024]

I respect that Twine Sugarcube is supposed to revert variables gracefully, but I've seen plenty of Sugarcube games break on back button use or window refresh. It's code -- there's always some way to invoke a beautiful disaster, haha.

In general, this is because these games use

You must be registered to see the links

and SugarCube history does not support them. There are

You must be registered to see the links

but most game devs are not aware of them, so the game state gets corrupted eventually when the player tries to go back.

 

[dopefish]

In general, this is because these games use

You must be registered to see the links

and SugarCube history does not support them. There are

You must be registered to see the links

but most game devs are not aware of them, so the game state gets corrupted eventually when the player tries to go back.

This doesn't cause the game state to get corrupted, it just means that the back button doesn't work:
> If a player clicks the history back button, then the engine will load the ephemeral passage again, leading to the redirect again, leaving the player at the same passage he tried to go back from.

 

[hf1024]

This doesn't cause the game state to get corrupted, it just means that the back button doesn't work:
> If a player clicks the history back button, then the engine will load the ephemeral passage again, leading to the redirect again, leaving the player at the same passage he tried to go back from.

This forces the player to click multiple times on the back button which can corrupt the state:

The only way to go back in this case is to spam the back button hoping that the engine goes 2 states back in history to prevent the automatic redirect. Doing that is nearly impossible on slow devices (phones) and sometimes corrupts the state.