Halo PC zombies

[urbanyoung]

Zombies walk fast.
Low gravity.
Force team change when human dies.

Ideas. Go.

Edit: Maybe I should explain...
I'm making a server that can support a ZOMBIE game with Halo PC (not CE). Zombies can walk faster, cant pick weapons and can jump higher. When a "human" (blue) player dies, they are changed to a zombie (red) and cannot change back.

I want some more ideas, everything listed here (and that I add) can be customized. ie you decide how fast zombies walk. 2x faster, 20x, 100x, half the speed, it's up to you.

Suggesting... If you're interested in the idea post, I want to gauge interest.

[§§}Church]

I cant wait, I'll DEFINITELY be adding zombies to the rotation on a server. At game end, last player on blue (last human) should be switched to red(zombie), and all zombies should be switched to human for the next round. And disable team switching mid-game. Also, dont change the team if the player wasnt killed by a zombie, IE was betrayed or suicided or fell off the map.

[{FC}SlimJim]

hey urban, obviously you know of IG brains. why not simply modify that application as it already has the features we all love (or ad a few that we dont have) for PC. it already has some support for PC anyways.

[urbanyoung]

Dec 16, 2010 8:41:23 GMT -8 {FC}SlimJim said:

hey urban, obviously you know of IG brains. why not simply modify that application as it already has the features we all love (or ad a few that we dont have) for PC. it already has some support for PC anyways.

I got told about that, and I was told it was quite buggy on PC. It is also written in c# and decompiling and analyzing it is more effort that it's worth. Plus, adding it to phasor gives a more integrated experience that can be customized more.

Thanks church will do that.

[§§}47]

ive played somethin like that on ce its really fun

[urbanyoung]

Low gravity can't be done

[[CC]#shiNe! aka LeCrae]

Shux.
Well I like the way people have It set on Halo PC here, If you die once while a zombie you get a tad faster, you die again you get a tad faster, and the process repeats till you get idk SUPER fast.
Grenades are annoying In Zombies, you should not put grenades on the map.

[urbanyoung]

I'll add the option to increase speed with death. Removing nades is up to the person building the map/gametype

[Timmeh]

Mhm, and maybe... just maybe... you can add NPC's so they're zombies (if you're soloing it in the server)?

I also suggest getting a new server for this.

[urbanyoung]

Dec 16, 2010 21:30:14 GMT -8 Timmeh said:

Mhm, and maybe... just maybe... you can add NPC's so they're zombies (if you're soloing it in the server)?

I also suggest getting a new server for this.

1. Maybe if I had a degree in game programming and knew about making AI.

2. What do you mean?

[§§}Predator]

Have you heard of Zombies Panic? It's the same basic rules but Humans can only stay in a specific area. Is it possible to make a kill zone around the specified area for Humans? Such as a kill zone surrounding one of the bases in Blood Gulch? I'm not sure if Halo 1 supports a kill zone or not..

[urbanyoung]

Hmm, I haven't heard of that. I guess a modder could put human spawns within a certain area and box them in to produce the same effect.

Here's the skeleton of the script system I will use to design the zombie gametype. If you have any more ideas for events you'd like to be notified about, post!

-- Phasor OnAction script, it is coded using Lua 5.14, you may edit with any text editor.
-- I encourage people to share their scripts, feel free to build off this script, which is an example for a zombie gametype.
-- This script is event driven (the functions are called when the event happens).
-- All player numbers are 0 based from 0-15
-- ONLY FUNCTIONS THAT SAY SO MAY HAVE A RETURN VALUE. DO NOT ADD TO OTHER FUNCTIONS.

-- called when a player joins. 'player' is the index of the new player
function OnPlayerJoin(player)
end

-- called when a player dies. 'player' is the index of the dead player, 'team' is their current team
function OnPlayerDeath(player, team)
end

-- called when a player kills another, 'killer' is the index of the killing player, 'victim' is the index of the dead player
function OnPlayerKill(killer, victim)
end

-- called when a player kills a team mate.
-- 'count' is the number of times 'killer' has team killed
function OnPlayerTeamKill(killer, victim, count)
end

-- called when a player is attempting to change team.
-- the return value should be boolean and specify whether or not the player is allowed to change team
-- true = yes, false = no. The return value is ignored for admins.
function OnPlayerTeamChange(player, team, dest_team)
end

[urbanyoung]

--[[
Phasor OnAction script, it is coded using Lua 5.14, you may edit with any text editor.
I encourage people to share their scripts, feel free to build off this script, which is an example for a zombie gametype.
This script is event driven (the functions are called when the event happens).
All player numbers are 0 based from 0-15
ONLY FUNCTIONS THAT SAY SO MAY HAVE A RETURN VALUE. DO NOT ADD TO OTHER FUNCTIONS.

Visible functions:
1. hprintf: This function takes 1 argument and writes text to the server console.
Syntax: hprintf(char* message)

Examples:
hprintf("Player " .. player " has just joined") - Remember, in Lua .. is used to join strings.
hprintf("This is a static message")

2. kickplayer: This funcition takes 1 argument and boots the specified player.
Syntax: kickplayer(int player)

Examples:
kickplayer(player) kicks player at index 'player'
kickplayer(0) kicks the first player

3. banplayer: This funcition takes 2 arguments and bans the specified player.
Syntax: banplayer(int player, char* duration)

Examples:
banplayer(player, 0) bans the player at index 'player' permanantely
banplayer(player, "1d") bans the player at index 'player' for 1 day

Notes: Acceptable ban durations include: d (days), h(hours), m (minutes). Same usage as sv_ban

4. setplayers: This function takes 2 arguments and sets the number of players each team will start with
Syntax: setplayers(int team, int max_players)

Examples:
setplayers(0, 1) allow red to start with every one player. as such blue will be allowed $max_players - 1
setplayers(1, $max_players / 2) this is the default option and makes each team have equal players

Notes: The players should only be set for one team, not both. The teams are filled alternatively until one team is full.
Calling this function does not guarantee the team sizes will be as specified, it depends on players in the server.
The team size can be manually exceeded by using changeteam (see below).

Team numbers:
0 - Red
1 - Blue

5. changeteam: This function takes 1 argument and changes the specified players team. Any team balance settings are ignored.
Syntax: changeteam(int player)

Examples:
changeteam(0) changes the first players team (if they exist)
changeteam(player) changes the team of the player at index 'player'

Notes: This function will always change the specified players team. Auto-balance and the setplayers limit are all ignored.

6. weaponchange: This function takes 2 arguments and specifies whether or not a player can pickup new weapons
Syntax: weaponchange(int player, bool canChange)

Examples:
weaponchange(player, 0) stops 'player' from being able to pickup weapons
weaponchange(player, 1) allows 'player' to pickup weapons (default)

7. setspeed: This function takes 2 arguments and sets a specific player's speed
Syntax: setspeed(int player, float speed)

Examples:
setspeed(player, 1.5)
setspeed(player, 1.0)

Notes: The default speed is 1.0, the higher the speed the more lag is observed while moving. Be sensible.
The speed doesn't need to be reset on death, only needs to be set once per game.

8. say: This function takes 1 argument and sends a message to the entire server
Syntax: say(char* message)

Examples:
say("Hello server, this is an automated message")

9. privatesay: This function takes 2 arguments and sends a message to the specified players
Syntax: privatesay(int player, char* message)

Examples:
privatesay(player, "Welcome to my server, the rules are...")

10. registertimer: This function takes 3 arguments and calls the specified function when the time limit runs out
Syntax: registertimer(int timerid, int delay, char* func)

Examples:
registertimer(1, 20000, "OnTimer") This creates a timer with id '1' and a delay of 20 seconds (20,000 ms). When the timer expires the function
OnTimer is called. The OnTimer function should return a value of either 1 or 0 which indicates whether or not the timer is reset or deleted.
1 indicates reset, 0 tells Phasor to delete the timer.

11. getname: This function takes 1 argument and returns the name of the specified player (if they exist)
Syntax: char* getname(int player)

Examples:
name = getname(player)
privatesay(player, "Your name is " .. name .. "!")

--]]


-- Set this to false to easily remove the zombie settings
zombies = true

-- Below are some global variables that control various aspects of the game, feel free to change
zombie_team = 0 -- 0 is red, 1 is blue
max_players = 0 -- this is populated when the script is loaded
zombie_speed = 2.0
human_speed = 1.0
zombie_count = 0.15 -- if value is less than 1 is it used as a percentage, more than or equal to one is absolute count

-- Don't modify below variables unless you know what you're doing
cur_blue_count = 0
cur_red_count = 0
cur_players = 0
last_team = 255

function round(num)
under = math.floor(num)
upper = math.floor(num) + 1
underV = -(under - num)
upperV = upper - num
if (upperV > underV) then
return under
else
return upper
end
end

-- called when the script is loaded
function OnScriptLoad()

if zombies == true then

cur_red_count = getteamsize(0)
cur_blue_count = getteamsize(1)

cur_players = cur_red_count + cur_blue_count

hprintf("Load Counts: total " .. cur_players .. " blue: " .. cur_blue_count .. " red: " .. cur_red_count)


end

end
-- called when a game is starting (before any players join)
function OnNewGame(map)

hprintf("Running map " .. map .. " from Lua")

-- reset our variables
cur_blue_count = 0
cur_red_coun = 0
cur_players = 0
end

-- called when a player's team is being chosen
function OnTeamDecision(cur_team)

cur_players = cur_players + 1
if zombies == true then

-- check if the number of zombies has been met
finalZombies = 0

if zombie_count >= 1 then
finalZombies = zombie_count
else
finalZombies = round(cur_players * zombie_count)
end

curCount = 0

-- check which team are the zombies
if zombie_team == 0 then
curCount = cur_red_count
else
curCount = cur_blue_count
end

decision = 0

-- check if the numer of zombies has been met
if curCount == 0 or (curCount < finalZombies and last_team ~= zombie_team) then

decision = zombie_team

if zombie_team == 0 then
cur_red_count = cur_red_count + 1
else
cur_blue_count = cur_blue_count + 1
end
else

if zombie_team == 0 then
cur_blue_count = cur_blue_count + 1
decision = 1
else
cur_red_count = cur_red_count + 1
decision = 0
end

end

hprintf("Decison: " .. decision)
last_team = decision

hprintf("Counts: total " .. cur_players .. " blue: " .. cur_blue_count .. " red: " .. cur_red_count)
return decision

end

return cur_team
end

-- called when a player leaves.
function OnPlayerLeave(player, team)

if zombies == true then

if team == 0 then
cur_red_count = cur_red_count - 1;
elseif team == 1 then
cur_blue_count = cur_blue_count - 1
end

cur_players = cur_players - 1

end
end

-- called when a player joins. 'player' is the index of the new player
function OnPlayerJoin(player, team)

-- send a welcome message to the new player
name = getname(player)

privatesay(player, "Welcome " .. name .. ". This server runs a development version of zombies")
privatesay(player, "It's not done but I need to test stability.....")

if zombies == true then

-- check if the player is a zombie
if team == zombie_team then

-- stop the zombie picking up weapons
weaponchange(player, 0)

-- change the player's speed
setspeed(player, zombie_speed)

privatesay(player, "YOU'RE A ZOMBIE. KILL THE HUMANS!")

else
privatesay(player, "YOU'RE A HUMAN. SURVIVE.")
end
end

end

-- called when a player dies. 'player' is the index of the dead player, 'team' is their current team
function OnPlayerDeath(player, team)
end

-- called when a player kills another, 'killer' is the index of the killing player, 'victim' is the index of the dead player
function OnPlayerKill(killer, victim)
end

-- called when a player kills a team mate.
-- 'count' is the number of times 'killer' has team killed
function OnPlayerTeamKill(killer, victim, count)
end

-- called when a player is attempting to change team.
-- if relevant is 1 the return value indicates whether or not they can change team. if 0 return value is ignored.
function OnTeamChange(relevant, player, team, dest_team)

if zombies == true then

if (relevant == 1) then
-- we don't let people change team
return false
else
-- we can't stop the person changing teams, bein done by an admin
if dest_team == 0 then
cur_red_count = cur_red_count + 1
cur_blue_count = cur_blue_count - 1
elseif dest_team == 1 then
cur_red_count = cur_red_count - 1
cur_blue_count = cur_blue_count + 1
end

-- change the players speed
if dest_team == zombie_team then
setspeed(player, zombie_speed)
else
setspeed(player, human_speed)

end
end
end
return true;
end

[§§}Predator]

Looks like you've been doing some good hard work on it all we are all very thankful for it, I can't wait to play . Also,

Dec 17, 2010 2:48:15 GMT -8 urbanyoung said:

Hmm, I haven't heard of that. I guess a modder could put human spawns within a certain area and box them in to produce the same effect.

I think with my mediocre modding knowledge, I should be able to place the Human Spawns, however I don't know how to 'box the humans in' so to speak. I know in some of the latest Halos such as Reach you can specify the kill zone I mentioned before. No idea if you can do the same thing in this Halo, but I will ask around.

[§§}grunt]

zombies should also b invisible

[urbanyoung]

I tried making an option for zombies to be invisible but didn't work as I hoped, need to do a bit more research. I only got as far as having the server think they're invisible but nobody could see it.

§§}Predator - The kill box sounds quite hard May not get around to it.

I hope people will spend about 20 minutes learning Lua so they can make their own scripts once released...

[§§}Predator]

Yeah Np Oxide, it is pretty hard. I asked around and almost no one knew what I was talking about, Bottles said he was going to get back to me as he thought he may know something. But its all good, if it is going to be this complicated to add things just to play Panic, don't bother. Normal Zombies will be epic anyway

Also, with making Zombies invisible, I think I told you this in the server yesterday but I didn't get a response because of Chat Lag. I think that in SparkEdit I can make it so that a Camo will spawn on top of every Zombie spawn. But, I don't think I can extend the time in which the Camo lasts or the time of respawn for it either.. May have to pull out HMT/HHT for that.

Then again however, *Breathes*, that would be a map mod.. and your making a server mod. I think thats what you told me in the server? I'm not sure.

[urbanyoung]

I probably just need to find the invis notification packet for invis to work.

Yeah, that's what I said. I don't want to rely on map mods, I want a 100% server controlled (and therefore dynamic) solution.

[§U}Zuko]

Pred, Are you forgetting that zombies can shoot when your outside of the panic area... So I don't think there should be a killzone spot.

[§§}Predator]

Yeah thats true, but I mean the MAIN purpose of the game (Panic) is stay within the area. If we could make the kill zone, it would cut out the zombies having to kill the player. But I know what your saying, a kill zone is not completely necessary, but it would make it easier for the zombie and to tell who has left the area.

Also if you need help with any of it Oxide, keep hitting me up on XFire.