From 1844369358f13045feed8d3c1069a9f67f383b24 Mon Sep 17 00:00:00 2001 From: klorpa <30924131+klorpa@users.noreply.github.com> Date: Sun, 9 Dec 2018 00:37:49 -0600 Subject: [PATCH] WIP --- devNotes/VersionChangeLog-Premod+LoliMod.txt | 4 ++-- slave variables documentation - Pregmod.txt | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/devNotes/VersionChangeLog-Premod+LoliMod.txt b/devNotes/VersionChangeLog-Premod+LoliMod.txt index d97801e75c2..50f04062ab1 100644 --- a/devNotes/VersionChangeLog-Premod+LoliMod.txt +++ b/devNotes/VersionChangeLog-Premod+LoliMod.txt @@ -6145,7 +6145,7 @@ -reworked saChoosesOwnJob to not be potentially broken -limited saChoosesOwnJob to prevent slaves from locking themselves in industrial dairies and overfull facilities -added a new universal rule to permit or deny slaves choosing their own jobs from joining facilities, off by default - -recalced underarm and pubic hair in slavegen, you should see things other than waxed consistantly now + -recalced underarm and pubic hair in slavegen, you should see things other than waxed consistently now 04/09/17 @@ -6335,7 +6335,7 @@ 23 -bugfixes - -some tweaks to things changed from single instance to week long isntances + -some tweaks to things changed from single instance to week long instances -minor FS reactions to certain player appearances 22 diff --git a/slave variables documentation - Pregmod.txt b/slave variables documentation - Pregmod.txt index 2332d9b3954..d585d553eb9 100644 --- a/slave variables documentation - Pregmod.txt +++ b/slave variables documentation - Pregmod.txt @@ -3539,17 +3539,17 @@ Advanced pregnancy control structure: Now, with support of human-animal pregnancy, there is need for ability to change values that been constant before. New structure designed for it. -.pregData property for slave should now contain object with describle pregnancy process. By default it will be set to human data. Templates stored in setup.pregData.x where "x" - name of species. +.pregData property for slave should now contain object with describable pregnancy process. By default it will be set to human data. Templates stored in setup.pregData.x where "x" - name of species. <<set slave.pregData = setup.pregData.human>> -In code at any time properties that contain data can be acessed now. Properties is RW, so slaves can be changed individually later. Example: +In code at any time properties that contain data can be accessed now. Properties is RW, so slaves can be changed individually later. Example: <<if slave.pregData.type == "human">> or <<set slave.pregData.normalOvaMin = 2, slave.pregData.normalOvaMax = 4>> (setting normal ova count 2-4 on every ovulation). - Proprty list: + Property list: type - name of species. Should math slave.ovaType normalOvaMin - normal/base ova count on ovulation (minimal) @@ -3561,6 +3561,6 @@ or fetusCTR - array with CTR control points. These three array is linked, and values in second and third should be in the same order as in first. (Week of .fetusWeek[i] is correspond to .fetusSize[i] and fetusCTR[i]) - Control points - it's points of graph as if it builded on paper (one axis - fetusWeek, other - fetusSize/fetusCTR). This graph data used to get actual size of fetus, so no need for manual setting of every week data in array. + Control points - it's points of graph as if it built on paper (one axis - fetusWeek, other - fetusSize/fetusCTR). This graph data used to get actual size of fetus, so no need for manual setting of every week data in array. - What is CTR? In most medical data, human fetus size (length) measured as "crown to rump" from 1 to 20 weeks, and "crown to heel" later. Formula that calculate volume of womb should get data in single format. So there is need CTR rate - value that describe difference between full "crown to heel" and "crown to rump" length of fetus (also it's can be used to control aproximation of legs, hands and tails volume). For most animal fetus data it's always 1 as they are not bipedal and "crown to rump" is natural measurements for them. But CTR rate changes might be needed to get more accurate results for volume calculations, as fetus is not sphere and length - not always have the same relation to it's volume. + What is CTR? In most medical data, human fetus size (length) measured as "crown to rump" from 1 to 20 weeks, and "crown to heel" later. Formula that calculate volume of womb should get data in single format. So there is need CTR rate - value that describe difference between full "crown to heel" and "crown to rump" length of fetus (also it's can be used to control approximation of legs, hands and tails volume). For most animal fetus data it's always 1 as they are not bipedal and "crown to rump" is natural measurements for them. But CTR rate changes might be needed to get more accurate results for volume calculations, as fetus is not sphere and length - not always have the same relation to it's volume. -- GitLab