>>3827590
>it would've been easy to simply excise the R18 content without harming the game.
Specially because of how easy it is to use RPG Maker in general.
Ruby is a piss easy language, and the H-scenes are contained in their own Common Events.
I wiped out an example in like 5 minutes to show how easy it is to another Anon hours ago.
>Remove the H-scene related pictures at Graphics\Pictures, write a Ruby script containing an array of picture filenames that returns "false" if a certain picture isn't present in Graphics\Pictures, run this script in the different Common Events containing the code for the H-scenes and if it returns false you just throw in a text string like "This content requires a +18 patch." or w/e and an early exit.
>https://pastebin.com/iHMxy4i8

I think that, in a way, forcing people to download the patch is a good thing because then they'd have to get the intended experience whether they like it or not, but I highly doubt these fellas give 2 shits about that desu.

>>718214732
>>They could have just replaced the pictures with black squares, its still very fucking simple.
>That is literally what the H-scene toggle in the original did, you fucking retard.
NTA, but an in-game toggle doesn't modify an image file you silly goose. You misunderstood what that Anon said.

>The problem is the implications all over the place and the fact that there's fifty million separate instances of the rape button. You literally can't decouple BS from the sexual content.
Yeah, you totally can.
Remove the H-scene related pictures at Graphics\Pictures, write a Ruby script containing an array of picture filenames that returns "false" if a certain picture isn't present in Graphics\Pictures, run this script in the different Common Events containing the code for the H-scenes and if it returns false you just throw in a text string like "This content requires a +18 patch." or w/e and an early exit.
https://pastebin.com/iHMxy4i8

I said this like 3 times already, but these Otaku Plan guys are incompetent, it's that simple.