- Joined
- Feb 2, 2006
- Messages
- 1,609
If you want to provide a JASS API for GUI trigger users, you need to modify the files "UI/TriggerData.txt" and "UI/TriggerStrings.txt".
Once modified it can be hard to find your own additions. Besides that, you will get a problem when you want to provide multiple JASS APIs from different projects as GUI trigger actions, calls, events etc.
Therefore I've added the option "--merge" to my tool "wc3converter" in the wc3lib.
Merges the files to one (multiple files can be appended, the last file has the highest priority).
The new file can be placed as "UI/TriggerData.txt" in a custom MPQ archive.
The same works with trigger strings:
It helps you to keep your own files clean and to keep the original files as well.
Here you can see an example usage for my modification:
dmdf/src/TriggerData at master · tdauth/dmdf · GitHub
Once modified it can be hard to find your own additions. Besides that, you will get a problem when you want to provide multiple JASS APIs from different projects as GUI trigger actions, calls, events etc.
Therefore I've added the option "--merge" to my tool "wc3converter" in the wc3lib.
Code:
wc3converter --merge --overwrite NewTriggerData.txt UI/TriggerData.txt MyOwnTriggerData.txtMerges the files to one (multiple files can be appended, the last file has the highest priority).
The new file can be placed as "UI/TriggerData.txt" in a custom MPQ archive.
The same works with trigger strings:
Code:
wc3converter --merge --overwrite NewTriggerStrings.txt UI/TriggerStrings.txt MyOwnTriggerStrings.txtIt helps you to keep your own files clean and to keep the original files as well.
Here you can see an example usage for my modification:
dmdf/src/TriggerData at master · tdauth/dmdf · GitHub
