Scripting and SC2...

According to the BlizzChat Dev. Chat on Twitter:

It is stupid currently to upload custom scripts using the import manager each time in my opinion. Does this bother anyone else or am I just lazy?

I actually kind of like the idea of file oriented libraries.

I think that answer is a very short-sighted one. Especially when youre talking about a feature lost from the WE.

I must be missing something, because this seems completely intolerable.

Yes, i don't see why allowing to convert a trigger in plain galaxy would a lame suggestion.
Have to import a library each time you edit it is totally crazy.

This editor is powerfull (data editor) but it's really a pain in the ass if you don't wan't to use GUI but only galaxy.

I'm fine with the idea of fire-oriented libraries, but the fact is that it is a complete pain to get custom scripts into SC2 maps compared to WC3 and makes development of scripts hard because everytime you want to test a script, you have to reupload it rather than it being in the editor and already in your map.

It's a sad day.

Seems I shall be importing my scripts.

Bleh. Honestly, there is no reason to use galaxy now.

* It is going to be awful hard to use it in the editor.
* The language itself is horrible.
* Most the issues that made wc3's GUI suck so much are gone.
* The object editor is so flexible you won't need to code spells 99% of the time.

But still, you can't write GUI, just click, click and click.
It's a pretty major issue for me.
Plus spells are not all.

Meh, i guess i will do it in the hard way ...

And there are more to code than spells... which must be coded in a badly supported .galaxy or GUI...

SC2 GUI is much easier than wc3's though, thanks to the tree view of each action/condition etc , it requires less clicks.

As annoying as the clicks are, they are less annoying than all the stunts you'll need for galaxy.

GUI actually has as many features as galaxy anyway. You can basically write the other stuff in GUI. it sucks, but blizzard is not giving us a real alternative.

The object editor is impressive; while it reduces the code we would otherwise need for spells, there is more to scripting than just spells.

GUI is a pain in the ass to navigate and I am unable to script effectively with it. It supports all of the same features as galaxy, granted, nut that is hardly the issue. I'd sooner jump through hoops to implement a written script than waste time navigating submenus.

Vex has a good point, though. If you think of a typical WC3 map (an AoS or a TD or pretty much any other map) and remove all the custom spells from it, what remains can pretty much be easily done in GUI without much consequence. Even if it leaks like crazy, an AoS or TD creep spawning system isn't much of a problem since it only gets to spawn a few hundred units each game.

So, now that the data editor allows us to make most spells without trigger support, we can easily use GUI for the few things that are left. It may not be your preferred tool, but at least it is an adequate tool.

Of course, if you want to make an entirely scripted map, like a 3rd person shooter, then the lack of pure Galaxy support is an issue. Still, with some effort it should be possible to establish a decent development environment where you can somehow automate the import process so your map has the latest version of the libraries every time.

Pure galaxy support:

- Make trigger.
- Custom script.
- Top of custom script: 'return true; }'
- Bottom of custom script: 'bool BlizzSucks() {'
- Your Galaxy code in the middle.

Lame but works.

remember their Nova game from that editor trailer?