sotherbee wrote: ↑Sun Nov 26, 2017 4:08 pm
Hi. I've tried new features.
The idea is very interesting but script not works correctly.
For example:
07:00 Malena: I see you modified your chances to cum since last time
===
It happens even if I did't touch settings. In fact -every session.
How to correct this?
Best regards,
Soth
Did this start appearing immediately when you started using 1.06? Also, can you check in your MissBluev1.06/System/Flags folder if you have the following flags: pvCheckOrgasmChance, pvLockOrgasmChance, pvAccessLD? If you have any of those flags, deleting them should reset the feature.
This is from a fairly complex script (written originally by BoundSquirrel, though I made some minor changes for better integration with MB), so I wouldn't be surprised if there was a bug somewhere. On the other hand, it *seemed* to work fine when I tested it. It's going to take some time to go through and test it again. Is anyone else having this problem?
LegalizeRanch wrote: ↑Tue Nov 28, 2017 8:10 am
avatarbr wrote: ↑Tue Nov 28, 2017 12:42 am
Interesting, I checked the code, and looks like PtheV created a system(with system flags) to check if the orgasm chances were changed since the last session.
But I think the problem is, some scripts can change that (@DecreaseOrgasmChance and @IncreaseOrgasmChance), even without the user knowing. Not sure if he used that in MissBlue (HoT have a few), but this can cause that line to show up too.
Don`t think so. I found @increaseOrgasmChance only in pvCr_BeggingDecide and never found @decreaseOrgasmChance. But yeah, maybe he begs too much hehe. I think you should add a line there
- Spoiler: show
- (yes)
@NullResponse @IncreaseOrgasmChance @ChangeVar[orgAllowSet]=[orgAllowSet]+[1] @TempFlag(pvIncreasedOrgasmChance) @AFKOff
@End
With Miss Blue, there's only a chance of @IncreaseOrgasmChance, like you said. But it's reset at the end of the session, unless of course the session did not end properly (i.e. Teas AI crashed or you closed the program before the session ended). But yes, if you've added other scripts that change the orgasm settings it screws up this particular feature of the personality, unless you manually reset the orgasm settings before the next session.
LegalizeRanch wrote: ↑Tue Nov 28, 2017 8:10 am
Also, can anybody (preferrably author =)) explain, is this meant to look like that?
- Spoiler: show
- pvCr_OrgasmChanceLock.txt #PetName we've been doing this for a while @DeleteFlag(pvLockOrgasmChance) @SetFlag(pvAccessLD)
I dont understand connection between long denial and lock my orgasm setting from change? What if it set to "Always allows"?
The thing is, both the Long Denial and the Lock Orgasm Chance features bypass the native Tease AI orgasm settings. Some users may want the program to stick to those settings, in other words do not want the personality to say, you know what, I'm going to ignore your "always allow" setting and deny you for X days. That's why Miss Blue asks you at the beginning (in earlier versions it was at a later stage) whether you want to give her *complete* control of your orgasms. If you said yes, then both LD and LOC are unlocked. If you say no, Miss Blue will always stick to whatever your settings are. Note that outside of LD and LOC Miss Blue still uses your orgasm settings to determine your chance to cum, even if you said yes.
Maybe the script should be more clear about all this. I'd love some feedback here too, should this be made more obvious? Would you prefer an explicit warning about the consequences of the "complete control" decision?