You can do it also using object editor - mess around with the Carrier-launch abilties. Careful you don't spawn units which spawn themselves, as that can lag the game rather quickly.
EDIT1: Don't know why I had "only" instead of "also".
Has anyone found how to get map sizes past 256x256? I've looked through the patch-editor files and only found 1 thing worth while ; default map size. Setting this to 480x480 however crashed the editor on startup.
Are there any limits to sc2 nav meshing? Instead of going for a bigger map, could I just make units smaller (and thus, their pathing)?
If that's the Student Learning Edition than I wouldn't bother with it outside of education - the watermarks and annoying lack of features will slow you down, and teach you bad habits. If you can't afford/get industry-standard modeling tools, than go with the free ones. They'll have most of the tools you need for making sc2 models anyway (excluding possible import/export of .m3)
"There's no way to prove what version of the software we're using anyway."
Doesn't mean you should abuse it.
0
The easiest way is to..
GLOBAL boolean b = false
conditions: if b == true than don't run this trigger
set b = true kill unit u set b = false
Untested but this worked in wc3.
0
You can do it also using object editor - mess around with the Carrier-launch abilties. Careful you don't spawn units which spawn themselves, as that can lag the game rather quickly.
EDIT1: Don't know why I had "only" instead of "also".
0
Beump
0
Has anyone found how to get map sizes past 256x256? I've looked through the patch-editor files and only found 1 thing worth while ; default map size. Setting this to 480x480 however crashed the editor on startup.
Are there any limits to sc2 nav meshing? Instead of going for a bigger map, could I just make units smaller (and thus, their pathing)?
0
If that's the Student Learning Edition than I wouldn't bother with it outside of education - the watermarks and annoying lack of features will slow you down, and teach you bad habits. If you can't afford/get industry-standard modeling tools, than go with the free ones. They'll have most of the tools you need for making sc2 models anyway (excluding possible import/export of .m3)
"There's no way to prove what version of the software we're using anyway." Doesn't mean you should abuse it.
0
First code in GUI sc2 - be easy.
This is a simple flight simulator with easy to edit values.
-Uses arrow-keys for banking and tilting, while shift+ctrl control the engine.
-Unit does not rotate on the X and Y plane - possible with actors?
-I could not find out how to get a terrain's proper Z. "Get terrain Z" would return 0 regardless of the height. Maybe it's for cliffs..
-Explodes if you touch the ground
-Smooth camera and controls (you can hold a key down, rather than press it repeatedly)