Staredit Network

Would it be possible to add mathimatical calculations into starforge?

Example:

COND
- Always
ACTIONS
- Order all units owned by player 'idiot' to move to location ('move here' + 20)

It'd be SOOOO cool if we could!

And this would...? I really don't get what you is trying to say?

If you want to do mathematical operations in Starcraft, I am currently working on them.

Uhh, no real point yoshi, unless it was like

Order 1+(Number of Deaths of Unit) units to attack to location

It would be nice to center a location + (5,0), where 5 is the amount of tiles to the right 0 is the amount up.

And this is written into the CHK how? Starcraft doesn't really have the capacity without complicated systems.

Guys... He's yanking your respective chains...

The original plan for SF's trigger editor included variables and things like this:



And other things of the sort.

After I saw he made this posts months ago at Team SE forums, I gathered that... after I made my post.

for people who don't get it, its the exact same post I made on TSE 1 year ago

http://216.239.63.104/search?q=cache:X3o5r...t+RexyRex&hl=en

But my question is serious, I was wondering if heimdal was still planning on doing it.

Here's a nice little p->q for ya...

If there will be a new version of Starforge, then I am planning on adding advanced trigger features.

w00t! Sounds good to me

How about that "Starforge X" you were saying something about on BF?

this sounds alot like thw wc3 editor. in there you can use all sorts of varibles and stuff. for heavons sake, you dont even need locations (they call em regions) all ya need is the X and Y positions to create the units. but everywhere you look in the wc3 editor there is a variable there. ANYWHERE! its crazy...

and ya, how would you write this into the scx file? and how would sc reconise it with some sort of mod?

edit- oo and also, the thing i love about the wc3 editor is the, (Create unit at random point in region ___________)

It would have to be implemented through the use of multiple triggers, of which all but one get hidden to the user.

So you wold make Starforge interface with the actual triggers; when you type an "advanced" trigger it converts it for you? You still have to come up with a system or triggers I think.

For example:

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, #x[2-10:2, 13], Marine, Somewhere);

Actions:

¤ CreateUnit(#(x + 5), Firebat, SomewhereElse, CurrentPlayer);

Would map to:

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 2, Marine, Somewhere);

Actions:

¤ CreateUnit(7, Firebat, SomewhereElse, CurrentPlayer);

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 4, Marine, Somewhere);

Actions:

¤ CreateUnit(9, Firebat, SomewhereElse, CurrentPlayer);

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 6, Marine, Somewhere);

Actions:

¤ CreateUnit(11, Firebat, SomewhereElse, CurrentPlayer);

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 8, Marine, Somewhere);

Actions:

¤ CreateUnit(13, Firebat, SomewhereElse, CurrentPlayer);

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 10, Marine, Somewhere);

Actions:

¤ CreateUnit(15, Firebat, SomewhereElse, CurrentPlayer);

Trigger

Conditions:

¤ Bring(CurrentPlayer, Exactly, 13, Marine, Somewhere);

Actions:

¤ CreateUnit(18, Firebat, SomewhereElse, CurrentPlayer);

Of course, you could use this for just about any parameter too, not just numeric ones. You could programmatically access locations, strings, units, whatever you wanted.

Ooooh macros. That would be nice to see

It is possible already, just crack starcraft, go learn C++, open it in borland and write your own functions for starcraft
That's how blizzard did that, and that's the only real way to do that.

You spelled math"e"matics wrong yoshi.

[center]Thanks for bringing this topic back to life to point that great piece of information up.[/center]

Pretty darn trigger-intensive.

*sigh*
I would find this useful if not for the fact that it would suddenly make part of one of my ideas for a map not-so-special.
Oh well, not like I was actualy working on the damn map.
Screw it :\
*screws 'it'...*

Well, yes. The idea is that the mapper only sees one trigger, when it really represents several. You can control exactly how many triggers it creates when you "declare" the variable(s) you're going to use.

So basically if understand this right, it is impossible to write a trigger with variables, but instead [heimdal] will code it so that the the mapmaker would be able to ask write a simple trigger that will transfer into a complex system of many triggers using something such as player 85 deaths for instance or some other useless data that is stored in starcraft? (I hope this makes some sense.)

I know the mapper isn't hampered but regardless how you work the GUI you are still taking up space will all the triggers.