That is horrible. I wonder if it can be uncompiled and recompiled without the password requirements.And there is a problem... he added a second layer of security for the game to be able to play it that changes daily so SLDR or anyone that knows how to remove this, much appreciated. Will be pm'ing SLDR about removing it with a link. Yes I can give you the daily password but it only works for 3 days (unsure of how he did this)
Renpy Devs themselves have stated that actual DRM is unsupported in almost any form. Even something has simple as Steam DRM would be far to much work, for little to no gain(specially since Steam DRM can be beaten easily). The time checks are decent start, but won't stop anyone for long. Probably should have gone with a different Engine if they wanted to protect the Patreon versions of the game for any amount of time.Took about thirty seconds to disable the password system
I get what they were going for, but there isn't much they can do - Renpy is trivially easy to break into. As far as I'm aware, if you employ any actual encryption methods, Renpy can't read the files any more and the game won't run. The best you can do in Renpy is to delete the .rpy files and leave only .rpyc files (which are encrypted;You must be registered to see the links) and then pack them into .rpa files (You must be registered to see the links). This is what SadCrab did with Innocent Witches and Witch Trainer Russian Mod. It sucks and I sympathize, but you really can't stop piracy from happening.
And also, they implemented a time and date check to make sure the passwords hadn't expired, which means that the game technically had online DRM.
I'm working on the cheat and password-less build now, it'll be up in an hour or so.
So they're planning on checking the password or date each time you load in the future. They haven't written the xword_verify function yet, so I don't know exactly what it'll be like but I imagine I can just comment out this stuff to break it.#TODO add call xword_verify at bottom of after_load