ParticipantType Enum

scumbumbo

Deceased

Original Poster

#1

19th Feb 2016 at 5:09 AM

ParticipantType Enum

The interactions.ParticipantType doesn't seem to be included in the unzipped .pyo files, so as Inge was asking a question that made me wonder if there was a relevant participant type, I used inspect on the imported ParticipantType enum in game and dumped the information. There's some neat stuff in here which I had no idea you could use in an XML tuning ParticipantType. Certainly many of these wouldn't be valid except in specific tests, but my guess they can be used as part of a do_command argument, which was the question Inge posted.

Not sure if this is defined as part of the EXE or if it's a dynamic enum that gets built somewhere along the way (perhaps even defined in the XML somewhere I've never seen). Anyway, as I'd never seen a definitive list, so I thought I'd post it for all:

Code:

ParticipantType enum:
  ParticipantType.Invalid
  ParticipantType.Actor
  ParticipantType.Object
  ParticipantType.TargetSim
  ParticipantType.Listeners
  ParticipantType.All
  ParticipantType.AllSims
  ParticipantType.Lot
  ParticipantType.CraftingProcess
  ParticipantType.JoinTarget
  ParticipantType.CarriedObject
  ParticipantType.Affordance
  ParticipantType.InteractionContext
  ParticipantType.CustomSim
  ParticipantType.AllRelationships
  ParticipantType.CraftingObject
  ParticipantType.ActorSurface
  ParticipantType.ObjectChildren
  ParticipantType.LotOwners
  ParticipantType.CreatedObject
  ParticipantType.PickedItemId
  ParticipantType.StoredSim
  ParticipantType.PickedObject
  ParticipantType.SocialGroup
  ParticipantType.OtherSimsInteractingWithTarget
  ParticipantType.PickedSim
  ParticipantType.ObjectParent
  ParticipantType.SignificantOtherActor
  ParticipantType.SignificantOtherTargetSim
  ParticipantType.OwnerSim
  ParticipantType.StoredSimOnActor
  ParticipantType.Unlockable
  ParticipantType.LiveDragActor
  ParticipantType.LiveDragTarget
  ParticipantType.PickedZoneId
  ParticipantType.SocialGroupSims
  ParticipantType.PregnancyPartnerActor
  ParticipantType.PregnancyPartnerTargetSim
  ParticipantType.SocialGroupAnchor
  ParticipantType.TargetSurface
  ParticipantType.ActiveHousehold
  ParticipantType.ActorPostureTarget
  ParticipantType.InventoryObjectStack
  ParticipantType.AllOtherInstancedSims
  ParticipantType.CareerEventSim
  ParticipantType.StoredSimOnPickedObject
  ParticipantType.SavedActor1
  ParticipantType.SavedActor2
  ParticipantType.SavedActor3
  ParticipantType.SavedActor4
  ParticipantType.LotOwnerSingleAndInstanced
  ParticipantType.LinkedPostureSim
  ParticipantType.AssociatedClub
  ParticipantType.AssociatedClubMembers
  ParticipantType.AssociatedClubLeader
  ParticipantType.AssociatedClubGatheringMembers
  ParticipantType.ActorEnsemble
  ParticipantType.TargetEnsemble
  ParticipantType.TargetSimPostureTarget
  ParticipantType.ActorEnsembleSansActor

Inge Jones

One horse disagreer of the Apocalypse

#2

19th Feb 2016 at 8:26 AM

Is it ok if we discuss participants in general in this thread? Does "participant" refer to the instance of the object or sim the player clicked to make the menu come up?

"You can do refraction by raymarching through the depth buffer" (c. Reddeyfish 2017)

scumbumbo

Deceased

Original Poster

#3

19th Feb 2016 at 4:48 PM

Well, the short answer is that it depends on which participant type you specify. You can choose the "Object" type or the "TargetSim" type to make the choice you specifically inquired about.

A participant type is a choice of any of the types listed in the above post. You'll see these a lot in tests, and targets for outcomes or loot, etc. Basically it's used anytime the XML needs to make a choice of which participant the test or operation needs to be performed on. You'll see them used in various tags, or tunable enum lists. For instance:

A statistic change in an interaction needs to know who to apply the statistic change to, so looking at 0x2042 (Gardening_Water_All) we see two statistic changes in a row:

Code:

            <V t="statistic_change">
              <U n="statistic_change">
                <T n="advertise">False</T>
                <T n="amount">-10</T>
                <T n="stat">16616<!--Commodity: commodity_Motive_HygieneHands--></T>
              </U>
            </V>
            <V t="statistic_change">
              <U n="statistic_change">
                <T n="advertise">True</T>
                <T n="amount">35</T>
                <T n="stat">16602<!--Commodity: commodity_Gardening_Moisture--></T>
                <L n="subject">
                  <E>Object</E>
                </L>
              </U>
            </V>

The first one doesn't supply a "subject" so that gets the default for the subject tuning which is noted in the tuning description for interactions as being the "Actor". The second one specifies that it should not be the default, we don't want to make the Sim wetter we want to make the interaction object wetter, so "Object" is used for the subject.

Another common one is the "who" tag, most commonly used in a sim info test, but also some other tests, and it too defaults to the actor Sim. But I'm seeing some interesting usages in browsing these new findings. For instance, I had no idea you could add a statistic to an actual lot, but "Lot" is a valid participant type flag and is used in a statistic test in at least one interaction, from 0x2424 (Death_Anger):

Code:

        <V t="literal">
          <U n="literal">
            <L n="conditions">
              <V t="stat_based">
                <U n="stat_based">
                  <T n="stat">16668<!--Statistic: statistic_NPC-GrimReaper_Count--></T>
                  <U n="threshold">
                    <E n="comparison">LESS_OR_EQUAL</E>
                  </U>
                  <E n="who">Lot</E>
                </U>
              </V>
              <V t="time_based">
                <U n="time_based">
                  <T n="max_time">40</T>
                  <T n="min_time">40</T>
                </U>
              </V>
            </L>
            <E n="interaction_action">EXIT_NATURALLY</E>
          </U>
        </V>

Which is in a flexible length section and checks to see if the count of Grim Reapers on a lot is less than or equal to (again, we have to look to the TDesc to see what the default for the threshold comparison value is) zero. So once there are 0 (or fewer?) reapers on the lot for a period of 40 minutes that particular exit condition will fire, ending the interaction.

One last example, this time a list, where a buff is applied to a number of Sims. In this case, 0x231d (baby_Social_ShowOff), a buff is applied to the actor, everyone in their social group, and the targetted Sim as long as there are 3 or more Sims in the social group:

Code:

    <V t="buff">
      <U n="buff">
        <U n="buff_type">
          <V n="buff_reason" t="enabled">
            <T n="enabled">0x9C09275F<!--String: "(From being in a social group with at least 3 Sims)"--></T>
          </V>
          <T n="buff_type">125555<!--Buff: buff_Trait_WithMyFriends--></T>
        </U>
        <L n="subject">
          <E>Actor</E>
          <E>SocialGroupSims</E>
          <E>TargetSim</E>
        </L>
        <L n="tests">
          <L>
            <V t="social_group">
              <U n="social_group">
                <V t="enabled" n="threshold">
                  <U n="enabled">
                    <T n="value">3</T>
                  </U>
                </V>
              </U>
            </V>
          </L>
        </L>
      </U>
    </V>

scumbumbo

Deceased

Original Poster

#4

19th Feb 2016 at 4:54 PM

Quote: Originally posted by Inge Jones

Is it ok if we discuss participants in general in this thread?

I assume it's okay - but if not a moderator can move this from Resources to Modding Discussion. Might get more visibility there which could be good as I'm seeing some things I never really knew were possible in the XML now that I see all of these valid participant types. The only one's I'd really noticed previously from looking at the XML were Actor, Object and TargetSim.

plasticbox

Pettifogging Legalist!

retired moderator

#5

19th Feb 2016 at 5:47 PM

That's not the only ones that are in use though -- ObjectChildren for instance is used for harvesting ( = the actual harvestables that sit in the slots of the parent object); CarryObject and CraftingObject for crafting, ActorSurface or TaegetSurface I think I've also seen in that context (kitchen counters when crafting a food recipe, I believe?), PickedSim would be the sim that a sim is calling on the phone etc.

Stuff for TS2 · TS3 · TS4 | Please do not PM me with technical questions – we have Create forums for that.

In the kingdom of the blind, do as the Romans do.

Sign in to Mod The Sims