@SimGuruModSquad: I need help with this please

This is what the TunableTestSet.tdescfrag states within a sim_info test:



So why doesn't this work in a test?

Did the poor guy get laid off?

Hey!

The tuning for this is fairly complex, but you should be able to set it up to get what you want.

Here is how the pregnancy element is implemented:

....def _do_behavior(self, *args, **kwargs):
........subject = self.interaction.get_participant(self.pregnancy_subject)
........if subject is not None and subject.household.free_slot_count:
............if random.random() < self.pregnancy_chance_and_modifiers.get_multiplier(self.interaction.get_resolver()):
................parent_subject = self.interaction.get_participant(self.pregnancy_parent_subject) or subject
................subject.sim_info.pregnancy_tracker.start_pregnancy(subject, parent_subject)

The pregnancy_subject is the Sim who will become pregnant, and the pregnancy_parent_subject is the Sim who will be the parent. For bed_TryForBaby (and the other "Try for Baby" interactions), a test multiplies the pregnancy chance by 0 if the "Actor" Sim Info is Male (there also is a multiplier of 1.5 if the Actor is fertile). In bed_TryForBaby, the pregnancy_subject is Actor and the pregnancy_parent_subject is TargetSim.

Suppose that there are two Sims, Alice and Bob, who Try for Baby. The way the interaction is set up now, regardless of which Sim initiates the interaction, both Sims run bed_TryForBaby. This is because the affordance_to_push_on_target tunable is set to "Push Self or None". So these are the interactions that will be run:

Alice -> Bob
Actor: Alice
TargetSim: Bob
Actor is Male: False
Pregnancy chance: 80%

Bob -> Alice:
Actor: Bob
TargetSim: Alice
Actor is Male: True
Pregnancy chance: 80% * 0% = 0%

To support male pregnancy without the chance of both Sims becoming pregnant, the affordance_to_push_on_target could be changed to point to a new interaction that doesn't have a pregnancy basic extra. It is possible that the existing bed_WooHoo interaction would work, or you may need to copy bed_TryForBaby and remove the pregnancy aspect (some testing is required). Alternatively, the pushed interaction could be the one that causes pregnancy, instead of bed_TryForBaby. This approach has the downside that only one of the Sims (either the initiator or the target) would have the chance of becoming pregnant, but the implementation would be fairly simple.

Side note: PickedSim is only relevant when a UI picker shows up, so you don’t have to worry about that when dealing with WooHoo/Try for Baby.

Checking active_sim works, removing the male check, and only the played sim's target gets pregnant if the pregnancy_parent_subject and pregnancy_subject enums are reversed. It leaves the issue that a female can't initiate TryforBaby with a male and get pregnant, but that can be worked around in game play by just reversing their roles in the interaction.

the affordance_to_push_on_target makes no sense to me.
"push_self_or_none=sims4.tuning.tunable.Tunable(description='If true will push this affordance on the target sim, else push None'"

That doesn't appear to indicate that both sims will be run thru the code.

And Picker vs TargetSim IS an issue. According to an mts thread, a picked sim causes the TargetSim check to be null, and somehow forces the 0 multiplier as a result.

I'm not gonna worry about that right now, since I've removed any check on the TargetSim.

'To support male pregnancy without the chance of both Sims becoming pregnant, the affordance_to_push_on_target could be changed to point to a new interaction that doesn't have a pregnancy basic extra.'

Do you have any idea how hard it is to understand this statement with the little knowledge I have of all this brand new code?

I appreciate your response however.

If this code was placed in bed_TryforBaby, would it cause only the pregnancy_subject to pass thru the pregnancy code in question?


False

"jtravers88;12730422" wrote:
If this code was placed in bed_TryforBaby, would it cause only the pregnancy_subject to pass thru the pregnancy code in question?


False

Your change would probably would break this interaction, since it's important that both Sims run a variant of the WooHoo/TryForBaby interaction.
This field is a variant: False for "push_self_or_none" means that no interaction will be pushed. Instead, you will should refer to a specific interaction to push. Here's how you would change the tuning to push the bed_WooHoo interaction:


13099


This may or may not work ( I haven't tried it yet). If it doesn't you can make a copy of bed_TryForBaby (giving it a different ID) and remove everything inside the elements from that interaction. The reason I called this a "basic extra" is because it is inside the section of tuning, which is a list of actions to execute when a Sim runs the interaction. So a clone of bed_TryForBaby interaction without the pregnancy element should keep Try For Baby working just as it does now except that only the initiator would have a chance of getting pregnant.

TargetSim




Would I need to change the participant type in my copy of bed_TryForBaby to Actor? If not, what guides the app to use one for the initiator and one for the recipient of the interaction?

It might be mute since a check for active_sim = true with a 0 multiplier and active_sim = false with a 1 multiplier, after reversing the roles for subject and parent_subject seems to work fine. Target always gets pregnant, Actor never does, however both still get the pregnancy test on the toilet.

"jtravers88;12731876" wrote:



TargetSim




Would I need to change the participant type in my copy of bed_TryForBaby to Actor? If not, what guides the app to use one for the initiator and one for the recipient of the interaction?

When the other interaction is pushed on to the target, the actor and target are swapped for that Sim. So there should be no need to change the participant icon.

"jtravers88;12731876" wrote:

It might be mute since a check for active_sim = true with a 0 multiplier and active_sim = false with a 1 multiplier, after reversing the roles for subject and parent_subject seems to work fine. Target always gets pregnant, Actor never does, however both still get the pregnancy test on the toilet.

I like this solution!

' So a clone of bed_TryForBaby interaction without the pregnancy element should keep Try For Baby working just as it does now except that only the initiator would have a chance of getting pregnant. '

So I would have 2 bed_TryForBaby interactions (different ids), one with the pregnancy code, one without. How is it that one sim will pass thru one of them, and the other sim will pass thru the other one. How would I know that is going to happen?

This is just informational as I have no plan to try this but it is probably important to understand how I should know that cloning an interaction would cause one sim to perform one, and the other to perform the other... yea.