Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

0.7 version-bug (old saves) is fixed... (Patreon)

Published:
2017-10-21 11:55:24
Edited:
2017-10-21 11:56:38
Imported:
2026-06

Content

It seems, I totally messed up the patron-access content parts of the new version - as some of you already noticed and told me.  I started to solve this at the morning, and it is fixed by now.Sorry for the inconveniences, I hope this won't happen again. 

Comments

Artem

Could you also put hornsville.com/patronlogin.php link somewhere on your front page for users convenience?

Artem

When processing to the phase 2, I see "(if 0 < 1)[set: 0 to 1] Tapping the screen brings up a new message." in the beginning of the next text. And when I tap "a new menu appears.", it sends me to the dead end again. Do you even test your "fixes" before releasing?...

Sameer

I'm still getting the public version statement on the phase 2 page in the app. This was with a save I started yesterday, with all phase 2 tasks finished. Do I need to start a new game for the new content?

minibw

So far this is working for me once I started a new game -- managed to reach both the canon ending and the submission ending -- but the one thing I can't find is the gloryhole content in the club. The only thing I find when I "wander" the club is the initial meeting with Theo, but even that gets cut off after I go with Master Vlad and then I just can't wander anymore and there's nothing else to find. (I don't know if this has to do with it, but I get the message "(if 1 < 1)[set: 1 to 1]" whenever I go into the club.)

hornstown

The reason I'm not doing it is people who want to access the content without pledging. The content itself will be accessed, I have no illusions about that but if the login address was visible for everyone then people might attempt to guess/get patrons e-mail addresses as well and I don't want that to happen to you guys.

hornstown

I have remedied the rushed fix attempt of yesterday and things should be OK soon. I will have a new post when 7.1 goes live, hopefully in a few minutes.

Artem

Obscuring things is not the way to protect them. You could try to generate a random token/access key for each patron each month, send them by emails, embed hashed tokens in the list inside the app (you rebuild it often enough). And when someone uses his access token, send a usage request to your server for the statistics. When you see someone abuses his access (too many connections from different IPs), you can ban them.