signal (trigger)
- 4A Games
Overview
The trigger receives transmitted signals from another script or from the same script. Also, this block allows you to inform that one part of the script is complete and now it can run a new piece. For example, the player says goodbye to the NPC and receives a task from it. At the end of the conversation, you send a signal (for example, player_ready_for_task_2). In another script, it is kind of a trigger called start_game which will start new events. Thus, the trigger allows you to link multiple scripts.
Inputs
| activate | Allows the trigger to catch signals. |
| deactivate | Trigger stops catching signals. |
| payload | The entity on the caller side that was attached to the Payload pin. |
Outputs
| Event | Triggers on receiving the corresponding signal. |
Refs
- N\A
Properties
| Active? | Initial state of the trigger. If active, it can receive signals. Otherwise, it can't receive signals. |
| Signal | In this field, you write or paste the name for the transmitted signal via the action signal. |
Usage examples
Shortcuts
| Shift+S |
|---|
See also
Exodus SDK © 2005-2023, 4A Games Limited. Developed by 4A Games®.
4A Games® is a registered trademark, and 4A Games Limited, Exodus SDK and their respective logos are trademarks of 4A Games Limited.
Published by Deep Silver. Deep Silver is a division of PLAION GmbH, Austria. Deep Silver and Plaion are registered trademarks of PLAION GmbH.
Metro Exodus is inspired by the internationally best-selling novels METRO 2033 and METRO 2034 by Dmitry Glukhovsky.
All other trademarks, logos and copyrights are property of their respective owners. All rights reserved.
By using this site, downloading or using the Exodus SDK or related content, you are agreeing to be bound by the terms of the End User License Agreement.