Say you create a library named 'foo', The GUI generated consumer code wants to include "libfoo" (actually more like include "Lib0AE17DE9" by complete default).
However I have my code in TriggerLibs/foo.galaxy, and want the GUI to include that.
Any ideas on how to specify the include path? libNtve.SC2Lib doesn't seem to have any tags relating to it, yet it includes a very different path from both it's identifier and the default path the GUI wants to take with mine.
That's all fine, the issue is how to specify the galaxy code file(s) it will include. by default it will generate and include lib<id>.galaxy in the root of the mod/map. And since it doesn't generate any code for me that leaves me without GUI. Which makes the library more or less unconsumable by maps (ofc the script file is still available for inclusion but for consumer maps you'd generally want to use GUI)
Note that the natives are infact called Ntve, yet the included file is "TriggerLibs/NativeLib", so it has to be defined somewhere, just haven't been able to figure out where that is.
I don't think you can specify external galaxy files for inclusion, currently :(
The hack I'm using is to use a placeholder action at the top of my library that uses a custom script action to include all my files. (custom script is something along the lines of:
It also really helps if you save the map as a "SC2Components" (expanded), rather than a standard MPQ-based archived map so that you can edit the files without having to import every other minute.
Say you create a library named 'foo', The GUI generated consumer code wants to include "libfoo" (actually more like include "Lib0AE17DE9" by complete default).
However I have my code in TriggerLibs/foo.galaxy, and want the GUI to include that. Any ideas on how to specify the include path? libNtve.SC2Lib doesn't seem to have any tags relating to it, yet it includes a very different path from both it's identifier and the default path the GUI wants to take with mine.
Since so far this has been Ancient Greek to everyone i'll elaborate.
When you are creating a new library you are actually creating an XML file, with the following definition.
Creating actions, functions etc will simply add elements to this file.
That's all fine, the issue is how to specify the galaxy code file(s) it will include. by default it will generate and include lib<id>.galaxy in the root of the mod/map. And since it doesn't generate any code for me that leaves me without GUI. Which makes the library more or less unconsumable by maps (ofc the script file is still available for inclusion but for consumer maps you'd generally want to use GUI)
Note that the natives are infact called Ntve, yet the included file is "TriggerLibs/NativeLib", so it has to be defined somewhere, just haven't been able to figure out where that is.
Cheers.
@caspersc: Go
I don't think you can specify external galaxy files for inclusion, currently :(
The hack I'm using is to use a placeholder action at the top of my library that uses a custom script action to include all my files. (custom script is something along the lines of:
It also really helps if you save the map as a "SC2Components" (expanded), rather than a standard MPQ-based archived map so that you can edit the files without having to import every other minute.
http://nevir.net/sc2/Scripted_Map_Template.zip