3. The Ami dream sequence is completely different in the older version. Instead of the more unsettling 'Breed Your Niece' mini game Ami with the creepy eyes, this one is played more like a straight-up h scene. You can see an image of this segment still on the front page as one of the preview images.
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.
If this is an actual bug I'd love to know how he managed it. I can tell you there aren't any new copies of that image in the patches from 0.38 to 0.45 and I don't want to dig out an old hard drive to go further back. This feels incredibly stupid to be accidental. If it is something specific, the only thing I can point out is it's one of the few events that are named amis[event] rather than ami[event]
I mention it because as someone who has dabbled in programming, I know I could make detecting it months ahead really subtly / schizo'ly and then the actual lockouts crippling enough that I'd force someone else to spend an hour or so making a crack for it like they did for the current DRM. And the only thing stopping such a scenario is an ego trip.
And that I'm planning a playthrough where I try to grind up the ridiculous stuff (Ayane / Himawari events mainly but I might go for the sensei quest 'sex scenes' legitimately, and I don't want to also have to police my save file for red path instead of just using the guide mod which seems like a one way change. (Shampoo is also a fun thing to consider)
I know selebus and I can tell you that people underestimate what this man-child with an ego is capable of doing just for the bitterness of it.
I'd say it's more than likely that nothing is gonna happen if you use DRM but it's not absolutely impossible if he ends up adding countermeasures to it, that's why I discourage its use if you can get by without it. The first opportunity was during the whole renpy update, but through my regular combings of the game's code I didn't see anything out of the ordinary.
Since I too am obliged to "play" the game but I'm not a fucking idiot I also cheated Sensei-quest, but instead of using DRM I change some values in the game's code and then make sure to revert any changes after I'm done so that everything is left undetected.
My job here at this point is simply to make sure nothing fishy ever goes on and that if it does, that I can just give a clean save file to everyone who needs it
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.
My first thought was it must have broken when Selebus converted all the images to ".webp". But I looked in one of my old copy's of the game (v35 patched up to v41) and it was already a ".webp" and was not corrupted. So that's not what did it. If anyone wants to find when it broke it will be something between V35 and v41. I would guess a more recent version because someone surely would have seen it earlier if it happened a year ago.
I'm not sure why its getting more broken over time though. I wonder if the file size changed at all between them. Could be some strange behaviour of a corrupted ".webp", or something to do with compressing/decompressing a corrupted ".webp".
It almost has to be intentional unless he's using a script to prep downloads and it's re-saving that one image like 25 times per update. The fact it's not in the patches just full game downloads and is progressively getting worse
lmao nevermind. Going through the 0.45 happy event and I noticed that if you still had the shampoo, instead of getting the maya 2 profile unlock she just steals the shampoo back. Kinda bad omen for my grind everything hard run. Don't see any special variable saved for having it removed.
This was actually the pattern for the game's entire run. Character profiles didn't exist until the character was introduced in-game. Back in chapter 1, when Kirin was still in Wakana's class, her profile was in the side girl page. The side girl page when I started playing was just Sara, Haruka, Kaori, Karin, Kirin, and Maki, and the main girl page only had the first 10 girls, Molly, and Tsuneyo. There wasn't even a placeholder panel for girls who weren't in game yet. Just empty space.
We are barely at the half of Ch.4, so we might have a lot more of Sana's events where she will present herself or something. But hell, we still don't know the reason why certain girls the cover girls. Yet we can exclude some things:
1. It is definitely not the RAS thing, since we have Makoto, who is not a cover girl, yet we have her in RAS for so long already.
2. There is no 2nd floor girl for now.
3. (There should be third thing, but I literally forgot it while writing...)
Possible explanations:
1. They are characters that love Akira for real, not because of his dick or something.
2. It is a specific Chapter of this girl, where she reaches her peak.
3. Selebus is just trolling us, not having a special order of girls, just putting a random one here.
4. They are arranged in a certain order, signifying something.
Also, if we remember, before Ch.4 covers were just screenshots from really important events in Akira's life. I still remember Maya's old cover, and it was beautiful... So, something significant will happen with Sana, I believe in it.
But also, every old cover had some kind of glitch effect... What if... No, stop it. LoveStupidTheoriesGuy
My guess is that at some point Selly might indeed want to create a theming with cover girls, which was a more natural assumption to make when the girls up there were Ami/Maya/Ayane, girls that beam with importance well before entering their respective chapters. After Ch4, however, he might have scratched it (accompanied with a menu change) and/or I have to put this guess of mine on the shelf because there is no ruling based on "current character stats or progression" will qualify Sana as the most suitable candidate.
- Rooftop access is not it, like you said.
- Who Sensei really loves is not it as well.
- Who really loves Sensei is also probably not it if Noriko isn't the strongest candidate.
- Sexual progression is definitely not it, needless to say.
There are of course dumb craps like "hey it's roommate theme!" or "OH these are the exact same 4 girls that went to karaoke together by the end of Ch3!", but both feel too random and lack logical explanation to be a determining factor.
And I am mostly too grouchy to bank my hope on Sana's future development (i.e., waiting for Selly's endorsement) that has yet to come in Ch4. First, we weren't just two months into Ch4; we are already done with one reset in Ch4 and Sana's quarterly reports are essentially blank. Second, I asked myself if I could still confidently say "This cover girl's moments will for sure come later and justify everything" if the cover girl gets swapped with Kirin. If not, where do I draw the line and why? It's thoughts like these that push me into thinking "maybe there is no trend or reasoning in cover girl selection" instead of "Sana will be relevant at some point based on a history record that I can't elaborate".
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 tone 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.
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?
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.
