I have been playing around with tirgger libraries in my mod. You can set Map Initialization events, however it doesn't seem to run unless you link to a trigger in the library from your map.
My Tests:
- Create a library in your mod and a trigger that contains a Map Iitialization event and some Debug Text
- Create another trigger called "Do Nothing" and leave it empty
- Create a new map and add the mod as a dependency
- The trigger library will show the mod triggers
Test 1:
Run the map without any triggers in the map
Result: The Library Trigger does not run
Test 2:
Run the map, adding a trigger that contains an action to run the "Do Nothing" trigger
Result: The Library Trigger runs, displays debug test
Test 3:
Same as Test 2, but disabled the map trigger, or the run trigger action
Result: The Library Trigger runs, displays debug test
So unless my editor is being quirky, it seems that you must link to a trigger in the library, even if it is disabled or does nothing.
Has anyone else found the same results, or know how it is supposed to work?
My guess from reading this is that the editor is a lot less lenient with trigger errors when involving libraries. By that I mean.. if there is an error at all in a library, that entire library stops functioning. The editor seems quirky enough to do something to that level of overkill in my eyes.
Grr just ran into this problem myself. Was trying to make a mod that could simply be included in the map and applied transparently, without the author needing to do anything in particular. Hopefully Blizzard fixes this.
..so I'm not crazy...thank you for figuring this out, I thought I was completely out of luck with using a library of event triggers because they simply never fired.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I have been playing around with tirgger libraries in my mod. You can set Map Initialization events, however it doesn't seem to run unless you link to a trigger in the library from your map.
My Tests: - Create a library in your mod and a trigger that contains a Map Iitialization event and some Debug Text - Create another trigger called "Do Nothing" and leave it empty
- Create a new map and add the mod as a dependency - The trigger library will show the mod triggers
Test 1: Run the map without any triggers in the map Result: The Library Trigger does not run
Test 2: Run the map, adding a trigger that contains an action to run the "Do Nothing" trigger Result: The Library Trigger runs, displays debug test
Test 3: Same as Test 2, but disabled the map trigger, or the run trigger action Result: The Library Trigger runs, displays debug test
So unless my editor is being quirky, it seems that you must link to a trigger in the library, even if it is disabled or does nothing.
Has anyone else found the same results, or know how it is supposed to work?
My guess from reading this is that the editor is a lot less lenient with trigger errors when involving libraries. By that I mean.. if there is an error at all in a library, that entire library stops functioning. The editor seems quirky enough to do something to that level of overkill in my eyes.
Mmm I don't think it's that, I think it just doesn't load the library at all unless is sees that something is using it.
Grr just ran into this problem myself. Was trying to make a mod that could simply be included in the map and applied transparently, without the author needing to do anything in particular. Hopefully Blizzard fixes this.
It's not that big a deal. Just have a trigger in your mod called "Intiialize Mod" or something, then have the map using your mod run this trigger.
Even if the trigger does nothing, it doesn't matter, and chances are you will be supplying some sort of instructions to anyone that will use your mod.
IIRC, adding the triggerlib include in gameplay data solves this.
Hmm so do you add it to Default SC2 Gameplay Settings?
I wonder if something similar will solve the issue of imported mod images not showing up in your map?
..so I'm not crazy...thank you for figuring this out, I thought I was completely out of luck with using a library of event triggers because they simply never fired.