Chastity fixes

Fixes #562 (closed)

I've got saRules somewhat cleaned up now, but that hasn't solved the issue, unfortunately.

What exactly did you do? It looks like you just replaced the releaseRules checks with a go-between variable.

At least it will be useful during JSification.

I added a check for the "chastity" release rule wherever there was check for the "restrictive" release rule. I think I may have narrowed it down to the individual JS files (saServant.js, etc), but I'll need to do more testing before I can be sure.

I thought I did a lot of those though? You sure the ones that were missing it weren't job related?

You did a majority of them, but there were still quite a few that slipped through the cracks. It seems the culprit was the job-related passages, after all. I'll have a fix shortly.

But you must keep in mind that chastity will not stop customers from using them.

added 14 commits

• 07cdfcc5...d7ab3e67 - 12 commits from branch pregmodfan:pregmod-master
• ae3849eb - Fixed servants not respecting chastity rules
• e7975e6d - Merge branch 'pregmod-master' of https://gitgud.io/pregmodfan/fc-pregmod into hotfixes

Compare with previous version

Right. This affects only servants, for now - I'm not sure if any of the other jobs are affected by this bug as well.

About ready to wrap this up - should I get rid of the temp variable in saRules or should I just leave it?

Leave it in. It will be useful later in the passage's life.

added 1 commit

• 9e9d8705 - Updated TODO

Compare with previous version

Alright, I think that's everything, then.

changed the description

mentioned in commit 1d13d80c

merged