In addition, and maybe you want it this way, but your generating the box is outside of any events so it will happen once the campaign loads. I only mentioned this because it is between two events, as though you had meant to put it in one but reversed two lines. Again, any line not in an event will execute as soon as the script loads.

aprone might you look at the lure code, I believe it is still not working.
I've done several tests with it and it doesn't seem to be lureing the zombies anywhere, I've made the lure go off ten tiles away from the zombie at 100 radius/lure power whatever it is, and it doesn't seem to react to it, i've done it at 20 tiles 30 40 60 and 100 tiles and it has no affect on the zombie what so ever. The zombie is spawned before the lure so as i understand it it should be affected by it.
Also it doesn't seem to be accepting custome variables for the lure radius part of the command. where in your guide is has one at the rasius.
I sent you my code and since then i've changed it around, i've made it to where the lure is fired off every 5 seconds at the coordinates i provide through updating the variables with the timers. Still nothing though.

Thanks guys, it seems to be working now!
Best regards, Haramir.

ah, I see. Lol. Yeah that was me who messed that up because I thought the timer automatically ran out when an event ended.

Hi,
Actually, if you have multiple events set for a timer, e.g. one at half a minute, and one at one minute, then both of them will fire without you having to stop and start the timer again.
Thus, you only need to stop the timer, as I said in my previous post, when you are not using it any more. Resetting the timer also does not need a stop and start command.

Rob

I had a question about the asterisk operator for names. If we use it to generate loot like this:
add items 30 1 [coordinates] *
would that not generate one of the item? That is, if we say to generate 1 9mm ammo, the user literally finds 1 round, not 1 pack of 30 like you'd expect. So, using the above, would the user not then find single rounds, arrows, and shells? Of course it works fine for med kits, weapons, and armor, but for ammo I'm not sure what would happen.

I'm probably forgetting to reply to some stuff people have said, so my apologies if I have.

Mehgcap, when using the asterisk to generate random items, the client also fills in the amount with the standard amount for the item it randomly becomes.  So essentially, if you're using the * for the item name, you could have used any number for the amount and it wouldn't matter.  I should put that in the guide.

I'm still trying to finish up a few things before I post this next update, but I have figured out the issues with the lure command.  Some changes I've been making to the zombie AI, for a future feature I've been working towards adding, seemed to be conflicting with the lure.

Aprone, quick question. I was just reviewing the Swamp code you posted, the snippet describing zombie generation percentages, and I wanted to confirm something. The line:
fate = Int(Rnd * 100) + 1
generates a random number from 0 to 99 inclusive, hence the plus 1, right? That is, the variable "fate" is random and so the zombie distribution is also random, but also follows the guidelines set out by the subsequent if statements. So, you may have more or less that x percent Canines, but you'll always have roughly that number? I'm putting things in terms of a raw percentage now and will post that when I'm done, but I wanted to be sure I had the logic right.

Good point, and I'd suggest a tag like with recipes. Maybe we should start any post that has a campaign link in it with
SCS Campaign:
Again, that will make searching for actual campaign links much easier.

Yes, each map has its own range (I'm having fun converting the 130 numbers into percentages). I just thought I'd double check, as I don't know VB syntax. I thought Rnd was short for round, but I now see you must call your random Rnd, then cast to an integer with the Int function. Anyway, looking forward to the update.. Come on While statements!

Well the "while and" statements are officially next on my list to work on, but in the mean time here's the huge update that I've been talking about lately.

Campaign client 13 is now posted.  There is now "god mode" and "mortal mode" to become invisible to the zombies for debugging purposes.

I fixed a bug that prevented the "kill event" from triggering if you had zombie respawn turned on.  I rewrote a huge section of the zombie AI, so I assume the lure command is fixed now.  Now that I'm writing this I realize I never went back for a final test, and I probably should have.  Oh well, LOL!

The random speaking of the guards has been reduced, because it was annoying because of how frequently they spoke.

I put a tip in the guide that warns people against using location events that are set to a specific point.  You need at least a 1 square tile range so that the player has a chance to walk inside of it.

I also put something in the guide explaining that random items fill in their own amount, regardless of the amount you specify.

You can add computer controlled Allies!  At this time they do not fight zombies, so even though you specify a weapon for them, they'll just get slaughtered without putting up any kind of fight.  I'll add that feature when I can.

You can set the voice, speed, mission/behavior, and obedience of each ally if you aren't happy with the defaults.

You can play sounds so that they are played from the ally's location.

A death event has been added, as well as an ally death event.

The "item count" command as been added, so you can easily get a count of how many of some item the player has in their inventory.

New built in variables include [deadzombie.x] and [deadzombie.y].  These tell you the X and Y of where the most recent zombie was killed.  This is especially useful in the "kill event".

If you have allies, you can also use these new built in variables.  They require the ally's name, so lets pretend these are for an ally named Fred.  [ally.fred.x], [ally.fred.y], [ally.fred.hp], and [ally.fred.mission].  This gives you the ally's current X, Y, health, and mission/behavior.

You might wonder why you'd care to read back the ally's behavior setting since you set it yourself with scripts, but actually the player can change it if you've set the ally to be obedient.  There's a section on this in the guide.

I played around with this neat trick while testing, so I'll post it here to hopefully inspire people.  When entering a room with a child that had to be rescued (it was an ally of course), the kid is frightened and mistakes me for a zombie.  I set the ally's speed to negative 30 and its behavior on follow, so that it actually runs away from me.  I have to chase it to keep it from getting killed as it runs outside, and after several seconds a timer changes the speed back to normal and messages play out the story that the child realizes I am not a threat.

With custom voice work included in a campaign, these computer controlled allies will open up a thousand new possibilities for creating insane adventures!    I can't wait to see what you guys come up with.