It is being looked at, it will take a bit, because each time we crack it, they change it, so it's a game of cat and mouse.
I feel so bad for you every time you have to post/compress Inceton content. Watching some of the reactions is like watching monkeys trying to F a doorknob or something to that effect
would like to know the technical details of this car in mouse game . do they change how the system works or do they change where they store the needed info of the game etc .
script.rpyc and version.rpyc dummy files in the game folder.
I can confirm it works.
They didn't mess with it earlier since it wasn't playable, they didn't want to listen to everyone bitching and not reading it was not cracked yet...
Thank you for your reply. Interesting how it could be compressed then. I think I'll pass this time. I'm sure this little update will only make me more annoyed instead of enjoying it, as the chapter hasn't been finalised yet. Besides, we're just giving the developer ammunition to harden his authentication protection.
Oh, I C, thanks. Bitching around is a big problem here.
Not sure what you mean by how it can it be compressed...it's like every other Ren'Py game, it just has a login authenticator is all.
I've never compressed a game, but since the compressing tools just compress multimedia files (pics, videos, audios), I guess they don't need the game to be runnable to perform compression, since the scripts stay untouched.
Yes, it doesn't touch anything other than media files, but it can't be packed back to RPA since you can't use un.rpy on it and cannot build with the official SDK like every other Ren'Py game, but with the modified script, it can be decompiled and build it back with RPA just like how was like from the dev without the authenticator.
Because I did have the source.....yes, but you need to have a source … an uncompressed source ;-) I assumed the link to this source would be here
jfi: The compressed version usually makes it here first.
She's a side character only some
