Relax, take it easy.
I am going to add to what @goobdoob said above about putting your name on the walkthrough and a version number and recommend that you stop deleting your old walkthroughs from your second post since it is now linked in the OP of this thread.
Belle 2- go to the river. Don't know where the river is? Train pathfinding and go out of town and look. Visit it a few times.
Keep in mind that someone might get those hints and then save/close the game only coming back some days later. (haven't played that part of the game in a while so I don't remember if there's already a repeatable explanation somewhere)
All you'd need to do then is visit Samarra and see the ability to present evidence to her. Part of my design for this game is that I want to avoid a quest log and let people figure out things dynamically. I use clues to help the player keep track of things that might happen over a longer period of time, even if those clues aren't used directly in puzzles.
Anal has nothing to do with the last scene, as you can't anal Primrose yet. Like I said before, scene 5 is friends with benefits only.
Yes, but let's assume it's not (which isn't hard because it's not a percentage). That would mean it is possible we have played more than a small part of the game and there is less than 82% to explore and so on. I'm not saying I know what Belle's planned release is, but I doubt we'll be seeing up to version 0.99 until we see full release. So why confuse the matter more? Don't set unrealistic expectations because you just know there will be some idiot who'll complain that a game is completed after version 0.25 even though there still should have been 75% more content because "someone" once said that you could assume version numbers meant percentage.
I don't bother catering to people who cannot accept simple rules and expectations. This is a lesson I picked up as a software developer over the years. For example, if you give an estimated time of arrival (ETA) for a release of something, someone will always, inevitably, take it as a guarantee and a promise. You cannot take people like that seriously, and you can't just stop giving out ETAs because you don't want to deal with it. It's best just to ignore that kind of sentiment altogether and let it be that person's problem instead, and that's the approach I have. If someone starts complaining about the stuff you mentioned, it's not my problem and I won't let it become one.
Or people will listen to your estimate, then ignore it. This recently happened to me. I was told by my boss that my priority was project A. Finish it, then work on project B. So in our weekly (ugh) meeting I'd give status for project A, and inevitably the stakeholders for project B would ask what the status was, and when I was going to finish it. I got real tired of explaining every week that project B wasn't started, and wouldn't start until project A was done, and dealing with the "but we really need this!" comments. "Talk to my boss".
Yes, he did. But that didn't stop people from asking me about B during the week. /sigh
