I have download some galaxy.scripts but i dont know what to do with them. Is it possible to upload them or convert them as trigger so i can understand them. If its 0% not possible then how can i use that script. How can i applied it to the map? Please help.
I tried this when my map got corrupted and I had to use starbank to get the file back. There is no way to do it as described in my post Here. However, if you import the file, it will run as normal. if you'd like to make it into the GUI triggers, you'll have to do it yourself. Luckily it isn't too hard to understand how to read it. It took me about an hour to interpret my entire map code and recreate it in triggers, but I also know my way around the editor and know which actions do what.
Then right below the event you'll see the actions inside curly brackets, what you see above are the actions for the initial default trigger when you make a new map. You can sort of infer that it means these shown below in GUI triggers
Not really needed to convert to GUI, but there are also these other two sections above which initialize the trigger in the script version.
I hope that helps.
The first part is the event registration, actually.
TriggerAddEventMapInit(trigger t); translates to the Map Initialization event.
What you called the event earlier is just a check if the trigger should be run or just have its conditions evaluated, as in when using the Evaluate Trigger Conditions function.
And if you had conditions for the trigger they would be above that, and local variables above those.
Strictly speaking, the answer is no. The GUI -> Galaxy conversion is one-way. For example, comments will not appear in the Galaxy code and therefore can not be restored. Same goes for presets, macros etc.
However, a majority of the code could in theory be recovered. There is no such tool though, so you are probably better of reading and understanding Galaxy itself.
The approach I would suggest is to use the galaxy script as galaxy script until you actively need to maintain it, in which case you remake that part in triggers.
Galaxy script follows a C like style, especially if auto generated from GUI. Most lines translate directly into a GUI event/condition/action line.
Strictly speaking, the answer is no. The GUI -> Galaxy conversion is one-way. For example, comments will not appear in the Galaxy code and therefore can not be restored. Same goes for presets, macros etc.
However, a majority of the code could in theory be recovered. There is no such tool though, so you are probably better of reading and understanding Galaxy itself. mcdvoice
Your content helped me a lot to take my doubts, thank you very much.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I have download some galaxy.scripts but i dont know what to do with them. Is it possible to upload them or convert them as trigger so i can understand them. If its 0% not possible then how can i use that script. How can i applied it to the map? Please help.
@JEGCPR: Go
I tried this when my map got corrupted and I had to use starbank to get the file back. There is no way to do it as described in my post Here. However, if you import the file, it will run as normal. if you'd like to make it into the GUI triggers, you'll have to do it yourself. Luckily it isn't too hard to understand how to read it. It took me about an hour to interpret my entire map code and recreate it in triggers, but I also know my way around the editor and know which actions do what.
For example:
The Above is where you declare all your triggers. this should be part of the script.
Then if you scroll down you'll see this above snippet, which is the implementation of the trigger. The first part is the event.
Then right below the event you'll see the actions inside curly brackets, what you see above are the actions for the initial default trigger when you make a new map. You can sort of infer that it means these shown below in GUI triggers
This is really the gist of it.
Not really needed to convert to GUI, but there are also these other two sections above which initialize the trigger in the script version.
I hope that helps.
New to the Editor? Need a tutorial? Click Here
Want data assets? Click Here
The first part is the event registration, actually.
TriggerAddEventMapInit(trigger t); translates to the Map Initialization event.
What you called the event earlier is just a check if the trigger should be run or just have its conditions evaluated, as in when using the Evaluate Trigger Conditions function.
And if you had conditions for the trigger they would be above that, and local variables above those.
E.g.
Strictly speaking, the answer is no. The GUI -> Galaxy conversion is one-way. For example, comments will not appear in the Galaxy code and therefore can not be restored. Same goes for presets, macros etc.
However, a majority of the code could in theory be recovered. There is no such tool though, so you are probably better of reading and understanding Galaxy itself.
I have a galaxy script that I need converted to GUI.
Would you be able to convert it for me? I can pay you.
The approach I would suggest is to use the galaxy script as galaxy script until you actively need to maintain it, in which case you remake that part in triggers.
Galaxy script follows a C like style, especially if auto generated from GUI. Most lines translate directly into a GUI event/condition/action line.
Your content helped me a lot to take my doubts, thank you very much.