Emote Definition

HomeModdingReferenceSBCEmote Def

Overview

Inherits

• DefinitionBase

Requires an xsi:type attribute:

<Definition xsi:type="MyObjectBuilder_EmoteDefinition">

Defines a character emote that can be added to toolbars or triggered by chat commands.

These are found at the bottom of Emotes.sbc, because at the top they're defining hidden Animation Definition that are required by those emotes.

Animation controller info

 ↑   🔗 

It will first trigger emote event, followed by the subtypeId of the Animation Definition that is given by this.

Elements

 ↑   🔗 

ChatCommand <ChatCommand>	Type: String	Default: null
Optional. Defines the chat command to trigger this emote.
ChatCommandDescription <ChatCommandDescription>	Type: String	Default: null
Optional. Short help text for the chat command shown in the F1 help menu but only if <ChatCommandName> is also defined. Can be plain-text or a localization key (from .resx files), and because of that it will also scan for text variables to replace.
ChatCommandName <ChatCommandName>	Type: String	Default: null
Optional. Full help text for the chat command shown only for /help followed by the <ChatCommand>. Can be plain-text or a localization key (from .resx files), and because of that it will also scan for text variables to replace. If this is defined, the chat command will show up in the F1 help menu, however it will not be printed there, it will instead print <ChatCommandDescription>.
Priority <Priority>	Type: Int32	Default: 0
The emotes (this) and emotes directly from animations are placed in the same list then the list is sorted Priority in ascending order. What that list's order is used for is unclear, might be the order they appear in the gamepad HUD.
AnimationId <AnimationId>	Type: SerializableDefinitionId	Default: (empty)
The Id of an Animation Definition, meaning Type has to be AnimationDefinition. Example: <AnimationId Type="AnimationDefinition" Subtype="Angry" /> Note: This might not work if <Animations> is used unless it points to itself, test to confirm both.
Override <Override>	Type: AnimOverrideDef[]	Default: null
Optional. Overrides the <AnimationId> for a specific character <Id> (not <Name> this time). Can be defined multiple times to support multiple characters. Note: This might not work if <Animations> is used, test to confirm. Contains more elements: CharacterId <CharacterId> Type: SerializableDefinitionId Default: (invalid) The Id of a Character Definition, meaning Type has to be Character. Examples below. AnimationId <AnimationId> Type: SerializableDefinitionId Default: (invalid) The Id of an Animation Definition, meaning Type has to be AnimationDefinition. Examples below. Example: <Override> <CharacterId Type="Character" Subtype="Default_Astronaut_Female"/> <AnimationId Type="AnimationDefinition" Subtype="Angry_Female" /> </Override> <!-- ... -->
Animations <Animations>	Type: Animation[]	Default: null
Optional. List of other emote definitions to trigger based on random chance. Note: If this is defined with at least 1 entry, the root-level <AnimationId> and <Override> might not function. Each <Animation> can contain: Probability <Probability> Type: Single Default: 0 The weight for the <AnimationId> to be picked. If the numbers of all <Animations> don't add up to 1.0, they will each be divided by the total. AnimationId <AnimationId> Type: SerializableDefinitionId Default: (invalid) Id of another emote definition, meaning Type has to be EmoteDefinition. Example: <AnimationId Type="EmoteDefinition" Subtype="EmoteRPS_Paper" /> Example: <Animations> <Animation> <Probability>0.33333</Probability> <AnimationId Type="EmoteDefinition" Subtype="EmoteRPS_Paper"/> </Animation> <!-- ... --> </Animations>

(Top) | From DefinitionBase:

Common

 ↑   🔗 

Id <Id>	Type: SerializableDefinitionId	Default: (invalid)
The type and subtype combined make up a unique identifier for this definition. If two definitions use the same Type+Subtype (Subtypes are only unique per Type), then the last to load will override the first one(s). For more details see Things to know about SBC. TypeId <TypeId> Type: string Default: (invalid) Must be an existing type with or without the "MyObjectBuilder_" prefix. Some types require an xsi:type, refer to the vanilla files for the exact pairing. TypeId vs xsi:type SubtypeId <SubtypeId> Type: string Default: (empty) This can be invented and only needs to be unique per TypeId. Vanilla game re-uses some subtypes over multiple types (e.g. Iron is used for Ore type and Ingot type). An empty value is also a valid subtype (which vanilla also uses on at least 5 blocks). Type Type (attribute) Type: string Default: (invalid) Same behavior as <TypeId>, do not define both. Subtype Subtype (attribute) Type: string Default: (empty) Same behavior as <SubtypeId>, do not define both. Example: <Id> <TypeId>CubeBlock</TypeId> <SubtypeId>FancyTable</SubtypeId> </Id> Because it has attribute alternatives it can also be declared as: <Id Type="CubeBlock" Subtype="FancyTable" />
DisplayName <DisplayName>	Type: String	Default: null
If the object defined here is visible anywhere in the game GUI, this would be the name shown for it. In cases where it is used, it is very much required. Can be plain-text. If the text contains DisplayName_ then: A localization key (from .resx files) will be searched for. It will scan for text variables to replace.
Description <Description>	Type: String	Default: null
Optional. If the object defined here is shown with a description in the game GUI (Hotbar/G-menu, HUD, etc) then this is the place to write it. Can be plain-text. If the text contains Description_ then: A localization key (from .resx files) will be searched for. It will scan for text variables to replace. If the final text (plain, localized or variable-replaced) contains {0}, {1}, etc, then they will replaced by kb&m control binds defined in <DescriptionArgs>.
DescriptionArgs <DescriptionArgs>	Type: String	Default: null
Optional. A comma-separated list of control IDs which are referenced in <Description> by {number} tags, which then get replaced by the keyboard or mouse bind that the viewer has for those controls. Example: <Description>Press {0} to fire, {1} to change color, {2} to interact.</description> <DescriptionArgs>PRIMARY_TOOL_ACTION,CUBE_COLOR_CHANGE,USE</DescriptionArgs> And each player will see their current binds for those actions. The control IDs can be found in your %appdata%/SpaceEngineers/SpaceEngineers.cfg at the ControlsButtons section.
Icon <Icon>	Type: String[]	Default: null
Icon(s) for the definition which may or may not be used depending on the definition type. Path to a .dds or .png file relative to current mod's folder. Falls back to game folder if not found in current mod. Referencing assets in other mods Can be declared multiple times which will stack icons on top of eachother, however it will not work for all definitions. Known definitions to work or not work with multiple icons Working: Blocks, BlockVariantGroups and component items seen in G-menu, BlockInfo (HUD right side) and toolbars; Blueprints in terminal production tab; Blocks and PhysicalItems in gamepad HUD. Partial: Blocks seen in terminal. Not working: HandItems (uses PhysicalItem's icon instead); Blocks and BlockVariantGroups seen in build planner, radial menu and some economy GUIs; PhysicalItems in economy GUIs and stores; Prefabs in stores; BlueprintClass (tabs) in terminal production tab; BankingSystemDefinition (Game\BankingSystem.sbc); Emotes (both kinds of definitions) in gamepad HUD; Block skins; RespawnShips. Special cases: Economy contracts, FactionIcons Definition.
DLC <DLC>	Type: String[]	Default: null
Optional. The DLC subtypeId that this definition will require. For the IDs, refer to <SE>\Content\Data\Game\DLCs.sbc. Can be declared multiple times to require multiple DLCs. Most definition types won't check for this, the ones that do: blocks, emotes and possibly anything else that can be placed in the toolbar.
AvailableInSurvival <AvailableInSurvival>	Type: Boolean	Default: true
Depends on the definition if it uses this, and if it does then this determines whether it can be accessible in survival game mode. Currently known definitions that do use this: Blocks, BlockVariantGroups, BlockCategories and any definition that can show up in a toolbar. EntityStatComponent Definition and EntityStat Definition.
Public <Public>	Type: Boolean	Default: true
If the definition is visible or accessible in some cases. For blocks, this only hides them and they can still be built using projectors and other means.
Enabled Enabled (attribute)	Type: Boolean	Default: true
If set to false it will remove the definition after it's been loaded. Example usage: <Definition Enabled="false"> The "Definition" above is the opening element that for the entire definition, not an inner node like <DisplayName> is. The opening node can have a different name for other definitions, some examples <Component>, <Blueprint>, etc.
xsi:type xsi:type (attribute)	Type: string	Default: null
Name of an object that this definition will be deserialized as. Sometimes required, depends on the definition. The wiki page for any given definition will mention at the top what xsi:type it requires, if any. The game's sbc files are also a reference on what xsi:types are required for a given definition. This attribute is available on all elements and comes from the XML specification. This game relies on this attribute to change which sub-definition object is used to deserialize that element's contents. It's what allows, for example, a thruster to have unique elements (such as <MinPlanetaryInfluence>) that no other block definitions have. For more details on how this relates to the TypeId, and usage examples, see: Things to know about SBC - TypeId vs xsi:type.

---