Introduction
An interaction describes something a Sim can do or something the player can request through the game. Clicking a chair, choosing a conversation topic or opening a shopping dialog can involve different interaction classes, even though all appear as choices in the interface.
In tuning discussions, interaction and affordance often refer to the same interaction definition. There is a useful distinction when reading code: an affordance is the tuned definition/class the game can use; a running interaction is a particular instance created from it for an Actor, target and execution context. Being an affordance does not mean its tests pass or that it is currently visible in a menu.
Practice at a Workbench defines the activity, its tests and behavior. The workbench can reference that definition in its affordances.
Bella practices at a particular workbench. Mortimer can use the same definition for his own activity; their running instances have different Actors and contexts.
Consider a custom Give Encouragement interaction. It needs a menu entry, conditions that decide when it is available, behavior involving the two Sims and a consequence such as a moodlet. These pieces have different jobs: tests control eligibility, the interaction organizes execution, and loot can apply the result.
The names below describe related layers, not six mutually exclusive categories. An immediate interaction is a specialized super interaction; a social interaction can be a mixer; a picker can lead to another interaction. Start by finding an EA interaction with the same behavior you need, then inspect its class and references.
Read Tests & Logic first. This article connects those conditions to interactions; Actions, Loot & Outcomes explains their consequences.
Super interactions: the main activity
A SuperInteraction organizes a main activity. For a custom interaction such as Practice at a Workbench, this can include reaching the object, using an appropriate posture, playing behavior over time and finishing or being cancelled. The actual setup depends on the selected class and tuning.
The word “super” does not mean powerful, complicated or higher priority. It identifies a role in the interaction system. Specialized classes build on that role rather than requiring you to implement every part yourself.
Example: your workbench activity should last for a while and increase a skill. Find a comparable EA work activity. Inspect its constraints, animation setup, duration, tests and completion behavior together. Copying only its menu name will not reproduce the activity.
Immediate interactions: act without a queued activity
An ImmediateSuperInteraction is useful when the request should act directly rather than wait for the Sim to perform a normal queued activity. A practical EA example is replacing an object destroyed by fire. A custom settings option is another design that may suit this approach.
Immediate execution is not a shortcut for an activity that still needs routing and animation. Enable a feature and walk over and repair a machine have different execution needs, even if both begin with a click.
When inspecting XML, check the resource’s class and module attributes, such as c and m. Names like SuperInteraction and ImmediateSuperInteraction identify behavior classes; a resource’s descriptive name alone does not establish its type. Use current extracted tuning as the template for exact fields.
Social interactions: exchanges between Sims
Social interactions coordinate behavior between Sims. SocialSuperInteraction and SocialMixerInteraction serve different roles in that setup: the former can organize a social activity and its sub-interactions, while the latter supplies an exchange within a social context.
Give Encouragement might therefore be modeled on an existing social mixer rather than a generic object interaction. Compare a similar exchange for its targeting, compatibility and result behavior before changing the dialogue, tests or loot.
Keep the two Sims’ roles explicit. The Actor initiates the exchange; TargetSim is the intended recipient when that role exists in the current resolver. A test for the recipient’s mood should not accidentally check the Actor, and a reward moodlet should go to the Sim you intended. Participants & Resolvers explains how those roles are resolved.
The pie-menu category is a separate concern. Placing an entry under Friendly changes its presentation; it does not turn a generic interaction into a social mixer or provide the required social setup.
Mixer interactions: behavior within an activity
A MixerInteraction supplies behavior within an appropriate super-interaction context. Think of a main activity such as eating or talking, with smaller actions that can occur during it. A mixer depends on compatible context; creating its resource does not automatically make it a standalone activity on every object.
Example: you want a new conversation topic. Start with a comparable social mixer, then trace which social activity or affordance list makes it available. If you attach it in the wrong place, the resource can exist but never be offered in the context it needs.
Picker interactions: choose first, then act
A picker presents candidates and lets the player choose. You will encounter the base class PickerSuperInteraction and specialized classes or systems for particular kinds of selection. “PickerInteraction” is often used informally for this family; always check the actual class of the resource you are editing.
The interaction controls what is selected and what happens next. The picker dialog controls how choices are displayed. A portrait grid, an item list and a purchase window can look different, but the appearance alone does not tell you how the selected value is used.
Common selection purposes
- Sim picker: choose a person, for example the recipient of an invitation. Check the candidate filter and whether one or several Sims can be selected.
- Object or inventory picker: choose an existing item, for example a gift from an inventory. An existing object has its own identity and state; it is not the same as a catalog definition used to create a new object.
- Purchase picker: choose goods to buy. Candidate generation, prices, quantities and delivery are part of the purchase flow. A list of icons alone does not implement a shop.
- Recipe picker: choose what to cook or craft. Availability may depend on skills, ingredients and the object being used; the choice must connect to the corresponding crafting behavior.
- Trait picker: choose a trait to add or remove. Check which Sim receives it and which traits are eligible. Specialized implementations may use different filters and selection behavior, so inspect the actual class rather than treating all trait pickers as interchangeable.
- State picker: choose a supported object state, for example a mode on a device. The game’s
StatePickerSuperInteractionis a concrete class to inspect when researching this pattern. - Service or destination picker: choose a service to request or a place to travel. These flows need the corresponding service or travel system after selection; selecting a row does not itself hire an NPC or move a household.
These are purposes, not a complete list of interchangeable class names. Some use specialized interactions, some rely on feature-specific dialogs, and mods can define additional classes. Match the underlying behavior as well as the interface.
Follow one choice from beginning to end
Example: Select a Sim to Receive Encouragement. Opening the option first produces a list of eligible Sims. Selecting a row identifies the recipient. The next stage uses that selection to start the intended social behavior or apply an appropriate consequence. Closing the dialog should leave that choice unapplied.
There are several distinct places to inspect: the test that allows the picker to open, the filtering that populates its rows, any restrictions on selecting a row, and the behavior after confirmation. An empty picker can indicate a candidate-filter problem even when the opening interaction passes its tests.
Do not assume the selected Sim is the original TargetSim. The clicked target might be an object or another Sim; selection can introduce a different participant such as PickedSim or PickedObject where the interaction and resolver support it. Trace how the choice is passed on before assigning loot participants.
For a purchase picker, also test the destination of purchased objects. Inspect candidate sources, categories, prices, purchase loot and delivery separately. Those settings solve different problems within the same shopping feature.
Affordances and affordance lists: connect the interaction
An affordance is the interaction definition described in the introduction. An affordance list groups interaction references so another resource or system can use them. A list is a connection mechanism; it does not itself run every interaction it contains.
Direct object affordances and shared lists
An object’s _super_affordances is one place to look for its available super interactions. A reusable affordance-list snippet is a separate resource whose entries can be consumed elsewhere. Mixer lists similarly provide candidates for compatible activity contexts. Do not treat all three as the same field or assume they can accept every interaction class.
Example: a custom workbench. Creating Practice at a Workbench adds an interaction resource to your package. The intended workbench must also obtain a reference to it through the appropriate tuning or injection path. Only then can the game consider it and evaluate its tests.
Example: a custom conversation topic. The social mixer needs a compatible social connection, such as a mixer list used by the relevant activity. Check that the list expects mixer classes and that your interaction is compatible with its consuming activity. Putting an unrelated super interaction into that list is not equivalent to making a new conversation topic.
Adding an entry without replacing an entire EA resource
An override can replace an EA resource containing a list, but two mods replacing that same resource can conflict. An injector or framework can instead add entries through its supported configuration. The exact approach depends on the destination; support for an object’s super affordances does not automatically imply support for every mixer list or picker.
Creating a new list is also insufficient if nothing references it. Trace the full connection: the object or activity, the list it consumes, and the interaction in that list. After that, inspect tests and compatibility to understand whether the entry can actually appear.
Read and test a complete interaction
Use one small feature throughout your investigation. For Give Encouragement, identify the social class, its availability conditions, the receiving Sim, its connection to the social system and its final consequence. This keeps the references meaningful as you move between resources.
First confirm that the interaction is offered on the intended target. Then check a case where its conditions should fail. For a picker, check both confirmation and cancellation. For a queued activity, check completion and cancellation separately; an effect attached to the wrong lifecycle point can occur even when the intended activity was not completed.
If the entry is missing, inspect its connection and tests. If it appears but cannot run, inspect the execution context and constraints. If it runs but affects the wrong Sim or produces no result, follow its participants and result references into Actions, Loot & Outcomes. These are different failures and need different fixes.