Fortress Forever Wiki - User contributions [en]

Map Template:Sequential Territory Control

2009-12-22T14:42:12Z

Pon: redspawn_cp5 said blue team not red

{{Infobox manual/Header}}
=Foreword=
This is likely a temporary script/page until an offical Lua for this gametype is released. As such, the Lua script itself likely isn't up to the same standard as the official ones. It does work as intended, though.

It is set up to behave as close to the TFC version of warpath as I could get it, with my limited mapping experience.

Last updated: 12:52, 11 January 2008 (CST)
 
=Introduction=
In this game mode, each team must capture Command Points in order (no flag, just touch the Command Point), typically the Blue team capture 1 through 5, and the Red team 5 through 1. Upon a team capturing their final point, the round is reset.

An example of this style of map is Warpath.
 
=Entities=
==Start Gates==
*startgate_blue (func_door): Start gate for Blue team
*startgate_red (func_door): Start gate for Red team
 
==Spawns==
*bluespawn_cp1 (info_ff_teamspawn): Initial Blue team spawn
*bluespawn_cp2 (info_ff_teamspawn): --\
*bluespawn_cp3 (info_ff_teamspawn): -- Progressive spawns for the Blue team. "cp#" denotes Command Point control nessecary to be active(only current cp# spawns are active)
*bluespawn_cp4 (info_ff_teamspawn): --/
 
*redspawn_cp5 (info_ff_teamspawn): Initial Red team spawn
*redspawn_cp4 (info_ff_teamspawn): --\
*redspawn_cp3 (info_ff_teamspawn): -- Progressive spawns for the Red team. "cp#" denotes Command Point control nessecary to be active (only current cp# spawns are active)
*redspawn_cp2 (info_ff_teamspawn): --/
 
==Respawn Doors==
*bluerespawn_cp2_actual (func_door): --\
*bluerespawn_cp3_actual (func_door): -- Physical door for Blue spawns. All flags should be off, opening is controlled by another entity
*bluerespawn_cp4_actual (func_door): --/
 
*redrespawn_cp4_actual (func_door): --\
*redrespawn_cp3_actual (func_door): -- Physical door for Red spawns. All flags should be off, opening is controlled by another entity
*redrespawn_cp2_actual (func_door): --/
 
*bluerespawn_cp2 (trigger_ff_script): --\
*bluerespawn_cp3 (trigger_ff_script): -- Trigger for the respawn doors above. Fires output "OnStartTouch:Open" to corresponding "_actual" door
*bluerespawn_cp4 (trigger_ff_script): --/
 
*bluerespawn_cp4 (trigger_ff_script): --\
*bluerespawn_cp3 (trigger_ff_script): -- Trigger for the respawn doors above. Fires output "OnStartTouch:Open" to corresponding "_actual" door
*bluerespawn_cp2 (trigger_ff_script): --/
 
==Command Points==
*command_point_one (trigger_ff_script): Location for Command Point One
*command_point_two (trigger_ff_script): ... and
*command_point_three (trigger_ff_script): ... so
*command_point_four (trigger_ff_script): ... on
*command_point_five (trigger_ff_script): ... etc.
 
==Flags==
*cp1_flag (prop_dynamic_override): Flag used to denote CP ownership. Cannot be picked up.
*cp2_flag (prop_dynamic_override): ... and
*cp3_flag (prop_dynamic_override): ... so
*cp4_flag (prop_dynamic_override): ... on
*cp5_flag (prop_dynamic_override): ... etc.
 
==Flag Rotators==
*cp1_flag_rotator (func_rotating): Optional entity used to rotate flag on CP. Flag entity must have this entity as parent if used.
*cp2_flag_rotator (func_rotating): ... and
*cp3_flag_rotator (func_rotating): ... so
*cp4_flag_rotator (func_rotating): ... on
*cp5_flag_rotator (func_rotating): ... etc.
 
=Lua Script=
(NOTE: Uses a custom vgui graphic. The graphic is included in the source .vmf download linked to below the script, along with the below script)
<pre>------------------------------------------------
-- This started as cz2.lua, along with some other bits of lua from other official files, and then altered by myself
-- to accomodate warpath-style gameplay.
--
-- Pon.id
-- warpath_example.lua v1.00
------------------------------------------------

-----------------------------------------------------------------------------
-- includes
-----------------------------------------------------------------------------
IncludeScript("base_teamplay")
IncludeScript("base_location")
IncludeScript("base_respawnturret")

-----------------------------------------------------------------------------
-- globals
-----------------------------------------------------------------------------

-- Scoring globals
NUMBER_OF_COMMAND_POINTS = 5
POINTS_FOR_COMPLETE_CONTROL = 30
FORTPOINTS_FOR_COMPLETE_CONTROL = 1000
FORTPOINTS_FOR_CAP = 200

-- Other Globals (Initial round delay used only for first round, give people time to log in)

INITIAL_ROUND_DELAY = 45
NORMAL_ROUND_DELAY = 30
RECAPTURE_DELAY = 15

-- Counters for spawn validty
cp_blue = 1
cp_red = 5

-- A global table for storing some team info
team_info = {

[Team.kUnassigned] = {
team_name = "neutral",
color_index = 1,
skin = "0",
flag_visibility = "TurnOff"
},

[Team.kBlue] = {
team_name = "blue",
color_index = 2,
skin = "0",
flag_visibility = "TurnOn"
},

[Team.kRed] = {
team_name = "red",
color_index = 0,
skin = "1",
flag_visibility = "TurnOn"
}
}

-- This table is for keeping track of which team controls which CP
command_points = {
[1] = { controlling_team = Team.kBlue, cp_number = 1, disable_capture = 0, hudstatusicon = "hud_cp_1.vtf", hudposx = -40, hudposy = 36, hudalign = 4, hudwidth = 16, hudheight = 16 },
[2] = { controlling_team = Team.kUnassigned, cp_number = 2, disable_capture = 0, hudstatusicon = "hud_cp_2.vtf", hudposx = -20, hudposy = 36, hudalign = 4, hudwidth = 16, hudheight = 16 },
[3] = { controlling_team = Team.kUnassigned, cp_number = 3, disable_capture = 0, hudstatusicon = "hud_cp_3.vtf", hudposx = 0, hudposy = 36, hudalign = 4, hudwidth = 16, hudheight = 16 },
[4] = { controlling_team = Team.kUnassigned, cp_number = 4, disable_capture = 0, hudstatusicon = "hud_cp_4.vtf", hudposx = 20, hudposy = 36, hudalign = 4, hudwidth = 16, hudheight = 16 },
[5] = { controlling_team = Team.kRed, cp_number = 5, disable_capture = 0, hudstatusicon = "hud_cp_5.vtf", hudposx = 40, hudposy = 36, hudalign = 4, hudwidth = 16, hudheight = 16 }
}

icons = {
[Team.kBlue] = { teamicon = "hud_cp_blue.vtf", disabled = "hud_disabled.vtf" },
[Team.kRed] = { teamicon = "hud_cp_red.vtf", disabled = "hud_disabled.vtf" },
[Team.kUnassigned] = { teamicon = "hud_cp_neutral.vtf", disabled = "hud_disabled.vtf" }
}

function startup()

-- set up team limits
SetPlayerLimit( Team.kYellow, -1 )
SetPlayerLimit( Team.kGreen, -1 )

local team = GetTeam(Team.kBlue)
team:SetClassLimit( Player.kScout, 0 )
team:SetClassLimit( Player.kSniper, 0 )
team:SetClassLimit( Player.kSoldier, 0 )
team:SetClassLimit( Player.kDemoman, 0 )
team:SetClassLimit( Player.kMedic, 0 )
team:SetClassLimit( Player.kHwguy, 0 )
team:SetClassLimit( Player.kPyro, 0 )
team:SetClassLimit( Player.kSpy, 0 )
team:SetClassLimit( Player.kEngineer, 0 )
team:SetClassLimit( Player.kCivilian, -1 )

local team = GetTeam(Team.kRed)
team:SetClassLimit( Player.kScout, 0 )
team:SetClassLimit( Player.kSniper, 0 )
team:SetClassLimit( Player.kSoldier, 0 )
team:SetClassLimit( Player.kDemoman, 0 )
team:SetClassLimit( Player.kMedic, 0 )
team:SetClassLimit( Player.kHwguy, 0 )
team:SetClassLimit( Player.kPyro, 0 )
team:SetClassLimit( Player.kSpy, 0 )
team:SetClassLimit( Player.kEngineer, 0 )
team:SetClassLimit( Player.kCivilian, -1 )

-- Reset all command points
command_point_one:ChangeControllingTeam(Team.kBlue)
command_point_two:ChangeControllingTeam(Team.kUnassigned)
command_point_three:ChangeControllingTeam(Team.kUnassigned)
command_point_four:ChangeControllingTeam(Team.kUnassigned)
command_point_five:ChangeControllingTeam(Team.kRed)

-- Setup Doors for first round

setup_door_timer("startgate_blue", INITIAL_ROUND_DELAY)
setup_door_timer("startgate_red", INITIAL_ROUND_DELAY)

end

function precache()
-- precache sounds
PrecacheSound("yourteam.flagcap")
PrecacheSound("otherteam.flagcap")
PrecacheSound("otherteam.flagstolen")

PrecacheSound("misc.bizwarn")
PrecacheSound("misc.bloop")
PrecacheSound("misc.buzwarn")
PrecacheSound("misc.dadeda")
PrecacheSound("misc.deeoo")
PrecacheSound("misc.doop")
PrecacheSound("misc.woop")

-- Unagi Power! Unagi!
PrecacheSound("misc.unagi")

end

-----------------------------------------------------------------------------
-- Round Completion
-----------------------------------------------------------------------------

function complete_control_notification ( player )

SmartSound(player, "yourteam.flagcap", "yourteam.flagcap", "otherteam.flagcap")
SmartMessage(player, "Your team captured ALL Command Points!", "Your team captured ALL Command Points!", "The enemy team captured ALL Command Points!")

end

-----------------------------------------------------------------------------
-- Command Points
-----------------------------------------------------------------------------

base_cp_trigger = trigger_ff_script:new({
health = 100,
armor = 300,
grenades = 200,
nails = 200,
shells = 200,
rockets = 200,
cells = 200,
detpacks = 1,
gren1 = 4,
gren2 = 4,
item = "",
team = 0,
botgoaltype = Bot.kFlagCap,
cp_number = 0,
})

function base_cp_trigger:ontrigger( trigger_entity )
if IsPlayer( trigger_entity ) then
local player = CastToPlayer( trigger_entity )
local cp = command_points[self.cp_number]

local new_controlling_team = player:GetTeamId()
local old_controlling_team = cp.controlling_team
local team = GetTeam(new_controlling_team)

-- No capping if player's team already controls this CP
if player:GetTeamId() == cp.controlling_team then return end

-- No Capping if team doesn't own preceeding point
if new_controlling_team == Team.kBlue then
local last_blue_cp = self.cp_number - 1
if command_points[last_blue_cp].controlling_team ~= new_controlling_team then return end
elseif new_controlling_team == Team.kRed then
local last_red_cp = self.cp_number + 1
if command_points[last_red_cp].controlling_team ~= new_controlling_team then return end
end

-- No Capping if disabled due to recent capture
if cp.disable_capture == 1 then return end

-- Find out if any team has complete control
local team_with_complete_control = Team.kUnassigned
local control_count = { [Team.kBlue] = 0, [Team.kRed] = 0 }
control_count[new_controlling_team] = 1
for i,v in ipairs(command_points) do
if v.controlling_team ~= Team.kUnassigned and v.cp_number ~= self.cp_number then
control_count[v.controlling_team] = control_count[v.controlling_team] + 1
end
if control_count[v.controlling_team] == NUMBER_OF_COMMAND_POINTS then
team_with_complete_control = v.controlling_team
end
end

-- Ends round if a team has all cp's, else just sorts out a normal cp capture.
if team_with_complete_control ~= Team.kUnassigned then

-- Team points for complete control, more FortPoints too
team:AddScore(POINTS_FOR_COMPLETE_CONTROL)
player:AddFortPoints(FORTPOINTS_FOR_COMPLETE_CONTROL, "Final CP Captured")

AddSchedule("complete_control_notification", 0.1, complete_control_notification, player)

-- Reset all command points
command_point_one:ChangeControllingTeam(Team.kBlue)
command_point_two:ChangeControllingTeam(Team.kUnassigned)
command_point_three:ChangeControllingTeam(Team.kUnassigned)
command_point_four:ChangeControllingTeam(Team.kUnassigned)
command_point_five:ChangeControllingTeam(Team.kRed)

-- Reset extended spawn areas and door
cp_blue = 1
cp_red = 5

-- Reset doors and set up timers for the next round
setup_door_timer("startgate_blue", NORMAL_ROUND_DELAY)
setup_door_timer("startgate_red", NORMAL_ROUND_DELAY)

-- Clean up HUD and capture disabled status for all CP's
for i,v in ipairs(command_points) do
RemoveHudItemFromAll( v.cp_number .. "-disabled-" .. Team.kRed )
RemoveHudItemFromAll( v.cp_number .. "-disabled-" .. Team.kBlue )
v.disable_capture = 0
end

-- Respawns everyone/clean up map. Done in schedule to give delay
AddSchedule( "new_round_respawn", 0.1, new_round_respawn)

else

-- Give points to player for single cap
player:AddFortPoints(FORTPOINTS_FOR_CAP, "Captured CP" .. self.cp_number)

-- Set new owning team, change spawn validity, then disable capture for a bit
self:ChangeControllingTeam(new_controlling_team, old_controlling_team)
cp.disable_capture = 1
AddSchedule ("cp" .. self.cp_number .. "_reenable", RECAPTURE_DELAY, cp_reenable, cp, new_controlling_team)

-- have to do messages here since player is here
-- could just pass player to ChangeControllingTeam, but fuck you

SmartMessage(player, "You captured Command Point " .. self.cp_number, "Your team captured Command Point " .. self.cp_number, "The enemy team captured Command Point " .. self.cp_number)

-- sounds will get more and more crazy
-- NOTE: These checks are hardcoded for 5 CPs...if you have more CPs, change how these are checked

if control_count[new_controlling_team] == 4 then
SmartSound(player, "misc.unagi", "misc.unagi", "misc.bizwarn")
elseif control_count[new_controlling_team] == 3 then
SmartSound(player, "misc.woop", "misc.woop", "misc.buzwarn")
elseif control_count[new_controlling_team] == 2 then
SmartSound(player, "misc.doop", "misc.doop", "misc.dadeda")
else
SmartSound(player, "misc.bloop", "misc.bloop", "misc.deeoo")
end

end

-- give player some health and armor
if self.health ~= nil and self.health ~= 0 then player:AddHealth( self.health ) end
if self.armor ~= nil and self.armor ~= 0 then player:AddArmor( self.armor ) end

-- give player ammo
if self.nails ~= nil and self.nails ~= 0 then player:AddAmmo(Ammo.kNails, self.nails) end
if self.shells ~= nil and self.shells ~= 0 then player:AddAmmo(Ammo.kShells, self.shells) end
if self.rockets ~= nil and self.rockets ~= 0 then player:AddAmmo(Ammo.kRockets, self.rockets) end
if self.cells ~= nil and self.cells ~= 0 then player:AddAmmo(Ammo.kCells, self.cells) end
if self.detpacks ~= nil and self.detpacks ~= 0 then player:AddAmmo(Ammo.kDetpack, self.detpacks) end
if self.gren1 ~= nil and self.gren1 ~= 0 then player:AddAmmo(Ammo.kGren1, self.gren1) end
if self.gren2 ~= nil and self.gren2 ~= 0 then player:AddAmmo(Ammo.kGren2, self.gren2) end

end
end

function base_cp_trigger:ChangeControllingTeam( new_controlling_team, old_controlling_team )

-- Change the cap flag around
OutputEvent( "cp" .. self.cp_number .. "_flag", "Skin", team_info[new_controlling_team].skin )
OutputEvent( "cp" .. self.cp_number .. "_flag", team_info[new_controlling_team].flag_visibility)

local cp = command_points[self.cp_number]

-- remove old flaginfo icons and add new ones
RemoveHudItemFromAll( self.cp_number .. "-background-" .. cp.controlling_team )
RemoveHudItemFromAll( self.cp_number .. "-foreground-" .. cp.controlling_team )

AddHudIconToAll( icons[ new_controlling_team ].teamicon , self.cp_number .. "-background-" .. new_controlling_team , cp.hudposx, cp.hudposy, cp.hudwidth, cp.hudheight, cp.hudalign)

AddHudIconToAll( cp.hudstatusicon, self.cp_number .. "-foreground-" .. new_controlling_team , cp.hudposx, cp.hudposy, cp.hudwidth, cp.hudheight, cp.hudalign)

--
if (new_controlling_team ~= Team.kUnassigned) then
AddHudIconToAll( icons[ new_controlling_team ].disabled, self.cp_number .. "-disabled-" .. new_controlling_team , cp.hudposx, cp.hudposy, cp.hudwidth, cp.hudheight, cp.hudalign)
end

-- Change valid spawns

if new_controlling_team == Team.kBlue then
cp_blue = self.cp_number
if old_controlling_team == Team.kRed then
cp_red = self.cp_number + 1
end
elseif new_controlling_team == Team.kRed then
cp_red = self.cp_number
if old_controlling_team == Team.kBlue then
cp_blue = self.cp_number - 1
end
end

cp.controlling_team = new_controlling_team

end

command_point_one = base_cp_trigger:new({ cp_number = 1 })
command_point_two = base_cp_trigger:new({ cp_number = 2 })
command_point_three = base_cp_trigger:new({ cp_number = 3 })
command_point_four = base_cp_trigger:new({ cp_number = 4 })
command_point_five = base_cp_trigger:new({ cp_number = 5 })

-------------------------
-- Re-enable disabled CP after RECAPTURE_DELAY (default 15 seconds)
-------------------------

function cp_reenable (cp, team)
RemoveHudItemFromAll( cp.cp_number .. "-disabled-" .. team )
cp.disable_capture = 0
end

function new_round_respawn()
ApplyToAll({ AT.kRemovePacks, AT.kRemoveProjectiles, AT.kRespawnPlayers, AT.kRemoveBuildables, AT.kRemoveRagdolls, kReloadClips })
end

-------------------------------------------
-- HUD information
-------------------------------------------

function flaginfo( player_entity )
local player = CastToPlayer( player_entity )

for i,v in ipairs(command_points) do

AddHudIcon( player, icons[ v.controlling_team ].teamicon , v.cp_number .. "-background-" .. v.controlling_team , command_points[v.cp_number].hudposx, command_points[v.cp_number].hudposy, command_points[v.cp_number].hudwidth, command_points[v.cp_number].hudheight, command_points[v.cp_number].hudalign)
AddHudIcon( player, command_points[v.cp_number].hudstatusicon, v.cp_number .. "-foreground-" .. v.controlling_team , command_points[v.cp_number].hudposx, command_points[v.cp_number].hudposy, command_points[v.cp_number].hudwidth, command_points[v.cp_number].hudheight, command_points[v.cp_number].hudalign)

end
end

-------------------------------------------
-- Round start functions
-------------------------------------------

function setup_door_timer(doorname, duration)
CloseDoor(doorname)
AddSchedule("round_opendoor_" .. doorname, duration, round_start, doorname)
AddSchedule("round_10secwarn", duration-10, round_10secwarn)
end

function round_start(doorname)
BroadCastMessage("Gates are now open!")
BroadCastSound( "otherteam.flagstolen" )
OpenDoor(doorname)
end

function round_10secwarn() BroadCastMessage("10 Seconds until round starts") end

-------------------------------------------
-- Spawnpoints + Respawn door Stuff
-------------------------------------------

-- Spawn Points
base_blue_spawn = info_ff_teamspawn:new({ cp = 0, validspawn = function(self,player)
return player:GetTeamId() == Team.kBlue and self.cp == cp_blue
end })
base_red_spawn = info_ff_teamspawn:new({ cp = 0, validspawn = function(self,player)
return player:GetTeamId() == Team.kRed and self.cp == cp_red
end })
bluespawn_cp1 = base_blue_spawn:new({cp=1})
bluespawn_cp2 = base_blue_spawn:new({cp=2})
bluespawn_cp3 = base_blue_spawn:new({cp=3})
bluespawn_cp4 = base_blue_spawn:new({cp=4})
redspawn_cp5 = base_red_spawn:new({cp=5})
redspawn_cp4 = base_red_spawn:new({cp=4})
redspawn_cp3 = base_red_spawn:new({cp=3})
redspawn_cp2 = base_red_spawn:new({cp=2})

-- Spawn Doors (base entity)
blue_respawn_door = trigger_ff_script:new({cp = 0})
red_respawn_door = trigger_ff_script:new({cp = 0})

-- Spawn Doors (validity checks)
function blue_respawn_door:allowed( allowed_entity )
if IsPlayer( allowed_entity ) then
local player = CastToPlayer( allowed_entity )
if player:GetTeamId() == Team.kBlue and self.cp <= cp_blue then
return EVENT_ALLOWED
end
end
return EVENT_DISALLOWED
end

function red_respawn_door:allowed( allowed_entity )
if IsPlayer( allowed_entity ) then
local player = CastToPlayer( allowed_entity )
if player:GetTeamId() == Team.kRed and self.cp >= cp_red then
return EVENT_ALLOWED
end
end
return EVENT_DISALLOWED
end

--Spawn Doors (Validity checks failure)
function blue_respawn_door:onfailtouch( touch_entity )
if IsPlayer( touch_entity ) then
local player = CastToPlayer( touch_entity )
if player:GetTeamId() == Team.kBlue then
BroadCastMessageToPlayer( player, "You need to capture Command Point ".. self.cp .. " before you can use this respawn!" )
else
BroadCastMessageToPlayer( player, "Your team cannot use this respawn." )
end
end
end

function red_respawn_door:onfailtouch( touch_entity )
if IsPlayer( touch_entity ) then
local player = CastToPlayer( touch_entity )
if player:GetTeamId() == Team.kRed then
BroadCastMessageToPlayer( player, "You need to capture Command Point ".. self.cp .." before you can use this respawn!" )
else
BroadCastMessageToPlayer( player, "Your team cannot use this respawn." )
end
end
end

-- Spawn Doors (actual entities with command point condition attached)
bluerespawn_cp2 = blue_respawn_door:new({cp=2})
bluerespawn_cp3 = blue_respawn_door:new({cp=3})
bluerespawn_cp4 = blue_respawn_door:new({cp=4})
redrespawn_cp2 = red_respawn_door:new({cp=2})
redrespawn_cp3 = red_respawn_door:new({cp=3})
redrespawn_cp4 = red_respawn_door:new({cp=4})
</pre>
 
==Overridable Globals==
(NOTE: Replace the values used in the code above with whats needed, defaults are as close to TFC Warpath as possible)
*NUMBER_OF_COMMAND_POINTS (Default: 5): Amount of command points in play.
*POINTS_FOR_COMPLETE_CONTROL (Default: 30): Team points scored for capturing all points.
*FORTPOINTS_FOR_COMPLETE_CONTROL (Default: 1000): Fortress points scored for capturing final point.
*FORTPOINTS_FOR_CAP (Default: 200): Fortress points scored for capturing a non-final point.
*INITIAL_ROUND_DELAY (Default: 45): Delay before start of first round (to give people time to log in).
*NORMAL_ROUND_DELAY (Default: 30): Delay before start of all other rounds.
*RECAPTURE_DELAY (Default: 15): Time a point is inactive for after being captured.
 
=Downloads=
*[http://www.dcpaterson.ukfsn.org/tutorials/warpath_example/warpath_example_v1.rar Source .vmf] (Includes .vmf of an example map, the Lua Script, and a custom HUD graphic used):

[[Category:Map Templates]] [[Category:Mapping]]
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area2 abovecap

2008-02-03T15:00:16Z

Pon: Wrote article/new image template/remove old navbox code

=Command Point Two, Above the CP=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp2_area2_abovecap.jpg]]
|caption = '''Above Command Point 2''' Good Sentry Gun positions (Red '''SG''') are shown, as is the the Command Point (Red '''X'''), the Jump Point (Blue '''JP'''), and the routes that the Attackers will most often take (Blue '''Arrows''').
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area2|../cp3_area1_spawn}}

==Defenders==

This are will likely get very chaotic, with Sentry Guns, rockets and grenades very often going off all around you. Keep a cool head, and concentrate on defending the Command Point. Sentry Guns often work well, countering jumps to the CP if placed well. Often though, the Command Point should also be covered by a pipe-trap, just to be safe and to stop Spies running a nearby dropped flag in before being tracked and killed by the Sentry Guns.

Heavy classes should concentrate on smothering threats that the Sentry Guns are ill-equipped to deal with - Spies, enemies at distance, and so forth. If ever given the opportunity, such as the flag returning, try to push the battleline back as much as possible, perhaps if lucky as far back as the grenades, or beyond.

==Attackers==

A jump to the Command Point is very often the quickest way to capture this point - but is not always possible against a well organised defence, and especially an Engineer-heavy defence. If the flag is dropped near the Command Point, it will likely become so well defended as to be untouchable - which may mean you lose ground while attempting to run the flag again.

Taking down Sentry Guns will likely be a priority, as usual Spies are useful in the role, but most other classes can help in this reguard as well, if they can find a good spot to attack from (around the back of the Command Point can provide good cover for this).

{{Navigation Map Guides}}

What Fortress Forever Is

2008-02-03T14:39:28Z

Pon: remove old infobox manual

==What is Fortress Forever?==

Fortress Forever is a '''FREE''' online, multiplayer, class-based mod for the Half-Life 2 PC game. It was originally created by a group of Team Fortress Classic(TFC) players. After many years of waiting for the Release of TF2, with limited to no information at the time regarding TF2's production, most of the TFC community considered TF2 vaporware. With no evidence of continued production of TF2, the community took the TFC sequel into their own hands.

The project's early stages began in early August of 2004, where planning and forming began. http://www.fortress-forever.com launched in late november of that year. With the launch of the website much interest was sparked within the community. With a final promise of a TFC sequel many fans of the series gathered in support behind the team. Roughly three years in the making, and Fortress Forever was finally released on September 13th, 2007.

==Gameplay==

===Classes===
Fortress Forever can accommodate many types of playing. Thanks to the class system, it's easy choosing a loadout that fits your playing style. Like to run into the enemy's base, grab the flag and run out before half of the enemy team notices you? Try the Scout. Like to pick-off things from far away, but want weapons that'll work if somebody gets too close? Play as the Sniper. Ever had the urge to gib people with an enormous rocket launcher? Play the Soldier. Not good at using big guns, but you love to plan where things will be and what will happen? Play as the Engineer.

===Weapons===
In Fortress Forever we offer a wide variety of weapons to use against your opponent. Every class has their standard uniform of weapons. Standard Melee: which is used as last resort, humiliation, or just for fun. Standard Gun: these are your standard shotguns, super shotguns, and nailguns, which are shared by many classes. Then we have our Specialty Weapons: these include everything from the medkit to the Sentry gun. These are the weapons that are class specific, and are what give a class its uniqueness. You can read more about these weapons by clicking on the class descriptions to the right of the page.

===Game Types===
Fortress Forever has a wide variety of gametypes. You can start off with Capture the Flag, where you must grab the flag in the enemy's base and bring it back to yours. If you feel that's too cliche, then try out Attack and Defend, where one team tries to take control of points while the defenders try to stop them. Or are you the type that wants to defend and control something? Give Territory Control a test drive, where players must successfully capture and defend points on a map. If you want something completely different, try out Hunted, where a weak civilian must be escorted to a point by bodyguards while assassins try to kill him. Wanna show off your skills? Try out a conc map, where players must strategically use grenades and jumping to overcome obstacles. Don't care about any of that crap? Chill out in deathmatch mode, where the only thing you have to worry about is killing enemies.

===Maps===
Fortress Forever has a large variety of maps. Wanna play CTF in monkey-themed ancient temples? Go to [[Map:ff_monkey|ff_monkey]]. Feel the need to capture control points in a futuristic arena? [[Map:ff_cz2|ff_cz2]] is waiting. In the mood to take control of a ghost town in the desert? [[Map:ff_dustbowl|ff_dustbowl]] is for you. Ever has the urge to spill some blood at a soccer arena? [[Map:ff_dm|ff_dm]] wants you!

===Modability===
Fortress Forever is extremely easy to mod, thanks to the LUA scripting language. With it, you can edit nearly everything, from how much ammo is in a backpack to floors that fling the player across the map. With some time, you can make new gamemodes, such as a race between two players, co-op maps that force players to work together to survive hazards and pass obstacles, and even golf.

In addition, you can make maps for Fortress Forever as soon as you install it. Fortress Forever uses Half-Life 2's resources in addition to custom-made ones, so there are plenty of themes for you to utilize in your maps, such as Combine, City 17, Wild West, urban and even classic Half-Life 1.

==See Also==

{stub}

Map:ff dustbowl/cp2 area2

2008-02-03T14:15:46Z

Pon: Wrote article/new image template/remove old navbox code

=Command Point Two, Towards the CP=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp2_area2.jpg]]
|caption = '''Towards the Command Point, Command Point 2''' Useful Sentry Gun positions (Red '''SG''') are shown, as well as the Extraroute Exit (Blue '''EX'''), a useful Jump Point (Blue '''JP''') and the routes that the Attackers will most often take (Blue '''Arrows''').
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_choke|../cp2_area2_abovecap}}

==Defenders==

The last area before the Command Point, this can be defended quite well given the right set up. Aside from the marked Sentry Gun positions, Heavy classes such as the Soldier, HWGuy, and Demomen (who can pipe-trap the Jump Point area, or the flag if dropped) are useful here, they will help in controlling the flow of Attackers through the area.

Once the Extraroute is open, be wary of the Attackers using it as a means to bypass defence in this area, or sneaking Spies in to take down the Sentry Guns. Often, a Soldier covering it exclusivly is desirable, as it is just too vulnerable to leave unguarded for any length of time.

Another useful tactic is to have a Sniper or two hang back near the Command Point, and cover the two main routes.

==Attackers==

Sentry Guns can be a problem here, they can be placed high which makes them a bit more aukward to counter with Grenades, and the compact nature of the area means you'll often find heavier classes breathing down your neck at the same time. Careful planning and co-ordinated rushes will likely help immensly in overcoming the Defence.

The Extraroute, once open, leads to the '''EX''' point shown in the picture, and from there you can run through the building and come out near the Command Point, which is useful for running the flag, Spies sneaking in to take down Sentry Guns, and very often just generally useful for most other classes as well, as it saves fighting through the area.

The Jump point is useful for Scouts (if they picked up concs), Medics (grenades or concs), and Demomen (two yellow pipes, can launch self or team member). Soldiers can make use of it also, but are often less effective.

{{Navigation Map Guides}}

Map:ff dustbowl/cp2 area1 choke

2008-02-03T12:16:01Z

Pon: Wrote article/new image template/remove navbox code

=Command Point Two, Towards the Chokepoints=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp2_area1_choke.jpg]]
|caption = '''Towards the Chokepoints, Command Point 2''' A defensive Sentry Gun position (Red '''SG''') is shown, as well as a useful Sniper position (Red '''SN'''), and the routes that the Attackers will most often take (Blue '''Arrows'''). The Grenade Pack for this Command Point is also shown (White '''G''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_spawn|../cp2_area2}}

==Defenders==

As the Grenade pack is in this area, you will likely want to hold this Command Point as long as possible. To that end, Heavy classes will be useful as when the Attackers get this far, you likely won't have many Sentry Guns ready, unless your team has a high number of Engineers.

The lone Sentry Gun position shown here isn't perfect by any means, but it can surprise the enemy if they aren't expecting it. Mostly though, it will be useful in delaying the enemy while the rest of your team bolsters their defences. There are other good Sentry Gun positions in this area, such as to the right of the chokepoint entrance, and inside the building in the centre of the picture (not marked).

The two central arrows show point in the direction of the two routes that the enemy must take. The one to the left (pointed at, but not shown directly) had a drop that you can knock the enemy into, whilst the central one (shown) houses the Extraroute on it's right side, and has normal exits to both the left and right.

Finally, the arrow on the leftmost side shows the route around the back of the building, a route often used as it is near the Grenades, and provides cover.

==Attackers==

Like the Defenders, you will likely seek to control the Grenades, as they can provide Concussion Grenades for making jumps to the Command Point, as well as providing an overall firepower advantage. Beware that even once you control them, the enemy might make a run for them, often with a Spy or Demoman - and if your flag ever returns, expect the entire team to try to puch back and regain control of them and try to counter it.

The routes you can take here are both fairly obvious and limited, until the Extraroute opens. Once it does, it provides a useful shortcut around the usually well-defended chokepoint exits, and can be useful in running the flag if the defence is strong in the main routes of the map.

{{Navigation Map Guides}}

Map:ff dustbowl/cp2 area1

2008-02-03T11:57:36Z

Pon: Article written/new image template/remove old navbox

=Command Point Two, Attackers Spawn Exit=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp2_area1.jpg]]
|caption = '''View from the Attackers Spawn, Command Point 2''' Defensive SG positions (Red '''SG''') are shown, as well as a useful Sniper position (Red '''SN'''), and the routes the attackers may find useful (Blue '''Arrows''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_spawn|../cp2_area1_choke}}

==Defenders==

Shown in this picture is another route that the Attacking team might take, in comparison to the last picture. The route is the one to the right side of the pciture, behind the building. This route is useful for Spies to sneak around, and up to the top of that building to take out Sentry guns, so it is always useful to keep an eye on it.

Another thing of note is the Sniper position, high up and to the back of the picture (it is also where the previous picture was taken from). It provides a good view of much of the area, as well as some protection from enemy fire, but is aukward to get to for a lone Sniper. A Grenade jump can make it, but you'll likely need to practice the jump before being able to do so reliably.

'''Note:''' The leftmost Sentry Gun position currently is not very useful in Fortress Forever v1.11. It has been included in this picture as it should be made usable in the upcoming v2.0 patch.

==Attackers==

Offensivly, once you get out from your spawn, the routes you can take should vary. The leftmost arrow shows a good route for Soldiers, and possibly Demomen, to sneak up behind some defenses and cause some real damage. The rightmost route is most useful to Spies, who can use it to sneak around the back of Sentry Guns placed on the nearby building - but it is also useful for other weaker classes such as Scouts, who can use it to avoid the fire they would come under if using the main route. Heavier and slower classes are often best taking the main route itself, as it is more direct - and they will likely do a better job of pushing the defence back so that the area is secured.

{{Navigation Map Guides}}

Map:ff dustbowl/cp2 area1 spawn

2008-02-03T10:09:19Z

Pon: Wrote article/new image template/remove navbox

=Command Point Two, Attackers Spawn=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp2_area1_spawn.jpg]]
|caption = '''View of the Attackers Spawn, Command Point 2''' Defensive SG positions (Red '''SG''') are shown, as well as a useful Sniper position (Red '''SN'''), and the routes that the Attackers will most often take (Blue '''Arrows''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area2|../cp2_area1}}

==Defenders==

Once again, dual exits from the spawn complicate things a little, but given that they are close together, it's not as bad as their first spawn - most sentrygun placements will be able to cover both exits well enough. The usual threats exist, such as Spies and Snipers attempting to remove your Sentry Guns as quickly as possible, so be on the lookout for those.

Demomen and HWguys can be used effectivly here. Demomen can be very effective in holding the entrance - pipebombs and MIRV's can be used to great effect if you know how. HWguys are also useful as there isn't much room to maneuver through the main route, and can mop up any stragglers that make it through the gates.

One notable threat to look out for is Soldiers rocketjumping up the right-most route shown in the picture. Left unchecked, they can do alot of damage to your defenses.

==Attackers==

For the attacking team, this is likely to be a rush to your death more often than not. Timing is the key - timing and patience - do not get frustrated and make silly mistakes. It will often be possible to have a few seconds to run out the exit in between the grenades, rockets, and pipebombs, and when it appears, it must be taken advantage of.

If possible, a Sniper taking potshots at the enemy Sentries, Demomen, and HWguys should be employed, as it can help immensly in breaking out. Otherwise, the best bet is to try and sneak out as a Spy, and take down their defenses from behind (possibly even sabotaging a sentry or two if the chance arises)

{{Navigation Map Guides}}

Map:ff dustbowl/cp1 area2

2008-02-03T09:39:49Z

Pon: Minor revision to picture description

=Command Point 1, Towards the CP=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp1_area2.jpg]]
|caption = '''View of Command Point One''' Defensive SG positions (Red '''SG''') are shown, as well as the Command Point (Red '''X'''), a good covering Sniper Spot (Red '''SN'''), and the most common offensive routes (Blue '''Arrows'''). Also shown is the Extraroute exit (Blue '''EX'''), Jump Points (Blue '''JP'''), and a good offensive Sniper position (Blue '''SN''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area2_abovecap|../cp2_area1_spawn}}

==Defenders==

Special attention should be paid to the Jump Points, as these provide an easy way to get the flag right up to the Command Point, if not capture it. A few people (or perhaps an SG, if you have many Engineer's on the team) covering the roofs can help prevent this - Snipers, Soldiers, and HWGuys all all pretty good classes in this role.

Another thing to watch for in this shot is the route denoted by the left-most arrow, through the building. This route can be used by Spies to sneak in quite effectivly - even more so when the Extraroute is open. It will also likely be used by other classes, often Soldiers and Medics who can use the door it leads to as a protected point to fire upon Sentry Guns. Someone sneaky may also try to run the flag down this route, though it is uncommon.

==Attackers==

As was noted in the previous picture, an early push before the enemy Sentries are set up is often the quickest way to Capture this point, and prevent being bogged down. Another tactic, though uncommonly used, is to run the flag through the building shown in the left of the picture, which runs most of the way to the Command Point - it can be risky though, as if the flag is dropped inside there, it is more easily defended than if it were dropped in the open.

If the Extraroute opens (shot above is shown from the Extraroute opening), it can provide a few benefits. It is a good spot for a Sniper - dark, out of harm, and with a good view - but is also good for a Spy to make a less conspicous entrance into the area. In the Fortress Forever version of Dustbowl, it is also even better than ever for usage as a secondary Jump point, but is more also more open and noticable than the other one marked upon the picture above.

{{Navigation Map Guides}}

Map:ff dustbowl/cp1 area2 abovecap

2008-02-03T09:38:59Z

Pon: removal of navbox, new image template

=Command Point One, Looking out from the Command Point=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp1_area2_abovecap.jpg]]
|caption = '''View from above Command Point One''' Defensive SG positions (Red '''SG''') are shown, as well as the Command Point (Red '''X'''), and the most common offensive routes (Blue '''Arrows'''). Also shown is the Extraroute exit (Blue '''EX'''), Jump Points (Blue '''JP'''), and a good offensive Sniper position (Blue '''SN''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1|../cp1_area2}}

==Defenders==

Defensivly, this can be hard to hold, especially if the Attackers have made a good, quick rush from the first area. Sentry Guns are often vital to hold this Command Point for a decent length of time, and as such, Spy defence is also important.

To give the team's Engineers time to prepare their sentry guns, much of the rest of the team should attempt to block the Attackers progress in the chokepoints for as long as is possible. If you have many Engineers on the team, some may wish to forego building their Sentry Guns near the Attackers Spawn in favour of making this area secure ahead of time.

Another major threat, once the Attackers are assaulting the Command Point directly, is from a Jump to Cap - often from the top of the buildings that house the chokepoint exits. Even if the jump is unsuccessful, if the flag is close to the cap, a Spy can easily run it before being taken down by a Sentry Gun. As with most AvD maps, the Command Point is often best "pipe trapped" by a Demoman in addition to any other defenses.

When the Extraroute opens, beware of Snipers hiding there, as well as Spies using it as a route to sneak in undetected.

==Attackers==

Speed is of the essence here, if you can run the flag into the area before the Defence is fully set up it can make this Command Point a lot easier to capture. Once it begins to get locked down, usually by Sentry Guns, then a Jump to Cap may be the best idea - you may not make it, but might get it into prime position for someone else to finish the job.

As the area is likely going to have 2+ Sentry Guns, a Spy or two will likely be very useful in this area (though too many Spies is most definitly a mistake, back them up with some heavier/faster classes). If you see an opening to sabotage a Sentry Gun, then by all means take it - but don't get "tunnel vision", a dead Sentry Gun is better than multiple failed sabotage atempts.

If your team chooses to walk the flag, then be prepared for a hard slog, and try to make a combined rush instead of all running to your death single-file. A Sniper providing cover from the extraroute can help immensly if this is your tactic.

{{Navigation Map Guides}}

Map:ff dustbowl/cp1 area1

2008-02-03T09:37:39Z

Pon: New image template, remove navbox

=Command Point One, Chokepoint Entrances=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp1_area1.jpg]]
|caption = '''Back end of the Attacker's Spawn area, Command point One''' Denoted are good defensive spots for Sentry Guns ("'''SG'''") and Snipers ("'''SN'''"), as well as the Extra route ("'''EX'''"), and the Grenades ("'''G'''").
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1_spawn|../cp1_area2_abovecap}}

==Defenders==

The Grenades here are an early advantage to the defending team, who can use them quite effectivly to spam and harass the attacking team as they leave their spawn. They aren't easy to defend once the attackers have broken through, however. If you can keep control of them however, it will give your Engineer's time to set up their Sentry Guns to defend the Command Point, so it is worth delaying the enemy as much as possible here to allow them the chance to do so properly.

The chokepoints, shown in the picture above by the Blue Arrows, lend themselves to protection by Soldiers, Demomen, and HWGuys. They can also be a good point for Pyro's to check for Spies - narrow corridors don't give cloaked Spies much room to avoid the flames.

==Attackers==

Conversly, for the attackers, it's very advantageous to carry momentum and break through quickly, to deny the enemy Engineer's the chance to get set up. If that can be done, the Command Point is often captured soon after.

In terms of routes to the cap, the one on the right is preferable in most circumstances, as the building it leads to houses a ladder to a roof, from which a Conc or Grenade jump can help to push the flag right to the Command Point, if not capture itself. If you get bogged down, and the Extra route opens however, it can provide a similar, but slightly more open and risky, platform for a jump as well - as well as a good vantage point for a sniper to take down defenses around the Command Point.

{{Navigation Map Guides}}

Map:ff dustbowl/cp1 area1 spawn

2008-02-03T09:35:49Z

Pon: Using new image template, removing right navbox

=Command Point One, Attackers Spawn=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp1_area1_spawn.jpg]]
|caption = '''Attacker's Spawn area, Command point One''' Denoted are good defensive spots for Sentry Guns ("'''SG'''"), as well as the routes the attacking team will be forced to use 90% of the time.
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../|../cp1_area1}}

==Defenders==

The spawn exit is split into two, fairly seperate openings - one low, and one high. As such, having to concentrate on both is a drawback to the defenders. Well placed snipers can help in this reguard, as well as the standard tactic of building Sentry Guns to cover the entrances (there are a few points where a Sentry can cover both exits effectivly). Demomen can also work wonders, with a well-timed detpack, and pipes covering the exits for early spy rushes.

==Attackers==

For the attackers, a good spy or two who can take out the Sentry guns usually helps immensly. A Sniper at the lower exit can also be useful against Sentries covering that exit - though they aren't much help at the higher exit, unless you can get around the back of the hut and into some cover.

{{Navigation Map Guides}}

Map:ff dustbowl/cp1 area2

2008-02-03T09:27:56Z

Pon: Revising article, using new image template, removing right-hand avigation

=Command Point 1, Towards the CP=
<center>
{{Image
|image = [[Image:Ff_dustbowl_cp1_area2.jpg]]
|caption = '''View from above Command Point One''' Defensive SG positions (Red '''SG''') are shown, as well as the Command Point (Red '''X'''), a good covering Sniper Spot (Red '''SN'''), and the most common offensive routes (Blue '''Arrows'''). Also shown is the Extraroute exit (Blue '''EX'''), Jump Points (Blue '''JP'''), and a good offensive Sniper position (Blue '''SN''')
}}
</center> 
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area2_abovecap|../cp2_area1_spawn}}

==Defenders==

Special attention should be paid to the Jump Points, as these provide an easy way to get the flag right up to the Command Point, if not capture it. A few people (or perhaps an SG, if you have many Engineer's on the team) covering the roofs can help prevent this - Snipers, Soldiers, and HWGuys all all pretty good classes in this role.

Another thing to watch for in this shot is the route denoted by the left-most arrow, through the building. This route can be used by Spies to sneak in quite effectivly - even more so when the Extraroute is open. It will also likely be used by other classes, often Soldiers and Medics who can use the door it leads to as a protected point to fire upon Sentry Guns. Someone sneaky may also try to run the flag down this route, though it is uncommon.

==Attackers==

As was noted in the previous picture, an early push before the enemy Sentries are set up is often the quickest way to Capture this point, and prevent being bogged down. Another tactic, though uncommonly used, is to run the flag through the building shown in the left of the picture, which runs most of the way to the Command Point - it can be risky though, as if the flag is dropped inside there, it is more easily defended than if it were dropped in the open.

If the Extraroute opens (shot above is shown from the Extraroute opening), it can provide a few benefits. It is a good spot for a Sniper - dark, out of harm, and with a good view - but is also good for a Spy to make a less conspicous entrance into the area. In the Fortress Forever version of Dustbowl, it is also even better than ever for usage as a secondary Jump point, but is more also more open and noticable than the other one marked upon the picture above.

{{Navigation Map Guides}}

Map:ff dustbowl/cp3 cparea2

2008-02-02T15:05:46Z

Pon: Updating navbox/picture

{{Infobox manual/Header}}

=Command Point Three, Above the Command Point=

[[Image:Ff_dustbowl_cp3_cparea2.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp3_cparea1|../}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 cparea1

2008-02-02T15:03:44Z

Pon: Updating navbox/picture

{{Infobox manual/Header}}

=Command Point Three, Towards the CP=

[[Image:Ff_dustbowl_cp3_cparea1.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp3_midmap2|../cp3_cparea2}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 midmap2

2008-02-02T15:02:36Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Three, Looking down the Midmap=

[[Image:Ff_dustbowl_cp3_midmap2.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp3_midmap1|../cp3_cparea1}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 midmap1

2008-02-02T15:01:21Z

Pon: Updating navbox/picture

{{Infobox manual/Header}}

=Command Point Three, Looking up the Midmap=

[[Image:Ff_dustbowl_cp3_midmap1.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp3_area1_back|../cp3_midmap2}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 area1 back

2008-02-02T14:59:50Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Three, Back of First Area=

[[Image:Ff_dustbowl_cp3_area1_back.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp3_area1_spawn|../cp3_midmap1}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 area1 spawn

2008-02-02T14:58:39Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Three, Attackers Spawn Exit=

[[Image:Ff_dustbowl_cp3_area1_spawn.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area2_abovecap|../cp3_area1_back}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area2 abovecap

2008-02-02T14:57:33Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Two, Above the CP=

[[Image:Ff_dustbowl_cp2_area2_abovecap.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area2|../cp3_area1_spawn}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area2

2008-02-02T14:56:11Z

Pon: Updated picture/navbox

{{Infobox manual/Header}}

=Command Point Two, Towards the CP=

[[Image:Ff_dustbowl_cp2_area2.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_choke|../cp2_area2_abovecap}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area1 choke

2008-02-02T14:54:08Z

Pon: Updated picture/navbox

{{Infobox manual/Header}}

=Command Point Two, Towards the Chokepoints=

[[Image:Ff_dustbowl_cp2_area1_choke.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_spawn|../cp2_area2}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area1

2008-02-02T14:52:39Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Two, Attackers Spawn Exit=

[[Image:Ff_dustbowl_cp2_area1.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp2_area1_spawn|../cp2_area1_choke}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp2 area1 spawn

2008-02-02T14:51:12Z

Pon: Updating picture/navbox

{{Infobox manual/Header}}

=Command Point Two, Attackers Spawn=

[[Image:Ff_dustbowl_cp2_area1_spawn.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area2|../cp2_area1}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

File:Ff dustbowl cp3 cparea2.jpg

2008-02-02T14:48:53Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp3 cparea1.jpg

2008-02-02T14:48:43Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp3 midmap2.jpg

2008-02-02T14:48:29Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp3 midmap1.jpg

2008-02-02T14:48:16Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp3 area1 back.jpg

2008-02-02T14:48:03Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp3 area1 spawn.jpg

2008-02-02T14:47:52Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp2 area2 abovecap.jpg

2008-02-02T14:47:33Z

Pon:

File:Ff dustbowl cp2 area2.jpg

2008-02-02T14:47:22Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp2 area1 spawn.jpg

2008-02-02T14:47:07Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp2 area1 choke.jpg

2008-02-02T14:46:53Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

File:Ff dustbowl cp2 area1.jpg

2008-02-02T14:46:39Z

Pon: Large Screenshot for FF_dustbowl mapguide

Large Screenshot for FF_dustbowl mapguide

Talk:Map:ff push

2008-02-02T12:39:50Z

Pon:

There are backpacks in this map, but they don't work for some reason. --[[User:Hirohito|Hirohito]] 21:42, 27 January 2008 (CST)

Here are some screenshots for anybody ready to make a guide: 
http://www.fortress-forever.com/wiki/Image:Ff_push0072.gif - Spawn Room. 
http://www.fortress-forever.com/wiki/Image:Ff_push0074.gif - Doors that lead to the rest of the map. 
http://www.fortress-forever.com/wiki/Image:Ff_push0083.gif - Where the door on the right leads to. 
http://www.fortress-forever.com/wiki/Image:Ff_push0075.gif - Where the door down the hall leads to. 
http://www.fortress-forever.com/wiki/Image:Ff_push0076.gif - Shot of area right before ball room. 
http://www.fortress-forever.com/wiki/Image:Ff_push0080.gif - The hallways (and lasers) that lead to the capture point room. 
http://www.fortress-forever.com/wiki/Image:Ff_push0080.gif - The resupply area. 
http://www.fortress-forever.com/wiki/Image:Ff_push0081.gif - The capture point. 
http://www.fortress-forever.com/wiki/Image:Ff_push0084.gif - Ball Room. 
http://www.fortress-forever.com/wiki/Image:Ff_push0085.gif - Another ball room view. 
http://www.fortress-forever.com/wiki/Image:Ff_push0086.gif - Area right before ball room. 
http://www.fortress-forever.com/wiki/Image:Ff_push0088.gif - Me running into the lasers. 

Um, guys? The images shown on the page are of gridiron. Fix. [[User:Greenday5494|Greenday5494]] 23:50, 1 February 2008 (CST)
:* They are placeholders until the article is written up properly. Feel free to help write it, you don't need to be on the Wiki Team to contribute! --[[User:Pon|Pon]] 06:39, 2 February 2008 (CST)

Map:ff dustbowl/cp1 area2

2008-02-01T13:06:26Z

Pon: Correcting the navbox, few other things

{{Infobox manual/Header}}

=Command Point 1, Towards the CP=

[[Image:Ff_dustbowl_cp1_area2.jpg|frame|center|View from above Command Point One. Defensive SG positions (Red '''SG''') are shown, as well as the Command Point (Red '''X'''), a good covering Sniper Spot (Red '''SN'''), and the most common offensive routes (Blue '''Arrows'''). Also shown is the Extraroute exit (Blue '''EX'''), Jump Points (Blue '''JP'''), and a good offensive Sniper position (Blue '''SN''')]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area2_abovecap|../cp2_area1_spawn}}

==Defenders==

The most critical thing for this area, usually, is for the team's Engineers to get their guns set up and ready before a major push from the Attackers take place. This often means that other classes should try to delay them in the chokepoints between here and the previous area. Snipers, positioned roughly where the above shot is taken (or perhaps a little further along the back wall), can also help delay anyone that gets through.

Special attention should be paid to the Jump Points, as these provide an easy way to get the flag right up to the Command Point, if not capture it. A few people (or perhaps an SG, if you have many Engineer's on the team) covering the roofs can help prevent this - Snipers, Soldiers, and HWGuys all all pretty good classes in this role.

As with most of the Command Point areas, Spies can be a nuisance. In this area particularly, there are a few good routes for them to sneak in under the radar, so it is worth being vigilant (but not paranoid).

==Attackers==

An early push, before the enemy Sentries are set up, is often the quickest way to Capture this point, and prevent being bogged down. A Jump from to the Command Point can also help break an existing deadlock - though you may not reach the CP yourself, if the flag is close enough, a Spy can run in and capture before their SG's take him down.

Overall, a Spy has many uses in this area, especially in the takedown of Sentry Guns. If you feel Sabotage is an option, then by all means go for it, but don't get "tunnel vision" - an SG removed is better than wasting time with failed Sabotage attempts.

If the Extraroute opens, it can provide a few benefits. It is a good spot for a Sniper - dark, out of harm, and with a good view - but is also good for a Spy to make a less conspicous entrance into the area. In the Fortress Forever version of Dustbowl, it is also even better than ever for usage as a secondary Jump point, but is more also more open and noticable than the other one marked upon the picture above.

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp1 area2 abovecap

2008-02-01T12:58:44Z

Pon: Filling in article

{{Infobox manual/Header}}

=Command Point One, Looking out from the Command Point=

[[Image:Ff_dustbowl_cp1_area2_abovecap.jpg|frame|center|View from above Command Point One. Defensive SG positions (Red '''SG''') are shown, as well as the Command Point (Red '''X'''), and the most common offensive routes (Blue '''Arrows'''). Also shown is the Extraroute exit (Blue '''EX'''), Jump Points (Blue '''JP'''), and a good offensive Sniper position (Blue '''SN''')]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1|../cp1_area2}}

==Defenders==

Defensivly, this can be hard to hold, especially if the Attackers have made a good, quick rush from the first area. Sentry Guns are often vital to hold this Command Point for a decent length of time, and as such, Spy defence is also important.

To give the team's Engineers time to prepare their sentry guns, much of the rest of the team should attempt to block the Attackers progress in the chokepoints for as long as is possible. If you have many Engineers on the team, some may wish to forego building their Sentry Guns near the Attackers Spawn in favour of making this area secure ahead of time.

Another major threat, once the Attackers are assaulting the Command Point directly, is from a Jump to Cap - often from the top of the buildings that house the chokepoint exits. Even if the jump is unsuccessful, if the flag is close to the cap, a Spy can easily run it before being taken down by a Sentry Gun. As with most AvD maps, the Command Point is often best "pipe trapped" by a Demoman in addition to any other defenses.

When the Extraroute opens, beware of Snipers hiding there, as well as Spies using it as a route to sneak in undetected.

==Attackers==

Speed is of the essence here, if you can run the flag into the area before the Defence is fully set up it can make this Command Point a lot easier to capture. Once it begins to get locked down, usually by Sentry Guns, then a Jump to Cap may be the best idea - you may not make it, but might get it into prime position for someone else to finish the job.

As the area is likely going to have 2+ Sentry Guns, a Spy or two will likely be very useful in this area (though too many Spies is most definitly a mistake, back them up with some heavier/faster classes). If you see an opening to sabotage a Sentry Gun, then by all means take it - but don't get "tunnel vision", a dead Sentry Gun is better than multiple failed sabotage atempts.

If your team chooses to walk the flag, then be prepared for a hard slog, and try to make a combined rush instead of all running to your death single-file. A Sniper providing cover from the extraroute can help immensly if this is your tactic.

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp1 area1

2008-02-01T12:35:57Z

Pon: /* Command Point One, Chokepoint Entrances */ Heading correction

{{Infobox manual/Header}}

=Command Point One, Chokepoint Entrances=

[[Image:Ff_dustbowl_cp1_area1.jpg|frame|center|Back end of the Attacker's Spawn area, Command point One. Denoted are good defensive spots for Sentry Guns ("'''SG'''") and Snipers ("'''SN'''"), as well as the Extra route ("'''EX'''"), and the Grenades ("'''G'''").]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1_spawn|../cp1_area2_abovecap}}

==Defenders==

The Grenades here are an early advantage to the defending team, who can use them quite effectivly to spam and harass the attacking team as they leave their spawn. They aren't easy to defend once the attackers have broken through, however. If you can keep control of them however, it will give your Engineer's time to set up their Sentry Guns to defend the Command Point, so it is worth delaying the enemy as much as possible here to allow them the chance to do so properly.

The chokepoints, shown in the picture above by the Blue Arrows, lend themselves to protection by Soldiers, Demomen, and HWGuys. They can also be a good point for Pyro's to check for Spies - narrow corridors don't give cloaked Spies much room to avoid the flames.

==Attackers==

Conversly, for the attackers, it's very advantageous to carry momentum and break through quickly, to deny the enemy Engineer's the chance to get set up. If that can be done, the Command Point is often captured soon after.

In terms of routes to the cap, the one on the right is preferable in most circumstances, as the building it leads to houses a ladder to a roof, from which a Conc or Grenade jump can help to push the flag right to the Command Point, if not capture itself. If you get bogged down, and the Extra route opens however, it can provide a similar, but slightly more open and risky, platform for a jump as well - as well as a good vantage point for a sniper to take down defenses around the Command Point.

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp1 area1

2008-02-01T12:33:58Z

Pon: Adding navigation

{{Infobox manual/Header}}

=Command Point One, Attackers Spawn=

[[Image:Ff_dustbowl_cp1_area1.jpg|frame|center|Back end of the Attacker's Spawn area, Command point One. Denoted are good defensive spots for Sentry Guns ("'''SG'''") and Snipers ("'''SN'''"), as well as the Extra route ("'''EX'''"), and the Grenades ("'''G'''").]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1_spawn|../cp1_area2_abovecap}}

==Defenders==

The Grenades here are an early advantage to the defending team, who can use them quite effectivly to spam and harass the attacking team as they leave their spawn. They aren't easy to defend once the attackers have broken through, however. If you can keep control of them however, it will give your Engineer's time to set up their Sentry Guns to defend the Command Point, so it is worth delaying the enemy as much as possible here to allow them the chance to do so properly.

The chokepoints, shown in the picture above by the Blue Arrows, lend themselves to protection by Soldiers, Demomen, and HWGuys. They can also be a good point for Pyro's to check for Spies - narrow corridors don't give cloaked Spies much room to avoid the flames.

==Attackers==

Conversly, for the attackers, it's very advantageous to carry momentum and break through quickly, to deny the enemy Engineer's the chance to get set up. If that can be done, the Command Point is often captured soon after.

In terms of routes to the cap, the one on the right is preferable in most circumstances, as the building it leads to houses a ladder to a roof, from which a Conc or Grenade jump can help to push the flag right to the Command Point, if not capture itself. If you get bogged down, and the Extra route opens however, it can provide a similar, but slightly more open and risky, platform for a jump as well - as well as a good vantage point for a sniper to take down defenses around the Command Point.

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Talk:How to make a server

2008-01-31T11:20:52Z

Pon:

*I am thinking about making an IRC channel for the wiki. I know that Squeek idle's in #ffwiki on gamesurge and quakenet. What do you guys think about making it an actual channel with help options? [[User:DrSatan-12955|DrSatan-12955]] 23:48, 19 January 2008 (CST)

* Ok this is getting pretty big. Any ideas / suggestions on how I can chop this down a bit? If you guys think it looks ok then that's fine by me, but it seems to be getting rather large and I'm not sure if we want that or not. I'm sure I can make more pages to account for it and what not, but let me know if you think I need to or not! [[User:DrSatan-12955|DrSatan-12955]] 02:37, 20 January 2008 (CST)
:* Maybe cut down the ammount of headings you use. For example, the types of server could just be given a short paragraph each, instead of each one with it's own heading. I think if you get the size of the contents box down a bit it might look a bit better and give the illusion that it's not such a long article --[[User:Pon|Pon]] 05:20, 31 January 2008 (CST)

Template:Guide Navbox/Mapguide

2008-01-30T02:30:31Z

Pon: Undo revision 6803 by Pon (Talk) Link problem NOT MY FAULT! (for once! :p)

{| align="center" style="width:200px; border: 1px solid #000000; background-color: #f5faff;" cellpadding="5" cellspacing="0"
|-
! colspan="3" style="background: #dce7ed; padding:0 1em;" align="center" width="100%"|'''{{{1}}} Mapguide'''
|-
| [[{{{2}}}|←]]
! align="center" width="75%"|[[../|Main Article]]
| [[{{{3}}}|→]]
|}

<noinclude>
==How to use this template==

'''Usage:''' <pre>{{Guide Navbox/Mapguide|1|2|3}}</pre>

'''Variables:'''

'''1''' - Title of Navbox, e.g. ''Well'' 
'''2''' - Backwards link, e.g. ''../bases'' 
'''3''' - Forward link, e.g. ''../yard'' 
</noinclude>

Template:Guide Navbox/Mapguide

2008-01-30T02:16:14Z

Pon: Small issue with links

{| align="center" style="width:200px; border: 1px solid #000000; background-color: #f5faff;" cellpadding="5" cellspacing="0"
|-
! colspan="3" style="background: #dce7ed; padding:0 1em;" align="center" width="100%"|'''{{{1}}} Mapguide'''
|-
| [[../{{{2}}}|←]]
! align="center" width="75%"|[[../|Main Article]]
| [[../{{{3}}}|→]]
|}

<noinclude>
==How to use this template==

'''Usage:''' <pre>{{Guide Navbox/Mapguide|1|2|3}}</pre>

'''Variables:'''

'''1''' - Title of Navbox, e.g. ''Well'' 
'''2''' - Backwards link, must be subpage of main article, e.g. ''bases'' 
'''3''' - Forward link, must be subpage of main article ''yard'' 
</noinclude>

Map:ff dustbowl/cp1 area2

2008-01-30T02:10:42Z

Pon: Adding correct Pic/Info

{{Infobox manual/Header}}

=Placeholder=

[[Image:Ff_dustbowl_cp1_area2.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../cp1_area1|../cp1_area2}}

==Defenders==

The most critical thing for this area, usually, is for the team's Engineers to get their guns set up and ready before a major push from the Attackers take place. This often means that other classes should try to delay them in the chokepoints between here and the previous area. Snipers, positioned roughly where the above shot is taken (or perhaps a little further along the back wall), can also help delay anyone that gets through.

Special attention should be paid to the Jump Points, as these provide an easy way to get the flag right up to the Command Point, if not capture it. A few people (or perhaps an SG, if you have many Engineer's on the team) covering the roofs can help prevent this - Snipers, Soldiers, and HWGuys all all pretty good classes in this role.

As with most of the Command Point areas, Spies can be a nuisance. In this area particularly, there are a few good routes for them to sneak in under the radar, so it is worth being vigilant (but not paranoid).

==Attackers==

An early push, before the enemy Sentries are set up, is often the quickest way to Capture this point, and prevent being bogged down. A Jump from to the Command Point can also help break an existing deadlock - though you may not reach the CP yourself, if the flag is close enough, a Spy can run in and capture before their SG's take him down.

Overall, a Spy has many uses in this area, especially in the takedown of Sentry Guns. If you feel Sabotage is an option, then by all means go for it, but don't get "tunnel vision" - an SG removed is better than wasting time with failed Sabotage attempts.

If the Extraroute opens, it can provide a few benefits. It is a good spot for a Sniper - dark, out of harm, and with a good view - but is also good for a Spy to make a less conspicous entrance into the area. In the Fortress Forever version of Dustbowl, it is also even better than ever for usage as a secondary Jump point, but is more also more open and noticable than the other one marked upon the picture above.

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 cparea2

2008-01-30T01:42:50Z

Pon: Last of the Placeholders!

{{Infobox manual/Header}}

=Command Point One, Looking out from the Command Point=

[[Image:Ff_dustbowl_cp1_area2_abovecap.jpg|frame|center|Placeholder Page. Navigation box below not setup correctly yet]]
{{Guide Navbox/Mapguide|Dustbowl Valley|../|../cp1_area1}}

==Defenders==

Placeholder

==Attackers==

Placeholder

{{Navigation Map Guides}}
{{Infobox manual/Footer}}

Map:ff dustbowl/cp3 cparea1

2008-01-30T01:42:20Z

Pon: Penultimate Placeholder Page

Map:ff dustbowl/cp3 midmap2

2008-01-30T01:41:49Z

Pon: Placeholder, again

Map:ff dustbowl/cp3 midmap1

2008-01-30T01:41:27Z

Pon: Placeholder page...

Map:ff dustbowl/cp3 area1 back

2008-01-30T01:40:47Z

Pon: Again with the placeholdings

Map:ff dustbowl/cp3 area1 spawn

2008-01-30T01:40:23Z

Pon: Placeholder page

Map:ff dustbowl/cp2 area2

2008-01-30T01:39:47Z

Pon: Placeholder page... yawn