Yeah, this file was mostly stripped from newlines.. and whitespaces in general. I don't know why he did that.
Anyway, I guess you don't really need to modify it, since you can just re-link the dependency that's still up on bnet, right? If no, I could fix the file for you (in the past I wrote some scripts for cases like this).
// Custom Script: Custom Script //-------------------------------------------------------------------------------------------------- include "TriggerLibs/GAx3"
There's another Galaxy file, where all the functions are actually declared.
It's because author coded it all by hand, and in Triggers there are just metadata definitions of these functions - pretty much like you've said. So they can be accessed from the GUI. But actual function declarations are in this custom file.
Triggers file defines all the elements which are present in Triggers component of the Editor, and as such it is file exclusive to the editor, it is ignored by the game if present - the process of generating Galaxy code is done by editor.
What you probably did, thus I'm kind of confused why you're saying it has no *.galaxy file included. Perhaps you were looking in root directory for MapScript.galaxy? In case of libraries the file is put into Base.SC2Data subdirectory, i.e. Base.SC2Data/LibGAx3.galaxy.
Keep in mind that the version of GAx3 linked above is very old and likely not up to date.
But most importantly, GAx3 is still up on Battle.net:
There are some copies, but always look for the one from the author itself - Renee.
It was even updated this month, what indicates any bugs introduced by recent SC2 patches were addressed.
You probably just need to link it again into your map.
Yeah, this file was mostly stripped from newlines.. and whitespaces in general. I don't know why he did that.
Anyway, I guess you don't really need to modify it, since you can just re-link the dependency that's still up on bnet, right? If no, I could fix the file for you (in the past I wrote some scripts for cases like this).
btw. If you wanna work with Galaxy code I recommend this : https://marketplace.visualstudio.com/items?itemName=talv.sc2galaxy :p
Although the feature which you would need right new - that is pretty print/format code is not yet finished.
Previously known as: SomeoneTookMyNameTT
Yep, you did miss an include statement:
// Custom Script: Custom Script
//--------------------------------------------------------------------------------------------------
include "TriggerLibs/GAx3"
There's another Galaxy file, where all the functions are actually declared.
It's because author coded it all by hand, and in Triggers there are just metadata definitions of these functions - pretty much like you've said. So they can be accessed from the GUI. But actual function declarations are in this custom file.
Previously known as: SomeoneTookMyNameTT
Previously known as: SomeoneTookMyNameTT