Create a script_struct in radiant, give it a targetname of custom_poi. Then create a trigger_multiple where you want the safe zone to be. Now, select the struct first, then select the trigger, hit W to link them. Place the struct where you want the zombies to go when you're in the exclusion zone. Then do this in gsc:
Code Snippet
Plaintext
#using scripts\codescripts\struct; #using scripts\zm\_zm_utility; #using scripts\shared\flag_shared; //edit: You might need this too
function poi_test(){ level flag::wait_till("all_players_connected"); //edit poi = struct::get("custom_poi", "targetname"); poi.trig = GetEnt(poi.target, "targetname"); poi.trig SetCursorHint("HINT_NOICON"); poi.trig SetHintString("Zombie exclusion volume"); // attract_dist, num_attractors, added_poi_value, start_turned_on, initial_attract_func, arrival_attract_func, poi_team poi zm_utility::create_zombie_point_of_interest(100000, 99, 25, false); // num_attract_dists, attract_dist poi thread zm_utility::create_zombie_point_of_interest_attractor_positions(5, 100); poi thread zm_utility::wait_for_attractor_positions_complete(); while(1){ poi.trig waittill("trigger", player); if(player IsTouching(poi.trig)){ while(player IsTouching(poi.trig)){ poi.poi_active = true; //Turns point of interest on wait(1); } }else poi.poi_active = false; //Turns point of interest off wait(1); } }
Last Edit: June 13, 2017, 09:14:50 pm by Archaicvirus
I will test this when I get the chance, so thanks! But 1 question I have is how linking the struct and the trigger change the outcome of what the zombies do?
Linking the struct to the trigger does nothing, other then making the trigger easier to grab in script. It's just something I generally do to keep things simple. But essentially when you link two objects, the object that targets the other gains the kvp: target: (targetname of targeted object). So now struct.target equals the targetname of the object that the struct is targeting. COnfusing?
Haha yea sorry man, it's kind of hard to explain, but it's really easy in the end. Double Post Merge: June 13, 2017, 10:04:39 pmActually to be honest, linking the two objects does do more then what I described before. Generally when you link objects, the targeted object will auto-generate a targetname kvp. It will be like "auto1" or if you've linked a lot of objects, "auto17". This is useful for a lot of different reasons. Lets say you wanted to make multiple exclusion zones, you could link the two objects like I said, then save them as a prefab. So when you stamp copies of that prefab around the map, the targetname of the struct will stay the same, but each trigger will have an "auto3" or some number generated unique to it's parent's struct. That way you could do something like this:
Code Snippet
Plaintext
function init(){ //Edit - changed to struct::get_array not struct::get. points = struct::get_array("exclusion_zone", "script_noteworthy"); foreach(point in points){ point.trig = GetEnt(point.target, "targetname"); point zm_utility::create_zombie_point_of_interest(100000, 99, 25, false); point thread zm_utility::create_zombie_point_of_interest_attractor_positions(5, 100); point thread zm_utility::wait_for_attractor_positions_complete(); point thread exclusion_zone(); } }
I haven't tested this exact script, but it comes from one of my scripts and I'm doing something similar, although I wrote this a little different for your application. But again linking objects does have a benefit depending on what you're trying to do. This method makes it so you don't have to write a separate function each time you want to make another exclusion zone. And also I haven't tried this with a trigger multiple, but I have this working on a trigger_use. So you might not want a hintstring on a trigger multiple.
Another idea you could do, is make multiple exclusion zones (triggers), but link only one struct to all of them, so no matter which exclusion zone the player is in, the zombies will always go to the same place.
Last Edit: June 16, 2017, 01:27:43 am by Archaicvirus
Foreach means you are iterating through an array (in this case), so you are saying for each item in this group, do this to them. Here's a more practical explanation.
Code Snippet
Plaintext
function test() { //Edit - adjusted for clarity
//First, define the array. //Objects excluding script_struct's in radaint should use GetEntArray("key", "value"); and not struct::get_array poi_array = struct::get_array("exclusion_zone", "targetname"); //Let's say you have 5 structs all named exclusion_zone
//When you do a foreach() loop, you can name the 'item' in the 'group' anything you want //For example below, 'foreach(struct in poi_array)' you can call 'struct' anything, it's a temporary variable only defined //within the for() loop. //Like foreach(thing in things), or foreach(guy in things), but the 'things' has to be an array, that you //define outside of and before the for() loop occurs. This can be used with any array, regardless of it's contents or application. foreach(struct in poi_array) { //For each struct in the array "poi_array" defined above, //execute this code 1 time for each struct:
function test2() { poi_array = struct::get_array("exclusion_zone", "targetname"); //Let's say you have 5 structs all named exclusion_zone
//This is the same as foreach, except in an array, //the first object is index 0, then 1, 2 etc. //And you loop through that array with 'i' which starts at 0, //and loops until poi_array[4], which would be the 5th index. for(i = 0; i < poi_array.size; i++) {
IPrintLnBold("Hello I am struct #:"+i); trigger = GetEnt(poi_array[i].target, "targetname"); poi_array[i].trig = trigger; poi_array[i] thread some_function();
} }
function some_function() { //Each poi struct becomes 'self' in this function. //So self.trig is the same as poi_array[i].trig above or struct.trig in the first function
self.trig waittill("trigger", player); IPrintLnBold("Hello my target is at"+self.trig.origin); }
//Or, if you're really hungry, you could do function get_donuts(){ a_dozen = GetEntArray("box_of_donuts", "script_food"); foreach(donut in a_dozen){ donut thread deep_fry(); while(donut.is_cooking){ donut waittill("minimum internal temperature reached"); donut.is_done_cooking = true; } donut thread dip_in_chocolate_glaze(); donut thread cover_in_sprinkles(); break; //For a taste test. :)
}
Hope that explains it a little better.
edit* - Fixed some typos in the scripts and the earlier replies as well.
Last Edit: June 17, 2017, 05:21:29 am by Archaicvirus
I got your pm, but if you don't mind, post the exact script you're using in code tags here, and I'll take a look at it. That way other people can learn from this, and I can see which one of my examples you're using. And also, what is your radiant setup? Give me a brief explanation on the trigger and struct setup you have. A screen shot of their kvp's will also help.
Last Edit: June 17, 2017, 05:06:34 am by Archaicvirus
//***************************************************************************** // MAIN //*****************************************************************************
if(player IsTouching(poi.trig)){ while(player IsTouching(poi.trig)){ poi.poi_active = true;//Turns point of interest on IPrintLnBold("Inside"); wait(1); } }else poi.poi_active = false;//Turns point of interest off IPrintLnBold("Outside!"); wait(1);
don tuse the else-statement here, the if-statement was allready true so it wont execute the code under the else-statement
Reply
Wolfilms 
Apeldoorn
