Difference between revisions of "Trigger load"
Outerbeast (talk | contribs) m |
Outerbeast (talk | contribs) m (Added links) |
||
| Line 1: | Line 1: | ||
| − | trigger_load allows to read external map-data into an entity keyvalue from mapname.save in the "maps"-folder, which is stored on the server running the map. Its counterpart is [[trigger_save]]. Supports custom keyvalues. | + | trigger_load allows to read external map-data into an entity keyvalue from mapname.save in the "maps"-folder, which is stored on the server running the map. Its counterpart is [[trigger_save]]. Supports [[Mapping/Custom Keyvalues|custom keyvalues]]. |
== Keyvalues == | == Keyvalues == | ||
Latest revision as of 21:41, 19 March 2023
trigger_load allows to read external map-data into an entity keyvalue from mapname.save in the "maps"-folder, which is stored on the server running the map. Its counterpart is trigger_save. Supports custom keyvalues.
1 Keyvalues
Label to read from : netname
A label under which data is stored.
Destination Entity : target
Entity to write value to.
Destination Keyvalue : message
Name of the keyvalue of the destination entity to write loaded value to.
Trigger after loading : m_iszTrigger
This is triggered after the load-operation, even if nothing was loaded.
2 Notes
If the requested data was not found or no save-file for the map has been created, yet, the target keyvalue won't be touched.
3 Issues
This will only set the keyvalue of the first destination entity found.