Empires Wiki - User contributions [en]

Falcon Firearms Mark 10

2019-10-31T11:22:55Z

Lightning:

== NOTE - This page is WIP by Lightning, Currently working out formatting and layout for other weapon pages.==
{{Infobox Infantry Weapon
|Picture = BE_PISTOL1_1.png
|Name = 'X' Pistol / Mark 10
|InService = 153-AGC - Present
|UsedBy = Brenodi Empire, Civilan Market
|Classes = Rifleman, Engineer, Grenadier, Scout
|Designer = [[Falcon Firearms Incorporated|Falcon Firearms Incorporated]]
|Designed = 148-AGC
|Manufacturer = [[Falcon Firearms Incorporated|Falcon Firearms Incorporated]]
|Produced = 151-AGC
|Variants = Mark 10, Mark 12, Model 'X'
|Cartridge = [[.40 Falcon|.40 Falcon]],[[9mm Brenodi|9mm Brenodi]]
|Calibre = .40, 9x18mm
|Action = Short Recoil, Double-Action Only
|ROF = 300 RPM
|Range = 50M, 100 Max
|FeedSystem =
12 Round Box Magazine (.40)
15 Round Box Magazine (9MM)
|Sights = Double-Post Holographic
}}

== History ==
When Brenodian troops came up against [[Northern Faction]] Special Forces, it was found the current Mark 9 Pistol was insufficient for dealing with modern threats. The Military Acquisition Board of the Brenodian Military put out a formal request in 148-AGC to all manufacturers to come up with a new 'Mark 10' Sidearm for the Military. Several Sidearms were put forward towards this military trial two years later in 150-AGC. Ultimately the submission by Falcon Firearms survived all tests of the trials, capable of penetrating the new Northern Faction's Body Armor at 50 Meters utilizing a new proprietary cartridge, the [[.40 Falcon]]. Which was a massive improvement in ballistic capability over the older [[9mm Brenodi]] Cartridge.

[[Category:Weapons|Lore]]

Falcon Firearms Mark 10

2019-10-30T23:05:21Z

Lightning:

.40 Falcon

2019-10-30T20:13:46Z

Lightning:

The .40 Falcon was Developed along side the [[Falcon Firearms Mark 10]] Sidearm in order to meet the new standards faced by Northern Faction body armor

Falcon Firearms Mark 10

2019-10-30T20:11:31Z

Lightning: Created page with "== NOTE - This page is WIP by Lightning, Currently working out formatting and layout for other weapon pages.== {{Infobox Infantry Weapon |Picture = BE_PISTOL1_1.jpg |Name = 'X..."

== NOTE - This page is WIP by Lightning, Currently working out formatting and layout for other weapon pages.==
{{Infobox Infantry Weapon
|Picture = BE_PISTOL1_1.jpg
|Name = 'X' Pistol / Mark 10
|InService = 153-AGC - Present
|UsedBy = Brenodi Empire, Civilan Market
|Classes = Rifleman, Engineer, Grenadier, Scout
|Designer = [[Falcon Firearms Incorporated|Falcon Firearms Incorporated]]
|Designed = 148-AGC
|Manufacturer = [[Falcon Firearms Incorporated|Falcon Firearms Incorporated]]
|Produced = 151-AGC
|Variants = Mark 10, Mark 12, Model 'X'
|Cartridge = [[.40 Falcon|.40 Falcon]],[[9mm Brenodi|9mm Brenodi]]
|Calibre = .40, 9x18mm
|Action = Short Recoil, Double-Action Only
|ROF = 300 RPM
|Range = 50M, 100 Max
|FeedSystem =
12 Round Box Magazine (.40)
15 Round Box Magazine (9MM)
|Sights = Double-Post Holographic
}}

== History ==
When Brenodian troops came up against [[Northern Faction]] Special Forces, it was found the current Mark 9 Pistol was insufficient for dealing with modern threats. The Military Acquisition Board of the Brenodian Military put out a formal request in 148-AGC to all manufacturers to come up with a new 'Mark 10' Sidearm for the Military. Several Sidearms were put forward towards this military trial two years later in 150-AGC. Ultimately the submission by Falcon Firearms survived all tests of the trials, capable of penetrating the new Northern Faction's Body Armor at 50 Meters utilizing a new proprietary cartridge, the [[.40 Falcon]]. Which was a massive improvement in ballistic capability over the older [[9mm Brenodi]] Cartridge.

Weapons of the Brenodi Empire

2019-10-30T20:09:33Z

Lightning:

{{Sitenav|Weapons}}

'''Brenodi Empire Weapons Appendix'''

{{Note|As of 1.08, most weapons have seen balance changes and new visuals. Images shown here may have been replaced by improved versions.}}

== '''Pistols''' ==
'''Pistols are semi-automatic weapons designed for close quarter combat, although they can sometimes prove quite useful over longer ranges.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_PISTOL1_1.jpg|thumb|left|Falcon Manufacturing "X" Pistol]][[Image:BE_PISTOL1_2.jpg|thumb|left|Falcon Manufacturing "X" Pistol]] ||
{|
| colspan="2" | '''[[Falcon Firearms Mark 10|Falcon Firearms Mark 10]]'''
|-
| colspan="2" | Standard issue Brenodi pistol. Useful in a pinch.
|-
| colspan="2" | Falcon Manufacturing's X model is the tenth in their line of semi-automatic pistols manufactured exclusively for the Imperial Army.
|-
| width="100px" | Damage || 30
|-
| Clip Size || 14
|-
| Carry Limit || 24 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 300 Rounds Per Minute
|-
| Fire Mode || Semi-Automatic
|-
| Class || [[Engineer]], [[Scout]], [[Grenadier]], [[Rifleman]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_PISTOL2_1.jpg|thumb|left|Falcon Manufacturing "Tundra Falcon" Pistol]][[Image:BE_PISTOL2_2.jpg|thumb|left|Falcon Manufacturing "Tundra Falcon" Pistol]] ||
{|
| colspan="2" | '''Falcon Manufacturing "Tundra Falcon" Pistol'''
|-
| colspan="2" | A higher caliber version of its counterpart. It has a smaller clip, but each shot deals more damage.
|-
| colspan="2" | The "Tundra Falcon" earned it's name from it's use in the capture of [[Map:emp_glycencity|Glycen City]].
|-
| width="100px" | Damage || 40
|-
| Clip Size || 10
|-
| Carry Limit || 24 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 130 Rounds Per Minute
|-
| Fire Mode || Semi-Automatic
|-
| Class || [[Grenadier]], [[Rifleman]]
|}
|}

== '''Submachine Guns''' ==
'''Submachine Guns are automatic weapons designed for close to medium quarter combat. They have a high rate of fire, but a low damage potential.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_SMG1_1.jpg|thumb|left|Kren Industrial KR-3 SMG]][[Image:BE_SMG1_2.jpg|thumb|left|Kren Industrial KR-3 SMG]] ||
{|
| colspan="2" | '''Kren Industrial KR-3'''
|-
| colspan="2" | Standard issue SMG. Accurate but weak.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 24
|-
| Clip Size || 30
|-
| Carry Limit || 120 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 600 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Engineer]], [[Scout]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_SMG2_1.jpg|thumb|left|Kren Industrial NZ-0 SMG]][[Image:BE_SMG2_2.jpg|thumb|left|Kren Industrial NZ-0 SMG]] ||
{|
| colspan="2" | '''Kren Industrial NZ-0'''
|-
| colspan="2" | An average SMG with a good balance of firepower and accuracy.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 14
|-
| Clip Size || 30
|-
| Carry Limit || 120 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 700 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Engineer]], [[Scout]]
|}
|}

== '''Assault Rifles''' ==
'''Rifles are (semi-)automatic weapons that are designed for all-range combat. They have a high rate of fire and a high damage potential.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_RIFLE1_1.jpg|thumb|left|Brenodi Empire L3 Assault Rifle]][[Image:BE_RIFLE1_2.jpg|thumb|left|Brenodi Empire L3 Standard Issue Assault Rifle]] ||
{|
| colspan="2" | '''Kren Industrial L3 Assault Rifle'''
|-
| colspan="2" | The standard issue ranged rifle with iron sights for improved accuracy at range.
|-
| colspan="2" | Kren Industrial's L3 Assault Rifle is the flagship rifle of the Imperial Army. The successor to the L2, the L3 was developed during the uprising of the Northern Faction. Differences between the L2 and L3 include the new ironsight aiming system, which allows for greater accuracy at long range. Some soldiers have complained that the ironsights block all peripheral vision, but others believe they are a welcome addition.
|-
| width="100px" | Damage || 35
|-
| Clip Size || 30
|-
| Carry Limit || 150 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 1080 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_RIFLE2_1.jpg|thumb|left|Brenodi Empire L3-TUC3 Heavy Assault Rifle]][[Image:BE_RIFLE2_2.jpg|thumb|left|Brenodi Empire L3-TUC3 Heavy Assault Rifle]] ||
{|
| colspan="2" | '''Kren Industrial L3-TUC3 Heavy Assault Rifle'''
|-
| colspan="2" | The TUC3 variant of the L3 assault rifle is chambered for larger rounds and modified with a larger clip.
|-
| colspan="2" | TUC3 stands for Total Urban Combat, and of course, is the successor to the L2-TUC2 rifle of the Kolntus-Emin war.
|-
| width="100px" | Damage || 50
|-
| Clip Size || 40
|-
| Carry Limit || 150 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 920 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

== '''Machine Guns''' ==

{|
|- valign="top"
| width="450px" | ||
{|
| colspan="2" | '''Kren Industrial DU-7 "The Duke" Heavy Machine Gun'''
|-
| colspan="2" | Equipped with a very large clip, this machine gun is ideal for suppressive fire.
|-
| colspan="2" | "The Duke" got it's name from the sheer power of the .50 BMG rounds it uses.
|-
| width="100px" | Damage || 25
|-
| Clip Size || 200
|-
| Carry Limit || 400 Rounds
|-
| Accuracy || Poor
|-
| Rate Of Fire || 920 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

== '''Ranged Rifles''' ==

{|
|- valign="top"
| width="450px" | [[Image:BE_RR_1.jpg|thumb|left|Falcon Manufacturing BZ-S Ranged Rifle]][[Image:BE_RR_2.jpg|thumb|left|Falcon Manufacturing BZ-S Ranged Rifle]] ||
{|
| colspan="2" | '''Falcon Manufacturing BZ-S Scout Rifle'''
|-
| colspan="2" | Ranged rifle equipped with a good zoom but a small clip.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 110
|-
| Clip Size || 15
|-
| Carry Limit || 60 Rounds
|-
| Accuracy || Excellent
|-
| Rate Of Fire || 48 Rounds Per Minute
|-
| Fire Mode || Bolt Action
|-
| Class || [[Scout]]
|}
|}

== '''Anti-tank Weapons''' ==

''Kren Industrial's DA-M14N Anti-Tank weapon has two selectable modes. It functions as a long range guided Rocket Launcher and as an arc-fired Mortar. A group of Imperial scouts has learned that the Northern Faction are secretly building an Air Force, and as a result, all DA-M14N's will soon be retrofitted with Anti-Air capabilities.''

{|
|- valign="top"
| width="450px" | [[Image:BE_MORTAR_1.jpg|thumb|left|Brenodi Empire DA-M14N Anti-Tank Weapon - Rocket Launcher]][[Image:BE_MORTAR_2.jpg|thumb|left|Brenodi Empire DA-M14N Anti-Tank Weapon - Mortar]] ||
{|
| colspan="2" | '''Kren Industrial DA-M14N - Rocket Launcher Configuration'''
|-
| colspan="2" | Guided rocket launcher, well suited to the anti-armor role.
|-
| colspan="2" |
|-
| width="100px" | Damage || 80
|-
| Clip Size || 1
|-
| Carry Limit || 5 Rockets
|-
| Accuracy || Good
|-
| Rate Of Fire || 20 Rockets Per Minute
|-
| Class || [[Grenadier]]
|}
|}

{|
|- valign="top"
| width="450px" | ||
{|
| colspan="2" | '''Kren Industrial DA-M14N - Mortar Configuration'''
|-
| colspan="2" | Long range mortar that must be propped in a crouch before firing. Its range makes it ideal for destroying structures.
|-
| colspan="2" |
|-
| width="100px" | Damage || 110
|-
| Clip Size || 1
|-
| Carry Limit || 10 Rounds
|-
| Accuracy || Excellent
|-
| Rate Of Fire || 15 Rounds Per Minute
|-
| Class || [[Grenadier]]
|}
|}

== '''Explosives''' ==

{|
|- valign="top"
| width="450px" | [[Image:BE_MINE_1.jpg|thumb|left|Brenodi Empire Mine (Side)]][[Image:BE_MINE_2.jpg|thumb|left|Brenodi Empire Mine (Top)]] ||
{|
| colspan="2" | '''Brenodi Mine'''
|-
| colspan="2" | Defensive landmine that is effective for infantry and armor.
|-
| width="100px" | Damage || 110
|-
| Carry Limit || 5 Mines
|-
| Class || [[Grenadier]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_GREN.jpg|thumb|left|Brenodi Empire Standard Issue Grenade]] ||
{|
|-
| colspan="2" | '''Concussion Grenade'''
|-
| colspan="2" | A blinding flash grenade that effects turrets and infantry.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Scout]]
|-
| colspan="2" | '''Explosive Grenade'''
|-
| colspan="2" | A frag grenade that damages armor, buildings and infantry (damage dealt to buildings is reduced by 10).
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Rifleman]]
|-
| colspan="2" | '''Seismic Grenade'''
|-
| colspan="2" | Extremely effective at destroying buildings and defensive structures.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Engineer]]
|-
| colspan="2" | '''Smoke Grenade'''
|-
| colspan="2" | Effective for assaults or temporary visual cover.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Scout]]
|-
|}
|}

{{Tip|You can prime grenades. All grenades have a fuse of 6 seconds (except the concussion grenade, it has a fuse of 4 seconds). Just hold the grenade as long as you deem necessary. When released, the fuse will keep running, and the grenade will explode prematurely. Use this to your advantage to give the enemy no chance to escape. A grenade will always retain a minimum fuse of 2 seconds. You cannot blow yourself up when priming a grenade.}}

== '''Equipment''' ==
'''Equipment are all hand-held objects that may prove useful to the playing class. '''

{|
|- valign="top"
| width="450px" | [[Image:BE_BINOC.jpg|thumb|left|Brenodi Empire Binoculars]]||
{|
| colspan="2" | '''Binoculars'''
|-
| colspan="2" | Used to observe enemy activity and call in strikes.
|-
| width="100px" | Class || [[Scout]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_TOOL_2.jpg|thumb|left|Brenodi Empire Engineer Tool]][[Image:BE_TOOL_3.jpg|thumb|left|Brenodi Empire Engineer Tool]] ||
{|
| colspan="2" | '''Engineer Tool'''
|-
| colspan="2" | Used to build structures, heal units or deconstruct enemy structures / vehicles. Also used to place [[turrets]], [[walls]], [[Surveillance | surveillance gear]] and [[Ammo_Crates | ammo crates]].
|-
| width="100px" | Damage || 26
|-
| Class || [[Engineer]]
|}
|}

[[Category:Gameplay]] [[Category:Weapons]]

.40 Falcon

2019-10-30T20:01:25Z

Lightning: Created page with "test"

test

Template:Infobox Infantry Weapon

2019-10-30T19:55:39Z

Lightning:

{| style="float: right;" class="wikitable"
|+ Weapon
|-
! colspan="2" | {{{Name}}}
|-
| align="center" colspan="2" | [[File:{{{Picture}}}|200px|{{{Picture}}}]]
|-
! colspan="2" | Service History
|-
! In Service
| {{{InService}}}
|-
! Used By
| {{{UsedBy}}}
|-
! Classes
| {{{Classes}}}
|-
! colspan="2" | Production History
|-
! Designer
| {{{Designer}}}
|-
! Designed
| {{{Designed}}}
|-
! Manufacturer
| {{{Manufacturer}}}
|-
! Produced
| {{{Produced}}}
|-
! Variants
| {{{Variants}}}
|-
! colspan="2" | Specifications
|-
! Cartridge
| {{{Cartridge}}}
|-
! Calibre
| {{{Calibre}}}
|-
! Action
| {{{Action}}}
|-
! Rate of Fire
| {{{ROF}}}
|-
! Effective Range
| {{{Range}}}
|-
! Feed System
| {{{FeedSystem}}}
|-
! Sights
| {{{Sights}}}
|-
|}

Template:Infobox Infantry Weapon

2019-10-30T19:46:21Z

Lightning:

{| style="float: right;" class="wikitable"
|+ Weapon
|-
! colspan="2" | {{{Name}}}
|-
| align="center" colspan="2" | [[File:{{{Picture}}}|200px|{{{Picture}}}]]
|-
! colspan="2" | Service History
|-
! In Service
| {{{InService}}}
|-
! Used By
| {{{UsedBy}}}
|-
! colspan="2" | Production History
|-
! Designer
| {{{Designer}}}
|-
! Designed
| {{{Designed}}}
|-
! Manufacturer
| {{{Manufacturer}}}
|-
! Produced
| {{{Produced}}}
|-
! Variants
| {{{Variants}}}
|-
! colspan="2" | Specifications
|-
! Cartridge
| {{{Cartridge}}}
|-
! Calibre
| {{{Calibre}}}
|-
! Action
| {{{Action}}}
|-
! Rate of Fire
| {{{ROF}}}
|-
! Effective Range
| {{{Range}}}
|-
! Feed System
| {{{FeedSystem}}}
|-
! Sights
| {{{Sights}}}
|-
|}

Templates

2019-10-30T12:11:41Z

Lightning:

{{Sitenav|Templates}}

The following templates may be used within the wiki pages to reduce redundancy and allow for easy mass updates.
== Templates ==
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%"
|-
| [[Template:Do|Do]]
| [[Special:Whatlinkshere/Template:Do|backlinks]]
| {{Do|some text}}
|-
| [[Template:Fixme|Fixme]]
| [[Special:Whatlinkshere/Template:Fixme|backlinks]]
| {{Fixme|some text}}
|-
| [[Template:Inuse|Inuse]]
| [[Special:Whatlinkshere/Template:Inuse|backlinks]]
| {{Inuse}}
|-
| [[Template:See|See]]
| [[Special:Whatlinkshere/Template:See|backlinks]]
| {{See|[[some text]]}}
|-
| [[Template:Stub|Stub]] ([[Stub|topic]])
| [[Special:Whatlinkshere/Template:Stub|backlinks]]
| {{stub}}
|-
| [[Template:Note|Note]]
| [[Special:Whatlinkshere/Template:Note|backlinks]]
| {{Note|some text}}
|-
| [[Template:Tip|Tip]]
| [[Special:Whatlinkshere/Template:Tip|backlinks]]
| {{Tip|some text}}
|-
| [[Template:Warning|Warning]]
| [[Special:Whatlinkshere/Template:Warning|backlinks]]
| {{Warning|some text}}
|-
| [[Template:Wrongtitle|Wrongtitle]]
| [[Special:Whatlinkshere/Template:Wrongtitle|backlinks]]
| {{Wrongtitle|some_text}}
|-
| [[Template:Sitenav|Sitenav]]
| [[Special:Whatlinkshere/Template:Sitenav|backlinks]]
| {{Sitenav|Templates}}
|-
| [[Template:SitenavNested|SitenavNested]]
| [[Special:Whatlinkshere/Template:SitenavNested|backlinks]]
| {{SitenavNested|Special:Categories|Inbetween link}}
|}

= Infoboxes =
[[Template:Infobox_Infantry_Weapon|Infobox_Infantry_Weapon]]

Template:Infobox Infantry Weapon

2019-10-29T22:33:08Z

Lightning: Created page with "{| style="float: right;" class="wikitable" |+ Weapon |- ! colspan="2" | {{{Name}}} |- | align="center" colspan="2" | {{{Picture}}} |- ! colspan="2..."

{| style="float: right;" class="wikitable"
|+ Weapon
|-
! colspan="2" | {{{Name}}}
|-
| align="center" colspan="2" | [[File:{{{Picture}}}|200px|{{{Picture}}}]]
|-
! colspan="2" | {{{Service History}}}
|-
! In Service
| {{{InService}}}
|-
! Used By
| {{{UsedBy}}}
|-
! colspan="2" | {{{Production History}}}
|-
! Designer
| {{{Designer}}}
|-
! Designed
| {{{Designed}}}
|-
! Manufacturer
| {{{Manufacturer}}}
|-
! Produced
| {{{Produced}}}
|-
! Variants
| {{{Variants}}}
|-
! colspan="2" | {{{Production History}}}
|-
! Designer
| {{{Designer}}}
|-
|}

Weapons of the Brenodi Empire

2019-10-29T18:56:25Z

Lightning: Testing

{{Sitenav|Weapons}}

'''Brenodi Empire Weapons Appendix'''

{{Note|As of 1.08, most weapons have seen balance changes and new visuals. Images shown here may have been replaced by improved versions.}}

== '''Pistols''' ==
'''Pistols are semi-automatic weapons designed for close quarter combat, although they can sometimes prove quite useful over longer ranges.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_PISTOL1_1.jpg|thumb|left|Falcon Manufacturing "X" Pistol]][[Image:BE_PISTOL1_2.jpg|thumb|left|Falcon Manufacturing "X" Pistol]] ||
{|
| colspan="2" | '''[[Falcon Manufacturing "X" Pistol|Falcon Manufacturing X Pistol]]'''
|-
| colspan="2" | Standard issue Brenodi pistol. Useful in a pinch.
|-
| colspan="2" | Falcon Manufacturing's X model is the tenth in their line of semi-automatic pistols manufactured exclusively for the Imperial Army.
|-
| width="100px" | Damage || 30
|-
| Clip Size || 14
|-
| Carry Limit || 24 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 300 Rounds Per Minute
|-
| Fire Mode || Semi-Automatic
|-
| Class || [[Engineer]], [[Scout]], [[Grenadier]], [[Rifleman]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_PISTOL2_1.jpg|thumb|left|Falcon Manufacturing "Tundra Falcon" Pistol]][[Image:BE_PISTOL2_2.jpg|thumb|left|Falcon Manufacturing "Tundra Falcon" Pistol]] ||
{|
| colspan="2" | '''Falcon Manufacturing "Tundra Falcon" Pistol'''
|-
| colspan="2" | A higher caliber version of its counterpart. It has a smaller clip, but each shot deals more damage.
|-
| colspan="2" | The "Tundra Falcon" earned it's name from it's use in the capture of [[Map:emp_glycencity|Glycen City]].
|-
| width="100px" | Damage || 40
|-
| Clip Size || 10
|-
| Carry Limit || 24 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 130 Rounds Per Minute
|-
| Fire Mode || Semi-Automatic
|-
| Class || [[Grenadier]], [[Rifleman]]
|}
|}

== '''Submachine Guns''' ==
'''Submachine Guns are automatic weapons designed for close to medium quarter combat. They have a high rate of fire, but a low damage potential.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_SMG1_1.jpg|thumb|left|Kren Industrial KR-3 SMG]][[Image:BE_SMG1_2.jpg|thumb|left|Kren Industrial KR-3 SMG]] ||
{|
| colspan="2" | '''Kren Industrial KR-3'''
|-
| colspan="2" | Standard issue SMG. Accurate but weak.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 24
|-
| Clip Size || 30
|-
| Carry Limit || 120 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 600 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Engineer]], [[Scout]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_SMG2_1.jpg|thumb|left|Kren Industrial NZ-0 SMG]][[Image:BE_SMG2_2.jpg|thumb|left|Kren Industrial NZ-0 SMG]] ||
{|
| colspan="2" | '''Kren Industrial NZ-0'''
|-
| colspan="2" | An average SMG with a good balance of firepower and accuracy.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 14
|-
| Clip Size || 30
|-
| Carry Limit || 120 Rounds
|-
| Accuracy || Fair
|-
| Rate Of Fire || 700 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Engineer]], [[Scout]]
|}
|}

== '''Assault Rifles''' ==
'''Rifles are (semi-)automatic weapons that are designed for all-range combat. They have a high rate of fire and a high damage potential.'''

{|
|- valign="top"
| width="450px" | [[Image:BE_RIFLE1_1.jpg|thumb|left|Brenodi Empire L3 Assault Rifle]][[Image:BE_RIFLE1_2.jpg|thumb|left|Brenodi Empire L3 Standard Issue Assault Rifle]] ||
{|
| colspan="2" | '''Kren Industrial L3 Assault Rifle'''
|-
| colspan="2" | The standard issue ranged rifle with iron sights for improved accuracy at range.
|-
| colspan="2" | Kren Industrial's L3 Assault Rifle is the flagship rifle of the Imperial Army. The successor to the L2, the L3 was developed during the uprising of the Northern Faction. Differences between the L2 and L3 include the new ironsight aiming system, which allows for greater accuracy at long range. Some soldiers have complained that the ironsights block all peripheral vision, but others believe they are a welcome addition.
|-
| width="100px" | Damage || 35
|-
| Clip Size || 30
|-
| Carry Limit || 150 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 1080 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_RIFLE2_1.jpg|thumb|left|Brenodi Empire L3-TUC3 Heavy Assault Rifle]][[Image:BE_RIFLE2_2.jpg|thumb|left|Brenodi Empire L3-TUC3 Heavy Assault Rifle]] ||
{|
| colspan="2" | '''Kren Industrial L3-TUC3 Heavy Assault Rifle'''
|-
| colspan="2" | The TUC3 variant of the L3 assault rifle is chambered for larger rounds and modified with a larger clip.
|-
| colspan="2" | TUC3 stands for Total Urban Combat, and of course, is the successor to the L2-TUC2 rifle of the Kolntus-Emin war.
|-
| width="100px" | Damage || 50
|-
| Clip Size || 40
|-
| Carry Limit || 150 Rounds
|-
| Accuracy || Good
|-
| Rate Of Fire || 920 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

== '''Machine Guns''' ==

{|
|- valign="top"
| width="450px" | ||
{|
| colspan="2" | '''Kren Industrial DU-7 "The Duke" Heavy Machine Gun'''
|-
| colspan="2" | Equipped with a very large clip, this machine gun is ideal for suppressive fire.
|-
| colspan="2" | "The Duke" got it's name from the sheer power of the .50 BMG rounds it uses.
|-
| width="100px" | Damage || 25
|-
| Clip Size || 200
|-
| Carry Limit || 400 Rounds
|-
| Accuracy || Poor
|-
| Rate Of Fire || 920 Rounds Per Minute
|-
| Fire Mode || Fully Automatic
|-
| Class || [[Rifleman]]
|}
|}

== '''Ranged Rifles''' ==

{|
|- valign="top"
| width="450px" | [[Image:BE_RR_1.jpg|thumb|left|Falcon Manufacturing BZ-S Ranged Rifle]][[Image:BE_RR_2.jpg|thumb|left|Falcon Manufacturing BZ-S Ranged Rifle]] ||
{|
| colspan="2" | '''Falcon Manufacturing BZ-S Scout Rifle'''
|-
| colspan="2" | Ranged rifle equipped with a good zoom but a small clip.
|-
| colspan="2" | Story goes here.
|-
| width="100px" | Damage || 110
|-
| Clip Size || 15
|-
| Carry Limit || 60 Rounds
|-
| Accuracy || Excellent
|-
| Rate Of Fire || 48 Rounds Per Minute
|-
| Fire Mode || Bolt Action
|-
| Class || [[Scout]]
|}
|}

== '''Anti-tank Weapons''' ==

''Kren Industrial's DA-M14N Anti-Tank weapon has two selectable modes. It functions as a long range guided Rocket Launcher and as an arc-fired Mortar. A group of Imperial scouts has learned that the Northern Faction are secretly building an Air Force, and as a result, all DA-M14N's will soon be retrofitted with Anti-Air capabilities.''

{|
|- valign="top"
| width="450px" | [[Image:BE_MORTAR_1.jpg|thumb|left|Brenodi Empire DA-M14N Anti-Tank Weapon - Rocket Launcher]][[Image:BE_MORTAR_2.jpg|thumb|left|Brenodi Empire DA-M14N Anti-Tank Weapon - Mortar]] ||
{|
| colspan="2" | '''Kren Industrial DA-M14N - Rocket Launcher Configuration'''
|-
| colspan="2" | Guided rocket launcher, well suited to the anti-armor role.
|-
| colspan="2" |
|-
| width="100px" | Damage || 80
|-
| Clip Size || 1
|-
| Carry Limit || 5 Rockets
|-
| Accuracy || Good
|-
| Rate Of Fire || 20 Rockets Per Minute
|-
| Class || [[Grenadier]]
|}
|}

{|
|- valign="top"
| width="450px" | ||
{|
| colspan="2" | '''Kren Industrial DA-M14N - Mortar Configuration'''
|-
| colspan="2" | Long range mortar that must be propped in a crouch before firing. Its range makes it ideal for destroying structures.
|-
| colspan="2" |
|-
| width="100px" | Damage || 110
|-
| Clip Size || 1
|-
| Carry Limit || 10 Rounds
|-
| Accuracy || Excellent
|-
| Rate Of Fire || 15 Rounds Per Minute
|-
| Class || [[Grenadier]]
|}
|}

== '''Explosives''' ==

{|
|- valign="top"
| width="450px" | [[Image:BE_MINE_1.jpg|thumb|left|Brenodi Empire Mine (Side)]][[Image:BE_MINE_2.jpg|thumb|left|Brenodi Empire Mine (Top)]] ||
{|
| colspan="2" | '''Brenodi Mine'''
|-
| colspan="2" | Defensive landmine that is effective for infantry and armor.
|-
| width="100px" | Damage || 110
|-
| Carry Limit || 5 Mines
|-
| Class || [[Grenadier]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_GREN.jpg|thumb|left|Brenodi Empire Standard Issue Grenade]] ||
{|
|-
| colspan="2" | '''Concussion Grenade'''
|-
| colspan="2" | A blinding flash grenade that effects turrets and infantry.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Scout]]
|-
| colspan="2" | '''Explosive Grenade'''
|-
| colspan="2" | A frag grenade that damages armor, buildings and infantry (damage dealt to buildings is reduced by 10).
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Rifleman]]
|-
| colspan="2" | '''Seismic Grenade'''
|-
| colspan="2" | Extremely effective at destroying buildings and defensive structures.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Engineer]]
|-
| colspan="2" | '''Smoke Grenade'''
|-
| colspan="2" | Effective for assaults or temporary visual cover.
|-
| width="100px" | Carry Limit || 5 Grenades
|-
| Class || [[Scout]]
|-
|}
|}

{{Tip|You can prime grenades. All grenades have a fuse of 6 seconds (except the concussion grenade, it has a fuse of 4 seconds). Just hold the grenade as long as you deem necessary. When released, the fuse will keep running, and the grenade will explode prematurely. Use this to your advantage to give the enemy no chance to escape. A grenade will always retain a minimum fuse of 2 seconds. You cannot blow yourself up when priming a grenade.}}

== '''Equipment''' ==
'''Equipment are all hand-held objects that may prove useful to the playing class. '''

{|
|- valign="top"
| width="450px" | [[Image:BE_BINOC.jpg|thumb|left|Brenodi Empire Binoculars]]||
{|
| colspan="2" | '''Binoculars'''
|-
| colspan="2" | Used to observe enemy activity and call in strikes.
|-
| width="100px" | Class || [[Scout]]
|}
|}

{|
|- valign="top"
| width="450px" | [[Image:BE_TOOL_2.jpg|thumb|left|Brenodi Empire Engineer Tool]][[Image:BE_TOOL_3.jpg|thumb|left|Brenodi Empire Engineer Tool]] ||
{|
| colspan="2" | '''Engineer Tool'''
|-
| colspan="2" | Used to build structures, heal units or deconstruct enemy structures / vehicles. Also used to place [[turrets]], [[walls]], [[Surveillance | surveillance gear]] and [[Ammo_Crates | ammo crates]].
|-
| width="100px" | Damage || 26
|-
| Class || [[Engineer]]
|}
|}

[[Category:Gameplay]] [[Category:Weapons]]

Refinery

2019-10-29T18:47:54Z

Lightning: Grammatical and Formatting changes

{{BuildingOverview}}

[[Image:IMPRefinery.jpg|thumb|right|Brenodi Empire Refinery]]
[[Image:be_refinery.gif|thumb|right|Brenodi Empire Refinery: Height Comparison]]
[[Image:NFRefinery.jpg|thumb|right|Northern Faction Refinery]]
[[Image:nf_refinery.gif|thumb|right|Northern Faction Refinery: Height Comparison]]

=Function=
All armies require [[resources]] to function, and the refinery provides them. By building refineries on [[Resource Node|Resource Nodes]], your faction gains resources periodically for each operational refinery.

=Stats=
*Cost : 100
*Health when initially built : 25
*Maximum health : 150
*Weapons that cannot harm vehicles are not able to harm this building.

=Tips=
{{Tip|It is generally a good idea to build turrets and walls near refineries to prevent their destruction by enemies.}}
{{Note|Depending on the [[Maps|map]] or the [[Gameplay_Types|play mode]], refineries may be the only way of generating resources for your faction.}}

[[Category:Structures|Refinery]]

Surveillance

2019-10-29T18:45:25Z

Lightning: Images for the new BE Camera, some other changes.

{{BuildingOverview}}

[[Image:Camera.jpg|thumb|right|Nothern Faction Surveillance Camera]]
[[Image:IMPRadarDish2.jpg|thumb|right|Nothern Faction Surveillance Radar Dish]]
[[File:Imperial Engineer Camera.png|thumb|left|Brenodi Empire Surveillance Camera]]
[[File:Imperial Engineer Radar.png|thumb|left|Brenodi Empire Surveillance Radar Dish]]

= Function =
[[Engineer|Engineers]] can construct a single camera or radar dish. The camera will reveal enemy infantry on the mini-map and the radar dish will reveal enemy [[vehicles]] and [[structures]]. Also, the enemy units will have an orange diamond drawn around them on your HUD if they are in the Surveillance Equipment area of effect. You will be able to see it even from behind terrain and obstacles. When a [[Engineer|engineer]] reaches the rank of [[Skills#Overview|Staff Sergeant]] They are able to build a second piece of Surveillance Equipment

{{Tip|It is possible to destroy Surveillance Equipment using small arms fire -- which includes bullets and melee attacks.}}
[[Category:Structures|Surveillance]]

File:Imperial Engineer Radar.png

2019-10-29T18:43:50Z

Lightning: Screenshot of The Brenodi Empires Current Engineer Radar Model

Screenshot of The Brenodi Empires Current Engineer Radar Model

File:Imperial Engineer Camera.png

2019-10-29T18:41:52Z

Lightning: Screenshot of the latest model of the BE Camera

Screenshot of the latest model of the BE Camera

Armory

2019-10-29T18:35:11Z

Lightning: Amended misinformation, added a new tip and fixed formatting.

{{BuildingOverview}}

[[Image:NFarmory2.jpg|thumb|right|Northern Faction Armory]]
[[Image:nf_armory.gif|thumb|right|Northern Faction Armory: Height Comparison]]
[[Image:Brenodi_armory.jpg|thumb|right|Brenodi Empire Armory]]
[[Image:be_armory.gif|thumb|right|Brenodi Empire Armory: Height Comparison]]

= Function =
The armory contains [[Ammo Crates]] which allows an infantryman to resupply their ammunition and heal themselves on the frontline. Like the [[Barracks]], players may change their class here. Vehicles may also resupply their ammunition while in the vicinity of an armory.

=Stats=
*Cost : 75
*Health when initially built : 25
*Maximum health : 100
*Weapons that cannot harm vehicles are not able to harm this building.

= Infantry Tips =
{{Tip|While you may not be able to hear your enemies reloading and cocking their weapons, what you can hear is when they are opening ammunition and health crates. If you hear this sound, chances are good that your opponent is preoccupied with loading up on supplies and will be easily caught off guard. If you hear that familiar 'click' then charge in, guns blazing!}}

{{Tip|To instantly reload all your weapons, press the loadout button ('''B''' by default) while inside an armory or barrack, then click "Accept". This may give you a split-second advantage you would have otherwise lost.}}

((Tip|The Brenodi Empire Armory has two different entrances, use this to your advantage when attacking one.}}

[[Category:Structures|Armory]]

Ammo Crates

2019-10-29T18:26:54Z

Lightning: - Ammended Staff Sergeant+ being able to place crates infinitely, changed it to 60 second cooldown

{{BuildingOverview}}

[[Image:NFAmmoCrate.jpg|thumb|right|Northern Faction Ammunition Crate]]
[[Image:IMPCrates.jpg|thumb|right|Imperial Medical and Ammunition Crates]]
[[Image:NFCrates.jpg|thumb|right|Northern Faction Medical and Ammunition Crates]]

= Function =
Ammunition and Medical crates are boxes from which players may refill their ammo. Ammunition crates will always prioritize ammo for the weapon you are currently holding, and only once you have reached the maximum will it begin to restock your other weapons. It will only restock one magazine at a time.

A temporary ammo crate can be placed anywhere on the map by an [[Engineer|engineer]]. Ammunition crates will last for 120 seconds, although they will take 200 seconds until another may be placed. Ammunition and Medical crates can also be found inside an [[Armory]] and in various locations on some maps alongside health crates. Upon reaching Staff Sergeant, the Engineer may place Ammunition crates at an increased rate, as the cooldown timer is reduced to 60 seconds.

= Tips =

{{Tip|To use an ammo crate, target it in your crosshair and press the 'use' button (default: 'e').}}

{{Tip|Due to its size, the NF ammo crate can be used as quick and temporary cover in many areas.}}

{{Tip|Vehicles can have their ammunition resupplied if an [[Engineer|engineer]] places one down nearby.}}
[[Category:Structures|Ammo Crates]]

Ammo Crates

2019-10-29T18:18:25Z

Lightning: Minor Grammatical Changes

{{BuildingOverview}}

[[Image:NFAmmoCrate.jpg|thumb|right|Northern Faction Ammunition Crate]]
[[Image:IMPCrates.jpg|thumb|right|Imperial Ammunition and Medical Crates]]
[[Image:NFCrates.jpg|thumb|right|Northern Faction Ammunition and Medical Crates]]

= Function =
Ammunition crates are boxes from which players may refill their ammo. It is important to note that you do not spawn with the maximum allotted ammo, and so may increase the amount you are carrying even before you go into combat. Ammunition crates will always prioritize ammo for the weapon you are currently holding, and only once you have reached the maximum will it begin to restock your other weapons.

A temporary ammo crate can be placed anywhere on the map by an [[Engineer|engineer]]. Ammunition crates will last for 120 seconds, although they will take 200 seconds until another may be placed. Ammo crates can also be found inside an [[Armory]] and in various locations on some maps alongside health crates. Upon reaching Staff Sergeant, the Engineer may place an unlimited amount of crates, as the cooldown timer is set to 0.

{{Tip|To use an ammo crate, target it in your crosshair and press the 'use' button (default: 'e').}}

{{Tip|Due to its size, the NF ammo crate can be used as quick and temporary cover in many areas.}}

[[Category:Structures|Ammo Crates]]

VehicleScript.massoverride

2017-03-04T02:12:39Z

Lightning: Created page with "This overrides the default value for the mass of a vehicle (default is whatever the HL2 jeep is) prefix: <pre> "massoverride" "Integer" or "massoverride" "1800" </pre>"

This overrides the default value for the mass of a vehicle (default is whatever the HL2 jeep is)

prefix:
<pre>
"massoverride" "Integer"
or
"massoverride" "1800"
</pre>

VehicleHandlingScripts

2017-03-04T02:00:20Z

Lightning: /* body */

{{ScriptingDocumentation}}
__NOTOC__
==Overview==
Vehicle handling scripts have quite a few variables. This tries to describe the parameters you can use to fine tune vehicle handling.

Also see: https://developer.valvesoftware.com/wiki/Vehicles_(Scripting_Parameters)

==vehicle Properties==

===body===
[[VehicleScript.massCenterOverride | massCenterOverride]] 
[[VehicleScript.massoverride | massoverride]] 
[[VehicleScript.addgravity | addgravity]] 
[[VehicleScript.maxangularvelocity | maxangularvelocity]] 

===engine===
[[VehicleScript.horsepower | horsepower]] 
[[VehicleScript.maxrpm | maxrpm]] 
[[VehicleScript.maxspeed | maxspeed]] 

===steering===
[[VehicleScript.degreesSlow | degreesSlow]] 

===axle===
A vehicle can have multiple axle definitions.

[[VehicleScript.torquefactor | torquefactor]] 

==vehicle_sounds Properties==
A vehicle_sounds entry can have multiple of the following sections:

===state===
[[VehicleScript.SoundState.Name | Name]] 

[[Category:Scripting]]

User:Lightning

2017-03-04T01:56:16Z

Lightning: Created page with " Hi, Welcome to my profile ===What i Do=== I work on the Handling Scripts for Empires right now, the wiki section for those can be found here: Here"

Hi, Welcome to my profile

===What i Do===
I work on the Handling Scripts for Empires right now, the wiki section for those can be found here: [[VehicleHandlingScripts|Here]]

VehicleScript.massCenterOverride

2017-03-02T20:53:56Z

Lightning:

massCenterOverride does exactly as you would think, overrides where the central point of gravity on a vehicle is 
 
'''Prefix''' 
<pre>
"massCenterOverride" "0 10 -1.5"
</pre>
- First coordinate moves the center left/right (Strongly advise against changing it if you don't want a lop-sided vehicle 
- Second coordinate moves the center front/back 
- Third coordinate moves the center up/down 

'''
Quote from Viromans old jeep script which contains alot of useful information:''' 
<pre>
"massCenterOverride" "0 10 -1.5"
// leave at vec3_origin for no override - duke edit - as steve mentioned, this greatly affects wether it rolls or not, and setting it higher (So the center is higher up) tends to lower to tendency to flip
// Drag: First coordinate moves center left/right (don't change it), second : front, rear --> setting it <0 limits the turning ability of a tank "on spot" and a bit on the move, setting it > 0 makes turning slower in the beginning and way faster if you keep the keys pressed ; third: up/down --> moving it up? (-) counters flipping but hinders hill climbing
</pre>

VehicleScript.massCenterOverride

2017-03-02T20:53:08Z

Lightning: Created page with " massCenterOverride does exactly as you would think, overrides where the central point of gravity on a vehicle is '''Prefix''' <pre> "massCenterOverride" "0 10 -1.5" </pre> -..."

massCenterOverride does exactly as you would think, overrides where the central point of gravity on a vehicle is

'''Prefix'''
<pre>
"massCenterOverride" "0 10 -1.5"
</pre>
- First coordinate moves the center left/right (Strongly advise against changing it if you don't want a lop-sided vehicle
- Second coordinate moves the center front/back
- Third coordinate moves the center up/down

'''
Quote from Viromans old jeep script which contains alot of useful information:'''
<pre>
"massCenterOverride" "0 10 -1.5"
// leave at vec3_origin for no override - duke edit - as steve mentioned, this greatly affects wether it rolls or not, and setting it higher (So the center is higher up) tends to lower to tendency to flip
// Drag: First coordinate moves center left/right (don't change it), second : front, rear --> setting it <0 limits the turning ability of a tank "on spot" and a bit on the move, setting it > 0 makes turning slower in the beginning and way faster if you keep the keys pressed ; third: up/down --> moving it up? (-) counters flipping but hinders hill climbing
</pre>

VehicleHandlingScripts

2017-03-02T20:43:41Z

Lightning: /* engine */

{{ScriptingDocumentation}}
__NOTOC__
==Overview==
Vehicle handling scripts have quite a few variables. This tries to describe the parameters you can use to fine tune vehicle handling.

Also see: https://developer.valvesoftware.com/wiki/Vehicles_(Scripting_Parameters)

==vehicle Properties==

===body===
[[VehicleScript.massCenterOverride | massCenterOverride]] 

===engine===
[[VehicleScript.horsepower | horsepower]] 
[[VehicleScript.maxrpm | maxrpm]] 
[[VehicleScript.maxspeed | maxspeed]] 

===steering===
[[VehicleScript.degreesSlow | degreesSlow]] 

===axle===
A vehicle can have multiple axle definitions.

[[VehicleScript.torquefactor | torquefactor]] 

==vehicle_sounds Properties==
A vehicle_sounds entry can have multiple of the following sections:

===state===
[[VehicleScript.SoundState.Name | Name]] 

[[Category:Scripting]]

Talk:VehicleHandlingScripts

2017-03-02T20:41:36Z

Lightning: Created page with "<pre> Viromans Jeep Script - Given to me by Lazybum - Lightning // Brenodi Empire Jeep; "vehicle" { //"gravity" "10" //"max_traction_force" "240000" // Acceleration limi..."

<pre>
Viromans Jeep Script - Given to me by Lazybum - Lightning
// Brenodi Empire Jeep;

"vehicle"
{
//"gravity" "10"
//"max_traction_force" "240000" // Acceleration limit per wheel :)
//"max_traction_slip" "6" // This value describes at what spin value the wheels will be most efficient. Normaly should be set to 6.
//"gravity" "700" // gravity acceleration in inches/s^2. Normally should be set to ~400
//"engine_max_torque" "18000000" // Higher values increase acceleration and top speed
//"air_drag" "5" //0.8 This value affects acceleration, top speed and wheel spin. Affects the vehicle mostly on high speeds.
//"damage_collision_modifier" "100.0" <-- doesn't work
//"ground_resistance" "4" // This value affects acceleration, top speed and wheel spin. Affects the vehicle mostly on low speeds.
"body"
{
//countertorquefactor" "0.75"
"massCenterOverride" "0 10 -1.5"
// leave at vec3_origin for no override - duke edit - as steve mentioned, this greatly affects wether it rolls or not, and setting it higher (So the center is higher up) tends to lower to tendency to flip
// Drag: First coordinate moves center left/right (don't change it), second : front, rear --> setting it <0 limits the turning ability of a tank "on spot" and a bit on the move, setting it > 0 makes turning slower in the beginning and way faster if you keep the keys pressed ; third: up/down --> moving it up? (-) counters flipping but hinders hill climbing
"massoverride" "1500" //1900 in kg, leave at 0 for no override (kg)
"addgravity" "2" //0.33 keeps car down
"maxAngularVelocity" "100" //50 VM:ANTI FLIP OFF CLIFF DEVICE! Side effect of limiting turn radius at high speed.
"keepuprighttorque" "1" //fastdigger.txt HL2
"tiltforce" "90" //10 fastdigger.txt HL2 VM: Only seems to effect empty vehicles - Super flipping out when driven off cliffs
"tiltforceheight" "32" //64 fastdigger.txt HL2 VM: Only seems to effect empty vehicles - Super flipping out when driven off cliffs
"ground_resistance" "9000" // This value affects acceleration, top speed and wheel spin. Affects the vehicle mostly on low speeds.

}
"engine"
{
//VM Notes:
//* If you increase the MAXRPM and don't bring up the AXELRATIO it lowers total HP of engine.
//* Increasing the MAXRPM increases time spent in each gear if you set shift up/down as you
// would a normal vehicle. This could be bad since first gear has high torque and will
// quickly reach max vehicle speed. Set the shift up/down low should do the trick.
//* If you comment out horsepower here and run vehicle_flush all the vehicles that are currently
// spawned of this type will have 0 Horse power.

"horsepower" "350" // engine power. VM: Set at 350 due to engine.txt (standard hp) file. When you use vehicle_flush command... THIS file overwrites the engine.txt file of the vehicle you are currently in.
"maxrpm" "10000" //1500 max rounds per minute VM: higher MAXRPM allows for finer tuning of shifting and gear power
"maxspeed" "60" // forward mph
"maxReverseSpeed" "20" // backward mph
"autotransmission" "1" // true for auto, false for manual
"axleratio" "18" //8 //3.56 ratio of engine rev to axle rev VM: Low value = lower HP and acceleration.

//VM Notes:
//1st gear is also reverse. //2004 Chevrolet Corvette C5 Z06 gear ratio
"gear" "5.5" //3.5 1st gear (max 6 gears) 2.97
"gear" "4.0" //1.8 2nd gear 2.07
"gear" "2.5" //1.26 3rd gear 1.43
"gear" "1.9" //1.0 4th gear 1.0
"gear" "1.84" //0.84 5th gear 0.84

// VM: Does this shit even work!? I think its actually shifting but, its not tied to audio. It gets overwiten by engine.txt?
"shiftuprpm" "6000" //600 max RPMs to switch to a higher gear
"shiftdownrpm" "2500" //250 min RPMs to switch to a lower gear

//VM: Coasting
"autobrakeSpeedGain" "1.1" // 10% speed gain while coasting, put on the brakes after that //VM: can coast down hills faster then engines set speed. Scout speed takes you into this area too so, you can use this to cap scout speed.
"autobrakeSpeedFactor" "3.0" // Brake is this times the speed gain

// Empires - YES boost for ME!
"boost"
{
"force" "1.5" // 1.5 car body mass * gravity * inches / second ^ 2
"duration" "1.0" // 1 second of boost
"delay" "0.5" // 15 seconds before you can use it again
"torqueboost" "1" // enable "sprint" mode of vehicle, not force type booster
"maxspeed" "80" // maximum turbo speed
"force" "5.5" // 1.5 car body mass * gravity * inches / second ^ 2
}
}

"steering"
{
"degreesSlow" "40" //40 angle in degrees of steering
"degreesFast" "20" //20 angle in degrees of steering
"steeringExponent" "1.0" // steering function is linear, then raised to this power to be slower at the beginning of the curve, faster at the end

"slowcarspeed" "10" // this is the max speed of "slow"
"fastcarspeed" "20" // this is the min speed of "fast"
"slowsteeringrate" "2" // this is the speed the wheels are steered when the vehicle is "slow"
"faststeeringrate" "0.75" // this is the speed the wheels are steered when the vehicle is "fast"

"steeringRestRateSlow" "5.0" // this is the speed at which the wheels move toward their resting state (straight ahead)
"steeringRestRateFast" "2.0"
"turnThrottleReduceSlow" "0.0" //0.1
"turnThrottleReduceFast" "0.3" //0.5
"brakeSteeringRateFactor" "6"
"throttleSteeringRestRateFactor" "2"

//boost control
"degreesBoost" "10" // steering cone at max boost speed (blend toward this after max speed) VM: scout speed takes you here too it seems
"boostSteeringRestRateFactor" "1.7"
"boostSteeringRateFactor" "1.7"

//Others
//"powerSlideAccel" "300" //250 Allows you to spin the CORRECT DIRECTION not opposit when hand breaking
"skidallowed" "1" // true/false skid flag
"dustcloud" "1" // flag for creating a dustcloud behind vehicle

//"turnbrake" "10" //"0.25" works?
}

"wheelsperaxle" "2" // wheels per axle

// front axle
"axle"
{
"torquefactor" "1" //1.5 VM: How much of the engine HP is placed on this axel.
"brakefactor" "0.2" // normalized to 1 across all axles VM: setting high brakes in front can flip a light vehicle on braking action. Like it would a bike.
//"offset" "0 -68 25" //
//"wheeloffset" "40 0 0" //

"wheel"
{
//"is_steering" "1" // Boolean value. Is this a steering wheel?
//"max_grip" "20" // Normaly should be set to 1. This value defines the maximum wheel grip and handling. Higher values increase wheel
//"torque_distribution" "3" // How much engine power is transfered to this wheel. The sum of all wheels can exceed 1 which will result in increasing engine power.

"radius" "18" // VM: The size of the wheel. Setting this lower then the acual radius of the wheel will make the vehicle sink into the ground. Setting it higher will make the vehicle float.
"mass" "300" //300 in kg VM: The heavier the wheels the more gravity affects you thus you are glued to the ground.
"inertia" "0.05" //.05/ steady the car (fixes the oscillation of the axles about z)
"damping" "0" //affects fishtailing
"rotdamping" "0" //.05 usually 0
"material" "Rubber_Friction_20" //"jeeptire"
"skidmaterial" "Rubber_Friction_4" //"slidingrubbertire" // surface properties when sliding
"brakematerial" "Rubber_Friction_8" //"brakingrubbertire" // surface properties wen breaking
}

"suspension"
{
//"position_offset" "25" // Physics hack: normaly should be set to zero. Offset by which the steering force and fake mass transfer is shifted in Z axis. Higher values may stabilize handling.
"springConstant" "70" //70 Strength of spring, lower values will make spring weaker
"springDamping" "2" //2
"stabilizerConstant" "110" //110
"springDampingCompression" "4" //4 VM: Set it to 60 for Dancing vehicle
"maxBodyForce" "300" //250
}
}

// rear axle
"axle"
{
"torquefactor" "0" // VM: Placing torque on back wheels NOT suggested for small vehicles since it totaly screws up steering control.
"brakefactor" "0.9"

"wheel"
{
"radius" "18" // VM: The size of the wheel. Setting this lower then the acual radius of the wheel will make the vehicle sink into the ground. Setting it higher will make the vehicle float.
"mass" "300" //300 in kg VM: The heavier the wheels the more gravity affects you thus you are glued to the ground.
"inertia" "0" //.05 steady the car (fixes the oscillation of the axles about z)
"damping" "0" //affects fishtailing
"rotdamping" "0" //.05
"material" "Rubber_Friction_20" //"jeeptire"
"skidmaterial" "Rubber_Friction_4" //"slidingrubbertire" // surface properties when sliding
"brakematerial" "Rubber_Friction_8" //"brakingrubbertire" // surface properties wen breaking
}
"suspension"
{
"springConstant" "70" //70 Strength of spring, lower values will make spring weaker
"springDamping" "2" //2
"stabilizerConstant" "110" //110
"springDampingCompression" "4" //4 VM: Set it to 60 for Dancing vehicle
"maxBodyForce" "300" //250
}
}
}

"vehicle_sounds"
{
// List gears in order from lowest speed to highest speed

//VM Notes:
// MAX_SPEED - When to play the shift sound vs how fast your vehicle is going.
// Doesn't seem to actaully tie in with when your vehicle is actually shifting
// code side. So... Give it your best guess.
// SPEED_APPROACH_FACTOR - How fast to REV up the engine sound. Lower gears should rev up faster.

"gear"
{
"max_speed" "0.1" //0.3
"speed_approach_factor" "1" //1
}

"gear"
{
"max_speed" "0.2" //0.5
"speed_approach_factor" "0.07" //0.07
}
"gear"
{
"max_speed" "0.7" //0.75
"speed_approach_factor" "0.07" //0.07
}
"gear"
{
"max_speed" "0.6" //0.90
"speed_approach_factor" "0.035" //0.035
}
"gear"
{
"max_speed" "1" //0.95
"speed_approach_factor" "0.015" //0.015
}
"gear"
{
"max_speed" "2.0" //2
"speed_approach_factor" "0.03" //0.03
}
"state"
{
"name" "SS_START_WATER"
"sound" "ATV_start_in_water"
"min_time" "0.5"
}
"state"
{
"name" "SS_SHUTDOWN"
"sound" "ATV_engine_stop"
}
"state"
{
"name" "SS_IDLE"
"sound" "ATV_engine_idle"
}
"state"
{
"name" "SS_START_IDLE"
"sound" "ATV_engine_start"
//"min_time" "0.5"
}
"state"
{
"name" "SS_SHUTDOWN_WATER"
"sound" "ATV_stall_in_water"
"min_time" "0.5"
}
"state"
{
"name" "SS_REVERSE"
"sound" "ATV_reverse"
//"min_time" "0.7"
}
"state"
{
"name" "SS_GEAR_0"
"sound" "ATV_rev"
//"min_time" "0.2"
}
"state"
{
"name" "SS_GEAR_0_RESUME"
"sound" "ATV_engine_idle"
//"min_time" "0.15"
}
"state"
{
"name" "SS_GEAR_1"
"sound" "ATV_firstgear"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_1_RESUME"
"sound" "ATV_firstgear_noshift"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_2"
"sound" "ATV_secondgear"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_2_RESUME"
"sound" "ATV_secondgear_noshift"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_3"
"sound" "ATV_thirdgear"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_3_RESUME"
"sound" "ATV_thirdgear_noshift"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_4"
"sound" "ATV_fourthgear"
//"min_time" "0.5"
}
"state"
{
"name" "SS_GEAR_4_RESUME"
"sound" "ATV_fourthgear_noshift"
//"min_time" "0.5"
}
"state"
{
"name" "SS_SLOWDOWN_HIGHSPEED"
"sound" "ATV_throttleoff_fastspeed"
//"min_time" "0.25"
}
"state"
{
"name" "SS_SLOWDOWN"
"sound" "ATV_throttleoff_slowspeed"
//"min_time" "0.25"
}
"state"
{
"name" "SS_TURBO"
"sound" "ATV_turbo_on"
//"min_time" "2.5"
"min_time" "0.5"

}
"crashsound"
{
"min_speed" "350"
"min_speed_change" "250"
"sound" "ATV_impact_medium"
"gear_limit" "1"
}
"crashsound"
{
"min_speed" "450"
"min_speed_change" "350"
"sound" "ATV_impact_heavy"
}

"skid_lowfriction" "ATV_skid_lowfriction"
"skid_normalfriction" "ATV_skid_normalfriction"
"skid_highfriction" "ATV_skid_highfriction"
}
</pre>

Maps

2008-03-09T20:06:49Z

Lightning:

{{Sitenav|Maps}}

A few different maps are currently in existence, each offering different terrain, objectives, and play styles. If you know of any more maps, please add them. If you are interested in creating maps, see the [[Mapping]] page.

== Gameplay Types ==
Different [[Gameplay Types]] are available to offer a different set of challenges and are dependent on the map in question.

== Official Maps ==
The following maps are officially included in the current distribution of Empires. They are listed under headings according to the group who created them.

=== Development Team ===
* [[Map:emp_canyon|emp_canyon]]
* [[Map:emp_crossroads|emp_crossroads]]
* [[Map:emp_duststorm|emp_duststorm]]
* [[Map:emp_escort|emp_escort]]
* [[Map:emp_glycencity|emp_glycencity]]
* [[Map:emp_isle|emp_isle]]
* [[Map:emp_money|emp_money]]
* [[Map:emp_streetsoffire|emp_streetsoffire]]
* [[Map:emp_urbanchaos|emp_urbanchaos]]

=== Community ===
* [[Map:emp_cyclopean|emp_cyclopean]] by halbalbador
* [[Map:emp_district402|emp_district402]]
* [[Map:emp_mvalley|emp_mvalley]] by R_yell
* [[Map:emp_Slaughtered|emp_Slaughtered]] by =HELLION=

=== No Longer Official ===
* [[Map:emp_badland|emp_badland]] by Gobanzo Mon
* [[Map:emp_cdr_canyon|emp_cdr_canyon]]
* [[Map:emp_gauntlet|emp_gauntlet]]

== Custom Maps ==
These maps are created by the Empires community. Some will be of a high enough standard to become official maps.

=== Released ===
These are completed maps, which may be included in the regular rotations on some designated custom map servers. Individual download links can be found on each map's page.
* [[Map:emp_2base|emp_2base]] by jimather
* [[emp_canals]] by R_yell
* [[Map:emp_lastcity|emp_lastcity]]
* [[Map:Emp_Maze|Emp_Maze]] by Cyber(Gunner)
* [[Map:emp_oasis|emp_oasis]] by Stu
* [[Map:emp_ovi_canyon|emp_ovi_canyon]]
* [[Map:emp_railroad|emp_railroad]] by Broccoli
* [[Map:emp_stu_city|emp_stu_city]] by Stu
* [[Map:emp_stu_crater|emp_stu_crater]] by Stu

=== BETA ===
These maps are at a playable state, but are not yet polished enough to be called final. Often they will have active threads in the [http://forums.empiresmod.com/forumdisplay.php?f=8 mapping forums], where bugs can be reported and feedback given.
* [[Map:emp_desolation|emp_desolation_beta1]] by JJ45
* [[Map:emp_empcannon|emp_empcannon_beta4]] by InstantDeath
* [[Map:emp_fastestmap|emp_fastestmap_v3]] by Unknown
* [[Map:emp_fortB|emp_fortB]] by DarkSim
* [[Map:emp_gorge|emp_gorge]] by Aurificationalist
* [[Map:emp_perfume|emp_perfume]] by Cyber(Gunner)
* [[Map:emp_Red_Alert|emp_Red_Alert]] by blizzerd
* [[Map:emp_tictactoe|emp_tictactoe_rc3]] by Broccoli
* [[Map:emp_vehicletraining|emp_vehicletraining_rc2]] by Silk

=== Coming Soon ===
Maps in this section are under active development, but are not yet available for public download.
* [[Map:emp_ashmountain|emp_ashmountain]] by Broccoli
* [[Map:emp_rooftop|emp_rooftop]] by Arklansman

=== Concept ===
The maps below are only ideas at this stage. Often this will involve designing the layout and the visual style of the map, as well as the [[Gameplay_Types|gametype]] and any back-story to the setting.
* [[Map:emp_cityscape|emp_cityscape]] by Kylegar
* [[Map:emp_coastal|emp_coastal]]
* [[Map:emp_crash|emp_crash]] by vallav
* [[Map:Emp_Forts|Emp_Forts]] by Cyber(Gunner_Yeyz)
* [[Map:emp_highway|emp_highway]]
* [[Map:emp_IsleOfWar|emp_IsleOfWar]]
* [[Map:emp_lighthouse|emp_lighthouse]] by CourtJesterG
* [[Map:emp_nukedcity|emp_nukedcity]] by Extrems
* [[Map:emp_tropical|emp_tropical]] by JJ45

[[Category:Maps|Maps]]

Configuring Hammer for Empires

2007-12-19T17:21:09Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}
[[Image:Tools.png|thumb|right| To get to the Hammer configuration window...]]

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Once hammer is open go to 'tools' at the top, then click 'options' which brings up the hammer configuration window required for this tutorial. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Build_programs.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

Configuring Hammer for Empires

2007-12-19T16:11:00Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}
[[Image:Tools.png|thumb|right| Game configuration tab]]

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Once hammer is open go to 'tools' at the top, then click 'options' which brings up the hammer configuration window required for this tutorial. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Build_programs.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

Configuring Hammer for Empires

2007-12-19T16:06:36Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Once hammer is open go to 'tools' at the top, then click 'options' which brings up the hammer configuration window required for this tutorial. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Build_programs.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

Configuring Hammer for Empires

2007-12-19T16:02:32Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Build_programs.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

Configuring Hammer for Empires

2007-12-18T19:57:29Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab (note: bad quality pic : ()]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Build_programs.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

File:Build programs.png

2007-12-18T19:56:47Z

Lightning:

Configuring Hammer for Empires

2007-12-18T19:54:13Z

Lightning:

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.png|thumb|right| Game configuration tab (note: bad quality pic : ()]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Hammer1.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

File:Hammer1.png

2007-12-18T19:48:59Z

Lightning: uploaded a new version of "Image:Hammer1.png"

Configuring Hammer for Empires

2007-12-18T19:30:00Z

Lightning: /* Build Programs */

{{Sitenav|[[Mapping]] > Configuring Hammer for Empires}}

{{Note|Before you do anything, make sure you have installed Hammer Editor, available through Steam under the ''Tools'' section.}}

{{Note|As of the release of the Orange Box update to Hammer, you will need to right click on the Source SDK, click Properties, and select Set Launch Options. Here you will need too add "-engine ep1" without quotes.}}

Start by opening Hammer Editor through the Empires SDK link in your ''Tools'' section in the Steam client. Follow the directions below.
== Game Configuration Tab ==
[[Image:Hammer1.Gif|thumb|right| Game configuration tab (note: bad quality pic : ()]]

'''Add following .fgd files into your fgd list:'''
* Base.fgd
* Halflife2.fgd
* Empires.fgd (located at $SteamDir\SteamApps\SourceMods\Empires\mapsrc\fgd\empires.fgd)

'''The Game executable Directory should be set to:'''
$SteamUserDir\half-life 2 deathmatch\hl2

'''The game directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires

'''The hammer vmf directory should be set to:'''
$SteamDir\SteamApps\SourceMods\Empires\mapsrc

All relative to where you installed empires, meaning that if you configured your folders to be called somthing else then you need to specify the paths according to that

== Build Programs ==
[[Image:Hammer1.png|thumb|right| Build programs tab]]
'''Game executable:'''
$SteamUserDir\half-life 2 deathmatch\hl2.exe
'''BSP executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vbsp.exe
'''VIS executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vvis.exe
'''RAD executable:'''
$SteamUserDir\sourcesdk\bin\ep1\bin\vrad.exe
'''Place compiled maps in this directory before running the game:'''
$SteamDir\SteamApps\SourceMods\Empires\maps

[[Category:Mapping|Configuring Hammer]]

File:Hammer1.png

2007-12-18T19:28:37Z

Lightning:

Flag Maps

2007-03-03T16:22:08Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife2 except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]

13. Now im going to show you how to set up the spawns for the neutral flags. For these, each flag will need spawns for each team rather than just one. Take a look at the picture below. Both of thoses spawn points are for the same flag its just that one team is traveling in one direction and the other in the oppersite. So when placing spawns bare in mind which direction the teams are traveling.

[[Image:step_13.gif|medium|step 13]]

14. For these spawn points you need to make sure that you have 'enabled?' set to no

15. Now for the ammo and health boxes these are set up in a simular way to the spawn points. These is a different entity for each team.

Brenodi
'emp_imp_ammo_crate' for the ammo box and 'emp_imp_health_crate' for the health box

NF
'emp_nf_ammo_crate' for the ammo box and 'emp_nf_health_crate' for the health box

[[Image:step_15.gif|medium|step 15]]

16. If the ammo crates and health crates are linked with a flag you will have to set them up the the corisponding flag. If they are just on the map and do not have anything to do with a flag you will need to set the flag number to 0.

17. I think thats everything you need to make a working flag map but for just for good measures (and because pickjaoe wanted to know) ill tell you how to make hanging flags.

18. Ok hanging flags... you have made a normal flag pole using 'emp_cap_model' well this is exectly the same exept you change the type of model you use. So it's...

models/common/props_system/flag2_neutral.mdl for a neutral hanging flag

models/common/props_system/flag2_imp.mdl for a brenodi hanging flag

models/common/props_system/flag2_nf.mdl for a nf flag

end of tutorial

Tutorial made by supaste

Flag Maps

2007-03-03T16:21:35Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

{{note|under construction}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife2 except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]

13. Now im going to show you how to set up the spawns for the neutral flags. For these, each flag will need spawns for each team rather than just one. Take a look at the picture below. Both of thoses spawn points are for the same flag its just that one team is traveling in one direction and the other in the oppersite. So when placing spawns bare in mind which direction the teams are traveling.

[[Image:step_13.gif|medium|step 13]]

14. For these spawn points you need to make sure that you have 'enabled?' set to no

15. Now for the ammo and health boxes these are set up in a simular way to the spawn points. These is a different entity for each team.

Brenodi
'emp_imp_ammo_crate' for the ammo box and 'emp_imp_health_crate' for the health box

NF
'emp_nf_ammo_crate' for the ammo box and 'emp_nf_health_crate' for the health box

[[Image:step_15.gif|medium|step 15]]

16. If the ammo crates and health crates are linked with a flag you will have to set them up the the corisponding flag. If they are just on the map and do not have anything to do with a flag you will need to set the flag number to 0.

17. I think thats everything you need to make a working flag map but for just for good measures (and because pickjaoe wanted to know) ill tell you how to make hanging flags.

18. Ok hanging flags... you have made a normal flag pole using 'emp_cap_model' well this is exectly the same exept you change the type of model you use. So it's...

models/common/props_system/flag2_neutral.mdl for a neutral hanging flag

models/common/props_system/flag2_imp.mdl for a brenodi hanging flag

models/common/props_system/flag2_nf.mdl for a nf flag

end of tutorial

Tutorial made by supaste

Flag Maps

2007-03-03T16:20:43Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

{{note|under construction}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife2 except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]

13. Now im going to show you how to set up the spawns for the neutral flags. For these, each flag will need spawns for each team rather than just one. Take a look at the picture below. Both of thoses spawn points are for the same flag its just that one team is traveling in one direction and the other in the oppersite. So when placing spawns bare in mind which direction the teams are traveling.

[[Image:step_13.gif|medium|step 13]]

14. For these spawn points you need to make sure that you have 'enabled?' set to no

15. Now for the ammo and health boxes these are set up in a simular way to the spawn points. These is a different entity for each team.

Brenodi
'emp_imp_ammo_crate' for the ammo box and 'emp_imp_health_crate' for the health box

NF
'emp_nf_ammo_crate' for the ammo box and 'emp_nf_health_crate' for the health box

[[Image:step_15.gif|medium|step 15]]

16. If the ammo crates and health crates are linked with a flag you will have to set them up the the corisponding flag. If they are just on the map and do not have anything to do with a flag you will need to set the flag number to 0.

17. I think thats everything you need to make a working flag map but for just for good measures (and because pickjaoe wanted to know) ill tell you how to make hanging flags.

18. Ok hanging flags... you have made a normal flag pole using 'emp_cap_model' well this is exectly the same exept you change the type of model you use. So it's...

models/common/props_system/flag2_neutral.mdl for a neutral hanging flag
models/common/props_system/flag2_imp.mdl for a brenodi hanging flag
models/common/props_system/flag2_nf.mdl for a nf flag

end of tutorial

Tutorial made by supaste

Flag Maps

2007-03-03T16:11:41Z

Lightning:

Basic Conquest Map

2007-03-03T16:08:12Z

Lightning:

{{Sitenav|[[Mapping]] > Basic Conquest Map}}

(Please ensure that you have completed the [[Configuring Hammer for Empires]] guide before continuing).

This guide is for showing you how to set up the conquest style map seen in maps such as Isle and Duststorm. This guide excludes the teaching of resource nodes and mini maps. Also remember that this tutorial is written in a way in which hammer n00bs can understand so if what is being talked about is to simple... skip it!

1. Ok to start with, load up the source SDK (under "Tools" in steam) and open the Hammer Editor. This is the software used to create maps for any source-powered game.
Upon loding your screen should look like this...

[[Image:Step 1.png|medium|step 1]]

2. Create a new map by going 'File' -> 'New'. The screen should now look like this...

[[Image:Step 2.png|medium|step 2]]

3. Now select the block tool on the left hand side.

[[Image:Step 3.png|medium|step 3]]

4. Move your mouse to the 2D top view (the top right view) and use the mouse wheel to zoom in and out. To move the view, hold the space bar and drag with the left mouse button. When you are satisfied that you can navigate in this view, drag out a square using the left mouse button whilst the block tool is selected. Make it around 4096 by 4096 units. You will see a white outline where the block will be created. Press return on your keyboard to place the block.

[[Image:Step 4.png|medium|step 4]]

5. After you have done this the box should appear in the 3D view (top left view) but thanks to a new update from steam, this might not work first time. To correct this, click the camera tool and then click on a 2D view then scroll out in the 3D view.

[[Image:Step 5.png|medium|step 5]]

6. The next thing to do is to get used to moving around in the 3D view, there are two ways to equaly useful ways to do this.

A) With the camera tool selected, click and hold the left mouse button in the 3D view. This rotates your view on the spot. The right mouse button moves your view left, right, up and down (relative to where you are looking). Holding both mouse buttons at once zooms the view in and out.

B) No tool needs to be selected in this way of moving all you have to do is move your mouse into the 3D view and zoom in and out with the 'W' and 'S' keys and pan left and right with the 'A' and 'D' keys changing your direction with the arrow keys much like in spectator view on most source games only using arrow keys insted of the mouse.

Once you are comfortable with moving around, move on to step 6.5.

6.5. At this stage, your newly placed block will look like this. This is the default white texture.

[[Image:Step 6.5.png|medium|step 6.5]]

6.1. This makes it hard to see what you're doing, and doesn't look all that good either, so we are going to put a different texture on it. Half-Life 2 comes with many different textures, most of which can be used for this kind of object. In this case, I'm going to have it as grass. To find your texture, select browse at the right hand side.

[[Image:Step 6.6.png|medium|step 6.6]]

6.2. Now type in the filter "grass".

[[Image:Step 6.7.png|medium|step 6.7]]

6.3. Select the specific texture that you want by double clicking it. You will then be brought back to the editing screen, where you should now select your block and click the apply texture button.

[[Image:Step 6.8.png|medium|step 6.8]]

7. Now we are going to place some entities. These are what really make the map function. Some examples would be the baracks and the command vehicles. To begin, click the entity tool.

[[Image:Step 7.png|medium|step 7]]

8. You will notice that when you do this, at the right hand side of the screen, two previously greyed out dropdown boxes will now become available. The top one is used to decide what you are placing (in this case, leave it on "Entities") and the bottom box chooses what you are placing out of that category. The other options relate to prefabs, and are not relevant to this tutorial. We will be using the bottom box to select the Brenodi barracks entity. This is named '''emp_building_imp_barracks'''.

[[Image:Step 8.png|medium|step 8]]

9. The easiest way to place entities in the map is via the 3D view. Clicking anywhere on your ground, a barracks should appear. Chances are, it hasn't been placed exactly how you want it (it is probably too high) so this means we will have to use the 2D views to position it how we want it.

[[Image:Step 9.png|medium|step 9]]

10. To move a object in the 2D view simply select it (by clicking on it in the 3D view), and drag it around. Notice it will snap to the grid. In order to change the grid size, use the '[' and ']' keys. This works exactly the same in all of the 2D views.

11. Once you have positioned the Brenodi barracks where you want it, do the same with the NF one ('''emp_building_nf_barracks''')...

[[Image:Step 11.png|medium|step 11]]

12. Now we need to add the command vehicles ('''emp_imp_commander''') and ('''emp_nf_commander'''). This works exactly the same as the barracks, but leave them ever so slightly above the ground so that when the game starts they drop to the floor rather than being stuck in the ground. The Brenodi CV's front wheels will look all screwed up; dont worry, this will correct itself in-game.

[[Image:Step 12.png|medium|step 12]]

13. The next thing to now do is to make the sky box. For this tutorial we are going to be using a 2D skybox, as this is much simpler than a 3D one. Effectively all we are going to do is use the block tool to make a box around the map, and use the skybox tool texture on it to turn it into sky. I find it best to start making this from the edge of our map in the top view.

[[Image:Step 13.png|medium|step 13]]

14. Now you have one side of your skybox (untextured) but it is not the right height so you need to go into a different 2D view and begin resizing it. I would say that about 1087 units high would be enough, but keep in mind that the commander can only move inside this box. If it's too short, his view of the battle will be severely limited. Also remember that when making these bits it sometimes helps you later on to have blocks meet at corners rather then edges (as shown in bottem right 2D view).

[[Image:Step 14.png|medium|step 14]]

15. I think its a good time to tell you how to copy a block as this comes in useful when doing lots of brushwork. To copy a block, all you have to do is select it and drag it with your mouse in a 2D view whilst holding the shift key. Try doing this with the block we made in step 13. Also you can delete blocks you have made by selecting them and pressing the 'delete key'

[[Image:Step 15.png|medium|step 15]]

16. Now do the same with the other two sides.

[[Image:Step 16.png|medium|step 16]]

17. Now we need to add a ceiling, start by dragging a box in the top 2D view the same size and shape as the floor then bring it up to meet the corners of the side of your map.

[[Image:Step 17.png|medium|step 17]]

18. You will want to texture the ceiling and the walls, texture them as skyboxes this is done in the same way as how we textured the floor only you use the skybox texture search 'skybox' or 'tools' to find it.

[[Image:Step 18.png|medium|step 18]]

19. Next we need to add 'Emp_info_params' this a entity that tells hammer how many resources each team starts with, how many reinforcements each team has and various other things. When you place it it should appear as a red cube when selected and a purple cube when not selected. To edit the propities of it double click it in the 3D view. (Dont forget if you want to play this map set the resources quite high as resource nodes are not in this tutorial)

[[Image:Step 19.png|medium|step 19]]

20. Lastly we need to add 'emp_info_map_overview' this is also a entity and is selected in the same way as 'Emp_info_params'

[[Image:Step 20.png|medium|step 20]]

21. Dont forget that to play your map go to file- runmap and hit ok to compile! Have fun!

end of tutorial

Tutorial made by supaste with special thanks to Broccoli and other people who did corrections for me (add your name if i missed you)

Flag Maps

2007-03-03T16:01:26Z

Lightning:

Flag Maps

2007-03-03T15:52:21Z

Lightning:

Flag Maps

2007-03-03T15:50:04Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

{{note|under construction}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife2 except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]

13. Now im going to show you how to set up the spawns for the neutral flags. For these, each flag will need spawns for each team rather than just one. Take a look at the picture below. Both of thoses spawn points are for the same flag its just that one team is traveling in one direction and the other in the oppersite. So when placing spawns bare in mind which direction the teams are traveling.

[[Image:step_13.gif|medium|step 13]]

14. For these spawn points you need to make sure that you have 'enabled?' set to no

15. Now for the ammo and health boxes these are set up in a simular way to the spawn points. These is a different entity for each team.

Brenodi
'emp_imp_ammo_crate' for the ammo box
'emp_imp_health_crate' for the health box

NF
'emp_nf_ammo_crate' for the ammo box
'emp_nf_health_crate' for the health box

[[Image:step_15.gif|medium|step 15]]

File:Step 15.gif

2007-03-03T15:49:48Z

Lightning:

Flag Maps

2007-03-03T15:30:50Z

Lightning:

Flag Maps

2007-03-03T14:49:45Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

{{note|under construction}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife2 except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]

13. Ok so those spawns were easy enough to set up because they never had to change the team which controlled them but now im going to show you how to set up the spawns for the neutral flags. For these each flag will need spawns for each team rather than just one. Take a look at the picture below. Both of thoses spawn points are for the same flag its just that one team is traveling in one direction and the other in the oppersite. So when placing spawns bare in mind which direction the teams are traveling.

[[Image:step_13.gif|medium|step 13]]

14. For these spawn points you need

File:Step 13.gif

2007-03-03T14:49:39Z

Lightning:

File:Step 12.gif

2007-03-03T14:30:58Z

Lightning:

Flag Maps

2007-03-03T14:30:36Z

Lightning:

{{Sitenav|[[Mapping]] > Flag Maps}}

{{note|under construction}}

This tutorial is intended to teach you how to make the flag style maps as seen in escort and district.

1. To start off you should build the area you would like the battle to take place in. Here's mine in 3D wireframe its very simple for the sake of this tutorial.

[[Image:step_1.gif|medium|step 1]]

2. You must then plan where the capture flags will be. (blue is Brenodi, grey is neutral and red is NF)After doing this you must number each flag. 1 must always be the first Northen Faction flag and the highest number must always be the first Brenodi flag.

(notice that 4 is the highest number brenodi starts here and that 1 is the lowest number NF starts here)
[[Image:step_2.gif|medium|step 2]]

3. Next you will want to place these flags on your map. To do this first you will need to go to entities on the righthand side of hammer and select 'emp_resource_point_prop' and place it on your map in the 3D view.

[[Image:step_3.gif|medium|step 3]]

4. For my map i need 4 flags as shown in my plan so before i shift+drag the first 'emp_cap_model' i made 3 times i will set it up properly. Bring up the object properties of 'emp_cap_model' the only things that are not set up by default are the Brenodi and NF models. For this tutorial we will just use the flag pole models.
So make northen faction model 'models/common/props_system/flagpole01_nf.mdl'
And the brenodi model 'models/common/props_system/flagpole01_imp.mdl'
Leave everything else the same for the time being.

[[Image:step_4.gif|medium|step 4]]

5. The next step is to shift+drag the 'emp_cap_model' so for my map i need to do this 3 times. The below image is a 2D wireframe view. All the purple boxes are flags.

[[Image:step_5.gif|medium|step 5]]

6. You must now number your flags by bringing up the object properties of each individual 'emp_cap_model' and changing number of the parent capture point.
(remember-1 is always NF, highest number is always brenodi)

[[Image:step_6.gif|medium|step 6]]

7. Now you are ready to create the 'emp_cap_point' this is a brush based entity which activates when a player steps into it. So first you need to click the block tool, drag a box around the area that a player can capture a point. (mine will be just bigger than the flag)You must then change the texture of this modle to 'nodraw'. This texture does exactly what it says on the tin - it creates a object which is not drawn.

[[Image:step_7.gif|medium|step 7]]

8. You must now change this brush into a entity. To do this simply click on the brush and then with your keyboard press 'ctrl+t'. This will have brought up the object properties menu. Change the class to a 'emp_cap_point'

[[Image:step_8.gif|medium|step 8]]

9. Now that we have a capture point we need to make it comunicate with the correct flag. To do this make sure the properties menu is up and change the 'number of this capture point' to the flag you want it to capture. You can have more that one capture point per flag but you must set them up the same (i think)

10. There are lots of settings that you may wish to change on the capture point propertys bu ill let you work them out as each one is individual for most flags.

11. Now onto spawn points. When a flag is captured on most maps you will want that team to be able to spawn at a nearer flag. To do this we need a entity called 'emp_info_player' these are simular to info_player_start used in halflife except there is one for each team in empires. Brenodi has 'emp_info_player_imp' and NF has 'emp_info_player_nf' so its easy to tell them apart. For starting spawn points which are already captured you will need place a 'emp_info_player' double click it and change the number of the parent capture point to its corisponding flag.

12. Dont forget that as this spawn will be there at the start of the game you will need to change 'enabled?' to yes.

[[Image:step_12.gif|medium|step 12]]