Hi all,

So I am currently learning how to script in CoD4 and I am coming along. This might 4th set of tools I have learned and scripted in so I not a huge newb but very new to the CoD toolset.

I have got AI to spawn when linked to a trigger and some basic scripts like firing script off a trigger and thread and notify basics and such.

My question is why did IW link there enemy actor placments with script origins in blackout? This seems to be fundamental work flow so I would like to know why :).

If I figure it out I will post up the solution.

Cheers,
-W

script_origins are locators in 3d space, they mark a location for a script. But they can also be used as helper/dummy objects. You can access them like other entities via script and read their properties (key-value-pairs, e.g. script_noteworthy, can be set in Radiant).

A possibility of using script_origins:

There's a trigger at the mountain top, where the player stands. When triggered, you get two origins placed in radiant via script

start = getent("start_node", "targetname");
end =getent("end_node", "targetname");

start_node is near the trigger, end_node at the bottom of the mountain. You move the player from where he stands to the start location, then to the bottom location.

org = spawn("script_origin", player.origin); // helper origin
player linkto(org);
org moveto(start.origin, 2);
wait 2;
org moveto(end.origin, 4);
org waittill("movedone");
player unlink();
org delete();

There are also nodes (basically like script_origins), which accept certain key-value-pairs to control AI behaviour etc. I'm not sure if such KVPs work on script_origins the same as script nodes. You may have a look at stock scripts and see what they do.

Thanks for the response, much appreciated :)

A few quick questions on your code.

What does linkto do? Does it take the specified enties and somehow make them aware of each other in some way?

Which leads me to...

"org moveto (start.origin, 2);"

Which seems like it would on entity org call function moveto and gives the location of our defined start.origin and tells it to go there (I am guessing what this last parameter does) at speed 2.

So now with talking it out here a bit more does the linkto (in this case because its a script node) take whatever its linked to and treat as the same entity in script?

So would this code do the same thing as your code without linking?

org = spawn("script_origin", player.origin); // helper origin
player moveto(start.origin, 2);
wait 2;
player moveto(start.origin, 2);
org waittill("movedone");
org delete();

Thanks again sir.

-W

linkto links an entity to another. If child is linked to parent and you move parent, parent and child will move together, keeping the relation they had when they were linked. Example:

parent at 2/5
child at 4/5
child linkto parent
move parent to 3/6
parent moves to 3/6, child to 5/6 (parent moved relatively +1/+1, so did the child)

linkto does nothing else then this, AI is not involved.

the moveto parameters are:
point, time, acceleration time, deceleration time (the latter 2 are optional)

See: http://zeroy.com/script/motion/moveto.htm

your script wouldn't work:
- org waittill("movedone"); will wait for org movement, but player was moved
- there's no point in spawning/using org-entitiy in your script
- it's not possible to use moveto on a player, that's why i use the helper origin in my code. moveto works for script_origins and you can link players to them. It's an indirect way of moving a player.

Gotcha. Link seems like Attach in Unreal and Script Origins are like Notes. Thanks again.
-W

edited on Jan. 25, 2012 03:47 pm by Wraith411

Glad to helped you :)

Not sure if it's like attach, there's an attach() function in CoD too which might be more like the Unreal attach - but both do about the same either way ;)