Does this game actually have animations?
I'm like right after reset 3, haven't seen a single animated scene yet.
Is the 'animated' tag there just for the elevator-look scenes effects?
Anybody know?
Does this game actually have animations?
I'm like right after reset 3, haven't seen a single animated scene yet.
Is the 'animated' tag there just for the elevator-look scenes effects?
Anybody know?
There are animations, but they do not appear in story scenes.
Whenever an act is unlocked with a girl, it may create a repeatable animated scene. For example -- in the screenshot I included, "Hang Out" would potentially trigger a story scene, if one is available, or a static scene in which Affection is raised if a story scene isn't available, but the "Have sex" options are all animations.
There are animations available at the dorms, when you invite girls over via phone, or when you visit some of the girls at their hangout/work (Maki at the sex shop, Sara at the bar, Haruka at the coffee shop, etc).
Some animations may become unavailable for story reasons in certain parts of the game.
ONE theme that I might deem satisfactory is "how this girl shapes the respective chapter". Sana's role in Ch4 is that she could potentially be painted as the root cause of the Sensei Sad Arc; not being fucked properly in the infirmary by the end of Ch3 leads to Sensei receiving divine punishment and subsequently settles the overall mournful tune of Ch4, even if this isn't her fault at all. Alas, this is a take and not character stats so I am less inclined to put all the eggs into the same basket, even if the basket is my own headcannon.
There are animations, but they do not appear in story scenes.
Whenever an act is unlocked with a girl, it may create a repeatable animated scene. For example -- in the screenshot I included, "Hang Out" would potentially trigger a story scene, if one is available, or a static scene in which Affection is raised if a story scene isn't available, but the "Have sex" options are all animations.
There are animations available at the dorms, when you invite girls over via phone, or when you visit some of the girls at their hangout/work (Maki at the sex shop, Sara at the bar, Haruka at the coffee shop, etc).
Some animations may become unavailable for story reasons in certain parts of the game.
Done for now, I'll be back when 0.50.0 drops, playing every 5 updates is very rewarding, but requires a lot of patience.
What I didn't like is how to get the latest happy event, but luckily even if you have the automod turned off (I only had it for the menu images), it will unlock it for you, because the creator of the mod felt the same.
anybody mind sharing the specifics of the importance of the "shampoo?" in my playthrough, if removed from the fridge it would lead to a game over so I never took it. is there more to the shampoo than that?
Speaking of finding something unexpected from replaying, can any of you guys check your Ami's event Important Things or more specifically, an image file named "amisroomonefive25"? Mine looks...glitched. View attachment 4254849
At first I thought I doodled too much and might have overwritten something by accident, but I was thoroughly vexed when I found out that image files with the same name straight out of fresh downloads of v0.41, v0.42, or v0.45 from subscriberstar all look like that (in fact the the one in v0.45 is even more glitched); for now the only source I have that gives the "correct image" is an old v0.28 copy of mine. View attachment 4254851
I am guessing the reason why I now have the glitched image is because of the renpy upgrade that forced me to download the entire copy instead of simply doing update patch.
Well this is weird as shit. The images appear to contain hidden data that (I think) was placed there deliberately, but most of it is meaningless.
amisroomonefive25.webp was still normal in 0.39. Starting with 0.40, each full game version includes a new version of the image with different corruption. The data in the files is identical except for one block starting at offset 0x8000 that is exactly 0x1000 bytes (4KiB) long.
The modified bytes in the 0.40 image themselves contain an image file, specifically a tiny jpeg showing Singapore's ArtScience Museum. This is smaller than the 4KiB block, the rest of which is padded with zeros.
Here's where it gets even weirder. Each of 0.43 to 0.45 contains data that is at least partially meaningful when viewed as text, but they all seem to have to do with mundane windows services.
0.43 is an XML config file for windows update (with a bunch of zeroed bytes padding it out).
0.45 mostly isn't interpretable as text, but it does have "EBFGONED" near the start, which google suggests is part of the header for OneDrive log files.
It's hard for me to imagine a mechanism by which this could have happened accidentally, especially when you consider that this one 4KiB block in one image out of thousands is the only thing being corrupted, the data in the corrupted block keeps changing, and two non-consecutive images (0.40 and 0.42) have the same complete jpeg inserted in them.
On the other hand, I can't imagine what this is supposed to accomplish if it is deliberate. Is it an elaborate troll? Is it setup for future DRM (but then why repeatedly edit the file instead of only once)? And why is the changed image not in the update patches?
I'll attach the original images and the extracted binary in case anyone else wants to play around with this.
Well this is weird as shit. The images appear to contain hidden data that (I think) was placed there deliberately, but most of it is meaningless.
amisroomonefive25.webp was still normal in 0.39. Starting with 0.40, each full game version includes a new version of the image with different corruption. The data in the files is identical except for one block starting at offset 0x8000 that is exactly 0x1000 bytes (4KiB) long.
The modified bytes in the 0.40 image themselves contain an image file, specifically a tiny jpeg showing Singapore's ArtScience Museum. This is smaller than the 4KiB block, the rest of which is padded with zeros.
Here's where it gets even weirder. Each of 0.43 to 0.45 contains data that is at least partially meaningful when viewed as text, but they all seem to have to do with mundane windows services.
0.43 is an XML config file for windows update (with a bunch of zeroed bytes padding it out).
0.45 mostly isn't interpretable as text, but it does have "EBFGONED" near the start, which google suggests is part of the header for OneDrive log files.
It's hard for me to imagine a mechanism by which this could have happened accidentally, especially when you consider that this one 4KiB block in one image out of thousands is the only thing being corrupted, the data in the corrupted block keeps changing, and two non-consecutive images (0.40 and 0.42) have the same complete jpeg inserted in them.
On the other hand, I can't imagine what this is supposed to accomplish if it is deliberate. Is it an elaborate troll? Is it setup for future DRM (but then why repeatedly edit the file instead of only once)? And why is the changed image not in the update patches?
I'll attach the original images and the extracted binary in case anyone else wants to play around with this.
Well this is weird as shit. The images appear to contain hidden data that (I think) was placed there deliberately, but most of it is meaningless.
amisroomonefive25.webp was still normal in 0.39. Starting with 0.40, each full game version includes a new version of the image with different corruption. The data in the files is identical except for one block starting at offset 0x8000 that is exactly 0x1000 bytes (4KiB) long.
The modified bytes in the 0.40 image themselves contain an image file, specifically a tiny jpeg showing Singapore's ArtScience Museum. This is smaller than the 4KiB block, the rest of which is padded with zeros.
Here's where it gets even weirder. Each of 0.43 to 0.45 contains data that is at least partially meaningful when viewed as text, but they all seem to have to do with mundane windows services.
0.43 is an XML config file for windows update (with a bunch of zeroed bytes padding it out).
0.45 mostly isn't interpretable as text, but it does have "EBFGONED" near the start, which google suggests is part of the header for OneDrive log files.
It's hard for me to imagine a mechanism by which this could have happened accidentally, especially when you consider that this one 4KiB block in one image out of thousands is the only thing being corrupted, the data in the corrupted block keeps changing, and two non-consecutive images (0.40 and 0.42) have the same complete jpeg inserted in them.
On the other hand, I can't imagine what this is supposed to accomplish if it is deliberate. Is it an elaborate troll? Is it setup for future DRM (but then why repeatedly edit the file instead of only once)? And why is the changed image not in the update patches?
I'll attach the original images and the extracted binary in case anyone else wants to play around with this.
This same error was reported in LiLcord a couple months back, but Sel didn’t seem to think much of it.
Clearly it is a corrupted image, though, so… Either Sel is in denial or just isn’t aware of it.
"Yeah, that's definitely not a problem with the game"
I've got two possible readings
1) "It's a you problem" -- Sel bellieves the user did something to corrupt his install
2) "It's there on purpose" -- It's not a problem with the game because it's like that by design.
The breakdown of exactly how the images are corrupted would indicate that it's most likely option number 2.
Well this is weird as shit. The images appear to contain hidden data that (I think) was placed there deliberately, but most of it is meaningless.
amisroomonefive25.webp was still normal in 0.39. Starting with 0.40, each full game version includes a new version of the image with different corruption. The data in the files is identical except for one block starting at offset 0x8000 that is exactly 0x1000 bytes (4KiB) long.
The modified bytes in the 0.40 image themselves contain an image file, specifically a tiny jpeg showing Singapore's ArtScience Museum. This is smaller than the 4KiB block, the rest of which is padded with zeros.
Here's where it gets even weirder. Each of 0.43 to 0.45 contains data that is at least partially meaningful when viewed as text, but they all seem to have to do with mundane windows services.
0.43 is an XML config file for windows update (with a bunch of zeroed bytes padding it out).
0.45 mostly isn't interpretable as text, but it does have "EBFGONED" near the start, which google suggests is part of the header for OneDrive log files.
It's hard for me to imagine a mechanism by which this could have happened accidentally, especially when you consider that this one 4KiB block in one image out of thousands is the only thing being corrupted, the data in the corrupted block keeps changing, and two non-consecutive images (0.40 and 0.42) have the same complete jpeg inserted in them.
On the other hand, I can't imagine what this is supposed to accomplish if it is deliberate. Is it an elaborate troll? Is it setup for future DRM (but then why repeatedly edit the file instead of only once)? And why is the changed image not in the update patches?
I'll attach the original images and the extracted binary in case anyone else wants to play around with this.
We know that Sel has screwed around by adding code inside images before. These additions, however, seem so random that I can't see them being intentional.
I'm imagining him writing a script to compile/compress each release—and inadvertently including a line to paste whatever's in his buffer into the middle of that file. So whatever's open when he runs the script gets dumped in there.
Or it could be some mad genius thing that we're just too stupid to understand.
Speaking of finding something unexpected from replaying, can any of you guys check your Ami's event Important Things or more specifically, an image file named "amisroomonefive25"? Mine looks...glitched. View attachment 4254849
At first I thought I doodled too much and might have overwritten something by accident, but I was thoroughly vexed when I found out that image files with the same name straight out of fresh downloads of v0.41, v0.42, or v0.45 from subscriberstar all look like that (in fact the the one in v0.45 is even more glitched); for now the only source I have that gives the "correct image" is an old v0.28 copy of mine. View attachment 4254851
I am guessing the reason why I now have the glitched image is because of the renpy upgrade that forced me to download the entire copy instead of simply doing update patch.
Hey folks. I remember playing this game years ago on Android before switching phones. Can't find the mobile link anymore. Is it joiplay only now? Or just strictly PC?
Honestly I remember not even playing for the porn, I just want *ANSWERS*
OK, freak shit aside, what's the point of developing a game this way ? Serious hard on for having everything done your way ? I haven't played since maybe chapter 2 was released and replaying the game, I can't imagine anyone has ever gotten all the scenes without URM and the guide mods. It's just not possible especially considering the most useless decisions in the game end up locking you out of entire event chains. It was annoying before but with this much content it's just a chore. He doesn't even want people to play the game.
anybody mind sharing the specifics of the importance of the "shampoo?" in my playthrough, if removed from the fridge it would lead to a game over so I never took it. is there more to the shampoo than that?
It's a troll that either bricks your save, or makes it worse by preventing you from going to the dorms if you avoid the bricking. It you kept it all this time it would have been removed during the 0.45 happy event, though you wouldn't get the Maya2 profile outfit and no special variable is set for doing so. Taking the shampoo is 100% a detriment to your save file unless Sel specifically checks for the lack of Maya2 profile pic at a point after 0.45 (so can't be one of the generic events, but he could do the thing he did for senseiissad and wrap everything in an idential looking menu but code wise is different)
This is technically something he's willing to do but it breaks his usual practice of making a specific variable and then checking if it's true. (instead checking for false after a point it should be true)
