When you go to the 2nd dorm floor on a certain day of a week (when otoha is around) the game checks if you have certain images in your game folder, if you have them then the game goes to Sel site and tryes to get access there, if it failed - then the game shuts down, delete saves and script gets erased leaving only encrypted "You would not download a car"
That's not 100% correct as far as i've seen.
At first, when the game starts it loads the gui.rpy and or gui.rpyc (<- seems to be intermediate code) among others.
(I'll be assuming that it's only the gui.rpy for simplicity.)
In the gui.rpy is a code block that does roughly the following:
- There is an image file in the game's folders. (*Dorm2Summersomethingsomething*.png, this one is always in the base game.)
- The code opens the file, searches for a specific part in it and loads that data, and this is rather interesting, as a code string.
- That code string is then also excuted.
The new code then:
- Opens specific .png's, like it did with the dormblahblah file, from the care packages.
- This time it's not about code but ID's.
(I don't know how the backend service on Sel's server handles this exactly so lets assume the following:
You buy a care package, it has a special "fresh" .png, in a database on Sel's end that .png get's a unique ID tied to your IP (Hopefully not your IP, because bad), that info/connection get's stored on Sel's end and you get the special .png with an ID, within your CP.)
- Code reaches out to Sel's server with the CP ID's.
- If the information stored on Sel's end doesn't match the data the code transmitted -> DRM happens.
So unless you took counter measures like discribed on p1 and have at least one care package installed, the DRM always happens. No special scene or event required.
There's another funny thing about all this.
The reason we got to know about this and spicifically the code behind might be Osako's fault.
Maybe we didn't hear that much of her recently is because she's still in prison for her misbehavior
