discussion HTML Favorite Teacher [v1.71] [SluttyStar]

[spaaaace]

This is one of the better real porn games imo.

 

[SilentHunter]

Unfortunately, the potentially good plot quickly begins to sag, which, combined with numerous bugs, makes this game not very interesting to play. The author clearly tried to create an interesting story, but in the end, we only get unfinished storylines. The quality of the media files is mediocre. Perhaps when the game is free of bugs, it will be worth returning to, but at this stage of development, it is not worth spending your time on it.

 

[Throwaway_goat]

this game is complete and utter dogshit. The sandbox is a shitty grind and the rest of it is just a bunch of obnoxious linear 'go to the library at 10AM on a Tuesday to advance this quest' missions that are practically opaque without constantly checking the hint system, and the game goes out if its way to make it as tiresome as possible, there's a $QuestNextDay flag enforcing the fact that you only advance 1 stage of any quest per boring shitty daily routine and 80% of the rest of the code is checking that it's between 10 and 1030 on Tuesday. The writing is a mix of incomphrensible ESL and LLM AI writing, the code is a mess with constant broken images, dead ends etc, the sex scenes are not hot at all, and the 'corrupting the school' mechanic has barely any content to see even if you cheat the girls a million points in obedience and exhibitionism.
I'll play almost anything if it's porn. Don't play this one.

 

[SilentHunter]

Tried to play latest version (v1.61). Alas, the game remains unplayable. There are still too many bugs.
Here cheat codes for v1.61.
silkweaver - +500 cash
hornetslash - Attraction menu
needlepoint - Special items added to your inventory
threadbound - Secret items added
spidercraft - Charm increased +1
webstrike - Endurance increased +1
loomhistory - Back button active
weaversgift - All Gallery Unlocked

 

[sendmefeetplea]

my god

 

[SilentHunter]

As of v1.65, the game remains unplayable. From the word "absolutely". I decided to stop tracking the development of this project. We don't have much time in this life, it's better to spend it on more interesting things.

 

[trigun.core]

Is this anything like Wife Trainer Files by chance?

 

[jawstheguppy]

Yeah, not really digging this one.

It's kind of a shame, as I like sandbox style games more than VN's, but this one kind of has the worst of both worlds. A lot of story, combined with the story being absolutely terrible. Meanwhile the game isn't exactly grabbing me, there's no hidden tutorial style system to guide the player in understanding what their goal is.

 

[SilentHunter]

Although gameplay-breaking bugs persist in the game, I still decided to notify the admins about the availability of the next update (v1.67). I want to warn you right away - the game is still an extreme case of pain in the ass, play at your own risk, you have been warned!

 

[paulkersey]

I think of all the education that I've missed
But then my homework was never quite like this!

Got it bad, got it bad, got it bad
I'm hot for teacher
I got it bad, so bad
I'm hot for teacher

 

[SilentHunter]

v 1.68 is out. And the game is still unplyable.

 

[SilentHunter]

v 1.69 is out. Problems with softlocks still remains.

 

[SilentHunter]

A good analysis has been published on the neighboring site regarding the issues on which it is impossible to play this game:

"

I looked in the code few version ago to try to fix it, but it needs complete rework... The problem is that not everything is stored in the SugarCube state. There are native javascript variables and events. If something outside of the SugarCode state get bugged there is no way to fix it and you don't know when this happens, so you don't know how old save to return, it could be hours ago...
Things that I suspect can break the game are:
1.The back button in a lot of places.

2. Any form of cheating, some events are connected to stat raise, if you jump too much it can never trigger. Even simple changes as energy or money can break some state if they are changed in a middle of event. I think that the whole non SugarCube code is remain of some anticheat system, I can't imagine other reason why it's there. It's like Denovo, but worst...

3. Save and load...the native js variables and timers are not saved in the save. I don't know for sure, but I suspect that save/load in a wrong moment can break the game, similar to the back button. By wrong moment I don't mean a matter of second, some in game events takes days or weeks in game time and saving and loading during them can break the game.

I don't think that it's worth to try to navigate around all thous problems, but if you must... never use the back button, never cheat for anything, never refresh the page, never save/load, play it in one session without stopping the browser, shutdown or restart the PC and be sure to not have plugins that optimize the tab memory usage if you leave the tab for anything, progress all story lines at the same time, never focus on one of them and progress it too much... be prepared to start a new game with every update... And I can't guaranty that it won't bug, probably it'll... this is just the best chance to avoid the problems that I saw in few minutes looking at the code, probably there are plenty more that I don't know...

My advise, consider this game dear unless you see a change log that says something like complete rework, refactoring or something like this".
(c) zaarin3

 

[SilentHunter]

As of v.1.71 the bugs are still there, and you can still enjoy softlocks, which can only be circumvented by editing the code (console commands won't help). It was the last chance I gave this game, and it's on my blacklist from now on.