I may differ what to be "checked" by the scene-tracker(imho sometimes it seems to much)
I had a really long discussion with myself regarding the scene tracker, both on what scenes to include and what information to give.
For the first point my decision was to include everything that is (or seem to be) needed to see another scene. Like by example the fetish quests, that generally have at most one or two lewd images, but are mandatory to see all the scenes that need to know the fetish.
As for the second point, I goes for the lazy path. If it's tested by the game, then it's included in the scene tracker. I know that it make no sense sometimes, like by example the taboo/not taboo when the scene don't regard the mother or the sister. But it ensure me that I haven't forgot something, while offering me the possibility to limit my works ; the same conditions and description can be used for more girls, when not all of them.
AttributeError: 'Person' object has no attribute 'AONpsylocked'
Normally this have been fixed with the version 1.09a or 1.09b.
When the psy part changed in 0.42, I reused a variable that was intended for this. But at first I totally forgot that initially it could, and was, created on demand, while the extended use I added needed it to exist by default.
AONscenesTracker.json
"MCbend_sanOutfit" and "MCbend_sanOutfitFinish" is (wrongly(?)) for
[ "allie", "chelsea", "denise", "kelly", "larson", "mary", "nikki", "samantha", "sandra", "sulynn", "terri" ]
instead only for
[ "sandra" ]
Hmmm, I need to check, but from the name of it yes, it looks like a copy/paste that I haven't corrected.
"NCHDLPlot8Sarah": does NOT get registered, even tho I did it
Yeah, this one is half voluntary.
The scene have had a lot of changes in the 0.42, and I don't know, it felt half broke, or half corrected. Therefore I let the tracker with the initial scheme. I think it's less annoying for the player to be forced to redo it once, when the full quest is definitively fixed, than to have to redo it every time the quest will be adjusted.
###this is about your mindcrafting-cheat !
Yeah, there were a big issue with this. Normally fixed with the 1.09b. I should have changed the way it works four or five times, and every time there were something that wasn't take in count it "this" or "that" context.
Your guess is correct, the "+" was the cause of the last problem in date. It was mandatory with the previous way I handled mind crafting, and totally breaking with the new way... except that I forgot this detail at first.
Normally this time it works and everything is take in count, but honestly I'm still not totally sure about this. And like the game is too open, I can't effectively test all the possibilities.
(not that it matters...; )
"general" question: why do you go beyond the -999...999 init-offset?
(by RenPy-SDK defined as "user"-area, iirc)
is this really necessary?
It's more a question of habit that something really needed. The only effective limit is -1457 (from memory) because below Ren'py isn't fully initialized itself.
and then there you always activate the console. Why?[/spoiler]
There's two reason. Firstly because I need it when working on the game, and it don't really matter that it stay. Secondly because some people can't use the key combination needed to trigger the configuration interface, therefore (while it's not explicitly said in the mod) they can open it by typing "AON" (or is it "aon", rhaa my memory is a mess right now ;( ) from the console.
Thanks a lot for the return. I haven't commented on everything, but I'll look a all what you said, including the part I think that are now fixed, just in case.