Difference between revisions of "Event Reference"

From Tuxepedia
Jump to navigation Jump to search
(Replaced content with "== Introduction == This page is a reference for all the available actions and conditions available in Tuxemon. You can use this reference to create new map events for your own maps. All action and condition parameters are separated with a comma (<code>,</code>). == Condition Reference == Event Reference Condition == Action Reference == Event Reference Action == Behavior Reference == Event Reference Behavior")
Tag: Replaced
 
(172 intermediate revisions by the same user not shown)
Line 5: Line 5:
== Condition Reference ==
== Condition Reference ==


Here is a list of currently implemented conditions. New event conditions can be created by creating a new page under the '''tuxemon/event/conditions''':
[[Event Reference Condition]]
 
=== battle_is ===
Check to see if the player has fought against NPC and won, lost or draw.
 
'''Parameters'''
* <code>character</code>: Npc slug name (e.g. "npc_maple").
* <code>result</code>: One among "won", "lost" or "draw".
 
'''Examples'''
* <code>is battle_is npc_maple,won</code> 
 
=== button_pressed ===
Check to see if a particular key has been pressed. E.g. <code>K_RETURN</code>.
 
'''Parameters'''
* <code>key</code>: A pygame key constant such as <code>K_RETURN</code>. For a list of all possible keys, refer to the [https://www.pygame.org/docs/ref/key.html Pygame Key Page]
 
'''Examples'''
* <code>is button_pressed K_RETURN</code> 
* <code>is button_pressed K_ESCAPE</code> 
* <code>not button_pressed K_SPACE</code>
 
=== combat_started ===
Check to see if combat has currently started.
 
'''Parameters'''
* <code>None</code>
 
'''Examples'''
* <code>is combat_started</code>
 
=== dialog_open ===
Check to see if a dialog window is currently open.
 
'''Parameters'''
* <code>None</code>
 
'''Examples'''
* <code>is dialog_open</code> 
* <code>not dialog_open</code>
 
=== has_item ===
Check to see if the NPC has an item in his inventory.
 
'''Parameters'''
* <code>character</code>: Either "player" or npc slug name (e.g. "npc_maple").
* <code>item</code>: The item slug name (e.g. "item_cherry").
* <code>operator (optional)</code>: Numeric comparison operator. Accepted values are "less_than", "greater_than", "equals", "less_or_equal" and "greater_or_equal". The default value is "greater_or_equal".
* <code>quantity (optional)</code>: Quantity to compare with. Must be a non-negative integer. The default value is 1.
 
'''Examples'''
* <code>is has_item player,potion</code>
* <code>is has_item player,potion,greater_than,2</code>
 
=== has_monster ===
Checks to see the player has a monster in his party.
 
'''Parameters'''
* <code>monster_slug</code>: The slug of the monster to check for.
 
'''Examples'''
* <code>is has_monster txmn_pigabyte</code>
 
=== has_party_breeder ===
Check to see if the player has a male and female monster in the party (monster not basic, basic is the first step in the evolution stage).
 
'''Examples'''
* <code>is has_party_breeder</code>
 
=== has_tech ===
Check to see if the player has a technique in his party (one of the monsters).
 
'''Parameters'''
* <code>technique</code>: Technique slug name (e.g. "bullet").
 
'''Examples'''
* <code>is has_tech bullet</code>
 
=== money_is ===
Check to see if the player has a certain amount of money (pocket).
 
'''Parameters'''
* <code>slug</code>: Slug name (player).
* <code>operator</code>: One of "==", "!=", ">", ">=", "<" or "<=".
* <code>amount</code>: Amount of money.
 
'''Examples'''
* <code>is money_is player,>=,500</code>
 
=== monster_flair ===
[...]
 
=== monster_property ===
[...]
 
=== music_playing ===
Check to see if the specified music file is currently playing.
 
'''Parameters'''
* <code>music_file</code>: The music file to check.
 
'''Examples'''
* <code>is music_playing 472452_8-Bit-Ambient.ogg</code> 
 
=== npc_at ===
Check to see if the npc is inside the event's area. This event will check the event object's <code>X</code>, <code>Y</code>, <code>Width</code>, and <code>Height</code> properties and checks to see if the npc is within those bounds. That includes event areas that are greater than one tile in size. You can optionally include an <code>x,y</code> parameter to specify a single tile location.
 
'''Parameters'''
* <code>name</code>: The name of the NPC.   
* <code>x</code>: X tile coordinates that the player is at (optional) 
* <code>y</code>: Y tile coordinate that the player is at (optional)
 
'''Examples'''
* <code>is npc_at Maple</code> 
* <code>is npc_at Maple,4,3</code>
 
=== npc_exists ===
Check to see if an NPC exists on the current map with <code>npc_name</code>.
 
'''Parameters'''
* <code>npc_name</code>: The name of the NPC on the current map.
 
'''Examples'''
* <code>not npc_exists Apple</code>
 
=== npc_facing_tile ===
Check to see if the npc is facing a particular tile. This event will check the event object's <code>X</code>, <code>Y</code> coordinates for the tile to check for.
 
'''Parameters'''
* <code>name</code>: The name of the NPC.   
 
'''Examples'''
* <code>is npc_facing_tile Maple</code> 
 
=== npc_facing ===
Check to see if the npc is facing: <code>up</code>, <code>down</code>, <code>left</code> or <code>right</code>.
 
'''Parameters'''
* <code>name</code>: The name of the NPC.   
* <code>direction</code>: Direction to check for: (<code>up</code>, <code>down</code>, <code>left</code>, <code>right</code>)
 
'''Examples'''
* <code>is npc_facing Maple,up</code> 
* <code>not npc_facing Maple,down</code>
 
=== party_size ===
Perform a check on the player's party size. The <code>check</code> parameter can be: <code>equals</code>, <code>less_than</code>, or <code>greater_than</code>.
 
'''Parameters'''
* <code>check</code>: The check to run against the party size. Can be: <code>equals</code>, <code>less_than</code>, or <code>greater_than</code>.
* <code>party_size</code>: The size of the party to check against.
 
'''Examples'''
* <code>is party_size less_than,1</code> 
* <code>not party_size equals,0</code> 
* <code>is party_size greater_than,4</code>
 
=== player_at ===
Check to see if the player is inside the event's area. This event will check the event object's <code>X</code>, <code>Y</code>, <code>Width</code>, and <code>Height</code> properties and checks to see if the player is within those bounds. That includes event areas that are greater than one tile in size. You can optionally include an <code>x,y</code> parameter to specify a single tile location.
 
'''Parameters'''
* <code>x</code>: X tile coordinates that the player is at (optional) 
* <code>y</code>: Y tile coordinate that the player is at (optional)
 
'''Examples'''
* <code>is player_at</code> 
* <code>is player_at 4,3</code>
 
=== player_defeated ===
[...]
 
=== player_facing_npc ===
Check to see if the player is facing an NPC with the name <code>npc_name</code>.
 
'''Parameters'''
* <code>npc_name</code>: The name of the NPC on the current map.
 
'''Examples'''
* <code>is player_facing_npc Apple</code>
 
=== player_facing_tile ===
Check to see if the player is facing a particular tile. This event will check the event object's <code>X</code>, <code>Y</code> coordinates for the tile to check for.
 
'''Parameters'''
* <code>None</code>
 
'''Examples'''
* <code>is player_facing_tile</code> 
 
=== player_facing ===
[...]
 
=== player_moved ===
[...]
 
=== to_talk ===
[...]
 
=== to_use_tile ===
[...]
 
=== true ===
The <code>true</code> condition will always evaluate to *True* (unless the "not" operator is used)
 
'''Parameters'''
* <code>None</code>
 
'''Examples'''
* <code>is true</code> 
* <code>not true</code>
 
=== tuxepedia_is ===
[...]
 
=== variable_is ===
[...]
 
=== variable_set ===
Check to see if <code>variable_name</code> has been set to <code>value</code>.
 
'''Parameters'''
* <code>variable_name:value</code>: A key, value pair of the variable to look up and the expected value.
 
'''Examples'''
* <code>is variable_set battle_won:yes</code> 
* <code>not variable_set current_badges:4</code> 
* <code>is variable_set talked_to_prof:false</code>


== Action Reference ==
== Action Reference ==


Here is a list of currently supported actions. New event actions can be created by creating a new page under the '''tuxemon/event/actions''':
[[Event Reference Action]]
 
=== add_contacts ===
[...]
 
=== add_item ===
Add the specified itemto the player's party.
 
'''Parameters'''
* <code>item_name</code>: The name of the item to add as defined in the monster JSON under <code>resources/db/item</code>. 
 
'''Examples'''
* <code>add_item hatchet</code>
 
=== add_monster ===
Add the specified monster to the player's party.
 
'''Parameters'''
* <code>monster_name</code>: The name of the monster to add as defined in the monster JSON under <code>resources/db/monster</code>. 
* <code>monster_lvl</code>: The level of the monster to start at.
 
'''Examples'''
* <code>add_monster fruitera,10</code>
 
=== battles_print ===
[...]
 
=== breeding ===
[...]
 
=== call_event ===
Executes the actions from another event, ignoring its conditions. This can be especially useful for scenarios where you might need multiple sets of conditions that could be true, such as executing an action when the player is at a certain position OR has a certain item in their inventory.
 
'''Parameters'''
* <code>event_id</code>: The id of the event whose actions should be executed. 
 
'''Examples''' 
* <code>call_event 11</code>   
* <code>call_event 8</code>
 
=== change_state ===
[...]
 
=== clear_kennel ===
[...]
 
=== clear_tuxepedia ===
[...]
 
=== clear_variable ===
[...]
 
=== copy_variable ===
[...]
 
=== create_npc ===
Creates an NPC and places them on the current map.
 
'''Parameters'''
* <code>name</code>: The name of the NPC to create. This NPC should exist in <code>resources/db/npc</code> in JSON format. 
* <code>tile_pos_x</code>: The X-tile coordinate to place the NPC. 
* <code>tile_pos_y</code>: The Y-tile coordinate to place the NPC. 
* <code>animations</code>: The name of the sprite to use for the animations in <code>resources/sprites</code>. 
* <code>behavior</code>: The NPC's movement behavior. Currently not implemented. 
 
'''Examples'''
* <code>create_npc Maple,2,3,maple,wander</code> 
* <code>create_npc Pine,1,6,maple,stand</code>
 
=== delayed_teleport ===
[...]
 
=== dialog_chain ===
Deprecated. Use [#dialog dialog]
 
=== dialog ===
Opens the dialog box with provided text. For line breaks, use the <code>\n</code> character. You may also use special variables in dialog events. If you have multiple dialog commands they will display sequentially. Using <code>$<nowiki>{{</nowiki>end<nowiki>}}</nowiki></code> does nothing as it used to denote the end of a dialog chain. Here is a list of available variables:
   
* <code>$<nowiki>{{</nowiki>name<nowiki>}}</nowiki></code> - The current player's name.
 
'''Parameters'''
* <code>text</code>: The text to display in a dialog window.
 
'''Examples'''
* <code>dialog Red:\n This is some dialog!</code> 
* <code>dialog $<nowiki>{{</nowiki>name<nowiki>}}</nowiki>:\n Hello there! \nHow are you?</code> 
 
=== fadeout_music ===
Fades out music over <code>x</code> milliseconds.
 
'''Parameters'''
* <code>time_seconds</code>: Time in milliseconds to fade out the currently playing music.
 
'''Examples'''
* <code>fadeout_music 2</code>
 
=== get_player_monster ===
[...]
 
=== kennel_print ===
[...]
 
=== lock_controls ===
[...]
 
=== modify_npc_attribute ===
[...]
 
=== modify_player_attribute ===
[...]
 
=== money_print ===
[...]
 
=== npc_face ===
Makes the npc face a particular direction. Parameter can be set to: <code>left</code>, <code>right</code>, <code>up</code>, or <code>down</code>.
 
'''Parameters'''
* <code>name</code>: The name of the npc.   
* <code>direction</code>: Direction to make the player face. Can be set to: <code>left</code>, <code>right</code>, <code>up</code>, or <code>down</code>.
 
'''Examples'''
* <code>npc_face Maple,left</code> 
* <code>npc_face Pine,up</code>
 
=== npc_move ===
Determines the NPC's movement behaviour.
 
'''Examples'''
* <code>npc_move spyder_homemakerpapertown, down 1, right 1, up 1, left 1</code> 
 
=== npc_run ===
Sets the NPC's speed to the universal run speed. 
 
'''Examples'''
* <code>npc_run npc_mom</code>
 
=== npc_speed ===
Sets the NPC's walk speed.
 
'''Examples'''
* <code>npc_speed npc_mom, 0.2</code>
 
=== npc_walk ===
Sets the NPC's speed to the universal walk speed. 
 
'''Examples'''
* <code>npc_walk npc_mom</code>
 
=== npc_wander ===
Sets the NPC's behaviour to wander about instead of stand in place.
 
'''Examples'''
* <code>npc_wander npc_mom</code>
 
=== open_shop ===
[...]
 
=== pathfind ===
Moves an NPC to a certain tile on the map.
 
'''Parameters'''
* <code>name</code>: The name of the NPC to be moved.
* <code>tile_pos_x</code>: The X-tile coordinate to have the NPC to walk to. 
* <code>tile_pos_y</code>: The Y-tile coordinate to have the NPC to walk to.   
 
'''Examples'''
* <code>pathfind Maple,2,3</code>
* <code>pathfind Pine,1,6</code>
 
=== pause_music ===
Pauses the currently playing music.
 
'''Parameters'''
* <code>None</code>
 
'''Examples'''
* <code>pause_music</code>
 
=== play_map_animation ===
Plays an animation on the map. The <code>position</code> parameter can also be <code>player</code> if you want to draw the animation at the player's location. Loop can be either <code>loop</code> or <code>noloop</code>.
 
'''Parameters'''
* <code>animation_name</code>: The name of the animation to play under <code>resources/animations/tileset</code>. 
* <code>duration</code>: The amount of time in seconds between each frame. 
* <code>loop</code>: Whether or not to loop the animation. Can be either <code>loop</code> or <code>noloop</code> to loop the animation. 
* <code>position</code>: The position to draw the animation. Can either be an <code>x,y</code> coordinate or <code>player</code> to draw the animation over the player.
 
'''Examples'''
* <code>play_map_animation grass,0.1,noloop,player</code> 
* <code>play_map_animation sign01,0.4,loop,33,10</code>
 
=== play_music ===
Plays an audio file located under "music/" on a loop.
 
'''Parameters'''
* <code>filename</code>: The name of the music file to play under "music/" 
 
'''Examples'''
* <code>play_music 472452_8-Bit-Ambient.ogg</code>
 
=== play_sound ===
Plays an audio file located under "sounds/".
 
'''Parameters'''
* <code>filename</code>: The name of the sound file to play under "sounds/" 
 
'''Examples'''
* <code>play_sound combat/falling_Macro.ogg</code> 
 
=== player_face ===
Makes the player face a particular direction. Parameter can be set to: <code>left</code>, <code>right</code>, <code>up</code>, or <code>down</code>.
 
'''Parameters'''
* <code>direction</code>: Direction to make the player face. Can be set to: <code>left</code>, <code>right</code>, <code>up</code>, or <code>down</code>.
 
'''Examples'''
* <code>player_face left</code> 
* <code>player_face up</code>
 
=== player_resume ===
Does not currently have a purpose.
 
'''Parameters'''
* <code>None</code> 
 
'''Examples'''
* <code>player_resume</code> 
 
=== player_stop ===
Stops the player's current movement.
 
There is currently no way to stop a player from inputting another movement after being stopped ([https://github.com/Tuxemon/Tuxemon/issues/790 issue #790])
 
'''Parameters'''
* <code>None</code> 
 
'''Examples'''
* <code>player_stop</code> 
 
=== print ===
[...]
 
=== quit ===
[...]
 
=== random_encounter ===
Randomly start a battle based on the encounter group looked up via the <code>encounter_id</code>. Encounter groups contain a list of monsters that can be encountered as well as their level and encounter rate. In most circumstances you will pair this action with the <code>player_at</code> and <code>player_moved</code> conditions.
 
Here is an example encounter file:
 
''resources/db/encounter/1.json'' 
 
    json
    {
    "id": 1,
    "monsters": [
        {
            "monster_slug": "bigfin",
            "encounter_rate": 10,
            "level_range": [
                1,
                6
            ]
        },
        {
            "monster_slug": "dandylion",
            "encounter_rate": 10,
            "level_range": [
                1,
                6
            ]
        },
        {
            "monster_slug": "tux",
            "encounter_rate": 10,
            "level_range": [
                1,
                6
            ]
        }
    ]
    }
 
'''Parameters'''
* <code>encounter_id</code>: The id of the encounter JSON file to use for random battles under <code>resources/db/encounter</code>.
* <code>total_prob</code>: The probability of an encounter, with 100 = 100% probability of an encounter. If not set, then the probability of an encounter is the sum of all encounter_rates in the encounter JSON file (as a percentage).
 
'''Examples'''
* <code>random_encounter route1</code>
* <code>random_encounter route1,20</code>
 
=== random_integer ===
[...]
 
=== random_monster ===
[...]
 
=== remove_contacts ===
[...]
 
=== remove_monster ===
Removes the specified monster from the player's party.
 
'''Parameters'''
* <code>monster_slug</code>: The slug of the monster to remove as defined in the monster JSON under <code>resources/db/monster</code>. 
 
'''Examples'''
* <code>remove_monster fruitera</code>
 
=== remove_npc ===
Removes an NPC from the current map.
 
'''Parameters'''
* <code>name</code>: The name of the NPC to remove. 
 
'''Examples'''
* <code>remove_npc Maple</code> 
* <code>remove_npc Pine</code>
 
=== rename_monster ===
[...]
 
=== rename_player ===
[...]
 
=== rumble ===
[...]
 
=== screen_transition ===
Fades the screen to black and back over <code>x</code> seconds.
 
'''Parameters'''
* <code>transition_time</code>: Time in seconds to fade the screen to black.
 
'''Examples'''
* <code>screen_transition 2</code>
 
=== set_battle ===
[...]
 
=== set_code ===
[...]
 
=== set_economy ===
[...]
 
=== set_inventory ===
Overwrites the inventory of the npc or player.
 
'''Parameters'''
* <code>npc_slug</code>: The slug of the player or NPC.
* <code>inventory_slug</code>: The slug of the inventory that will overwrite the NPC's existing inventory.
 
'''Examples'''
* <code>set_inventory shopkeeper,new_stock</code>
 
=== set_kennel_visible ===
[...]
 
=== set_kennel ===
[...]
 
=== set_money ===
[...]
 
=== set_monster_flair ===
[...]
 
=== set_monster_health ===
Changes the hp of a monster in the current player's party. The action parameters may contain a monster slot and the amount of health.
 
'''Parameters'''
* <code>slot</code>: The slot the monster appears in. If no slot is specified, all monsters are healed.
* <code>health</code>: A float value between 0 and 1, which is the percent of max hp to be restored to. If no health is specified, the hp is maxed out.
 
'''Examples'''
* <code>set_monster_health 1,1</code>
=== set_monster_level ===
Changes the level of a monster in the current player's party.
 
'''Parameters'''
* <code>slot</code>: The slot the monster appears in. If no slot is specified, all monsters are leveled.
* <code>level</code>: The amount by which to level. If no level is specified, the level is reverted to 1.
 
'''Examples'''
* <code>set_monster_level 1,100</code>
 
=== set_monster_level ===
[...]
 
=== set_monster_status ===
[...]
 
=== set_npc_attribute ===
[...]
 
=== set_player_attribute ===
[...]
 
=== set_tuxepedia ===
[...]
 
=== set_variable ===
Sets an arbitrary variable to a particular value. This action is good for seeing if battles with NPCs have been fought or not. These variables are also saved when the player saves the game.
 
Also used to set the [[:Category:Environment|environment]].
 
'''Parameters'''
* <code>variable_name:value</code>: A key, value pair of the <code>variable_name</code> to set with <code>value</code>. 
 
'''Examples'''
* <code>set_variable battle_won:yes</code> 
* <code>set_variable talked_to_prof:true</code>
* <code>set_variable environment:grass</code>
 
=== spawn_monster ===
[...]
 
=== start_battle ===
Start a battle with an NPC defined in <code>resources/db/npc</code>.
 
Here is an example NPC file:
 
''resources/db/npc/maple.json'' 
 
    json
    {
    "monsters": [
        {
            "attack": 50,
            "defense": 7,
            "name": "Snowball",
            "special_attack": 9,
            "level": 5,
            "monster_slug": 1,
            "hp": 50,
            "speed": 7,
            "special_defense": 7,
            "exp_give_mod": 3,
            "exp_req_mod": 27
        }
    ],
    "id": 1,
    "name": "Maple"
    }
 
'''Parameters'''
* <code>npc_slug</code>: The NPC's slug as defined in the NPC's JSON file in <code>resources/db/npc</code>.
 
'''Examples'''
* <code>start_battle npc_maple</code>
 
=== start_cinema_mode ===
[...]
 
=== stop_cinema_mode ===
[...]
 
=== store_monster ===
[...]
 
=== teleport_faint ===
[...]
 
=== teleport ===
Teleports the player to a given position on a map. This teleport is immediate and does not have any transition animation.
 
'''Parameters'''
* <code>map_name</code>: The map file to teleport the player to. 
* <code>x</code>: The X-tile coordinate to teleport the player to. 
* <code>y</code>: The Y-tile coordinate to teleport the player to.
 
'''Examples'''
* <code>teleport map1.tmx,3,4</code> 
* <code>teleport room1.tmx,8,1</code>
 
=== transfer_money ===
[...]
 
=== transition_teleport ===
Teleports the player to a given position on a map with a screen transition over <code>x</code> seconds.
 
'''Parameters'''
* <code>map_name</code>: The map file to teleport the player to. 
* <code>x</code>: The X-tile coordinate to teleport the player to. 
* <code>y</code>: The Y-tile coordinate to teleport the player to. 
* <code>transition_time</code>: The time in seconds the transition will last.
 
'''Examples'''
* <code>teleport map2.tmx,1,6,1.5</code> 
* <code>teleport room1.tmx,8,1,4</code>
 
=== translated_dialog_chain ===
Deprecated. Use [#translated_dialog translated_dialog]
 
=== translated_dialog_choice ===
Asks the player to select a choice. The translations for the text are looked up based on a given key.
 
'''Parameters'''
* <code>choice_keys</code>: Keys to reference translated text choices separated by colons.
* <code>variable</code>: The variable to store the answer which will be the key for the translated text.
 
'''Examples'''
* <code>translated_dialog_choice yes:no,myvariable</code>
 
=== translated_dialog ===
Opens the dialog box with translated text for a given key found in <code>resources/db/locale/<locale>.json</code>. Optional variable replacement will also be translated if the value is a key in the locale file. For line breaks, use the <code>\n</code> character. If you have multiple translated_dialog commands they will display sequentially. Using <code>$<nowiki>{{</nowiki>end<nowiki>}}</nowiki></code> does nothing as it used to denote the end of a dialog chain. You may also use special variables in dialog events. Here is a list of available variables:
   
* <code>$<nowiki>{{</nowiki>name<nowiki>}}</nowiki></code> - The current player's name.
 
'''Parameters'''
* <code>dialog_key</code>: The translated text for a given key found in <code>resources/db/locale/<locale>.json</code> to display in a dialog window.   
* <code>parameters</code>: Optional comma-separated <code>var=value</code> parameters to replace variables in the translation text. The <code>value</code> can either be text or a key found in <code>resources/db/locale/<locale>.json</code>.
 
'''Examples'''
* <code>translated_dialog received_x,name=a brand new car!</code> 
* <code>translated_dialog received_x,name=item_potion</code> 
* <code>translated_dialog combat_fainted,name=$<nowiki>{{</nowiki>name<nowiki>}}</nowiki></code> 
* <code>translated_dialog combat_opponent_call_tuxemon,user=$<nowiki>{{</nowiki>name<nowiki>}}</nowiki>,name=some guy</code> 
 
=== tuxepedia_print ===
[...]
 
=== unlock_controls ===
[...]
 
=== variable_math ===
Performs a mathematical operation on the key in the player.game_variables dictionary.
 
'''Parameters'''
* <code>variable_name</code>
* <code>operation</code>: +, -, * or /
* <code>value</code>
 
'''Examples'''
* <code>variable_math badge_count,+,1</code>
 
=== wait ===
Pauses execution of all events for the given amount of time in seconds.
 
'''Parameters'''
* <code>seconds</code>: The amount of time in seconds to wait for. 


'''Examples'''
== Behavior Reference ==
* <code>wait 2.0</code> 
* <code>wait 5.2</code>


=== withdraw_monster ===
[[Event Reference Behavior]]
[...]

Latest revision as of 15:23, 2 February 2026

Introduction[edit | edit source]

This page is a reference for all the available actions and conditions available in Tuxemon. You can use this reference to create new map events for your own maps. All action and condition parameters are separated with a comma (,).

Condition Reference[edit | edit source]

Event Reference Condition

Action Reference[edit | edit source]

Event Reference Action

Behavior Reference[edit | edit source]

Event Reference Behavior

Retrieved from "https://wiki.tuxemon.org/index.php?title=Event_Reference&oldid=37487"