Armagetron Advanced - User contributions [en]

TST29.9.2019

2013-10-19T03:00:47Z

Epsy: /* Server Settings */ Fixed config name

<center><font size="7">T S T</font></center><br>
<center><font size="5">Team Sumo Tournament - Sunday, October 20, 2013!</font></center>
----
<center><font size="4"><b>Sign-ups are Open!</b></font></center><br>

{{:TeamSumoTournament/Blurb}}
<font size="4">[http://forums3.armagetronad.net/viewtopic.php?f=60&t=23346 '''Sunday, October 20, 2013''']</font>

=General Information=
===About===
*This is the Team Sumo Tournament.
*Times and brackets are listed below.
*You will also find official settings and guidelines below.

===Rules===
*Each team is allowed only 2 Players. This is a '''2v2v2v2''' tournament.
*Servers will be chosen and positioned on the brackets.
*Teams will be randomized then placed on the brackets.
*Team editing will be '''locked''' after the brackets are up.
*If you have '''played''' a match with a partner, you are '''NOT''' allowed to join another team as you have already locked yourself with the previous team by playing with them.
*On the day of the event, team captains are allowed to replace there teammate if he does not show up.
*Each team has 5 minutes after the posted time to be ready or they will be forced to forfeit. If the other team is in a match from a previous round in the tournament they will have 8 minutes after the match to get their team ready and the match started.
*Be friendly and have fun.

===Settings===

*Practically default Sumo settings, apart from the changes said, here.
*The first team to win two matches advances to the next round.
*First team to reach 900 points wins a match.
*10 rounds only.
*In the open
*Finals are first to 2 match wins.

===Server Settings===
RESOURCE_REPOSITORY_CLIENT http://resource.hashpickup.net/
RINCLUDE epsy/sumo/TST/game-2010.09-2.cfg
RINCLUDE epsy/generic/teamcolors4-1.0.aacfg.cfg

===Teams===
To add your team onto the list, simply fill in this template and then post it at the end of the desired location's list.
#'''TEAMNAMEHERE''' | Captain (@forums) | Player 2 |

====USA====
#'''OMG BECKY!''' | Razzle (Razzle@x)| Dazzle
#'''[http://www.lagtest.net/ Srinivasa]''' Ramanujan (asdfasdf@forums) | Hardy (johnny.nbk@forums)
#'''[http://www.lost-history.com/gilgamesh.php/ The Immortals]''' | Gilgamesh (gilgamesh@forums) | Enkidu
#'''Cheese Under Pie''' | Capone (Shock@forums) | Paladin
#'''Did you catch it?''' | orion (orion@forums)| b3n
#'''XxixXyoloswag420bongXxixX''' | mecca (Mecca@forums) | TaZ
#'''Video Game Arcade''' | Wreckit Ralph (iamthing1@forums) | Fixit Felix
#'''dBdeezNutz''' | tRonPaul (biasoner@forums) | Nil |
#'''Backstreet Boys''' | Zurd (ZURD101@forums) | MCP |
#'''[http://crossfitsyndicate.com/wp-content/uploads/2013/02/archer_crossFit_dangerzone_meme.jpg/ Zone For Sale]''' Nanu (nanu@aagid) | Agility
#'''teamoldskewlll''' | Biggysmalls (@forums) | IZZIMAHIZZI|
#'''What does the fox say?''' Garingdingding! (cowgoesmooo@forums) | Waapapapapapow! |
#'''X and Y''' | Xerneas (Xerneas@aagid) | Yveltal |
#'''Villains''' | Cruella De Vil (Villains@forums) | Wizard | Dr. Evil
#'''The Otter Illusion''' | Otter (otter@forums) | Illusion |
#'''Team^ß'''|Andrei (Andrei_35@forums) | Cyclo

====Europe====
#'''[http://www.youtube.com/watch?v=x-64CaD8GXw/ SCUMM]''' | Fish Breath Patrick (django@aagid) | Misty the Well-Tanned
#'''The Sexiest team ever''' | Chinchilla (DrunkDuck@forums) | soska
#'''whatever''' | liz (Vogue@forums) | wap
#'''Team ugly''' | vov (vov@x) | House
#'''[http://images4.wikia.nocookie.net/__cb20111013003324/seuss/images/d/d3/Thing1-and-thing2.jpg/ Box Dwellers]''' | Thing 1 (Thing1@forums) | Thing 2
#'''panda is a masochist''' | Jericho (Jericho@x) | Panda
#'''Surprise''' | o.o (o.o!@forums) | u.u
#'''[http://www.youtube.com/watch?v=Q-ejz2RmueE/ The Winchesters]''' | Sam Winchester (eagles@forums) | Dean Winchester
#'''Magick team''' | izissise (izissise@forums) | Welanor
#'''KingBrezKrone''' | Krikio (Krikio@forums) | slov
#'''Crazy Drones''' | Voodoo (voodoo@forums) | pike
#'''Das Leben der Anderen''' | blondie (blondie@killst.tk) | korrigan
#'''[http://i.imgur.com/PFwE6Wo.jpg/ PG Tips]''' | ¶Potter (ppotter@forums) | Hoax
#'''[http://news.phoenix-clan.org/ Tron Times]''' | Nagi (Nagi@forums) | Venom
#'''This is it''' | Hydramist (Hydra@forums) | Kalimist
#'''Metal's Team''' | Metal (Metal@phoenix-clan.org) | Nate

====Global Moderators====
To sign up to be a global moderator, PM either J-Dawgg Or Soul in advance :) Server Donators will Automatically be placed under here.

* Pathetique@forums
* Kyle@ct/jedi
* Light@forums

=Servers=
===Server List===
<nowiki>* '''Server Name''' ([[User talk:ServerAdmin|ServerAdmin]]) <code>Address:Port</code> ''Location''</nowiki>

====USA====

* '''Pathetique's''' ([[User:Pathetique|Pathetique]]) <code>wdc.dbdclan.co:4545</code> ''Washington, D.C (US)''
* '''CT USA''' ([[User:Kyle|kyle@ct/jedi]]) <code>crazy-tronners.com:4535</code> ''Atlanta, Georgia (US)''
* '''Lowkey's US''' ([[User:Lowkey|Lowkey@forums]]) <code>67.18.189.128:4535</code> ''Connecticut (US)''
* '''Renegade's USA''' ([[User:Cookie|Renegade@forums]]) <code>happytrontime.tk:4534</code> ''Atlanta, Georgia''
* '''Light's USA''' ([[User:Light|Light@lightron.org]]) <code>lightron.org:4544</code> ''Pennsylvania, USA''

====Europe====

* '''CT LIV''' ([[User:Kyle|kyle@ct/jedi]]) <code>Address: liv.crazy-tronners.com:4541</code> ''Germany (EU)''
* '''CT OWL''' ([[User:Kyle|kyle@ct/jedi]]) <code>Address: owl.crazy-tronners.com:4535</code> ''Somewhere (EU)''

=Challenge Board=
===Times===

'''Opening Round Starting Time'''
GMT: '''18:00 (5PM)'''
BST: '''19:00 (6PM)'''
CEST: '''20:00 (7PM)'''
EDT:''' 2:00PM'''
CDT: '''13:00PM (Noon)'''
MDT: '''12:00AM'''
PDT: '''11:00AM'''
MST: '''11:00AM'''(Important if you live in the majority part of AZ)

'''2nd Round Starting Time'''
GMT: '''18:45 (5:45PM)'''
BST: '''19:45 (6:45PM)'''
CEST: '''20:45 (7:45PM)'''
EDT:''' 2:45PM'''
CDT: '''13:45PM (Noon)'''
MDT: '''12:45AM'''
PDT: '''11:45AM'''
MST: '''11:45AM'''(Important if you live in the majority part of AZ)

{{TST Brackets
| RD1=First Round
| RD2=Second Round
| RD3=Finals
| group1=
| group2=
| group3=
| subgroup1=Backup Server:
| subgroup2=Backup Server:
| subgroup3=Backup Server:
| subgroup4=Backup Server:
| team-width=220

| RD1-server01=<b><font color="#FF0000">USA</font></b>
| RD1-player01=
| RD1-score01=
| RD1-player02=
| RD1-score02=
| RD1-player03=
| RD1-score03=
| RD1-player04=
| RD1-score04=

| RD1-server02=<b><font color="#FF0000">USA</font></b>
| RD1-player05=
| RD1-score05=
| RD1-player06=
| RD1-score06=
| RD1-player07=
| RD1-score07=
| RD1-player08=
| RD1-score08=

| RD1-server03=<b><font color="#FF0000">USA</font></b>
| RD1-player09=
| RD1-score09=
| RD1-player10=
| RD1-score10=
| RD1-player11=
| RD1-score11=
| RD1-player12=
| RD1-score12=

| RD1-server04=<b><font color="#FF0000">USA</font></b>
| RD1-player13=
| RD1-score13=
| RD1-player14=
| RD1-score14=
| RD1-player15=
| RD1-score15=
| RD1-player16=
| RD1-score16=

| RD1-server05=<b><font color="#0000FF">EURO</font></b>
| RD1-player17=
| RD1-score17=
| RD1-player18=
| RD1-score18=
| RD1-player19=
| RD1-score19=
| RD1-player20=
| RD1-score20=

| RD1-server06=<b><font color="#0000FF">EURO</font></b>
| RD1-player21=
| RD1-score21=
| RD1-player22=
| RD1-score22=
| RD1-player23=
| RD1-score23=
| RD1-player24=
| RD1-score24=

| RD1-server07=<b><font color="#0000FF">EURO</font></b>
| RD1-player25=
| RD1-score25=
| RD1-player26=
| RD1-score26=
| RD1-player27=
| RD1-score27=
| RD1-player28=
| RD1-score28=

| RD1-server08=<b><font color="#0000FF">EURO</font></b>
| RD1-player29=
| RD1-score29=
| RD1-player30=
| RD1-score30=
| RD1-player31=
| RD1-score31=
| RD1-player32=
| RD1-score32=

| RD2-server01=<b><font color="#FF0000">USA</font></b>
| RD2-player01=
| RD2-score01=
| RD2-player02=
| RD2-score02=
| RD2-player03=
| RD2-score03=
| RD2-player04=
| RD2-score04=

| RD2-server03=<b><font color="#0000FF">EURO</font></b>
| RD2-player05=
| RD2-score05=
| RD2-player06=
| RD2-score06=
| RD2-player07=
| RD2-score07=
| RD2-player08=
| RD2-score08=

| RD3-server01=<b><font color="#00FF00">USA</font></b>
| RD3-player01=
| RD3-score01=
| RD3-player02=
| RD3-score02=
| RD3-player03=
| RD3-score03=
| RD3-player04=
| RD3-score04=

}}

User:Epsy

2013-09-15T15:27:29Z

Epsy: updated

Active developer of Armagetron Advanced, owner of the pickup channel.

== Contact ==

You can contact me in our [[IRC Channel]], write me a [http://forums.armagetronad.net/privmsg.php?mode=post&u=1588 private message on the forums] or just edit my [[User_talk:Epsy|Talk Page]] (Don't forget to sign with <code><nowiki>—~~~~</nowiki></code>!)

== Identities ==

* AAGID: epsy@x (main)
* AAGID: epsy@forums
* OpenID: https://launchpad.net/~epsy

== Things in [[Armagetron Advanced]] that you can blame me for ==

* The warmup session in 0.4alpha
* Some of the (not yet merged) cockpit code

== Stuff I do related to Armagetron Advanced ==

* I own the pickup channel(http://www.hashpickup.net/) and some of its servers.
* I run the @x AAGID authority, for which you can register at http://x.hashpickup.net/ .
* I authored the [http://forums3.armagetronad.net/viewtopic.php?f=79&t=22652&p=266473#p266473 King of the fortress] ruleset, and host a couple servers running it.
* I organize Team Sumo Tournaments.

== Stuff I do not related to Armagetron Advanced ==

* I authored [http://pypi.python.org/pypi/clize clize], an argument parser for python.
* I run [http://www.reddit.com/user/tabledresser /u/tabledresser], a reddit bot that puts recent AMAs on the site in table format.

Blue Clan

2013-07-15T23:36:42Z

Epsy: Undo revision 43941 by YoloSwagman (talk)

6lu died July 13, 2013

Tournaments channel

2013-07-08T00:17:44Z

Epsy: Detailled who channel staffers would be

[[Category:Tournaments]]

#armagetron.tourneys is an IRC chat room on FreeNode dedicated to Armagetron Advanced tournaments. You can join without an IRC client using [http://webchat.freenode.net/?channels=armagetron%2Carmagetron.pickup%2Carmagetron.tourneys this website]. It is preferred that all tournament-related chat happens in this channel rather than on the main channel, on the pickup channel or on individual tournament channels, so that any tournament-related discussion or logs can easily be found.

==Channel Staffers==

Channel staffers are marked with voice(+v, have + next to their name in some clients) most of the time. Staffer status is given to users who take participation in the running of tournaments, are active on IRC and willing to help. If you need any help with the channel's operation, please feel free to ''ping'' them by mentioning their nickname.

==Channel Topic==

The channel topic is free for all to edit within reason, to provide an overview of the status of ongoing and upcoming tournaments or leagues. When editing, try to respect the formatting and take care to not erase other tournament info. If you need advice, feel free to ask anyone who has voice(+).

; /topic [new topic]
: This command sets the channel topic. Some IRC clients let you edit the topic line directly in their UI, so you may not need to use this command. Running the command with no argument usually displays the current channel topic.

==Dispute resolution==

Occasionally, disputes may require tournament participants, for instance team leaders, to use the channel to settle a dispute, perhaps with the help of a mediator. If it is needed for the conversation to be run without interference, a channel operator can set the channel up so that only the relevant parties can talk. Simply ask one of them.

==Staffer cheat sheet==

====Opping yourself====
; /msg chanserv op #armagetron.tourneys
: Grants yourself operator status(+o, @ next to your nickname) in the channel, so that you may exert actions such as setting moderated status, voicing other users, or setting bans.
; /msg chanserv deop #armagetron.tourneys
; /mode -o YourNickname
; /deop YourNickname
: Removes operator status for yourself. Please do this when you do not need operator status.

====Setting moderated mode====
; /mode +m
: Sets moderated status to the channel(+m) so that only voiced people can chat. Use this when it is important to make clear conversation between two parties of a dispute.
; /mode -m
: Undoes the above.
; /mode +v nickname
; /mode +vvv nickname nickname nickname
; /voice nickname nickname ...
: Gives the given users voice status(+v, + next to their nickname) so that they may chat even when the channel is moderated.
; /mode -v nickname
; /mode -vvv nickname nickname nickname
; /devoice nickname nickname ...
: Removes voice from the given users.

====Locking the topic====
; /mode +t
: Locks the topic so that only operators can edit it. Use this when users are spamming topic changes.
; /mode -t
: Undoes the above

====Dealing with troublemakers====
; /kick nickname
; /kickban nickname
: Removes the given user from the channel.

Competition Hub

2013-07-08T00:13:25Z

Epsy: Added link to Tournament channel

{{PlayerTbl}}<br />
Want to join a tournament, browse an old one, or [[Creating a Competition|organize/create a new one]]...well you're in the right place. See [[Tournaments channel]] for information on how to use the #armagetron.tourneys IRC chat room.

=Current/Upcoming Competition=
{{:DFT/Blurb}}<br/>
{{:Spoon/Blurb}}<br/>
{{:Ladle/Blurb}}<br/>
{{:Bowl/Blurb}}<br />
{{:CTFBRAWL/Blurb}}<br/>
{{:CTWF/Blurb}}<br/>
{{:IllegalExit/Blurb}}<br/>

=Suspended/Delayed Tournaments=
{{:4_Team_Fort/Blurb}}<br/>
{{:WarSumoTournament/Blurb}}<br/>

=Old tournaments=
{{:SBT/Blurb}}<br/>
{{:TiltBlurb}}<br/>
{{:LDFT/Blurb}}<br/>
{{:HSRacing/Blurb}}<br/>
{{:CarCurrus/Blurb}}<br/>
{{:Rddf/Blurb}}<br/>
{{:Wildcat_Tournament_september_2011/Blurp}}<br/>
{{:EZDF/Blurb}}<br/>
{{:TL/Blurb}}<br/>
{{:Onslaught/Blurb}}<br/>
{{:Fortress_Brawl/Blurb}}<br/>
{{:Sumo1v1Blurb}}<br/>
{{:USvsEU/blurb}}<br/>
{{:Crosseyed&PainlessBlurb}}<br/>
{{:IFC_Blurb}}<br/>
{{:Kings_of_the_Grid_Blurb}}<br />
{{:FFFBlurb}}<br/>
{{:AFL_Blurb}}<br/>
{{:AVE Fort/Blurb}}<br/>
{{:FTCM/Blurb}}<br/>

Tournaments channel

2013-07-08T00:01:25Z

Epsy: Created

[[Category:Tournaments]]

#armagetron.tourneys is an IRC chat room on FreeNode dedicated to Armagetron Advanced tournaments. You can join without an IRC client using [http://webchat.freenode.net/?channels=armagetron%2Carmagetron.pickup%2Carmagetron.tourneys this website]. It is preferred that all tournament-related chat happens in this channel rather than on the main channel, on the pickup channel or on individual tournament channels, so that any tournament-related discussion or logs can easily be found.

==Channel Staffers==

Channel staffers are marked with voice(+v, have + next to their name in some clients) most of the time. If you need any help with the channel's operation, please feel free to ''ping'' them by mentioning their nickname.

==Channel Topic==

The channel topic is free for all to edit within reason, to provide an overview of the status of ongoing and upcoming tournaments or leagues. When editing, try to respect the formatting and take care to not erase other tournament info. If you need advice, feel free to ask anyone who has voice(+).

; /topic [new topic]
: This command sets the channel topic. Some IRC clients let you edit the topic line directly in their UI, so you may not need to use this command. Running the command with no argument usually displays the current channel topic.

==Dispute resolution==

Occasionally, disputes may require tournament participants, for instance team leaders, to use the channel to settle a dispute, perhaps with the help of a mediator. If it is needed for the conversation to be run without interference, a channel operator can set the channel up so that only the relevant parties can talk. Simply ask one of them.

==Staffer cheat sheet==

====Opping yourself====
; /msg chanserv op #armagetron.tourneys
: Grants yourself operator status(+o, @ next to your nickname) in the channel, so that you may exert actions such as setting moderated status, voicing other users, or setting bans.
; /msg chanserv deop #armagetron.tourneys
; /mode -o YourNickname
; /deop YourNickname
: Removes operator status for yourself. Please do this when you do not need operator status.

====Setting moderated mode====
; /mode +m
: Sets moderated status to the channel(+m) so that only voiced people can chat. Use this when it is important to make clear conversation between two parties of a dispute.
; /mode -m
: Undoes the above.
; /mode +v nickname
; /mode +vvv nickname nickname nickname
; /voice nickname nickname ...
: Gives the given users voice status(+v, + next to their nickname) so that they may chat even when the channel is moderated.
; /mode -v nickname
; /mode -vvv nickname nickname nickname
; /devoice nickname nickname ...
: Removes voice from the given users.

====Locking the topic====
; /mode +t
: Locks the topic so that only operators can edit it. Use this when users are spamming topic changes.
; /mode -t
: Undoes the above

====Dealing with troublemakers====
; /kick nickname
; /kickban nickname
: Removes the given user from the channel.

Cockpit Reference

2013-03-13T00:03:09Z

Epsy: /* Common Attributes */ added blurb and camera attr info

{{Cockpits Blurb}}

This page describes all the cockpit-related features available in the 0.4-cockpit branch. It has not been merged into 0.4 yet. The current features are explained on the [[Cockpit Tutorial]] page.

==The boilerplate==

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE Resource SYSTEM "cockpit.dtd">

<Resource type="aacockpit" name="<span style="color: #999">cockpit name</span>" version="<span style="color: #999">a version</span>" author="<span style="color: #999">your name</span>" category="<span style="color: #999">a category</span>">
<Cockpit version="0.0.1">
<span style="color: #999">Widgets go here</span>
</Cockpit>
</Resource>

The attributes of the <code><Resource></code> tag form the path your cockpit will have to be placed at:

author/category/name-version.aacockpit.xml

If category is omitted or empty, the resource will be straight under the author directory. It can contain forward slashes, in which case the file will be several directories deep. See also [[Testing Resources]].

A few rules and recommendations:
* Don't use spaces/
* Don't use dashes(<code>-</code>) in the name.
* Use numbers or dotted numbers for your version. For example, you could use <code>1</code>, <code>1.5</code> or <code>0.4.3</code>. Make the version number increase as you publish updates and be consistent with the number of dots in it.
* Be consistent with your author name.

Inside the <code><Cockpit></code> tag is where the widgets go. A widget is an element on the HUD. Do '''not''' change the version on that tag. It may be used to introduce backward-compatibility changes in the future.

==Common Attributes==

These attributes can be applied to any widget like such:

<BarGauge camera="in" viewport="cycle">
<nowiki></nowiki>
</BarGauge>

===camera===

Specifies which cameras, separated by spaces, the widget should be shown in. If omitted, it is shown on all cameras. If it starts with a circumflex accent(<code>^</code>), then the widget will be shown in all cameras except those specified. Here are the accepted camera names:

{|
! camera="…"
! Full camera name
|-
| custom || Custom
|-
| follow || External
|-
| free || Free
|-
| in || Internal
|-
| server_custom || Server custom
|-
| smart || Smart
|-
| mer || Mercam
|-
| all || All cameras
|-
| * || All cameras
|}

===viewport===

===toggleSticky, toggleDefault===

===usetemplate===

==Common Tags==

===Position and Size===

Cockpit widgets are positioned with up to 4 tags:
# <code><Anchor></code> designates an anchor relative to the total output area. -1,-1 is the lower-left corner of the output, 1,1 is the higher-left corner.
# <code><Position></code> positions the widget, relative to the anchor you defined. One unit in a direction is the same amount of pixels than one unit in any other direction.
# <code><Size></code> gives the size of the widget. The units are also squares of pixels.
# <code><Align></code> defines what point in the widget corresponds to the point that was positionned with the two first tags. If unspecified, it defaults to the center of the widget.

====Anchor and Position====

Not all players play Armagetron on the same kind of display. Some play it on a 4:3 resolution, while others use 16:9 or 16:10. Or they could be playing splitscreen, causing each player's cockpit to be 2:3 or 32:9. While those last two cases are a bit extreme, your cockpit has to be able to adapt to 4:3 or 16:9 without trouble. Armagetron used to have one coordinate system that went from -1 to 1 horizontally and from -1 to 0.5 vertically. It was tailored for 4:3 outputs so to adapt cockpits for 16:9 it would just squish the cockpit vertically to fit.

This is no longer the case. Usually cockpit widgets are put near corners or edges of the output area. To help you do that, the <code><Anchor></code> tag lets you tell Armagetron just that. For instance:

<Anchor x="-1" y="-1" />

Setting the anchor at -1,-1 tells Armagetron that you are about to put your widget near the bottom left-hand side of the output. If you put it at 1,1, then you'd be in the upper right-hand side. Here is the coordinate space used for the anchor tag, on 4:3 and 16:9 outputs, respectively:

<div style="text-align: center">[[File:CockpitAnchor43.png|On a 4:3 output]] [[File:CockpitAnchor169.png|On a 16:9 output]]</div>

It will always scale to have x=-1 at the left, x=1 at the right, y=-1 at the bottom and y=1 at the top of the output. If you do not set an anchor, [[#Compatibility mode|compatibility mode]] will be implicitly triggered on the widget.

Once you have an anchor set, you can position your widget relative to it. The difference is that <code><Position></code>'s coordinate space always has a 1:1 ratio between width and height units.

<div style="text-align: center">[[File:CockpitPosition.png|How Position's coordinate space works for the previous Anchor example.]][[File:CockpitPosition169.png|The scale does not change with a different aspect ratio.]]</div>

0,0 is at the anchor you defined and the output is 2 units wide. Here, the blue elements symbolize the total output area and the anchor coordinates. The red elements show the coordinate space for the position. As you can see from the dashed square, it does not get resized vertically. If you were to write:

<Anchor x="-1" y="-1" />
<Position x=".1" y=".1" />

You would be telling Armagetron to position your widget close to the bottom left-hand corner, a fraction away from the edge of the output. It would be at an equal distance from the left and bottom edge of the screen, regardless of the output's aspect ratio.

====Size and Align====

The <code><Anchor></code> and <code><Position></code> tags have so far positioned a point on the screen.

<code><Size></code> an area of the screen to the point with its <code>width</code> and <code>height</code> attributes:

<Size width=".5" height=".4" />

This will give the widget an area that is a quarter of the width of the screen and is 5:4 in aspect ratio. The coordinate space for the size is the same as for the <code><Position></code> tag. The size is measured from edge to edge, with most widgets occupying exactly this space. Captions do not count towards it and can be on the outside of it.

<code><Align></code> is a convenience tag that lets you redefine how the widget aligns with its set position. It positions a point relative to the widget body, like <code><Anchor></code> sets a point relative to the output area.

====Adjusting position and size depending on aspect ratio====

The <code><Anchor></code> tag also accepts <code>minadjust</code> and <code>maxadjust</code> attributes. When the widget is processed, its <code><Position></code> and <code><Size></code> are multiplied by a factor. This factor is determined by dividing the output height by its width, then clamping that value so that it is at least <code>minadjust</code>'s value and at most <code>maxadjust</code>'s value. Those attributes both default to 1, so that no change is made by default.

For instance, a widget is positioned and sized like this:

<Anchor x="0" y="-1" minadjust="0.1" maxadjust="0.7" />
<Position x="0" y="0.1" />
<Align x="0" y="-1" />
<Size x="0.5" y="0.5" />

If the output size is 1024x768(or any 4:3 aspect output), the factor is <code>768/1024 = 0.75</code>. This is over the <code>maxadjust</code> parameter, so it becomes <code>0.7</code>. That factor then multiplies the <code><Position></code> and <code><Size></code> tags. The above code would be equivalent to, in this case:

<Anchor x="0" y="-1" />
<Position x="0" y="0.07" />
<Align x="0" y="-1" />
<Size x="0.35" y="0.35" />

If the output size is 1280x800(or any 16:10 aspect output), the factor is <code>800/1280 = 0.625</code>. This is between the adjust parameters, so it is unchanged. It is then used to multiply the position and size:

<Anchor x="0" y="-1" />
<Position x="0" y="0.0625" />
<Align x="0" y="-1" />
<Size x="0.3125" y="0.3125" />

===Background, Foreground and LineColor===

===Caption===

===DataSet===

==Widgets==

===Rectangle===

===BarGauge and VerticalBarGauge===

===NeedleGauge===

===Label===

===Map===

===Camview===

==Related settings==

==Compatibility mode==

Compatibility mode is activated on a widget when it either:

* has no <code><Anchor></code> tag,
* has an <code><Anchor></code> tag with its <code>oldcoord</code> attribute set to <code>true</code>.

When it is activated, the game will emulate the old coordinate system used for positioning widgets, and emulate quirks within the widgets themselves.

===Old coordinate system===

In the old coordinate system, <code><Position></code>'s coordinate system resizes to fit the output size so that <code>y=-1</code> is at the bottom of the output, <code>y=0.5</code> is at the top of the output, <code>x=-1</code> is at the left edge of the output, and <code>x=1</code> is at the right edge of the output. This coordinate system is shifted if using an <code><Anchor></code> different than <code>0,0.33</code>. <code><Size></code> operates on the same scale, but measures '''half''' the width and height of the object, as if from center to edge. <code><Anchor></code>'s <code>minadjust</code> and <code>maxadjust</code> are ignored.

This is an illustration of the old coordinate system. Note that 0.5 on the y axis is always the top of the screen.

[[Image:Cockpit Coordinate System.png|center|illustration of the coordinate system]]

===Label===

The widget will always be aligned from the top left corner, the width will be halved and used to horizontally space cells, the height will be used as text size. Setting cell dimensions is unsupported and the table is locked in auto-sizing mode.

===BarGauge===

The gauge body will only occupy the top half of the allocated room, the other half being reserved for captions.

===Camview===

The widget will always be aligned from the bottom-left corner.

Cockpit Reference

2013-03-12T22:40:11Z

Epsy: /* Compatibility mode */ Added widget specificities

{{Cockpits Blurb}}

This page describes all the cockpit-related features available in the 0.4-cockpit branch. It has not been merged into 0.4 yet. The current features are explained on the [[Cockpit Tutorial]] page.

==The boilerplate==

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE Resource SYSTEM "cockpit.dtd">

<Resource type="aacockpit" name="<span style="color: #999">cockpit name</span>" version="<span style="color: #999">a version</span>" author="<span style="color: #999">your name</span>" category="<span style="color: #999">a category</span>">
<Cockpit version="0.0.1">
<span style="color: #999">Widgets go here</span>
</Cockpit>
</Resource>

The attributes of the <code><Resource></code> tag form the path your cockpit will have to be placed at:

author/category/name-version.aacockpit.xml

If category is omitted or empty, the resource will be straight under the author directory. It can contain forward slashes, in which case the file will be several directories deep. See also [[Testing Resources]].

A few rules and recommendations:
* Don't use spaces/
* Don't use dashes(<code>-</code>) in the name.
* Use numbers or dotted numbers for your version. For example, you could use <code>1</code>, <code>1.5</code> or <code>0.4.3</code>. Make the version number increase as you publish updates and be consistent with the number of dots in it.
* Be consistent with your author name.

Inside the <code><Cockpit></code> tag is where the widgets go. A widget is an element on the HUD. Do '''not''' change the version on that tag. It may be used to introduce backward-compatibility changes in the future.

==Common Attributes==

===camera===

===viewport===

===toggleSticky, toggleDefault===

===usetemplate===

==Common Tags==

===Position and Size===

Cockpit widgets are positioned with up to 4 tags:
# <code><Anchor></code> designates an anchor relative to the total output area. -1,-1 is the lower-left corner of the output, 1,1 is the higher-left corner.
# <code><Position></code> positions the widget, relative to the anchor you defined. One unit in a direction is the same amount of pixels than one unit in any other direction.
# <code><Size></code> gives the size of the widget. The units are also squares of pixels.
# <code><Align></code> defines what point in the widget corresponds to the point that was positionned with the two first tags. If unspecified, it defaults to the center of the widget.

====Anchor and Position====

Not all players play Armagetron on the same kind of display. Some play it on a 4:3 resolution, while others use 16:9 or 16:10. Or they could be playing splitscreen, causing each player's cockpit to be 2:3 or 32:9. While those last two cases are a bit extreme, your cockpit has to be able to adapt to 4:3 or 16:9 without trouble. Armagetron used to have one coordinate system that went from -1 to 1 horizontally and from -1 to 0.5 vertically. It was tailored for 4:3 outputs so to adapt cockpits for 16:9 it would just squish the cockpit vertically to fit.

This is no longer the case. Usually cockpit widgets are put near corners or edges of the output area. To help you do that, the <code><Anchor></code> tag lets you tell Armagetron just that. For instance:

<Anchor x="-1" y="-1" />

Setting the anchor at -1,-1 tells Armagetron that you are about to put your widget near the bottom left-hand side of the output. If you put it at 1,1, then you'd be in the upper right-hand side. Here is the coordinate space used for the anchor tag, on 4:3 and 16:9 outputs, respectively:

<div style="text-align: center">[[File:CockpitAnchor43.png|On a 4:3 output]] [[File:CockpitAnchor169.png|On a 16:9 output]]</div>

It will always scale to have x=-1 at the left, x=1 at the right, y=-1 at the bottom and y=1 at the top of the output. If you do not set an anchor, [[#Compatibility mode|compatibility mode]] will be implicitly triggered on the widget.

Once you have an anchor set, you can position your widget relative to it. The difference is that <code><Position></code>'s coordinate space always has a 1:1 ratio between width and height units.

<div style="text-align: center">[[File:CockpitPosition.png|How Position's coordinate space works for the previous Anchor example.]][[File:CockpitPosition169.png|The scale does not change with a different aspect ratio.]]</div>

0,0 is at the anchor you defined and the output is 2 units wide. Here, the blue elements symbolize the total output area and the anchor coordinates. The red elements show the coordinate space for the position. As you can see from the dashed square, it does not get resized vertically. If you were to write:

<Anchor x="-1" y="-1" />
<Position x=".1" y=".1" />

You would be telling Armagetron to position your widget close to the bottom left-hand corner, a fraction away from the edge of the output. It would be at an equal distance from the left and bottom edge of the screen, regardless of the output's aspect ratio.

====Size and Align====

The <code><Anchor></code> and <code><Position></code> tags have so far positioned a point on the screen.

<code><Size></code> an area of the screen to the point with its <code>width</code> and <code>height</code> attributes:

<Size width=".5" height=".4" />

This will give the widget an area that is a quarter of the width of the screen and is 5:4 in aspect ratio. The coordinate space for the size is the same as for the <code><Position></code> tag. The size is measured from edge to edge, with most widgets occupying exactly this space. Captions do not count towards it and can be on the outside of it.

<code><Align></code> is a convenience tag that lets you redefine how the widget aligns with its set position. It positions a point relative to the widget body, like <code><Anchor></code> sets a point relative to the output area.

====Adjusting position and size depending on aspect ratio====

The <code><Anchor></code> tag also accepts <code>minadjust</code> and <code>maxadjust</code> attributes. When the widget is processed, its <code><Position></code> and <code><Size></code> are multiplied by a factor. This factor is determined by dividing the output height by its width, then clamping that value so that it is at least <code>minadjust</code>'s value and at most <code>maxadjust</code>'s value. Those attributes both default to 1, so that no change is made by default.

For instance, a widget is positioned and sized like this:

<Anchor x="0" y="-1" minadjust="0.1" maxadjust="0.7" />
<Position x="0" y="0.1" />
<Align x="0" y="-1" />
<Size x="0.5" y="0.5" />

If the output size is 1024x768(or any 4:3 aspect output), the factor is <code>768/1024 = 0.75</code>. This is over the <code>maxadjust</code> parameter, so it becomes <code>0.7</code>. That factor then multiplies the <code><Position></code> and <code><Size></code> tags. The above code would be equivalent to, in this case:

<Anchor x="0" y="-1" />
<Position x="0" y="0.07" />
<Align x="0" y="-1" />
<Size x="0.35" y="0.35" />

If the output size is 1280x800(or any 16:10 aspect output), the factor is <code>800/1280 = 0.625</code>. This is between the adjust parameters, so it is unchanged. It is then used to multiply the position and size:

<Anchor x="0" y="-1" />
<Position x="0" y="0.0625" />
<Align x="0" y="-1" />
<Size x="0.3125" y="0.3125" />

===Background, Foreground and LineColor===

===Caption===

===DataSet===

==Widgets==

===Rectangle===

===BarGauge and VerticalBarGauge===

===NeedleGauge===

===Label===

===Map===

===Camview===

==Related settings==

==Compatibility mode==

Compatibility mode is activated on a widget when it either:

* has no <code><Anchor></code> tag,
* has an <code><Anchor></code> tag with its <code>oldcoord</code> attribute set to <code>true</code>.

When it is activated, the game will emulate the old coordinate system used for positioning widgets, and emulate quirks within the widgets themselves.

===Old coordinate system===

In the old coordinate system, <code><Position></code>'s coordinate system resizes to fit the output size so that <code>y=-1</code> is at the bottom of the output, <code>y=0.5</code> is at the top of the output, <code>x=-1</code> is at the left edge of the output, and <code>x=1</code> is at the right edge of the output. This coordinate system is shifted if using an <code><Anchor></code> different than <code>0,0.33</code>. <code><Size></code> operates on the same scale, but measures '''half''' the width and height of the object, as if from center to edge. <code><Anchor></code>'s <code>minadjust</code> and <code>maxadjust</code> are ignored.

This is an illustration of the old coordinate system. Note that 0.5 on the y axis is always the top of the screen.

[[Image:Cockpit Coordinate System.png|center|illustration of the coordinate system]]

===Label===

The widget will always be aligned from the top left corner, the width will be halved and used to horizontally space cells, the height will be used as text size. Setting cell dimensions is unsupported and the table is locked in auto-sizing mode.

===BarGauge===

The gauge body will only occupy the top half of the allocated room, the other half being reserved for captions.

===Camview===

The widget will always be aligned from the bottom-left corner.

Cockpit Reference

2013-03-12T18:46:26Z

Epsy: /* Common Tags */ Fixed incorrect heading

{{Cockpits Blurb}}

This page describes all the cockpit-related features available in the 0.4-cockpit branch. It has not been merged into 0.4 yet. The current features are explained on the [[Cockpit Tutorial]] page.

==The boilerplate==

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE Resource SYSTEM "cockpit.dtd">

<Resource type="aacockpit" name="<span style="color: #999">cockpit name</span>" version="<span style="color: #999">a version</span>" author="<span style="color: #999">your name</span>" category="<span style="color: #999">a category</span>">
<Cockpit version="0.0.1">
<span style="color: #999">Widgets go here</span>
</Cockpit>
</Resource>

The attributes of the <code><Resource></code> tag form the path your cockpit will have to be placed at:

author/category/name-version.aacockpit.xml

If category is omitted or empty, the resource will be straight under the author directory. It can contain forward slashes, in which case the file will be several directories deep. See also [[Testing Resources]].

A few rules and recommendations:
* Don't use spaces/
* Don't use dashes(<code>-</code>) in the name.
* Use numbers or dotted numbers for your version. For example, you could use <code>1</code>, <code>1.5</code> or <code>0.4.3</code>. Make the version number increase as you publish updates and be consistent with the number of dots in it.
* Be consistent with your author name.

Inside the <code><Cockpit></code> tag is where the widgets go. A widget is an element on the HUD. Do '''not''' change the version on that tag. It may be used to introduce backward-compatibility changes in the future.

==Common Attributes==

===camera===

===viewport===

===toggleSticky, toggleDefault===

===usetemplate===

==Common Tags==

===Position and Size===

Cockpit widgets are positioned with up to 4 tags:
# <code><Anchor></code> designates an anchor relative to the total output area. -1,-1 is the lower-left corner of the output, 1,1 is the higher-left corner.
# <code><Position></code> positions the widget, relative to the anchor you defined. One unit in a direction is the same amount of pixels than one unit in any other direction.
# <code><Size></code> gives the size of the widget. The units are also squares of pixels.
# <code><Align></code> defines what point in the widget corresponds to the point that was positionned with the two first tags. If unspecified, it defaults to the center of the widget.

====Anchor and Position====

Not all players play Armagetron on the same kind of display. Some play it on a 4:3 resolution, while others use 16:9 or 16:10. Or they could be playing splitscreen, causing each player's cockpit to be 2:3 or 32:9. While those last two cases are a bit extreme, your cockpit has to be able to adapt to 4:3 or 16:9 without trouble. Armagetron used to have one coordinate system that went from -1 to 1 horizontally and from -1 to 0.5 vertically. It was tailored for 4:3 outputs so to adapt cockpits for 16:9 it would just squish the cockpit vertically to fit.

This is no longer the case. Usually cockpit widgets are put near corners or edges of the output area. To help you do that, the <code><Anchor></code> tag lets you tell Armagetron just that. For instance:

<Anchor x="-1" y="-1" />

Setting the anchor at -1,-1 tells Armagetron that you are about to put your widget near the bottom left-hand side of the output. If you put it at 1,1, then you'd be in the upper right-hand side. Here is the coordinate space used for the anchor tag, on 4:3 and 16:9 outputs, respectively:

<div style="text-align: center">[[File:CockpitAnchor43.png|On a 4:3 output]] [[File:CockpitAnchor169.png|On a 16:9 output]]</div>

It will always scale to have x=-1 at the left, x=1 at the right, y=-1 at the bottom and y=1 at the top of the output. If you do not set an anchor, [[#Compatibility mode|compatibility mode]] will be implicitly triggered on the widget.

Once you have an anchor set, you can position your widget relative to it. The difference is that <code><Position></code>'s coordinate space always has a 1:1 ratio between width and height units.

<div style="text-align: center">[[File:CockpitPosition.png|How Position's coordinate space works for the previous Anchor example.]][[File:CockpitPosition169.png|The scale does not change with a different aspect ratio.]]</div>

0,0 is at the anchor you defined and the output is 2 units wide. Here, the blue elements symbolize the total output area and the anchor coordinates. The red elements show the coordinate space for the position. As you can see from the dashed square, it does not get resized vertically. If you were to write:

<Anchor x="-1" y="-1" />
<Position x=".1" y=".1" />

You would be telling Armagetron to position your widget close to the bottom left-hand corner, a fraction away from the edge of the output. It would be at an equal distance from the left and bottom edge of the screen, regardless of the output's aspect ratio.

====Size and Align====

The <code><Anchor></code> and <code><Position></code> tags have so far positioned a point on the screen.

<code><Size></code> an area of the screen to the point with its <code>width</code> and <code>height</code> attributes:

<Size width=".5" height=".4" />

This will give the widget an area that is a quarter of the width of the screen and is 5:4 in aspect ratio. The coordinate space for the size is the same as for the <code><Position></code> tag. The size is measured from edge to edge, with most widgets occupying exactly this space. Captions do not count towards it and can be on the outside of it.

<code><Align></code> is a convenience tag that lets you redefine how the widget aligns with its set position. It positions a point relative to the widget body, like <code><Anchor></code> sets a point relative to the output area.

====Adjusting position and size depending on aspect ratio====

The <code><Anchor></code> tag also accepts <code>minadjust</code> and <code>maxadjust</code> attributes. When the widget is processed, its <code><Position></code> and <code><Size></code> are multiplied by a factor. This factor is determined by dividing the output height by its width, then clamping that value so that it is at least <code>minadjust</code>'s value and at most <code>maxadjust</code>'s value. Those attributes both default to 1, so that no change is made by default.

For instance, a widget is positioned and sized like this:

<Anchor x="0" y="-1" minadjust="0.1" maxadjust="0.7" />
<Position x="0" y="0.1" />
<Align x="0" y="-1" />
<Size x="0.5" y="0.5" />

If the output size is 1024x768(or any 4:3 aspect output), the factor is <code>768/1024 = 0.75</code>. This is over the <code>maxadjust</code> parameter, so it becomes <code>0.7</code>. That factor then multiplies the <code><Position></code> and <code><Size></code> tags. The above code would be equivalent to, in this case:

<Anchor x="0" y="-1" />
<Position x="0" y="0.07" />
<Align x="0" y="-1" />
<Size x="0.35" y="0.35" />

If the output size is 1280x800(or any 16:10 aspect output), the factor is <code>800/1280 = 0.625</code>. This is between the adjust parameters, so it is unchanged. It is then used to multiply the position and size:

<Anchor x="0" y="-1" />
<Position x="0" y="0.0625" />
<Align x="0" y="-1" />
<Size x="0.3125" y="0.3125" />

===Background, Foreground and LineColor===

===Caption===

===DataSet===

==Widgets==

===Rectangle===

===BarGauge and VerticalBarGauge===

===NeedleGauge===

===Label===

===Map===

===Camview===

==Related settings==

==Compatibility mode==

Compatibility mode is activated on a widget when it either:

* has no <code><Anchor></code> tag,
* has an <code><Anchor></code> tag with its <code>oldcoord</code> attribute set to <code>true</code>.

When it is activated, the game will emulate the old coordinate system used for positioning widgets, and emulate quirks within the widgets themselves.

===Old coordinate system===

In the old coordinate system, <code><Position></code>'s coordinate system resizes to fit the output size so that <code>y=-1</code> is at the bottom of the output, <code>y=0.5</code> is at the top of the output, <code>x=-1</code> is at the left edge of the output, and <code>x=1</code> is at the right edge of the output. <code><Size></code> operates on the same scale, but measures '''half''' the width and height of the object, as if from center to edge.
This is an illustration of the coordinate system:

[[Image:Cockpit Coordinate System.png|center|illustration of the coordinate system]]

Cockpit Reference

2013-03-12T15:29:04Z

Epsy: Started a section about the infamous oldcoord mode.

{{Cockpits Blurb}}

This page describes all the cockpit-related features available in the 0.4-cockpit branch. It has not been merged into 0.4 yet. The current features are explained on the [[Cockpit Tutorial]] page.

==The boilerplate==

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE Resource SYSTEM "cockpit.dtd">

<Resource type="aacockpit" name="<span style="color: #999">cockpit name</span>" version="<span style="color: #999">a version</span>" author="<span style="color: #999">your name</span>" category="<span style="color: #999">a category</span>">
<Cockpit version="0.0.1">
<span style="color: #999">Widgets go here</span>
</Cockpit>
</Resource>

The attributes of the <code><Resource></code> tag form the path your cockpit will have to be placed at:

author/category/name-version.aacockpit.xml

If category is omitted or empty, the resource will be straight under the author directory. It can contain forward slashes, in which case the file will be several directories deep. See also [[Testing Resources]].

A few rules and recommendations:
* Don't use spaces/
* Don't use dashes(<code>-</code>) in the name.
* Use numbers or dotted numbers for your version. For example, you could use <code>1</code>, <code>1.5</code> or <code>0.4.3</code>. Make the version number increase as you publish updates and be consistent with the number of dots in it.
* Be consistent with your author name.

Inside the <code><Cockpit></code> tag is where the widgets go. A widget is an element on the HUD. Do '''not''' change the version on that tag. It may be used to introduce backward-compatibility changes in the future.

==Common Attributes==

===camera===

===viewport===

===toggleSticky, toggleDefault===

===usetemplate===

==Common Tags==

===Position and Size===

Cockpit widgets are positioned with up to 4 tags:
# <code><Anchor></code> designates an anchor relative to the total output area. -1,-1 is the lower-left corner of the output, 1,1 is the higher-left corner.
# <code><Position></code> positions the widget, relative to the anchor you defined. One unit in a direction is the same amount of pixels than one unit in any other direction.
# <code><Size></code> gives the size of the widget. The units are also squares of pixels.
# <code><Align></code> defines what point in the widget corresponds to the point that was positionned with the two first tags. If unspecified, it defaults to the center of the widget.

====Anchor and Position====

Not all players play Armagetron on the same kind of display. Some play it on a 4:3 resolution, while others use 16:9 or 16:10. Or they could be playing splitscreen, causing each player's cockpit to be 2:3 or 32:9. While those last two cases are a bit extreme, your cockpit has to be able to adapt to 4:3 or 16:9 without trouble. Armagetron used to have one coordinate system that went from -1 to 1 horizontally and from -1 to 0.5 vertically. It was tailored for 4:3 outputs so to adapt cockpits for 16:9 it would just squish the cockpit vertically to fit.

This is no longer the case. Usually cockpit widgets are put near corners or edges of the output area. To help you do that, the <code><Anchor></code> tag lets you tell Armagetron just that. For instance:

<Anchor x="-1" y="-1" />

Setting the anchor at -1,-1 tells Armagetron that you are about to put your widget near the bottom left-hand side of the output. If you put it at 1,1, then you'd be in the upper right-hand side. Here is the coordinate space used for the anchor tag, on 4:3 and 16:9 outputs, respectively:

<div style="text-align: center">[[File:CockpitAnchor43.png|On a 4:3 output]] [[File:CockpitAnchor169.png|On a 16:9 output]]</div>

It will always scale to have x=-1 at the left, x=1 at the right, y=-1 at the bottom and y=1 at the top of the output. If you do not set an anchor, [[#Compatibility mode|compatibility mode]] will be implicitly triggered on the widget.

Once you have an anchor set, you can position your widget relative to it. The difference is that <code><Position></code>'s coordinate space always has a 1:1 ratio between width and height units.

<div style="text-align: center">[[File:CockpitPosition.png|How Position's coordinate space works for the previous Anchor example.]][[File:CockpitPosition169.png|The scale does not change with a different aspect ratio.]]</div>

0,0 is at the anchor you defined and the output is 2 units wide. Here, the blue elements symbolize the total output area and the anchor coordinates. The red elements show the coordinate space for the position. As you can see from the dashed square, it does not get resized vertically. If you were to write:

<Anchor x="-1" y="-1" />
<Position x=".1" y=".1" />

You would be telling Armagetron to position your widget close to the bottom left-hand corner, a fraction away from the edge of the output. It would be at an equal distance from the left and bottom edge of the screen, regardless of the output's aspect ratio.

===Size and Align===

The <code><Anchor></code> and <code><Position></code> tags have so far positioned a point on the screen.

<code><Size></code> an area of the screen to the point with its <code>width</code> and <code>height</code> attributes:

<Size width=".5" height=".4" />

This will give the widget an area that is a quarter of the width of the screen and is 5:4 in aspect ratio. The coordinate space for the size is the same as for the <code><Position></code> tag. The size is measured from edge to edge, with most widgets occupying exactly this space. Captions do not count towards it and can be on the outside of it.

<code><Align></code> is a convenience tag that lets you redefine how the widget aligns with its set position. It positions a point relative to the widget body, like <code><Anchor></code> sets a point relative to the output area.

===Adjusting position and size depending on aspect ratio===

The <code><Anchor></code> tag also accepts <code>minadjust</code> and <code>maxadjust</code> attributes. When the widget is processed, its <code><Position></code> and <code><Size></code> are multiplied by a factor. This factor is determined by dividing the output height by its width, then clamping that value so that it is at least <code>minadjust</code>'s value and at most <code>maxadjust</code>'s value. Those attributes both default to 1, so that no change is made by default.

For instance, a widget is positioned and sized like this:

<Anchor x="0" y="-1" minadjust="0.1" maxadjust="0.7" />
<Position x="0" y="0.1" />
<Align x="0" y="-1" />
<Size x="0.5" y="0.5" />

If the output size is 1024x768(or any 4:3 aspect output), the factor is <code>768/1024 = 0.75</code>. This is over the <code>maxadjust</code> parameter, so it becomes <code>0.7</code>. That factor then multiplies the <code><Position></code> and <code><Size></code> tags. The above code would be equivalent to, in this case:

<Anchor x="0" y="-1" />
<Position x="0" y="0.07" />
<Align x="0" y="-1" />
<Size x="0.35" y="0.35" />

If the output size is 1280x800(or any 16:10 aspect output), the factor is <code>800/1280 = 0.625</code>. This is between the adjust parameters, so it is unchanged. It is then used to multiply the position and size:

<Anchor x="0" y="-1" />
<Position x="0" y="0.0625" />
<Align x="0" y="-1" />
<Size x="0.3125" y="0.3125" />

===Background, Foreground and LineColor===

===Caption===

===DataSet===

==Widgets==

===Rectangle===

===BarGauge and VerticalBarGauge===

===NeedleGauge===

===Label===

===Map===

===Camview===

==Related settings==

==Compatibility mode==

Compatibility mode is activated on a widget when it either:

* has no <code><Anchor></code> tag,
* has an <code><Anchor></code> tag with its <code>oldcoord</code> attribute set to <code>true</code>.

When it is activated, the game will emulate the old coordinate system used for positioning widgets, and emulate quirks within the widgets themselves.

===Old coordinate system===

In the old coordinate system, <code><Position></code>'s coordinate system resizes to fit the output size so that <code>y=-1</code> is at the bottom of the output, <code>y=0.5</code> is at the top of the output, <code>x=-1</code> is at the left edge of the output, and <code>x=1</code> is at the right edge of the output. <code><Size></code> operates on the same scale, but measures '''half''' the width and height of the object, as if from center to edge.
This is an illustration of the coordinate system:

[[Image:Cockpit Coordinate System.png|center|illustration of the coordinate system]]

Cockpit Reference

2013-03-12T15:05:56Z

Epsy: /* Position and Size */ Added section content for <Align> and <Size> tags, and for the min-/maxadjust <Anchor> parameters

{{Cockpits Blurb}}

This page describes all the cockpit-related features available in the 0.4-cockpit branch. It has not been merged into 0.4 yet. The current features are explained on the [[Cockpit Tutorial]] page.

==The boilerplate==

<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE Resource SYSTEM "cockpit.dtd">

<Resource type="aacockpit" name="<span style="color: #999">cockpit name</span>" version="<span style="color: #999">a version</span>" author="<span style="color: #999">your name</span>" category="<span style="color: #999">a category</span>">
<Cockpit version="0.0.1">
<span style="color: #999">Widgets go here</span>
</Cockpit>
</Resource>

The attributes of the <code><Resource></code> tag form the path your cockpit will have to be placed at:

author/category/name-version.aacockpit.xml

If category is omitted or empty, the resource will be straight under the author directory. It can contain forward slashes, in which case the file will be several directories deep. See also [[Testing Resources]].

A few rules and recommendations:
* Don't use spaces/
* Don't use dashes(<code>-</code>) in the name.
* Use numbers or dotted numbers for your version. For example, you could use <code>1</code>, <code>1.5</code> or <code>0.4.3</code>. Make the version number increase as you publish updates and be consistent with the number of dots in it.
* Be consistent with your author name.

Inside the <code><Cockpit></code> tag is where the widgets go. A widget is an element on the HUD. Do '''not''' change the version on that tag. It may be used to introduce backward-compatibility changes in the future.

==Common Attributes==

===camera===

===viewport===

===toggleSticky, toggleDefault===

===usetemplate===

==Common Tags==

===Position and Size===

Cockpit widgets are positioned with up to 4 tags:
# <code><Anchor></code> designates an anchor relative to the total output area. -1,-1 is the lower-left corner of the output, 1,1 is the higher-left corner.
# <code><Position></code> positions the widget, relative to the anchor you defined. One unit in a direction is the same amount of pixels than one unit in any other direction.
# <code><Size></code> gives the size of the widget. The units are also squares of pixels.
# <code><Align></code> defines what point in the widget corresponds to the point that was positionned with the two first tags. If unspecified, it defaults to the center of the widget.

====Anchor and Position====

Not all players play Armagetron on the same kind of display. Some play it on a 4:3 resolution, while others use 16:9 or 16:10. Or they could be playing splitscreen, causing each player's cockpit to be 2:3 or 32:9. While those last two cases are a bit extreme, your cockpit has to be able to adapt to 4:3 or 16:9 without trouble. Armagetron used to have one coordinate system that went from -1 to 1 horizontally and from -1 to 0.5 vertically. It was tailored for 4:3 outputs so to adapt cockpits for 16:9 it would just squish the cockpit vertically to fit.

This is no longer the case. Usually cockpit widgets are put near corners or edges of the output area. To help you do that, the <code><Anchor></code> tag lets you tell Armagetron just that. For instance:

<Anchor x="-1" y="-1" />

Setting the anchor at -1,-1 tells Armagetron that you are about to put your widget near the bottom left-hand side of the output. If you put it at 1,1, then you'd be in the upper right-hand side. Here is the coordinate space used for the anchor tag, on 4:3 and 16:9 outputs, respectively:

<div style="text-align: center">[[File:CockpitAnchor43.png|On a 4:3 output]] [[File:CockpitAnchor169.png|On a 16:9 output]]</div>

It will always scale to have x=-1 at the left, x=1 at the right, y=-1 at the bottom and y=1 at the top of the output. If you do not set an anchor, [[#Compatibility mode|compatibility mode]] will be implicitly triggered on the widget.

Once you have an anchor set, you can position your widget relative to it. The difference is that <code><Position></code>'s coordinate space always has a 1:1 ratio between width and height units.

<div style="text-align: center">[[File:CockpitPosition.png|How Position's coordinate space works for the previous Anchor example.]][[File:CockpitPosition169.png|The scale does not change with a different aspect ratio.]]</div>

0,0 is at the anchor you defined and the output is 2 units wide. Here, the blue elements symbolize the total output area and the anchor coordinates. The red elements show the coordinate space for the position. As you can see from the dashed square, it does not get resized vertically. If you were to write:

<Anchor x="-1" y="-1" />
<Position x=".1" y=".1" />

You would be telling Armagetron to position your widget close to the bottom left-hand corner, a fraction away from the edge of the output. It would be at an equal distance from the left and bottom edge of the screen, regardless of the output's aspect ratio.

===Size and Align===

The <code><Anchor></code> and <code><Position></code> tags have so far positioned a point on the screen.

<code><Size></code> an area of the screen to the point with its <code>width</code> and <code>height</code> attributes:

<Size width=".5" height=".4" />

This will give the widget an area that is a quarter of the width of the screen and is 5:4 in aspect ratio. The coordinate space for the size is the same as for the <code><Position></code> tag. The size is measured from edge to edge, with most widgets occupying exactly this space. Captions do not count towards it and can be on the outside of it.

<code><Align></code> is a convenience tag that lets you redefine how the widget aligns with its set position. It positions a point relative to the widget body, like <code><Anchor></code> sets a point relative to the output area.

===Adjusting position and size depending on aspect ratio===

The <code><Anchor></code> tag also accepts <code>minadjust</code> and <code>maxadjust</code> attributes. When the widget is processed, its <code><Position></code> and <code><Size></code> are multiplied by a factor. This factor is determined by dividing the output height by its width, then clamping that value so that it is at least <code>minadjust</code>'s value and at most <code>maxadjust</code>'s value. Those attributes both default to 1, so that no change is made by default.

For instance, a widget is positioned and sized like this:

<Anchor x="0" y="-1" minadjust="0.1" maxadjust="0.7" />
<Position x="0" y="0.1" />
<Align x="0" y="-1" />
<Size x="0.5" y="0.5" />

If the output size is 1024x768(or any 4:3 aspect output), the factor is <code>768/1024 = 0.75</code>. This is over the <code>maxadjust</code> parameter, so it becomes <code>0.7</code>. That factor then multiplies the <code><Position></code> and <code><Size></code> tags. The above code would be equivalent to, in this case:

<Anchor x="0" y="-1" />
<Position x="0" y="0.07" />
<Align x="0" y="-1" />
<Size x="0.35" y="0.35" />

If the output size is 1280x800(or any 16:10 aspect output), the factor is <code>800/1280 = 0.625</code>. This is between the adjust parameters, so it is unchanged. It is then used to multiply the position and size:

<Anchor x="0" y="-1" />
<Position x="0" y="0.0625" />
<Align x="0" y="-1" />
<Size x="0.3125" y="0.3125" />

===Background, Foreground and LineColor===

===Caption===

===DataSet===

==Widgets==

===Rectangle===

===BarGauge and VerticalBarGauge===

===NeedleGauge===

===Label===

===Map===

===Camview===

==Related settings==

IllegalExit/Board

2013-01-24T19:31:20Z

Epsy: /* Participants */ Added G&D

{|- style="width: 100%; border: 2px solid #black;"
| style="background: lightgray; border: 1px solid #darkgray" | {{IllegalExitTbl}}
|}

[[File:IllegalExit05.png]]

=Policy=
Illegal Exit does not currently follow team rules popularized by other tournaments. You are not required to sign up substitutes and players can join or switch teams however they like before ''and during'' the tournament. The goal is for everyone to play as much as possible and make strong competition. Of course, as the tournament grows so will complaints and this policy may change.

=Participants=

===[http://wiki.armagetronad.org LFO]===
* sinewav@forums, Jericho@mym, Vogue@forums
* color: r3 g7 b11

===[http://forums.armagetronad.net Creeping Death]===
* orion@forums, Concord@forums, Gaz@forums
* color: r15 g0 b0

===[http://www.mymclan.com Open Team(ish)]===
* ElmosWorld@forums, fingerbib@forums (contact me if you wanna play (irc, forums, etc))
* color: r15 g13 b3

===[http://r.jumpingness.com/forum _~Rogue Tronners~_]===
* DaGarBBaGeMAN@forums, Titanaboa@forums, Overrated@forums
* color: r1 g15 b8

===[http://forums.armagetronad.net .LucK]===
* LucK@forums, ai1, ai2
* color: r0 g9 b6

===[http://forums.armagetronad.net {\/}adness]===
* Bytes@forums, Monkey@forums, Lowkey@forums
* color: r3 g16 b3

===[http://epsilon.x10.bz .e!Epsilon]===
* Absolution@forums, DeathZone@forums, nanu@aagid
* color: r0 g15 b0

===[http://wiki.armagetronad.org/index.php/Manic_Tentacles Manic Tentacles]===
* pike@ct/senior, ai1, ai2
* color: r15 g11 b14

===G&D===
* epsy@x, vov@forums, RoterBaron1337@forums
* color: r15 g8 b0

=Brackets=
To be completed one hour before event.

Cockpit Reference

2013-01-17T18:05:47Z

Epsy: /* Position and Size */ Added <Position> graphics and text.

File:CockpitPosition169.png

2013-01-17T17:56:12Z

Epsy: The scale is the same on a 16:9 aspect ratio.

The scale is the same on a 16:9 aspect ratio.

File:CockpitPosition.png

2013-01-17T17:49:53Z

Epsy: With an anchor at -1,-1 on the output described by the blue rectangle, this shows(in red) the specification of <Position>'s coordinate space.

With an anchor at -1,-1 on the output described by the blue rectangle, this shows(in red) the specification of <Position>'s coordinate space.

Cockpit Reference

2013-01-17T05:00:13Z

Epsy: /* Position and Size */ Completed part of the Anchor/Position ref

File:CockpitAnchor169.png

2013-01-17T03:45:24Z

Epsy: What the cockpit anchoring looks like on a 16:9 output.

What the cockpit anchoring looks like on a 16:9 output.

File:CockpitAnchor43.png

2013-01-17T03:43:08Z

Epsy: What the cockpit anchoring looks like on a 4:3 output.

What the cockpit anchoring looks like on a 4:3 output.

Cockpit Reference

2013-01-17T03:02:59Z

Epsy: Added subsection skeleton for common attributes.

Cockpit Reference

2013-01-17T01:33:52Z

Epsy: Created with a skeleton and the first section

Template:Cockpits Blurb

2013-01-16T23:39:02Z

Epsy: Add a category for cockpits

{{BoxLinkGroup|Cockpits|[[Cockpits List]] {{!}} [[Cockpit Tutorial]] {{!}} [[Cockpit Reference]]|Cockpit files can be used to customize the game's HUD in the current development builds and in the upcoming version 0.4.0.}}

[[Category:Cockpits]]

Cockpit Tutorial

2013-01-16T23:37:59Z

Epsy: Add the cockpits blurb

{{Cockpits Blurb}}

This document describes canonically how to create a cockpit resource file. Hopefully it'll be easy to read, too.

'''This is only fully implemented in the latest unreleased development versions. There's a [http://wiki.armagetronad.net/index.php?title=Cockpit_Tutorial&oldid=15841 snapshot of this article] that describes the features implemented in 0.3.0'''

== A Cockpit—The Concept ==

The cockpit is where you're sitting when you play the game. There is the concept of a virtual cockpit which is implemented in the internal camera view, but we'll ignore that, for the most part. Otherwise, the cockpit is where you're sitting and what you're using.

A cockpit resource file provides the layout of some of the visual items you see while you're playing. Traditionally, these were referred to as the HUD, and the HUD is still the main information that's carried in a cockpit file.

In the resource file, gauges and other things have been abstracted to a Widget. Each Widget is capable of displaying all of the information you're used to seeing, and is likely capable of displaying the same information in different formats...thanks to the cockpit resource file.

== Overview of the Cockpit file ==

The cockpit file consists of two sections. Technically they're just one, but you don't really have to worry about that. The two sections are pretty simple. The first just hooks it into the resource system for the whole game, using tags and stuff you may already know from the map files. The second section contains all the beautful cockpit stuff.

In the Cockpit section you'll find a series of widget tags that contain data tags to hook the widget into some game data. There's a caption, some position and size parameters, and so forth. You can also specify background and foreground colors, with gradiants, and with graphics, to provide a really custom gauge. Additionally, widgets can be associated with a camera, or made for all cameras, with the option of excluding specific cameras, offering the possibility to give a completely custom view for each camera you use. All of this gets mixed together and rendered to screen as your cockpit.

A complete gauge, in concept, isn't necessary a single widget in the cockpit file. As an example, you might want to build a "Performance" gauge that includes ping, frames per second, cpu usage, overall system load, and bandwidth usage. That would require placing several widgets together, stacked on top of each other or on each other's sides, to build the conceptual Performance gauge you intend. Here, we'll use "gauge" to refer to a specific gauge and "widget" to refer to the larger conceptual gauge. Most widgets that you'll build will just be gauges, so it's not a big deal. (Note: At the time of writing, all of the data in the hypothetical Performance gauge isn't available to the cockpit, but the system is easily extensible and there's no reason to think it will never be available)

Within each gauge there are a series of tags that are used to define what it looks like, what data it uses, and so forth. The tags that are available vary from gauge to gauge, but the meaning of each tag never varies. Two gauges that are diametrically opposite to each other might interpret the tag differently, but it will still mean the same thing for both gauges. That's an important subtlety that you should keep in mind.

== Construction of a Gauge ==

Each gauge is a layered affair. In technical terms, first the back of the gauge is painted. Then the middle is painted on top of the back, and finally the front is painted on top of the middle. This is intended to allow for complete configurability for each gauge. The middle layer is always the representation of the data, whatever it is. The back and front are equivalent in size and shape and are intended for window-dressing. By painting a texture with alpha-blended pixels it should be possible to reshape parts of the gauge and give it a unique appearance. Two gauges can be identical in all ways except which texture is used for the front and have very different appearances to the user.

Gauges that are text-driven are generally constructed on a table. While you don't have to use a table to build the gauge, the table allows you to organize it in rows and columns, which is the most useful way to organize data that you expect to read only in glances.

Each gauge has to specify which piece of data it displays, along with related pieces of data, and how to display them. This can vary dramatically! As an example, on the old HUD, in the rubber gauge, you saw a needle with some text to show the amount of rubber currently used. Then you had a minimum, which was 0, and a maximum, which varied from server to server. In the new rubber gauge you'll choose an appropriate widget and tell it where to get its minimum, its maximum, and its current data. Technically this is implemented with callbacks so that any data can be made available to be used by a gauge, even if it doesn't make sense to do so, and the callback name to use is what you'll give it in the cockpit file. If that doesn't make sense to you, don't worry about it. Just make sure to provide what's needed to show your gauge and be happy.

Every gauge supports an attribute called "camera". The camera attribute allows you to specify for which camera the gauge will appear. This in turn allows your cockpit to look/feel/be completely different depending on the user's camera. The primary purpose is to allow the internal camera to actually appear like you're inside the light cycle while providing minimal HUDs for the other cameras, and it's this purpose from which the name "cockpit" is derived. But you shouldn't let that block your creativity when you're creating your own nice cockpit. Possible cameras are:

* <code>custom</code>—Custom camera
* <code>follow</code>—Following camera (the one that follows the cycle, but doesn't turn by itself)
* <code>free</code>—Free camera
* <code>in</code>—Incam and the autoincam of the smartacm if enabled
* <code>server_custom</code>—Server–defined custom camera
* <code>smart</code>—Smartcam, default camera
* <code>mer</code>—The new mercam
* <code>all</code> or <code>*</code>—All cameras at once (default if you omit the attribute)

The camera attribute can contain multiple cameras separated by spaces, if it starts with a <code>^</code> the widget will appear in all cameras but the ones specified. Examples:

* <code>camera="in"</code>—Only show in incam mode
* <code>camera="^in free"</code>—Don't show in in– or freecam mode, but in everything else
* <code>camera="^all"</code>—Never show, kinda pointless.

Finally all gauges support the <code>viewport</code> attribute. Possible values are “top”, “cycle” and “all”, the latter being the default. “top” means that the widget will be rendered on top of the screen, “all” means it will be rendered for every player in multiplayer mode. Some data sources are only available in “all” mode, but you might not want a separate map for each player, so choose “top” then.

“cycle” is a special viewport, it means that the widget will be rendered over every cycle, just like the label (name). The orign of the coordinate system will be right above the centre of the label in this case.

== General Gauge Information ==

Every gauge supports an interpretation of some tags that are needed for every gauge. We'll discuss those here.

=== Data Source ===

The DataSet tag is a container that contains AtomicData tags. It defines all of the data that will be used to construct the gauge and may contain from 1 to 3 AtomicData tags within it. Here's an example:

<DataSet>
<AtomicData field="source" source="player_speed" />
<AtomicData field="minimum" source="0" />
<AtomicData field="maximum" source="max_speed" />
</DataSet>

As you can see, each AtomicData tag contains two attributes, field and source. Field may be any of source, minimum, or maximum. Source determines where the data will be retrieved. If the contents of source match up with a known location of data, then that location will be called. If not, then the contents of source will be the data. This is easier to understand by just reading the snippet given, where "player_speed" will put the player's cycle's current speed in the field "source", but it will just put "0" in the field "minimum". This snippet is a speed gauge, and you can easily visualize a needle with 0 on the left, "max_speed" on the right, and the player's current speed marked by the needle itself as on the old HUD.

A DataSet can have an id associated with it that you can use to refer to it later for presentation. This is most important in a Label. Indeed, it's required in a Label but it doesn't really make sense in a NeedleGauge, does it?

==== Possible contents for data sources ====

===== Numbers =====

Those can be whole numbers or fractions. Examples: <code>source="42"</code>, <code>source="1.5"</code>

===== Strings =====

Any text, example: <code>source="Hello World!"</code>

===== Configuration Items =====

Any config items as you would type them on the console to get their value: <code>source="CYCLE_RUBBER"</code>

===== Special Values =====

These values are replaced by actual data from the game. Here's a complete list of possibilities:


{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"
! souce="…"
! Content
|-
| player_rubber || The rubber that's used for the player currently being watched. Ranges from 0 to CYCLE_RUBBER.
|-
| current_ping || The ping time in milliseconds for the client. Note, in order for this to work, it needs to be assigned to all viewports, ie: viewport="all".
|-
| player_speed || The speed of the cycle currently being watched.
|-
| max_speed || The theorethical maximum of the speed a cycle can reach according to the current settings.
|-
| player_brakes || The amount of brakes left. Ranges from 0 to 1.
|-
| enemies_alive || The number of enemies alive, from the view of the player the viewport belongs to.
|-
| friends_alive || The number of teammates alive, from the view of the player the viewport belongs to.
|-
| current_framerate || The current framerate in frames per second.
|-
| current_acceleration || The current cycle acceleration in m/s^2. Note, this is instantaneous acceleration, not average acceleration.
|-
| time_since_start || The time the game is running in seconds.
|-
| current_minutes || The time of the day in minutes.
|-
| current_hours || The time of the day in hours.
|-
| current_hours12h || The time of the day in hours (12- hour format).
|-
| current_seconds || The time of the day in seconds.
|-
| current_score || The score of the player the viewport belongs to.
|-
| top_score || The highest score.
|-
| fastest_speed || The speed of the fastest cycle.
|-
| fastest_name || The name of the player that's fastest right now.
|-
| fastest_speed_round || The speed of the fastest cycle during the whole round. This doesn't have to be the fastest cycle on the grid, it is just the hightest “peak”.
|-
| fastest_name_round || The name of the player that reached the hightest speed during the round.
|-
| time_to_impact_front || The approximate time it will take the cycle to reach a wall in front of it. This source is stupid, it has no prediction, so if it returns 3 seconds and someone drives in front of you in that time it will jump
|-
| time_to_impact_right || Same as time_to_impact_front, but on the right side (if you were to turn in that direction without loss of speed)
|-
| time_to_impact_left || Same as time_to_impact_front, but on the left side (if you were to turn in that direction without loss of speed)
|-
| current_song || The filepath to the song that's currently played. Should be altered to display the title instead.
|-
| current_name || The name of the player that's currently being watched
|-
| current_colored_name || The name of the player that's currently being watched, in the correct color
|-
| current_pos_x || The position of the player in grid units, x- coordinate
|-
| current_pos_y || The position of the player in grid units, y- coordinate
|}

=== Position and Size ===

Position and size are given by two tags, aptly "Position" and "Size". The point given by position represents the center of the gauge. Don't forget this! It's common for the position point of a widget to be the top left corner, but that is not the case. Here, it's the center of the gauge. An example says everything that needs to be said:

<Position x="-0.165" y="-0.9" />
<Size height="0.15" width="0.15" />

Positions and sizes are not in pixels, but in units of a special coordinate plane. The point at the bottom left is always (-1, -1) and the point at the bottom right is always (1, -1). So the x- coordinate always goes from -1 (left) to 1 (right).

The y- coordinate is chosen in a way so x and y have the same scale. (-1, 1) would refer to the point that is (width of your screen) up from the bottom edge. Of course, for most screens this means this point is off the screen.

This is an illustration of the coordinate system:

[[Image:Cockpit Coordinate System.png|illustration of the coordinate system]]

=== Field Flags ===

Besides determining where the data should come from for a given field it is also necessary to tell the gauge whether or not to show that field. It's important to understand the distinction between using the data to draw the gauge and displaying the data on the gauge. The canonical example is the brake gauge displayed as a bar. In this example, minimum is always 0 and maximum is always 1, and current is always something in between. In order to compute the size of the gauge for the purpose of drawing the bar, you must have AtomicData for all three fields as discussed above. But you may not want to present that data. Maybe you just want to see the bar and nothing else. In that case, you need to deal with the field flags. How to actually use them is best seen in an example:

<ShowCurrent value="true" />
<ShowMaximum value="true" />
<ShowMinimum value="true" />

=== Reverse ===

Sometimes it's better to show a gauge the other way, ie the maximum on the left instead of on the right. This is how it's done:

<Reverse value="true" />

=== Caption ===

Every gauge can have a caption. The caption need not be displayed. Again, an example says everything that needs to be said:

<nowiki><Caption location="bottom">
<Text value="Speed" />
</Caption></nowiki>

Possible locations are top, bottom, and off. Location of "off" means the caption won't be displayed.

=== Layers ===

As previously discussed, each gauge is drawn with three layers. So far we've only talked about what is shown in the middle layer, the data layer. That is the gauge itself. In addition to the middle layer you have the background and foreground layers in which you can draw, and they are done with the aptly named Background and Foreground tags. You can put textures, solid colors, and gradients, or just leave the tag out completely if you don't need it. Here are some examples:

* A solid foreground color, red, with no alpha transparency.

<Foreground>
<Solid>
<Color r="1." g="0." b="0." alpha="1." />
</Solid>
</Foreground>

* A lightly transparent 3-color gradient. The "at" parameter marks the borders between the colors and ranges from 0 to 1. The orientation determines how the gradient will be drawn.

<Foreground>
<Gradient orientation="horizontal">
<Color r="0." g="1." b="1." alpha=".7" at="0" />
<Color r="0." g="0." b="1." alpha=".7" at=".5" />
<Color r="1." g="0." b="1." alpha=".7" at="0.8" />
</Gradient>
</Foreground>

: There are three different types of gradients, indicated by the orientation attribute. Possible values are "horizontal" and "vertical" which will make horizontal or vertical gradients. A special value is "value" which will result in a solid area which changes color according to the value of the displayed data. The color with at="0" will be used at the minimum value and at="1" will be used at the maximum.

==== Textures ====

There's some basic support for textures in recent builds. A texture can be added to any <code><Foreground /></code>/<code><Background /></code> tag, either instead or before the color or even gradient. Although you can specify a texture for all gauges that support foregrounds/backgrounds they only make sense for widgets that render more than just lines :-)

Here's an example of a working texture:

<Background>
<Image scale_x="1" scale_y="1" repeat="both">
<Graphic category="" author="wrtlprnft" version="1" name="wood_512" extension="jpg" uri="http://wrtlprnft.ath.cx/wood512.jpg" />
</Image>
<Solid>
<Color r="1." g="1." b="1." alpha=".5" />
</Solid>
</Background>

The <code><Image /></code> tag supports the following attributes:

;<code>scale_x</code>/<code>scale_y</</code>
:The scale factor for the texture. If both are set to <code>1</code> the texture is stretched so it covers the entire area of the widget.
;<code>repeat</code>
:Can be one of <code>none</code>, <code>x</code>, <code>y</code> or <code>both</code>. This specifies in which directions the texture will repeat itself. The area not covered by the image will be filled by the last row/column of the texture. Usually you'll want <code>both</code>, so this is the default.

The <code><Graphic /></code> tag contains information on where to find the texture. The attrubutes <code>author</code> (default: the author of the cockpit), <code>category</code> (default:the category of the cockpit), <code>name</code>, <code>version</code> and <code>extension</code> (default: <code>png</code>) specify the resource path of the texture, <code><author>/<category>/<name>-<version>.<aatex>.<extension></code>. If the attribute <code>uri</code> is given the file will be downloaded from the given URI instead of the resource repository if it's not already cached.

If there's a <code><Color /></code> or <code><Gradient /></code> tag after the <code><Image /></code> tag the color at each pixel of the texture will be multiplied by the color at the corresponding point of the gradient (or the single color given). In the example this is used to make a semitransparent background image.

'''General advice on textures''': Make sure the dimensions of every image you want are in powers of two, for example 64×64, 256×256, 512×512 or 1024×1024. Rectangular images are OK, too, so you can use 32×1024 images, too, if you really want to. Images of other dimensions will be scaled to be powers of two by OpenGL, which doesn't excactly lead to pretty results.

== Available Gauges ==

Here are all of the available gauges, along with which tags are supported.

=== NeedleGauge ===

A needle gauge requires all three fields to exist in the DataSet tag. It supports all general tags. Here's an example speed gauge:

<NeedleGauge camera="*">
<DataSet>
<AtomicData field="source" source="player_speed" />
<AtomicData field="minimum" source="0" />
<AtomicData field="maximum" source="max_speed" />
</DataSet>
<Position x="-0.165" y="-0.9" />
<Size height="0.15" width="0.15" />
<ShowCurrent value="true" />
<ShowMaximum value="true" />
<ShowMinimum value="true" />
<Caption location="bottom">
<Text value="Speed" />
</Caption>
<Foreground>
<Solid>
<Color r="1." g="0." b="0." alpha="1." />
</Solid>
</Foreground>
</NeedleGauge>

=== BarGauge ===

A bar gauge requires all three fields to exist in the DataSet tag. It supports all general tags. Here's an example rubber gauge:

<BarGauge camera="^in">
<DataSet>
<AtomicData field="source" source="player_rubber" />
<AtomicData field="minimum" source="0" />
<AtomicData field="maximum" source="cycle_rubber" />
</DataSet>
<Position x="-0.55" y="-0.9" />
<Size height="0.05" width="0.15" />
<ShowCurrent value="true" />
<ShowMaximum value="true" />
<ShowMinimum value="true" />
<Caption location="bottom">
<Text value="Rubber" />
</Caption>
<Background>
<Gradient orientation="value">
<Color r="0." g="1." b="0." alpha=".0" at="0." />
<Color r="0." g="1." b="0." alpha=".1" at=".3" />
<Color r="1." g="1." b="1." alpha=".2" at=".4" />
<Color r="1." g="1." b="1." alpha=".2" at="1." />
</Gradient>
</Background>
<Foreground>
<Gradient orientation="value">
<Color r="0." g="1." b="0." alpha=".7" at="0." />
<Color r="0." g="1." b="0." alpha=".7" at=".3" />
<Color r="1." g="1." b="0." alpha=".7" at=".6" />
<Color r="1." g="0." b="0." alpha=".7" at=".8" />
<Color r="1." g="0." b="0." alpha=".7" at="1." />
</Gradient>
</Foreground>
</BarGauge>

=== VerticalBarGauge ===

Identical to a BarGauge, but renders vertically instead. Labels are currently broken for it, so don't use them yet.

=== Label ===

A label may have only one field in each DataSet tag and that field must be "source". It also requires each DataSet to have an id, which you will use to reference that data farther down. It supports any number of DataSets. In addition, you need a Face to describe how to build the Label. Here's an example for the enemies alive gauge:

<pre>
<Label camera="*">
<DataSet id="enemies">
<AtomicData field="source" source="enemies_alive" />
</DataSet>
<DataSet id="friends">
<AtomicData field="source" source="friends_alive" />
</DataSet>
<Position x="0.06" y="-0.96" />
<Size height="0.035" width="0.017" /> 
<Caption location="off">
<Text value="Player Status" />
</Caption>
<Face>
<Table>
<Row>
<Cell><Text value="Enemies:" /></Cell>
<Cell><GameData data="enemies" /></Cell>
<Cell><Text value="Friends:" /></Cell>
<Cell><GameData data="friends" /></Cell>
</Row>
</Table>
</Face>
</Label>
</pre>

==== Tables ====

A table is much like a basic HTML table: It consists of rows, coulumns, and cells. Each cell can contain multiple <Text> or <GameData> nodes, they will just be concatenated. Here's an example of a table that shows the time, the framerate, and how long Armagetron Advanced is running:

<nowiki> <Label camera="*" viewport="top">
<DataSet id="hours">
<AtomicData source="current_hours12h" minwidth="2" fill="0" />
</DataSet>
<DataSet id="minutes">
<AtomicData source="current_minutes" minwidth="2" fill="0" />
</DataSet>
<DataSet id="ampm">
<Conditional field="source" lvalue="current_hours" rvalue="12" operator="le">
<IfTrue>
<AtomicData source="AM" />
</IfTrue>
<IfFalse>
<AtomicData source="PM" />
</IfFalse>
</Conditional>
</DataSet>
<DataSet id="fps">
<AtomicData source="current_framerate" />
</DataSet>
<DataSet id="seconds">
<AtomicData source="time_since_start" />
</DataSet>
<Position x="0.4" y="0.45" />
<Size height="0.04" width="0.02" /> 
<Caption location="top">
<Text value="Time/Fps/Timestamp" />
</Caption>
<Face>
<Table>
<Row>
<Cell><Text value="Time:" /></Cell>
<Cell><GameData data="hours" /><Text value=":" /><GameData data="minutes" /><Text value=" " /><GameData data="ampm" /></Cell>
</Row>
<Row>
<Cell><Text value="Framerate:" /></Cell>
<Cell><GameData data="fps" /><Text value=" FPS" /></Cell>
</Row>
<Row>
<Cell><Text value="Running for:" /></Cell>
<Cell><GameData data="seconds" /><Text value=" Seconds" /></Cell>
</Row>
</Table>
</Face>
</Label></nowiki>

=== Map ===

The Map is a very special gauge that displays a map of the arena. As a special gauge it has very special requirements. It supports Position, and Size, nothing else. Also, it will anchor its own aspect ratio, so it might not use the whole width or height you specified. The map will be as big as possible while keeping its aspect ratio and fitting in the width and height you specify.

Here's an example:

<Map camera="*" viewport="top">
<Position x="0.73" y="-0.72" />
<Size height="0.25" width="0.25" />
</Map>

==== Map Settings ====

You can configure the way the minimap looks by using a special <code><MapModes /></code> tag. It should contain one or more <code><MapMode /></code> tags, like this:

<Map>

<MapModes toggleKey="1">
<MapMode mode="full" rotation="spawn" />
<MapMode mode="closestZone" rotation="spawn" />
<MapMode mode="cycle" rotation="camera" zoomFactor="3" />
<MapMode mode="cycle" rotation="cycle" zoomFactor="3" />
<MapMode mode="cycle" rotation="spawn" zoomFactor="4" />
<MapMode mode="full" rotation="fixed" />
</MapModes>
</Map>

<code>toggleKey</code> is a cockpit key that can be used to switch between the settings given in the <code><MapMode /></code> tags. These are independent of each other. They can have the following attributes:

;<code>mode</code>
:The way the map pans. Currently the following values are implemented:
:;<code>full</code>
::The default; show the entire map
:;<code>cycle</code>
::Center around the cycle, like a radar
:;<code>closestZone</code>
::Center around the closest zone
;<code>zoomFactor</code>
:This determines how much of the map you see at once. If the mode is <code>full</code>, this doesn't have any effect, if it's <code>cycle</code> it'll be multiplied by the cycle's speed, and if it's <code>closestZone</code> it'll be multiplied by the zone's radius
;<code>roatation</code>
:This controls how the map is rotated. Valid values are:
:;<code>fixed</code>
::Don't rotate at all; positive y-coordinates will be at the top of the map.
:;<code>spawn</code>
::Rotate the map so the direction the cycle spawned in is facing upwards
:;<code>cycle</code>
::Rotate so the current cycle is always facing upwards
:;<code>camera</code>
::Rotate so the direction the camera is facing is pointing upwards on the map

== Gauge Templates ==

Templates can be used for multiple similar gauges. Say you want three gauges for Brakes, Speed and rubber, they're all the same exept for position, caption and data.

You could copy and paste the different attributes, but that leads to a larger file, and if you later decide you want your gauges smaller you'd have to edit all three of them. That's where templates come in.

This is how you define a template:

<WidgetTemplate id="MyTemplate">
<Size height="0.3" width="0.3" />
<Position y="-.7" x="0" />

</WidgetTemplate>

The <code>id</code> attribute is used to reference your template for later use. Inside a <code><WidgetTemplate /></code> you can have all possible tags for widgets.

This is how you use your template:

<NeedleGauge usetemplate="MyTemplate">
<Position x="-.5" y="0" />

</NeedleGauge>

This internally gets replaced by the following:

<NeedleGauge>
<Size height="0.3" width="0.3" />
<Position y="-.7" x="0" />

<Position x="-.5" y="0" />

</NeedleGauge>

See how there's two <code><Position /></code> tags now? Since there's more than one tag they'll get added to each other, resulting in the widget being positioned at (-.5, -.7). <code><Size /></code> tags will get multiplied, so you could scale a template. All other tags just overwrite each other, so the last one "wins".

You can use multiple templates in one tag by seperating their names by spaces, like this: <code><Label usetemplate="MyTemplate MyOtherTemplate">...</Label></code>

== Toggle Keys ==

Are you annoyed by the HUD map being to small, but don't like a big map permanently cluttering up your screen? There's a solution, toggle keys. You can map the five available toggle keys in the global keybord configuration screen, and what they do depends entirely on the cockpit file.

Here's an example of a HUD map that gets toggled by key 1 and is visible by default (that is, until you press the key and turn it off):

<Map camera="*" viewport="top" toggle="1" toggleSticky="true" toggleDefault="on" >
<Position x="0" y="-.25" />
<Size height=".75" width="0.7" />
</Map>

There are three attributes that influence toggling behavior:
;toggle
:The toggle key to be used, needs to be a number from 1-5 or 0 for no toggle key (default if you omit it)
;toggleSticky
:If the value is "true" (default) pressing the key and releasing it will change the visibility. If it is false pressing the key and holding it will change the state, but it will return the default once you release it.
;toggleDefault
:"on" (default) means the widget will be visible until you press the toggle key, "off" means it will be invisible first.

== For Server Admins ==

There are many new kinds of gauges that might be considered as cheating by some people, or at least it gives a certain advantage to people who use them.

If you want to disable certain data sources you can change the FORBID_COCKPIT_DATA setting. It contains a colon–separated list of data sources that will be disabled (it will just display 0 instead of a value):

FORBID_COCKPIT_DATA time_to_impact_front:time_to_impact_left:time_to_impact_right:player_rubber

This will prevent the client from displaying the time_to_impact data sources and the current rubber. Likewise the HUD minimap can be disabled by the following command:

FORBID_HUD_MAP 1

Bear in mind, though, that the server has no way of knowing if the client is actually following these rules. All data sources use data that is known to the client, it wouldn't be hard to hack a client to ignore this setting. This is basically the same problem as with the FORBID_CAMERA_* settings: You have to trust on the users of your servers to play fair.

== QA and release ==

For testing your cockpit, see [[Testing Resources]]. You can make your work available to others by uploading it to the [[Resource repository]]. If you do that, you might want to add an entry to [[Cockpits list]] to tell users about your cockpit.

[[Category:Client Features]]

Template:Cockpits Blurb

2013-01-16T23:36:10Z

Epsy: Unlink Cockpits as it is now just a redirect to Cockpits List

Cockpits List

2013-01-16T23:35:07Z

Epsy: Add the cockpits blurb

{{Cockpits Blurb}}

This is a list of a few cockpit files that are available. You can only use them if you have downloaded a version of Armagetronad later than 0.3.0_alpha4872 and if you know how to use the [[Console]]. Be aware that your use of upper/lowercase for the console command matters. To make your own cockpits see the [[Cockpit Tutorial]].

== Abyss ==

[[Image:Abyss-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Abyss]]
;Author
:[[User:Spidey|Spidey]]
;Description
:TODO-Spidey: add this.
;Console Command
:<code>COCKPIT_FILE spidey/abyss-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/spidey/abyss-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Classic ==

[[Image:Classic-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Classic cockpit]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]]
;Description
:This cockpit file tries to emulate the cockpit of 0.2.8 as much as possible. It doesn't include a HUD minimap and uses the traditional needle gauges. Boooooring.
;Console Command
:<code>COCKPIT_FILE wrtlprnft/classic-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/classic-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Essential ==

[[Image:Essential-0.0.5_(win).png|thumb|
Essential (win)]]
[[Image:Essential-0.0.5_(death+debug).png|thumb|
Essential (death+debug)]]
;Author
:[[User:rain|rain]]
;Description
:Simple, lightweight, or just essential.
:New version (0.0.5) is finally ready, some layout modifications and some features added. It is working good with aa v0.3_alpha_z1333. Enjoy.
;Toggle Keys
:1: hide/view brake and speed labels
:2: view/hide debug tools (see screenshots...)
;Console Command
:<code>COCKPIT_FILE rain/essential-0.0.1.aacockpit.xml</code>
:<code>COCKPIT_FILE rain/essential-0.0.5.aacockpit.xml</code>
;Resource Repository Link
:[http://resource.armagetronad.net/resource/rain/essential-0.0.1.aacockpit.xml Version 0.0.1]
:[http://resource.armagetronad.net/resource/rain/essential-0.0.5.aacockpit.xml Version 0.0.5]
<div style="clear:right;"></div>

== Essential Remix ==

[[Image:Screenshot_78.png|thumb|EssentialRemix v3.6 (alive)]]
[[Image:Essentialremix-0.3.1.aacockpit002.png|thumb|EssentialRemix v3.6 (death)]]
;Author
:[[User:Flex|Flex]]
;Description
:A "remix" to rains Essential Cockpit (New homepage at http://flex.armagetron.co.uk/essentialremix/).
;Toggle Keys (0.3.7)
*Toggle key 1: Toggle between the top right labels. Time & FPS / Fastest player & Max rubber.
*Toggle key 2: Show/Hide Minimap.
;Console Command
:<code>COCKPIT_FILE flex/cockpits/essentialremix-0.3.7.aacockpit.xml(http://flex.armagetron.co.uk/resource/flex/cockpits/essentialremix-0.3.7.aacockpit.xml)</code>
;Resource Repository Link
:[http://flex.armagetron.co.uk/resource/flex/essentialremix-0.3.6.aacockpit.xml Version 0.3.6]
:[http://flex.armagetron.co.uk/resource/flex/cockpits/essentialremix-0.3.7.aacockpit.xml Version 0.3.7] (Fixed the minimap not working on latest 0.3.x clients.)
<div style="clear:right;"></div>

== Pink ==

[[Image:Pink-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Pink]]
;Author
:[[User:Spidey|Spidey]]
;Description
:TODO-Spidey: add this.
;Console Command
:<code>COCKPIT_FILE spidey/pink-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/spidey/pink-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Playroom ==

[[Image:Playground-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Playground]]
;Author
:[[User:Lucifer|Lucifer]]
;Description
:This cockpit is designed for fortress play. All gauges are placed near where your eyes are normally focused so you never have to look far. Play with it enough and you find you always know your speed, amount of brake, and stuff. Enemies alive gauge is color-coded to show at a glance whether or not you're outnumbered. Look at the gauge itself to see how badly you're outnumbered, and look at the map to see where everybody is.
;Console Command
:<code>COCKPIT_FILE Lucifer/sick/Playroom-0.0.1.aacockpit.xml</code>
<div style="clear:right;"></div>

== Skypit ==

[[Image:Skypit-0.0.1.aacockpit.xml.png|thumb|Skypit]]
;Author
: LukeSky
;Description
:Toggle Key 1 -> Map
:Toggle Key 2 -> Time/FPS
;Console Command
:<code>COCKPIT_FILE lukesky/skypit-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/lukesky/skypit-0.0.1.aacockpit.xml Version 0.0.1]
<div sryle="clear:right;"></div>

== Standard Cockpit ==

[[Image:Standard-0.0.1.aacockpit.xml (Screenshot) (1).png|thumb|Standard cockpit in smartcam mode]]
[[Image:Standard-0.0.1.aacockpit.xml (Screenshot) (2).png|thumb|Standard cockpit in incam mode]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]] and [[User:Lucifer|Lucifer]]
;Description
:This is the default cockpit in 0.3.0. It has the new HUD map and bar gauges, but displays about the same data as 0.2.8.
:Try switching to incam mode for a camera tailored to incam playing.
;Console Command
:<code>COCKPIT_FILE Anonymous/standard-0.0.1.aacockpit.xml</code>
<div style="clear:right;"></div>

== Vanoriginal ==

[[Image:Vanoriginal-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Vanoriginal]]
;Author
:[[User:Vanhayes|Vanhayes]]
;Description
:I Made all the meters Vertical Bar guages, took out all of the information that was showed in the top right corner except time and FPS, though you can toggle them off.Put the enemies/friends alive meter from incam. You can also toggle off the map If it is in the way and you can toggle on the impact meters, Front left and right.The toggles are cockpit keys: 1(map),2(impact meters), and 5(FPS/Time)
;Console Command
:<code>COCKPIT_FILE Vanhayes/cockpit/vanoriginal-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/Vanhayes/cockpit/vanoriginal-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Wrtl's Cockpit ==

[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (1).png|thumb|
Wrtl's cockpit with everything at initial state]]
[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (2).png|thumb|
Wrtl's cockpit with the HUD map switched off]]
[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (3).png|thumb|
Wrtl's cockpit with dimmed 3D rendering]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]]
;Description
:This is my approach on creating the ultimate cockpit.
:The huge rubber gauge on the left helps you know instantly how risky you can play and the player information on the top right helps you determine if your help defending is needed.
:On the bottom right is a special gauge that shows the approximate time to the next impact with a wall, useful if you want to know if you outgrinded someone. You can switch of the big map by pressing the first cockpit key (bind it in global keyboard config) and dim the 3D rendering by pressing the second key—useful for chico maps.
;Console Command
:<code>COCKPIT_FILE wrtlprnft/testfile-0.0.1.aacockpit.xml</code>
;Resource Repository Links
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/testfile-0.0.1.aacockpit.xml Version 0.0.1]
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/testfile-0.0.3.aacockpit.xml Version 0.0.3—doesn't work with 0.3.0, will work with 0.3.1]
<div style="clear:right;"></div>

== Xevi's Cockpit ==

[[Image:Xevi-0.0.3.aacockpit.xml (Screenshot).png|thumb|Xevi's Cockpit, version 0.0.3]]
[[Image:Xevi-0.0.4.aacockpit.xml (Screenshot).png|thumb|Xevi's Cockpit, version 0.0.4]]
[[Image:Xevi_cockpit_05.JPG|thumb|Xevi's Cockpit, version 0.0.5]]
[[Image:Xevi.0.0.7.JPG|thumb|Xevi's Cockpit, version 0.0.7]]
;Author
:[[User:Xevic|Xevi]]
;Description
:Some evolutions of the real hud ;) there are also versions 0.0.1 and 0.0.2, but they are just a step to 0.0.3, then there is a couple of evolutions, in 0.0.4 I added wrtl's impact time widget. Version 0.0.5 adds warning bars, there is one for front impact, another for left and one for right. The new 0.0.6 is a improvement of last one with better look bars and better parameters. News on 7: bars tunning, front impact moved bottom to allow better notice, avoid chat and transparency problems there, new big map switch with toggle 3, now it won't desappear, it will appear the full screen version.
Enjoy them.
;Console Command
:<code>COCKPIT_FILE xevi/xevi-0.0.7.aacockpit.xml</code>
;Resource Repository Links
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.3.aacockpit.xml Version 0.0.3]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.4.aacockpit.xml Version 0.0.4]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.5.aacockpit.xml Version 0.0.5]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.6.aacockpit.xml Version 0.0.6]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.7.aacockpit.xml Version 0.0.7]
:[http://crazy-tronners.com/resource/xevi/xevi-0.0.8.aacockpit.xml Version 0.0.8] -> last version on 0.3.0
:[http://crazy-tronners.com/resource/xevi/xevi-0.0.9.aacockpit.xml Version 0.0.9] -> minimap 0.3.1 ready.
<div style="clear:right;"></div>

[[Category:Client Features]]

Cockpits

2013-01-16T23:33:52Z

Epsy: Redirect to Cockpits List

#REDIRECT [[Cockpits List]]

Cockpit

2013-01-16T23:33:40Z

Epsy: Redirect to Cockpits List

#REDIRECT [[Cockpits List]]

Template:Cockpits Blurb

2013-01-16T23:32:17Z

Epsy: Create a blurb for cockpit pages

{{BoxLinkGroup|[[Cockpits]]|[[Cockpits List]] {{!}} [[Cockpit Tutorial]] {{!}} [[Cockpit Reference]]|Cockpit files can be used to customize the game's HUD in the current development builds and in the upcoming version 0.4.0.}}

Template:BoxLinkGroup

2013-01-16T23:24:48Z

Epsy: Added a category

<includeonly><div class="box box-linkgroup" style="background: rgba(255,255,255,.65); padding: 2px;"><div class="linkgroup-links" style="background: lightgray;">'''{{{1}}}''' | {{{2}}}</div><div class="linkgroup-description">{{{3|}}}</div></div></includeonly><noinclude>This template is useful for grouping a few pages together and linking between them.

==Usage==

Give a title as first argument, and a <code><nowiki> {{!}} </nowiki></code>-separated list of links as second argument:

<nowiki>{{BoxLinkGroup|Title|[[Page One]] {{!}} [[Page Two]]}}</nowiki>

{{BoxLinkGroup|Title|[[Page One]] {{!}} [[Page Two]]}}

You can use the optional third argument to provide a description.

<nowiki>{{BoxLinkGroup|Title|[[Page One]] {{!}} [[Page Two]]|Description}}</nowiki>

{{BoxLinkGroup|Title|[[Page One]] {{!}} [[Page Two]]|Description}}

[[Category:Box Templates]]
</noinclude>

Template:BoxLinkGroup

2013-01-16T23:23:24Z

Epsy: Made description optional and added docs.

Template:!

2013-01-16T23:18:26Z

Epsy: A pipe for use in template calls.

Template:BoxLinkGroup

2013-01-16T23:15:16Z

Epsy: Created a template for grouped pages, like tournaments

Template:If

2013-01-16T23:06:43Z

Epsy: Created an if-then-else conditional for other templates

<includeonly>{{{else{{{test|}}}|{{{test{{{test|}}}|{{{then|}}}}}}}}}</includeonly><noinclude><code>if-then-else</code> conditional:

<nowiki>{{if|test=non-empty|then=yes|else=no}}</nowiki>

gives <code>yes</code>

<nowiki>{{if|test=|then=yes|else=no}}</nowiki>

gives <code>no</code>

Yanked from [http://meta.wikimedia.org/wiki/Template:Ifold WikiMedia].

[[Category:Utility_Templates]]
</noinclude>

Authentication for Players

2013-01-04T18:15:05Z

Epsy: /* Alternate Authentication Authorities */ reordered and added @x

{{Sections}} 

= Authentication for Players =

Authentication is the process of proving to a server who you are. In itself, it is not terribly useful, because you usually don't get anything for it; but the server will recognize you better, it will be impossible for others to destroy your stats by picking your name in your absence, it can make tournaments less stressful by only letting registered players participate, and it provides a more secure remote server administration interface.

== What you need ==

First, you need an account. The system is designed to be open and can accept accounts from various places; one place to get an account that works is the [http://forums.armagetronad.net official forum]. To the game, those accounts are identified as something that looks like an email address; a forum account would look like "<your user name>@forums". When you pick your username, you definitely should avoid non-ASCII characters (user names with those will likely change representation in the future), and it is wise to avoid the @ itself (and absolutely the "@forums", it gets added automatically), quotation marks, whitespace, and the symbols %, :, and \, an the sequence 0x. Not that the system can't handle them, but they have to be "escaped" or encoded and will look ugly, and if you ever want to ask a server administrator to give you elevated access rights, those symbols make it more difficult, leading to mistakes and you not getting your rights and missing the tournament.

What you also should definitely keep out of your username are clan tags. Clan affiliation can vary over time, and server admins are unlikely to go to the trouble to update their score tables to your new name, so you'll either use your past achievements or will have to go around with that outdated clan tag forever.

Second, what you don't need (but it's highly recommended anyway, see the notes on security below) is a new client. Yep. Even plain old Armagetron clients have the required functionality, way back to 0.2.6 and even earlier. See the history secion on why that is so.

What you also don't need is to post on the forums. Seriously. The only thing you may need to do on the forums if you have a very, very old account is to log out and log in again. If you just got the account, it should be ready to go.

Second, you need a server that supports authentication. The serverside part of the protocol was missing some bits all the time, again I refer you to the history section if you want to know details. Anyway, because the support is brand-new at the time of this writing, there are only a few servers out there that support authentication. At the time of this writing (outdated, pretty much all servers support it by now), those are:

*1v1 Sumo Bistro
*Bugfarm Elimination Sumo
*Chico's Brake Boost Styball
*Crazy Tronners C T F
*Crazy Tronners Catfight 2
*Crazy Tronners Open Sumo
*Crazy Tronners Wild Fortress Lounge
*Crazy Tronners Wild Sumo
*Day Tripper Fortress
*Fortress Café
*Strawberry Fields
*Tag Test
*Wild Cat
*¦×¦.Team.Sumo.Server

== Alternate Authentication Authorities ==

There are also other open-for-all authorities:

* [http://www.aagid.net @aagid]
* [http://crazy-tronners.com @ct]
* [http://deathbydistraction.net/forums @dbd]
* [http://trongame.de/forum @pru]
* [http://roadrunnerz.net @roadrunnerz.net]
* [http://x.hashpickup.net/ @x]
Some of these are tied to their forums, so all you have to do is register there.

If you only want an account that is valid on one server, talk to the administrator of that server, they can give you one.

== How to authenticate with a new client ==

Go to your player's setup menu and scroll down; you'll find an item titled "Global ID". Enter your account name there. For a forum account, that would be "<user name>@forums". The bit before the @ typically is your username, and the bit afterwards is the host where the authentication server runs, or an abbreviation thereof ("forums" is shorthand for "forums.authentication.armagetronad.net".) If you always want to be logged in to any server you play on, enable the toggle item below that, titled "Auto Login". If you don't want that, you have to hit the "Authentication" menu item in the ingame menu. If that menu item is missing, then the server does not support authentication.

You will be prompted for a password; check your username and enter the password of your account there, then press return. On the top of the menu, you can select whether you want to store your password. See the security section for recommendations. You will be either logged in or have received an error message on the console.

Of course, you can also use the following method:

== How to authenticate with an old client ==

Old clients (before 0.2.8) are missing the menu items where you can enter your account name and where you can trigger the login process. For them, you trigger the login procedure with chat commands. There are three variants.
* Plain "/login", will trigger authentication for a local server account.
* "/login <authority name>", will trigger login with an account at a remote authority.
In both cases, you'll have to enter your username at the password prompt, it will default to your current screen name (and due to a quirk, you will rename to the selected username after you logged in).
* The third way is to say "/login <account@authority>", this will try to log you log in as that, and preselect the username for you in the menu (in theory. This works for new clients only, sorry). Binding an instachat to that would probably not be a bad idea.

'''Keep in mind, that in the appearing login menu, you do not have to write the @authority part again.'''

Also beware, on old clients the "Abort" button disconnects you from the server.

== troubleshooting ==
# Make sure that you are typing your username exactly as it is at the place for authentication. For instance if you have the Player1 account on the forums it would be Player1@forums instead of player1@forums.
# If you are using an old client make sure that when you are prompted for a password that your username is correct. On older clients this will rename it to your gridname.
#Ensure that you are using the correct authority where you have an account.

== Benefits ==

Can vary. In default server settings, the only benefit you get is that the server can track you better in the hightscore tables. Other players will be able to see the account you used to log in, and that will make it harder for other players to imposter you.

One huge benefit of getting authenticated are organized tournaments. You are going to have far less problems in organized matches (clan wars and our [[Competition Hub|various other competitions]]) if you can authenticate to the server; At least, you're going to make the server administrator running the match happy because he doesn't have to constantly ask who you are :) Getting authenticated and registered with the competition manager or server admin (they'll have to authorize you) can give you access to the team management interface. If you have sufficient rights, you can

* lock your current team by saying "/lock". No further team members may then join, unless you
* invite your teammates to play with "/invite <player name>". Invited players that are not yet playing will also receive your team's /team messages.
* kick players out or revoke invitations with "/uninvite <player name>".
* unlock the team again to the public with "/unlock".

(As safeguard against teams getting orphaned in a state where nobody can invite new members or unlock it, /invite and /unlock can always be used by those active team members that have the highest access level.)

Of course, you can get the same functionality if the server admin is present and gives you the appropriate access rights with /op, but what if the server admin is a forgetful lazy bum who forgets about scheduled matches?

There may be some servers where you have to be authenticated to chat or to play, but that is not recommended; by default, servers should be open to anyone.

=== Benefits on specific servers ===

* Chico's Brake Boost Styball : [http://crazy-tronners.com/p4/commands.php Custom Commands].
* Crazy Tronners Open Sumo : [http://crazy-tronners.com/p4/commands.php Custom Commands].
* Crazy Tronners Wild Sumo : [http://crazy-tronners.com/p4/commands.php Custom Commands].

== Security ==

=== The main weakness ===

Naturally, the authentication system has been designed with security in mind. The original protocol that old clients support, however, was designed to be used on a small group of trusted servers, and that makes it vulnerable to attacks from the side of the server. The one attack that is easily possible basically works like this:
* as you enter a server, the server badmin uses a modified client to play on another server.
* as you trigger the authentication procedure, the badmin does the same on the other server.
* the badmin's server relays the communication between the other server and the badmin's client to your client, and your response is routed back.
That way, the badmin will be logged on to the other server with your user account. Such a thing is called man in the middle-attack, because the badmin is the man in the middle between you and the other server.

This is the most dangerous attack on the protocol, and the modified protocol on new clients (the ones with the "Authentication" button) has protection built in; the server IP address is entangled into the communication between server and client, so that the other server would notice that your login data was not intended for it. Unless the badmin also manages to counterfeit the other server's IP address, of course, which is not impossile; however, it would usually be much easier to steal your password by other means; web forums are a pretty insecure thing, passwords of unmodded phpBB are transmitted in plain text, for example.

=== Smaller Threats ===

- If someone gets his hands on the authentication database, he will have everything he needs to imposter anyone in it. The alternative would be to transmit something in clear text so that anyone wo intercepts it can imposter you any time.
- An infinite supply of throwaway remote accounts is possible; server admins have white and blacklists at their disposal against that, however.

If you have your own concerns, please voice them on the forums first. We don't want to let this section blow up with discussions.

=== Password Storage ===

The password menu allows you to store passwords on disk. This, of course, is insecure, as anyone who gets access to your configuration file, where the passwords are stored, will be able to use your account. The data is scrambled in a form that makes it not really feasible to extract the raw passwords, though. Anyway, our recommendation has to be not to store passwords on disk. That is especially true for users of 0.2.8.1 and earlier; there is a bug that will cause duplicate password entries to accumulate in your user.cfg.

=== Debug Recordings ===

For old clients, debug recordings where you enter passwords in the password menu are insecure, do not share them. While you can't read the password on the screen, it will be encoded in the recording and easy to extract. The same goes for the old ADMIN_PASS interface, of course.

For new clients and new servers, debug recordings are safe to share. They are cleared of the password storage data you may have in the config files, they do not contain local server accounts, and the keypresses you make while in the password menu are all replaced by "x", apart from the control keys that navigate the menu, of course.

Serverside debug recordings come with a performance penalty; as without ZThread, a recording server will make remote account lookups only between rounds.

== Small notes for server admins ==

To run an authentication server, you need an experimental version, either [http://beta.armagetronad.net/ 0.2.8_alpha20080209] (the server binaries for Linux and Windows have authentication built in) or later or SVN from the 0.2.8 branch:
svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/branches/0.2.8/armagetronad
Or of course, the same from bzr:
bzr co lp:armagetronad/0.2.8 armagetronad
followed by
cd armagetronad
./bootstrap.sh
./configure --enable-armathentication --disable-glout
make

The extra --enable-armathentication is important, authentication is not enabled by default. It is strongly recommended that you install the library [http://zthread.sourceforge.net/ ZThread] before; only with that, the requests to the remote authentication servers will be able to run in the background. Without ZThread, they will be done in the pauses between rounds. ZThread is a bit outdated and does not go well with recent versions of GCC; be sure to get the latest version (2.3.2) and to configure and build it like this (all as root):
CXXFLAGS=-fpermissive ./configure --prefix=/usr
make
make install
ldconfig

The '--prefix=/usr' is only required on systems that don't include /usr/local in /etc/ld.so.conf.

Then, have a look at the
[http://armagetronad.svn.sourceforge.net/viewvc/armagetronad/armagetronad/branches/0.2.8/armagetronad/config/settings_authentication.cfg?view=markup configration file settings_authentication.cfg], it should tell you how you can configure the system.

== Design ==

For details of the design of the system and the protocol, check out [[Hash Authentication Design|this document]].

== How to run an Armathentication Server ==

Check it out [[Authentication Server|here]].

== History ==

Back in 2001, when there was not yet a master server, the [http://www.krawall.de/ Krawall Gaming Network] approached Z-Man with a deal. They would run a master server and a couple of permanent game servers, which were pretty rare back then, and also wanted to distribute a special client with a bit of branding. Their condition: players from Germany would only be allowed to use the master server and play on the game servers with an account at Krawall.

Work was begun, a client-server protocol was specified and implemented, but somehow, the two functions only the KGN people could implement (password check and geocheck of the IPs) were never finished.

I found no source for it, but I remember a while back Tank produced a modified client that was able to authenticate over the Krawall protocol with accounts on the forums.

Then, lots of discussion about possible ways to implement authentication were started. Things got quite heated at times, with everyone accusing everyone else that their suggested scheme would not support critical feature X or would not have security propery Y. Here are some relevant threads:

[http://forums.armagetronad.net/viewtopic.php?t=1993 Authentication Thread of Doom]

[http://forums.armagetronad.net/viewtopic.php?t=2029 Distributed Authentication]

[http://forums.armagetronad.net/viewtopic.php?t=18178 XMPP integration]

[http://forums.armagetronad.net/viewtopic.php?t=18176 Krawall style, resulting in the code discussed here]

{{Sections}}

Talk:Cockpits list

2012-10-28T21:30:33Z

Epsy: moved Talk:Cockpits list to Talk:Cockpits List: consistency with other page capitalisations

#REDIRECT [[Talk:Cockpits List]]

Talk:Cockpits List

2012-10-28T21:30:33Z

Epsy: moved Talk:Cockpits list to Talk:Cockpits List: consistency with other page capitalisations

i like wrtl's, though i may have to tweek it some... never seen an impact gauge before ehhehe... [[User:2020|2020]] 24 june
:Then tweak it and give us your tweaked version, if it's any good I might even decide to use it myself ;)
:Hint: sign with <code><nowiki>--~~~~</nowiki></code> or <code><nowiki>—~~~~</nowiki></code> :) —[[User:Wrtlprnft|Wrtlprnft]] 16:34, 24 June 2006 (CEST)

Cockpits List

2012-10-28T21:30:32Z

Epsy: moved Cockpits list to Cockpits List: consistency with other page capitalisations

This is a list of a few cockpit files that are available. You can only use them if you have downloaded a version of Armagetronad later than 0.3.0_alpha4872 and if you know how to use the [[Console]]. Be aware that your use of upper/lowercase for the console command matters. To make your own cockpits see the [[Cockpit Tutorial]].

== Abyss ==

[[Image:Abyss-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Abyss]]
;Author
:[[User:Spidey|Spidey]]
;Description
:TODO-Spidey: add this.
;Console Command
:<code>COCKPIT_FILE spidey/abyss-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/spidey/abyss-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Classic ==

[[Image:Classic-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Classic cockpit]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]]
;Description
:This cockpit file tries to emulate the cockpit of 0.2.8 as much as possible. It doesn't include a HUD minimap and uses the traditional needle gauges. Boooooring.
;Console Command
:<code>COCKPIT_FILE wrtlprnft/classic-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/classic-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Essential ==

[[Image:Essential-0.0.5_(win).png|thumb|
Essential (win)]]
[[Image:Essential-0.0.5_(death+debug).png|thumb|
Essential (death+debug)]]
;Author
:[[User:rain|rain]]
;Description
:Simple, lightweight, or just essential.
:New version (0.0.5) is finally ready, some layout modifications and some features added. It is working good with aa v0.3_alpha_z1333. Enjoy.
;Toggle Keys
:1: hide/view brake and speed labels
:2: view/hide debug tools (see screenshots...)
;Console Command
:<code>COCKPIT_FILE rain/essential-0.0.1.aacockpit.xml</code>
:<code>COCKPIT_FILE rain/essential-0.0.5.aacockpit.xml</code>
;Resource Repository Link
:[http://resource.armagetronad.net/resource/rain/essential-0.0.1.aacockpit.xml Version 0.0.1]
:[http://resource.armagetronad.net/resource/rain/essential-0.0.5.aacockpit.xml Version 0.0.5]
<div style="clear:right;"></div>

== Essential Remix ==

[[Image:Screenshot_78.png|thumb|EssentialRemix v3.6 (alive)]]
[[Image:Essentialremix-0.3.1.aacockpit002.png|thumb|EssentialRemix v3.6 (death)]]
;Author
:[[User:Flex|Flex]]
;Description
:A "remix" to rains Essential Cockpit (New homepage at http://flex.armagetron.co.uk/essentialremix/).
;Toggle Keys (0.3.7)
*Toggle key 1: Toggle between the top right labels. Time & FPS / Fastest player & Max rubber.
*Toggle key 2: Show/Hide Minimap.
;Console Command
:<code>COCKPIT_FILE flex/cockpits/essentialremix-0.3.7.aacockpit.xml(http://flex.armagetron.co.uk/resource/flex/cockpits/essentialremix-0.3.7.aacockpit.xml)</code>
;Resource Repository Link
:[http://flex.armagetron.co.uk/resource/flex/essentialremix-0.3.6.aacockpit.xml Version 0.3.6]
:[http://flex.armagetron.co.uk/resource/flex/cockpits/essentialremix-0.3.7.aacockpit.xml Version 0.3.7] (Fixed the minimap not working on latest 0.3.x clients.)
<div style="clear:right;"></div>

== Pink ==

[[Image:Pink-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Pink]]
;Author
:[[User:Spidey|Spidey]]
;Description
:TODO-Spidey: add this.
;Console Command
:<code>COCKPIT_FILE spidey/pink-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/spidey/pink-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Playroom ==

[[Image:Playground-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Playground]]
;Author
:[[User:Lucifer|Lucifer]]
;Description
:This cockpit is designed for fortress play. All gauges are placed near where your eyes are normally focused so you never have to look far. Play with it enough and you find you always know your speed, amount of brake, and stuff. Enemies alive gauge is color-coded to show at a glance whether or not you're outnumbered. Look at the gauge itself to see how badly you're outnumbered, and look at the map to see where everybody is.
;Console Command
:<code>COCKPIT_FILE Lucifer/sick/Playroom-0.0.1.aacockpit.xml</code>
<div style="clear:right;"></div>

== Skypit ==

[[Image:Skypit-0.0.1.aacockpit.xml.png|thumb|Skypit]]
;Author
: LukeSky
;Description
:Toggle Key 1 -> Map
:Toggle Key 2 -> Time/FPS
;Console Command
:<code>COCKPIT_FILE lukesky/skypit-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/lukesky/skypit-0.0.1.aacockpit.xml Version 0.0.1]
<div sryle="clear:right;"></div>

== Standard Cockpit ==

[[Image:Standard-0.0.1.aacockpit.xml (Screenshot) (1).png|thumb|Standard cockpit in smartcam mode]]
[[Image:Standard-0.0.1.aacockpit.xml (Screenshot) (2).png|thumb|Standard cockpit in incam mode]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]] and [[User:Lucifer|Lucifer]]
;Description
:This is the default cockpit in 0.3.0. It has the new HUD map and bar gauges, but displays about the same data as 0.2.8.
:Try switching to incam mode for a camera tailored to incam playing.
;Console Command
:<code>COCKPIT_FILE Anonymous/standard-0.0.1.aacockpit.xml</code>
<div style="clear:right;"></div>

== Vanoriginal ==

[[Image:Vanoriginal-0.0.1.aacockpit.xml (Screenshot).png|thumb|
Vanoriginal]]
;Author
:[[User:Vanhayes|Vanhayes]]
;Description
:I Made all the meters Vertical Bar guages, took out all of the information that was showed in the top right corner except time and FPS, though you can toggle them off.Put the enemies/friends alive meter from incam. You can also toggle off the map If it is in the way and you can toggle on the impact meters, Front left and right.The toggles are cockpit keys: 1(map),2(impact meters), and 5(FPS/Time)
;Console Command
:<code>COCKPIT_FILE Vanhayes/cockpit/vanoriginal-0.0.1.aacockpit.xml</code>
;Resource Repository Link
:[http://beta.armagetronad.net/resource-browser/resource/Vanhayes/cockpit/vanoriginal-0.0.1.aacockpit.xml Version 0.0.1]
<div style="clear:right;"></div>

== Wrtl's Cockpit ==

[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (1).png|thumb|
Wrtl's cockpit with everything at initial state]]
[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (2).png|thumb|
Wrtl's cockpit with the HUD map switched off]]
[[Image:Testfile-0.0.1.aacockpit.xml (Screenshot) (3).png|thumb|
Wrtl's cockpit with dimmed 3D rendering]]
;Author
:[[User:Wrtlprnft|Wrtlprnft]]
;Description
:This is my approach on creating the ultimate cockpit.
:The huge rubber gauge on the left helps you know instantly how risky you can play and the player information on the top right helps you determine if your help defending is needed.
:On the bottom right is a special gauge that shows the approximate time to the next impact with a wall, useful if you want to know if you outgrinded someone. You can switch of the big map by pressing the first cockpit key (bind it in global keyboard config) and dim the 3D rendering by pressing the second key—useful for chico maps.
;Console Command
:<code>COCKPIT_FILE wrtlprnft/testfile-0.0.1.aacockpit.xml</code>
;Resource Repository Links
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/testfile-0.0.1.aacockpit.xml Version 0.0.1]
:[http://beta.armagetronad.net/resource-browser/resource/wrtlprnft/testfile-0.0.3.aacockpit.xml Version 0.0.3—doesn't work with 0.3.0, will work with 0.3.1]
<div style="clear:right;"></div>

== Xevi's Cockpit ==

[[Image:Xevi-0.0.3.aacockpit.xml (Screenshot).png|thumb|Xevi's Cockpit, version 0.0.3]]
[[Image:Xevi-0.0.4.aacockpit.xml (Screenshot).png|thumb|Xevi's Cockpit, version 0.0.4]]
[[Image:Xevi_cockpit_05.JPG|thumb|Xevi's Cockpit, version 0.0.5]]
[[Image:Xevi.0.0.7.JPG|thumb|Xevi's Cockpit, version 0.0.7]]
;Author
:[[User:Xevic|Xevi]]
;Description
:Some evolutions of the real hud ;) there are also versions 0.0.1 and 0.0.2, but they are just a step to 0.0.3, then there is a couple of evolutions, in 0.0.4 I added wrtl's impact time widget. Version 0.0.5 adds warning bars, there is one for front impact, another for left and one for right. The new 0.0.6 is a improvement of last one with better look bars and better parameters. News on 7: bars tunning, front impact moved bottom to allow better notice, avoid chat and transparency problems there, new big map switch with toggle 3, now it won't desappear, it will appear the full screen version.
Enjoy them.
;Console Command
:<code>COCKPIT_FILE xevi/xevi-0.0.7.aacockpit.xml</code>
;Resource Repository Links
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.3.aacockpit.xml Version 0.0.3]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.4.aacockpit.xml Version 0.0.4]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.5.aacockpit.xml Version 0.0.5]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.6.aacockpit.xml Version 0.0.6]
:[http://beta.armagetronad.net/resource-browser/resource/xevi/xevi-0.0.7.aacockpit.xml Version 0.0.7]
:[http://crazy-tronners.com/resource/xevi/xevi-0.0.8.aacockpit.xml Version 0.0.8] -> last version on 0.3.0
:[http://crazy-tronners.com/resource/xevi/xevi-0.0.9.aacockpit.xml Version 0.0.9] -> minimap 0.3.1 ready.
<div style="clear:right;"></div>

[[Category:Client Features]]

Cockpits

2012-10-28T21:29:31Z

Epsy: created introductory page linking to the other currently available cockpit pages

Cockpit files are what define the game's HUD. In version 0.4.0, and in current development builds, you can use this kind of files to replace the default HUD.

;[[Cockpits List]]
:A list of user-submitted cockpits
;[[Cockpit Tutorial]]
:How to make a cockpit from nothing
;[[Cockpit Reference]]
:Everything about cockpits from A to Z

Cockpit

2012-10-28T20:56:18Z

Epsy: create redirect to cockpits

#REDIRECT [[Cockpits]]

Template:WarSumoBrackets12

2012-10-21T17:10:50Z

Epsy: Fixed times to match the table beforehand

{{WarSumoBracket2 | RD1=Opening Round (17:15 GMT)
|RD2=First Round (18:15 GMT)
| RD3=Quarterfinals (19:00 GMT)
| RD4=Semi Finals (19:45 GMT)
| RD5=Finals (20:30 GMT)
| group1=
| group2=
| group3=
| subgroup1=
| subgroup2=
| subgroup3=
| subgroup4=
| team-width=220

| RD1-server01=
| RD1-team01=Addicted Animals
| RD1-score01=
| RD1-team02=~Bye 8~
| RD1-score02=

| RD1-server02=RoadRunnerz #1
| RD1-team03=What
| RD1-score03=
| RD1-team04=Dark Hordes
| RD1-score04=

| RD1-server03=Z-man's
| RD1-team05=Cheers Crew
| RD1-score05=
| RD1-team06=Wonder Pets
| RD1-score06=

| RD1-server04=
| RD1-team07=~Bye 1~
| RD1-score07=
| RD1-team08=Redemption/%
| RD1-score08=

| RD1-server05=
| RD1-team09=_~`Wild West_
| RD1-score09=
| RD1-team10=~Bye 4~
| RD1-score10=

| RD1-server06=RoadRunnerz #2
| RD1-team11=Music Lovers
| RD1-score11=
| RD1-team12=Spice Girls
| RD1-score12=

| RD1-server07=WST UK 001
| RD1-team13=\\african wildlyf
| RD1-score13=
| RD1-team14=Famous Wizards
| RD1-score14=

| RD1-server08=
| RD1-team15=~Bye 5~
| RD1-score15=
| RD1-team16=_~`The Rest of the West
| RD1-score16=

| RD1-server09=
| RD1-team17=Matrix
| RD1-score17=
| RD1-team18=~Bye 6~
| RD1-score18=

| RD1-server10=CT USA
| RD1-team19=rZ`
| RD1-score19=
| RD1-team20=Fox River 3
| RD1-score20=

| RD1-server11=CT LIV
| RD1-team21=Littles
| RD1-score21=
| RD1-team22=Wild and Westless
| RD1-score22=

| RD1-server12=
| RD1-team23=~Bye 3~
| RD1-score23=
| RD1-team24=ReDamnnnSon/%
| RD1-score24=

| RD1-server13=
| RD1-team25=Hobos
| RD1-score25=
| RD1-team26=~Bye 2~
| RD1-score26=

| RD1-server14=WST US
| RD1-team27=Blood Meridian
| RD1-score27=
| RD1-team28=Rz`2
| RD1-score28=

| RD1-server15=Ww 3
| RD1-team29=\\dino babies
| RD1-score29=
| RD1-team30=Speeders
| RD1-score30=

| RD1-server16=
| RD1-team31=~Bye 7~
| RD1-score31=
| RD1-team32=_~R~_
| RD1-score32=

| RD2-server01=RoadRunnerz #1
| RD2-team01=
| RD2-score01=
| RD2-team02=
| RD2-score02=

| RD2-server02=Z-man's
| RD2-team03=
| RD2-score03=
| RD2-team04=
| RD2-score04=

| RD2-server03=RoadRunnerz #2
| RD2-team05=
| RD2-score05=
| RD2-team06=
| RD2-score06=

| RD2-server04=WST UK 001
| RD2-team07=
| RD2-score07=
| RD2-team08=
| RD2-score08=

| RD2-server05=CT USA
| RD2-team09=
| RD2-score09=
| RD2-team10=
| RD2-score10=

| RD2-server06=CT LIV
| RD2-team11=
| RD2-score11=
| RD2-team12=
| RD2-score12=

| RD2-server07=WST US
| RD2-team13=
| RD2-score13=
| RD2-team14=
| RD2-score14=

| RD2-server08=Ww 3
| RD2-team15=
| RD2-score15=
| RD2-team16=
| RD2-score16=

| RD3-server01-1=Z-man's
| RD3-server01-2=RoadRunnerz #1
| RD3-team01=
| RD3-score01=
| RD3-team02=
| RD3-score02=

| RD3-server02-1=RoadRunnerz #2
| RD3-server02-2=WST UK 001
| RD3-team03=
| RD3-score03=
| RD3-team04=
| RD3-score04=

| RD3-server03-1=CT LIV
| RD3-server03-2=CT USA
| RD3-team05=
| RD3-score05=
| RD3-team06=
| RD3-score06=

| RD3-server04-1=WST US
| RD3-server04-2=Ww 3
| RD3-team07=
| RD3-score07=
| RD3-team08=
| RD3-score08=1

| RD4-server01-1=Z-man's
| RD4-server01-2=RoadRunnerz #2
| RD4-team01=
| RD4-score01=
| RD4-team02=
| RD4-score02=

| RD4-server02-1=WST US
| RD4-server02-2=CT LIV
| RD4-team03=
| RD4-score03=
| RD4-team04=
| RD4-score04=

| RD5-server01-1=Z-man's
| RD5-server01-2=WST US
| RD5-team01=
| RD5-score01=
| RD5-team02=
| RD5-score02=
}}

Ladle/Challenge Board

2012-07-25T00:27:09Z

Epsy: /* Subculture */ Fixed link to my server browser

Authentication Groups Draft

2012-04-02T00:07:28Z

Epsy: Added a clause on how the server should handle refreshes

==Things that were bad==

* "Group" authentication (subdirectories):
** Terrible usability: One must specifically authenticate to the subgroup for it to work, or the authority has to do arbitrary guesswork.
*** ie. <code>/login user@authority/directory</code>
*** As for authority guesswork, they can currently guess from the server's IP. The remote port data at this point is irrelevant, and the IP can be hidden by a proxy authority.
** Inability to express multiple groups
* Web Auth
** Needs DB access on the consumer end. Could be avoided
** Disabled by default in the reference implementations. Next to no adoption on the authority end.
** Only interfaces with websites specifically designed for it (read: none)

==Improvements that can be conducted==

==="Group" authentication===

====Group preference====

The server could take a list of preferred authorities/groups and forward it to the authorities. The setting would be optional.

PREFER_AUTHORITIES authority...
PREFER_AUTHORITIES ct/senior x/ctseniors x/ctoverseniors

When authentifying someone, the server can send the applicable authorities(same host) with the check requestas a <code>prefer</code> parameter. For instance, when querying <code>x.authentication.armagetronad.net</code>:

/armaauth/0.1/?query=check&method=md5user=john&hash=abcd&salt=efgh&prefer=ctseniors&prefer=ctoverseniors

The authority respond with the first group in the list that the user is allowed into.

Additionally, the server can provide a setting that would automatically provide group preferences based on "best" AUTHORITY_LEVEL settings. Similar to <code>/listadmins</code>, this poses a moderate security threat, advertising what authorities grant high access, so this should be disabled by default.

PREFER_AUTHORITIES_AUTO 1
AUTHORITY_LEVEL ct/senior 2
AUTHORITY_LEVEL x/ctsenior 2
AUTHORITY_LEVEL x/ctoversenior 1

/armaauth/0.1/?query=check&method=md5&user=johnhash=abcd&salt=efgh&prefer=ctoverseniors&prefer=ctseniors

An authority could "abuse" this system to voluntarily return different authorities than those requested. This could be used to create server tokens. For example:

PREFER_AUTHORITIES x/tournaments/ladle/servers/myserver
AUTHORITY_LEVEL x/tournaments/players/playing 8
AUTHORITY_LEVEL x/tournaments/players/captain 7

If it were the time for the finals, the authority could identify "myserver" as referring to the server used in the finals, and identify each player as playing or captain or neither, at login time.

===Updating preferences===

If the preferences have changed while people are in the server, it might be in the best interest of everyone to update the current players' status. Of course, everyone could log out and back in, but that's very impractical.

I suggest instead a mass update mechanism, by sending a bulk query to each authority. For instance:

/armaauth/0.1/?query=refresh&prefer=tournaments/ladle/servers/myserver&users=john&users=may&users=jack

The server may merge all queries to one per authentication host. The authority responds:

USER john@x/tournaments/players/playing
USER may@x/tournaments/players/captain
USER jack@x/tournaments/players

In case a user is not found, the authority should replace the corresponding USER line with:

USER_NOT_FOUND username

This system can be otherwise used to check player GIDs. If it matters, a client should be able to override the server time like such:

/armaauth/0.1/?query=refresh&prefer=tournaments/ladle/servers/myserver&users=john&users=may&users=jack&time=1333333333

On the server end, the server should change the players' GIDs accordingly, elevating players where relevant.

The server could initiate such a refresh at the command of a server admin, or before every new warmup(side note: the warmup system allows for multiple matches to be played simultaneously). All priviledges could also be first revoked at first on such an occasion, for instance for resetting temporary captains.

==Web Authentication==

===OpenID===

OpenID would standardize the process into something that has software already available for it. This would result in making it an easier process to convert software to consume OpenIDs. It would be signaled as "openid" in the METHODS response. More info TBD.

==Actually use MESSAGE==

The server would print the message to the client.

Authentication Groups Draft

2012-04-01T23:50:07Z

Epsy: Created

==Things that were bad==

* "Group" authentication (subdirectories):
** Terrible usability: One must specifically authenticate to the subgroup for it to work, or the authority has to do arbitrary guesswork.
*** ie. <code>/login user@authority/directory</code>
*** As for authority guesswork, they can currently guess from the server's IP. The remote port data at this point is irrelevant, and the IP can be hidden by a proxy authority.
** Inability to express multiple groups
* Web Auth
** Needs DB access on the consumer end. Could be avoided
** Disabled by default in the reference implementations. Next to no adoption on the authority end.
** Only interfaces with websites specifically designed for it (read: none)

==Improvements that can be conducted==

==="Group" authentication===

====Group preference====

The server could take a list of preferred authorities/groups and forward it to the authorities. The setting would be optional.

PREFER_AUTHORITIES authority...
PREFER_AUTHORITIES ct/senior x/ctseniors x/ctoverseniors

When authentifying someone, the server can send the applicable authorities(same host) with the check requestas a <code>prefer</code> parameter. For instance, when querying <code>x.authentication.armagetronad.net</code>:

/armaauth/0.1/?query=check&method=md5user=john&hash=abcd&salt=efgh&prefer=ctseniors&prefer=ctoverseniors

The authority respond with the first group in the list that the user is allowed into.

Additionally, the server can provide a setting that would automatically provide group preferences based on "best" AUTHORITY_LEVEL settings. Similar to <code>/listadmins</code>, this poses a moderate security threat, advertising what authorities grant high access, so this should be disabled by default.

PREFER_AUTHORITIES_AUTO 1
AUTHORITY_LEVEL ct/senior 2
AUTHORITY_LEVEL x/ctsenior 2
AUTHORITY_LEVEL x/ctoversenior 1

/armaauth/0.1/?query=check&method=md5&user=johnhash=abcd&salt=efgh&prefer=ctoverseniors&prefer=ctseniors

An authority could "abuse" this system to voluntarily return different authorities than those requested. This could be used to create server tokens. For example:

PREFER_AUTHORITIES x/tournaments/ladle/servers/myserver
AUTHORITY_LEVEL x/tournaments/players/playing 8
AUTHORITY_LEVEL x/tournaments/players/captain 7

If it were the time for the finals, the authority could identify "myserver" as referring to the server used in the finals, and identify each player as playing or captain or neither, at login time.

===Updating preferences===

If the preferences have changed while people are in the server, it might be in the best interest of everyone to update the current players' status. Of course, everyone could log out and back in, but that's very impractical.

I suggest instead a mass update mechanism, by sending a bulk query to each authority. For instance:

/armaauth/0.1/?query=refresh&prefer=tournaments/ladle/servers/myserver&users=john&users=may&users=jack

The server may merge all queries to one per authentication host. The authority responds:

USER john@x/tournaments/players/playing
USER may@x/tournaments/players/captain
USER jack@x/tournaments/players

In case a user is not found, the authority should replace the corresponding USER line with:

USER_NOT_FOUND username

This system can be otherwise used to check player GIDs. If it matters, a client should be able to override the server time like such:

/armaauth/0.1/?query=refresh&prefer=tournaments/ladle/servers/myserver&users=john&users=may&users=jack&time=1333333333

==Web Authentication==

===OpenID===

OpenID would standardize the process into something that has software already available for it. This would result in making it an easier process to convert software to consume OpenIDs. It would be signaled as "openid" in the METHODS response. More info TBD.

==Actually use MESSAGE==

The server would print the message to the client.

Authentication

2012-04-01T22:34:26Z

Epsy: Oops, fixed a typo in the link.

<strong>This is a development document. You may find information about the current authentication systems on [[Authentication for Players]].</strong>

Several possible ways of doing authentication are listed here.

== IM Based ==

Read about how we could profit from the work of others by abusing instant message systems in [[XMPP Based Authentication]].

== Full Blown ==

On the forum, a way to handle authentication with full fledged security and privacy has been worked out. It is based on public key cryptography and allows central or decentral player account management. Read about it in [[Key Based Authentication]]. Meriton has suggested another approach: [[Distributed Authentification Using Digital Signatures]].

== Test Balloon ==

Since the full blown protocol uses features not yet included in the game and is rather involved, an alternative, easier to implement scheme has been suggested. The drawback: It is vulnerable against attackers who can intercept and modify network communications. It's not that bad, being able to listen to network traffic alone is not enough. Read about it in [[Hash Based Authentication]].

Disadvantages over key based scheme:
* Less privacy, the authentication server is contacted on every login
* Less security, it suffices if an attacker can intercept and take over communication between the game and authentication server to log in as anyone. In the key based scheme, the attacker needs to steal the authority's private key.
* It does not support self-signed login where the fact that you're playing on a certain machine is taken as enough authentication.

Advantage:
* It's so simple we should be able to supply it as a patch to 0.2.8.

== What's Already There ==

Complete support for password verification is already built in into every client, and with the configure option --enable-krawall, server code that triggers it is activated on the server. What is missing is a function that actually retrieves the right password for a player. The test balloon would reuse it to minimize work to be done and to allow existing clients to participate.

Authentication there is handled like this:
* The client connects to the server as usual, sending the player's data, among that the player name.
* The server generates some random data (the salt) and sends it along with an authentication request to the client.
* The client takes a MD5 hash of the password, appends the salt and does another MD5 checksum of the combined data (that's called scrambling, and the MD5 hash of the password is called an egg).
* The client sends the resulted scrambled egg MD5 hash back to the server.
* The server has done the same operation on the MD5 hash of the password from the player database (The retrieval of that is the missing bit) and compares the result with what it gets from the client. If the results match, the client is authorized to use that player name.

== How To Set Up Authentication ==
Read the file <code>settings_authentication.cfg</code> in your [[Configuration Files]] directory for more details.

In short: One can configure the 0.3.x (perhaps even 0.2.8.x) server in a way, so that users can use their forum's user name and password for authenticating on your server. To aquire this, create a file <code>/etc/armagetronad-dedicated/server_info.cfg</code>, enable GLOBAL_ID 1 and assign a USER_LEVEL <username>@forums <level>. To login, type "/login forums" when connected to the server in-game (Using the menu didn't work for me).

You can define "local users", too, if you don't want to use external sources for authentication (Or if you just have no forum account). This would require these two settings: LOCAL_USER <name> <password> and USER_LEVEL <name>@ <level>

=== Example server_info.cfg ===
<pre>
GLOBAL_ID 1 # Enable external authentication authorities
USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges
# Login in-game by typing: /login forums

TRUST_LAN 1 # Allow login via local network (LAN)
LOCAL_USER itsme superpassword # Define username and password
USER_LEVEL itsme@ 0 # Grant "Owner" privileges
# Login in-game by using the Authentication menu
</pre>

Authentication

2012-04-01T22:33:26Z

Epsy: Added a link to Authentication For Players

<strong>This is a development document. You may find information about the current authentication systems on [[Authentication For Players]].</strong>

Several possible ways of doing authentication are listed here.

== IM Based ==

Read about how we could profit from the work of others by abusing instant message systems in [[XMPP Based Authentication]].

== Full Blown ==

On the forum, a way to handle authentication with full fledged security and privacy has been worked out. It is based on public key cryptography and allows central or decentral player account management. Read about it in [[Key Based Authentication]]. Meriton has suggested another approach: [[Distributed Authentification Using Digital Signatures]].

== Test Balloon ==

Since the full blown protocol uses features not yet included in the game and is rather involved, an alternative, easier to implement scheme has been suggested. The drawback: It is vulnerable against attackers who can intercept and modify network communications. It's not that bad, being able to listen to network traffic alone is not enough. Read about it in [[Hash Based Authentication]].

Disadvantages over key based scheme:
* Less privacy, the authentication server is contacted on every login
* Less security, it suffices if an attacker can intercept and take over communication between the game and authentication server to log in as anyone. In the key based scheme, the attacker needs to steal the authority's private key.
* It does not support self-signed login where the fact that you're playing on a certain machine is taken as enough authentication.

Advantage:
* It's so simple we should be able to supply it as a patch to 0.2.8.

== What's Already There ==

Complete support for password verification is already built in into every client, and with the configure option --enable-krawall, server code that triggers it is activated on the server. What is missing is a function that actually retrieves the right password for a player. The test balloon would reuse it to minimize work to be done and to allow existing clients to participate.

Authentication there is handled like this:
* The client connects to the server as usual, sending the player's data, among that the player name.
* The server generates some random data (the salt) and sends it along with an authentication request to the client.
* The client takes a MD5 hash of the password, appends the salt and does another MD5 checksum of the combined data (that's called scrambling, and the MD5 hash of the password is called an egg).
* The client sends the resulted scrambled egg MD5 hash back to the server.
* The server has done the same operation on the MD5 hash of the password from the player database (The retrieval of that is the missing bit) and compares the result with what it gets from the client. If the results match, the client is authorized to use that player name.

== How To Set Up Authentication ==
Read the file <code>settings_authentication.cfg</code> in your [[Configuration Files]] directory for more details.

In short: One can configure the 0.3.x (perhaps even 0.2.8.x) server in a way, so that users can use their forum's user name and password for authenticating on your server. To aquire this, create a file <code>/etc/armagetronad-dedicated/server_info.cfg</code>, enable GLOBAL_ID 1 and assign a USER_LEVEL <username>@forums <level>. To login, type "/login forums" when connected to the server in-game (Using the menu didn't work for me).

You can define "local users", too, if you don't want to use external sources for authentication (Or if you just have no forum account). This would require these two settings: LOCAL_USER <name> <password> and USER_LEVEL <name>@ <level>

=== Example server_info.cfg ===
<pre>
GLOBAL_ID 1 # Enable external authentication authorities
USER_LEVEL itsme@forums 0 # Grant user "itsme" from forums.armagetronad.net "Owner" privileges
# Login in-game by typing: /login forums

TRUST_LAN 1 # Allow login via local network (LAN)
LOCAL_USER itsme superpassword # Define username and password
USER_LEVEL itsme@ 0 # Grant "Owner" privileges
# Login in-game by using the Authentication menu
</pre>

Ladle/Challenge Board

2011-07-03T16:42:22Z

Epsy: /* Server List */ Fixed immortal dynasty de IP

{{:Ladle/Blurb}}

==Signing Up==
Please post your team name and the players who will play for your team below. If you're confused on how to do so, look at the examples below. You may also create a wiki page for your team. Placement on the Bracket is done randomly the Thursday before the Ladle.

<nowiki>{{LadleTeam|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ...|Wiki Page Name}}</nowiki>
or
<nowiki>{{LadleTeamExternal|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ...|http://teamwebsite.com}}</nowiki>
For more information, see [[Template:LadleTeam]] or [[Template:LadleTeamExternal]]. Make collecting authorities easier with [http://www.adventuresoftron.com/ this tool].

By signing up you agree to follow the [[Ladle/Operations#Rules_for_players|Rules]]. Rule breakers may be subject to disciplinary action. Team Captains, please be up to date on [[Ladle/Operations#How_the_Ladle_Works|how the Ladle works]] as well.

==Teams==
{{LadleTeamExternal|§ï¦¦ÿ þÛÐÐÿ|Thump, Spin|Thump@forums, INW@forums|2020, Helena, JameZflameZ, Scorch, Syde, 'Syre', Zimblunk|http://sillypuddy.pro-forum.co.uk/}}
{{LadleTeamExternal|Dark Syndicate|Milan, Spook|Milan@forums, Spook@forums|Animal, ChrisGW, Zion, CruZ, Akizo, Divine, Doctor, Fate, Plage, Sunny|http://dsexperimentalworks.net}}
{{LadleTeamExternal|Speedhax|Aíphaton, kult|Aiphaton@forums, helllo@forums|Magic, Flex, cyclo, rogerthat, Delta|http://www.speedersclan.org}}
{{LadleTeamExternal|PRU|Word|Word@forums, | Garial, Eggman, Fire, Sixzero, Ai , Hamar, Longball, Agility, Phenomenon, Daedalus, VonDutch|http://www.trongame.de}}
{{LadleTeam|TIC|toy, akira|bubble@forums, akira@forums| epsy, sine.wav, Vanhayes, subliminal.freq, tremor|TIC}}
{{LadleTeamExternal|uNa|Stripes, Lawkey|Stripes@forums, ~Loki@forums|Tweezy, Tock, Az95, DGM,J-Dawg , Doritoz,Roy, Ben Kenobi, WillyWonka|http://www.unaclan.smfnew.com}}
{{LadleTeamExternal|Meet Your Maker|eckz|Eckz@forums| bellum, chah, devicat, dimebag, envy, fini, insa, kairo, kim pine, liz, weed|http://www.meetyourmaker.com}}
{{LadleTeamExternal|Next Generation|Titanoboa, Demon|Titanoboa@forums, Demon@forums| King, Kriki, Spica, Tech, box, <^w{}w^>|http://speedersclan.org}}
{{LadleTeamExternal|DpG|Prema, 16|premaDpG@forums, *16@forums| , flea, Ubuntu, baggins, edition, FroGGer, 4m1c0, Hell©ats Duffel, lampan, jameyjames04, pRo.BallA, Hunkules, CR7, MaDnEsS, pioniri, lowlyworm, holer |http://respwn.us}}
{{LadleTeamExternal|Immortal Dynasty|Dal, Robo| Dalsue@forums, Robo@forums|Coco, Jester, Arilou, Tsugaru, Alpha, Yoda, Scene, AvA, compguygene|http://www.idclansite.info}}
{{LadleTeamExternal|Tx|Hoax, Deso|Hoax@forums, Desolate@forums| Rudy, olive, Durka, Karma, Speed, raph, Roterbaron|http://twixted-xats.com}}
{{LadleTeamExternal|Dv|teen, acid|teen@aagid, acid@forums| first0v, subfoucus, swiss, plate, boxed, quack, a_nub,prestige|http://unlimited-clan.com}}
{{LadleTeamExternal|Team.uNk|tls, Wildcat|thelastSunrise@unk.me, wildcat@forums| fingerbib, Potter, Luzifer, 0ma, NoobSaibot, bmg|http://unk.me}}
{{LadleTeamExternal|uNk.Team|noob13, MaZuffeR|noob13@forums, yesihavemyownauthority@mazuffer.com| Pr3, DrHouse, slash, Jip, dreadlord|http://unk.me}}
{{LadleTeamExternal|~*Speeders*~|FoFo, Psy|FoFo@forums, Psy@forums|mkay, viper, xyron, slov, nubilous, Free, algid|http://www.speedersclan.org}}
{{LadleTeam|Open Team|Lackadaisical|Lackadaisical@forums|LucK, CxDy, Poke' Master, over, Baphomet, ADD YO SELF gurl.}}
{{LadleTeamExternal|CTa|Woned, Gonzap|owned@forums, Gonzap@forums|mb53, puuquie, wap, emmy, safariskater, theroze, cronix|http://crazy-tronners.com}}
{{LadleTeamExternal|CTb|apparition|apparition@forums|gazelle, btd, punk, pike, orly?, voodoo|http://crazy-tronners.com}}
{{LadleTeamExternal|Already Dead|koala|Pre@forums| dariv, eber, syllabear, vov, zat|http://sillalive.freeforums.org/nothing-is-endless-t141.html#p1063}}
{{LadleTeamExternal|Rx|dukevin|dukevin@forums|iNoob, Slyfoxx, KeyLime, OddFuture, Who, TBA|http://insomniaclan.com}}

==Challenge Board==

===Brackets===
*All games are best of 3 matches (the first team to win 2 matches advances to the next round).
*All finals are played in the server listed in '''bold'''. Teams may agree to move to the backup server if there is a regional preference or problem with the primary server.<br />
To change brackets, edit [[Template:Ladle47Bracket]]

{{Ladle47Bracket}}<br />

===Times===

{{:Ladle/SummerTimes}}

==Servers==
Admins, by offering your server you agree to abide by the [[Ladle/Operations#Rules_for_server_owners_.26_operators|Rules for server owners and operators]]. It is also advisable that you are up to date on [[Ladle/Operations#How_the_Ladle_Works|how the Ladle works]] as well. Thank you.

===Server Configuration===
*Please review the changes [http://forums3.armagetronad.net/viewtopic.php?p=209381#p209381 here].
RINCLUDE ladle/ladle36.cfg(http://crazy-tronners.com/resource/ladle/ladle36.cfg)
RINCLUDE ladle/ladle47_authorities.cfg(http://adventuresoftron.com/aa/resource/ladle47_authorities.cfg)
SERVER_NAME 0x7fff7fLadle 47 0xff7f7f(0x7f7fffPlayer 1's Server0xff7f7f)

===Server List===
<nowiki>{{LadleServer|Your server name|ip|port|Location|[http://serverwebsite.com http://serverwebsite.com]}}</nowiki>

<u>'''Europe'''</u>
{{LadleServer|Immortal Dynasty's DE|178.63.118.135|4535|Germany (EU)|[[User talk:compguygene|compguygene]]}}
{{LadleServer|uNk's|unk.me|4536|Germany (EU)|[http://forums.unk.me noob13/Jip]}}
{{LadleServer|Crazy Tronner's LIV|liv.crazy-tronners.com|4541|Germany (EU)|[http://crazy-tronners.com/servertech CT Server Tech]}}
{{LadleServer|Crazy Tronner's MBX|85.114.128.17|4534|Germany (EU)|[http://crazy-tronners.com/servertech CT Server Tech]}}


<u>'''US & Others'''</u>
{{LadleServer|Immortal Dynasty's Kansas|208.94.246.202|4535|Kansas (US)|[[User talk:compguygene|compguygene]]}}
{{LadleServer|Immortal Dynasty's New York|63.251.20.188|4535|New York (US)|[[User talk:compguygene|compguygene]]}}
{{LadleServer|AoT|65.18.192.127|4541|Connecticut (NE US)|[http://forums3.armagetronad.net/ucp.php?i=pm&mode=compose&u=2439 sinewav]}}
{{LadleServer|Crazy Tronner's USA|usa.crazy-tronners.com|4535|Chicago, Illinois (US)|[http://crazy-tronners.com/servertech CT Server Tech]}}



===Subculture===

* [http://forums3.armagetronad.net/viewtopic.php?f=60&t=19311 Subculture]
* [http://generalconsumption.org/armagetronad/ladle Online Server Browser]

==Recordings/Screenshots==
Post all recordings/screenshots that you have of the ladle here, along with the names of the two teams in the match:

* http:// - TeamA vs TeamB

Ladle/Challenge Board

2010-04-17T13:19:42Z

Epsy: Fed link to forum thread

{{:Ladle/Blurb}}
<font size="4">[http://forums3.armagetronad.net/viewtopic.php?f=60&t=20173 '''Sunday, May 2nd, 2010!''']</font>

==Signing Up==
Please post your team name and the players who will play for your team below. If you're confused on how to do so, look at the examples below. You may also wish to create a wiki page for your team. The teams will be randomly selected for slot #s on the Thursday before the Ladle.

<nowiki>{{LadleTeam|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ..|Wiki Page Name}}</nowiki>
or
<nowiki>{{LadleTeamExternal|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ..|http://teamwebsite.com}}</nowiki>

For more information, see [[Template:LadleTeam]] or [[Template:LadleTeamExternal]].

By signing up you agree to follow the [[Ladle/Guidelines|Guidelines]]

==Teams==

==Servers==

===Server Configuration===
*Please review the changes [http://forums3.armagetronad.net/viewtopic.php?p=209381#p209381 here].
RINCLUDE ladle24.cfg(http://durka.ath.cx/resource/ladle/ladle24.cfg)
RINCLUDE ladle32_authorities.cfg(http://crazy-tronners.com/resource/ladle/ladle32_authorities.cfg)
SERVER_NAME 0x7fff7fLadle 32 0xff7f7f(0x7f7fffPlayer 1's Server0xff7f7f)

===Server List===
<nowiki>{{LadleServer|Your server name|ip|port|Location|[http://serverwebsite.com http://serverwebsite.com]}}</nowiki>

<u>'''Europe'''</u>
{{LadleServer|Crazy Tronner's LIV|liv.crazy-tronners.com|4542|Germany (EU)|[http://crazy-tronners.com/servertech CT Server Tech]}}
{{LadleServer|Z-Man's|simamo.de|4536|Frankfurt, Germany (EU)|[[User talk:Z-Man|Z-Man]]}}
{{LadleServer|The Server Pharm FR|fr.theserverpharm.net|4536|Roubaix, France (EU)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm DE|de.theserverpharm.net|4534|Frankfurt, Germany(EU)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|Dark Syndicate|gaming.junidas.de|4536|Frankfurt, Germany (EU)|[[User talk:G5|G5]]}}
{{LadleServer|PlsResUs!|trongame.de|4535|Germany (EU)|[http://trongame.de/forum/memberlist.php?mode=viewprofile&u=2 Ai]}}

<u>'''US & Others'''</u>
{{LadleServer|Crazy Tronner's USA|usa.crazy-tronners.com|4535|Chicago, Illinois (US)|[http://crazy-tronners.com/servertech CT Server Tech]}}
{{LadleServer|Twi¦×¦ted ¦×¦ats|xats.ath.cx|4541|Philadelphia, Pennsylvania (US)|[http://forums3.armagetronad.net/memberlist.php?mode=viewprofile&u=1152 Durka]}}
{{LadleServer|The Server Pharm PA0|173.212.246.162|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm PA1|64.191.33.74|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm PA2|64.191.127.248|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}


===Subculture===

* [http://forums3.armagetronad.net/viewtopic.php?f=60&t=19311 Subculture]
* [http://generalconsumption.org/armagetronad/ladle Online Server Browser]

==Challenge Board==
===Times===
{| border="1" cellpadding="15" cellspacing="5" style="text-align:center"
! (24 HOURS) || <span style="cursor:help;border-bottom: 1px dashed black" title="Pacific Daylight Time">PDT (GMT-7)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Eastern Daylight Time">EDT (GMT-4)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Greenwich Mean Time">GMT</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="British Summer Time">BST (GMT+1)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Central European Summer Time">CEST (GMT+2)</span>
|-
| '''Opening Round''' || 10:45 || 13:45 || 17:45 || 18:45 || 19:45
|-
|-
| '''Quarter Finals''' || 11:30 || 14:30 || 18:30 || 19:30 || 20:30
|-
|-
| '''Semi Finals''' || 12:15 || 15:15 || 19:15 || 20:15 || 21:15
|-
|-
| '''Finals''' || 13:00 || 16:00 || 20:00 || 21:00 || 22:00
|-
|}
([http://www.greenwichmeantime.com/ time conversion here])

===Brackets===
*All games are best of 3 matches (the first team to win 2 matches advances to the next round).
*If there are 2 servers listed for a specific game, the game will be played in each team's home server (European or American) if '''both''' teams are European or '''both''' are American. If there is a mixture, the game will be played in the server that is in '''bold'''.<br />
To change brackets, edit [[Template:Ladle33Bracket]]

{{Ladle33Bracket}}<br />

Ladle/Challenge Board

2010-04-17T13:11:57Z

Epsy: /* Times */ Arranged the time table, adding BST

{{:Ladle/Blurb}}
<font size="4">[http://link-to-forums-topic '''Sunday, May 2nd, 2010!''']</font>

==Signing Up==
Please post your team name and the players who will play for your team below. If you're confused on how to do so, look at the examples below. You may also wish to create a wiki page for your team. The teams will be randomly selected for slot #s on the Thursday before the Ladle.

<nowiki>{{LadleTeam|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ..|Wiki Page Name}}</nowiki>
or
<nowiki>{{LadleTeamExternal|Your Team Name|Team Captain's Name|Team Captain's Global ID|Teammate 1, Teammate 2, ..|http://teamwebsite.com}}</nowiki>

For more information, see [[Template:LadleTeam]] or [[Template:LadleTeamExternal]].

By signing up you agree to follow the [[Ladle/Guidelines|Guidelines]]

==Teams==

==Servers==

===Server Configuration===
*Please review the changes [http://forums3.armagetronad.net/viewtopic.php?p=209381#p209381 here].
RINCLUDE ladle24.cfg(http://durka.ath.cx/resource/ladle/ladle24.cfg)
RINCLUDE ladle32_authorities.cfg(http://crazy-tronners.com/resource/ladle/ladle32_authorities.cfg)
SERVER_NAME 0x7fff7fLadle 32 0xff7f7f(0x7f7fffPlayer 1's Server0xff7f7f)

===Server List===
<nowiki>{{LadleServer|Your server name|ip|port|Location|[http://serverwebsite.com http://serverwebsite.com]}}</nowiki>

<u>'''Europe'''</u>
{{LadleServer|Crazy Tronner's LIV|liv.crazy-tronners.com|4542|Germany (EU)|[http://crazy-tronners.com/servertech CT Server Tech]}}
{{LadleServer|Z-Man's|simamo.de|4536|Frankfurt, Germany (EU)|[[User talk:Z-Man|Z-Man]]}}
{{LadleServer|The Server Pharm FR|fr.theserverpharm.net|4536|Roubaix, France (EU)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm DE|de.theserverpharm.net|4534|Frankfurt, Germany(EU)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|Dark Syndicate|gaming.junidas.de|4536|Frankfurt, Germany (EU)|[[User talk:G5|G5]]}}
{{LadleServer|PlsResUs!|trongame.de|4535|Germany (EU)|[http://trongame.de/forum/memberlist.php?mode=viewprofile&u=2 Ai]}}

<u>'''US & Others'''</u>
{{LadleServer|Crazy Tronner's USA|usa.crazy-tronners.com|4535|Chicago, Illinois (US)|[http://crazy-tronners.com/servertech CT Server Tech]}}
{{LadleServer|Twi¦×¦ted ¦×¦ats|xats.ath.cx|4541|Philadelphia, Pennsylvania (US)|[http://forums3.armagetronad.net/memberlist.php?mode=viewprofile&u=1152 Durka]}}
{{LadleServer|The Server Pharm PA0|173.212.246.162|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm PA1|64.191.33.74|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}
{{LadleServer|The Server Pharm PA2|64.191.127.248|4535|Philadelphia, Pennsylvania (US)|[[User talk:Compguygene|Compguygene]]}}


===Subculture===

* [http://forums3.armagetronad.net/viewtopic.php?f=60&t=19311 Subculture]
* [http://generalconsumption.org/armagetronad/ladle Online Server Browser]

==Challenge Board==
===Times===
{| border="1" cellpadding="15" cellspacing="5" style="text-align:center"
! (24 HOURS) || <span style="cursor:help;border-bottom: 1px dashed black" title="Pacific Daylight Time">PDT (GMT-7)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Eastern Daylight Time">EDT (GMT-4)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Greenwich Mean Time">GMT</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="British Summer Time">BST (GMT+1)</span> || <span style="cursor:help;border-bottom: 1px dashed black" title="Central European Summer Time">CEST (GMT+2)</span>
|-
| '''Opening Round''' || 10:45 || 13:45 || 17:45 || 18:45 || 19:45
|-
|-
| '''Quarter Finals''' || 11:30 || 14:30 || 18:30 || 19:30 || 20:30
|-
|-
| '''Semi Finals''' || 12:15 || 15:15 || 19:15 || 20:15 || 21:15
|-
|-
| '''Finals''' || 13:00 || 16:00 || 20:00 || 21:00 || 22:00
|-
|}
([http://www.greenwichmeantime.com/ time conversion here])

===Brackets===
*All games are best of 3 matches (the first team to win 2 matches advances to the next round).
*If there are 2 servers listed for a specific game, the game will be played in each team's home server (European or American) if '''both''' teams are European or '''both''' are American. If there is a mixture, the game will be played in the server that is in '''bold'''.<br />
To change brackets, edit [[Template:Ladle33Bracket]]

{{Ladle33Bracket}}<br />

US vs EU

2010-04-10T09:46:51Z

Epsy: /* Europe */ nominated some people and reordered the list

= Information =

North America vs Europe..
<br>
----

= The Teams =

To nominate a player, add them to the list.
----
== North America ==
<nowiki>{{US Nominate|Player Name||Player@authority}}</nowiki>
=== Nominees ===
{{US Nominate|Durka||DDMJ@forums}}
{{US Nominate|Psyko||psyko@forums(?)}}
{{US Nominate|Woned||owned@forums}}

=== Confirmed Nominees ===
----

== Europe ==
<nowiki>{{EU Nominate|Player Name||Player@authority}}</nowiki>
=== Nominees ===
{{EU Nominate|akira||akira@forums}}
{{EU Nominate|FoFo||FoFo@forums}}
{{EU Nominate|Gonzap||Gonzap@forums}}
{{EU Nominate|judders||Judders@forums}}
{{EU Nominate|Lackadaisical||Lackadaisical@forums}}
{{EU Nominate|MaZuffeR||yesihavemyownauthority@mazuffer.com}}
{{EU Nominate|olive||olive@forums}}
{{EU Nominate|Xyron||??}}

=== Confirmed Nominees ===

Running Multiple Servers on a single Linux computer

2010-03-13T22:30:18Z

Epsy: Missed one.

== Introduction ==

If you like to experiment new settings, it might be that you come with a set of interesting servers. A shame if you cannot run them all at the same time. Here is how you can achieve this on a Linux server. Please refer to the lag and bandwidth chapters in the wiki before to run multiple servers. If you run too many, you might end with a very bad gameplay.

This chapter will present you an easy way to run multiple servers on a single Linux computer, using GNU screen.

== Server installation ==

First of all, you have to install the Armagetron Advanced Dedicated Server from source, not using the provided install script. This will allow to manage at will the settings and var directories. To do so, download the latest source package, and untar it in a temporary folder.

<code>bzr branch lp:armagetronad/0.2.8</code>

In the "configure" command, the prefix will be the application directory. I have choose to install it in /opt/armagetronad/. Make your own choice:

./configure --prefix=/opt/armagetronad/ --disable-glout --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts

Authentication:

./configure --prefix=/opt/armagetronad/ --disable-glout --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts --enable-armathentication

Then, compile and install:
./bootstrap.sh
make
make install

Now, armagetron advanced dedicated is installed in the /opt/armagetronad/ folder.

== Preparing the servers ==

=== The tree ===

CD to /opt/armagetronad/
cd /opt/armagetronad/

Create the following subdirectories:

mkdir servers 'This folder will be used to store server configurations
mkdir logs 'This one will be used to save the server logs
mkdir scripts 'And this one will be used to same the scripts we will see below

We have now to create our servers. To do so, go to the servers directory you have created earlier, and for each server, create a subfolder with a one-word name for the server, and two subfolders: var and settings. For exemple:

cd /opt/armagetronad/servers

To create a server called server1:

mkdir server1
mkdir server1/settings
mkdir server1/var
then copy your config files in the settings subfolder.

You can then create a second server, and more...

mkdir server2
mkdir server2/settings
mkdir server2/var
and so on...

=== The setting files ===

For each server, do not forget to create a "server_info.cfg" file (search the wiki about it), and to change the port number. Port can be from 4534 to 4540, meaning you can safely run up to 7 servers on the same computer, depending obviously on the settings of each servers, and the bandwidth they need.

We assume that you know enough about Server Administration to understand the above explainations. This article is about Advanced Server Administration, isn't it ?

== The scripts ==

Now you have to create the scripts to launch and log all your servers. To allow managing each server separately, we will use GNU Screen. GNU screen is a terminal window manager. If it is not install on your server, you can get it with the usual installation tool (yum install screen, apt get screen, etc...). Again... advanced.... We assume you know how to install applications on linux and therefore, we assume GNU screen has been installed

You have to create two scripts. The first one will run a server and start logging the window in which the server has started. The second one will execute the first one for each folder in the /opt/armagetronad/servers folder. It will create a window for each of them. Therefore, if you don't want a server to run, you will have to temporarily move the server folder out from the /opt/armagetronad/servers directory.

Save the scripts in the /opt/armagetronad/scripts directory. I use nano which is an easy text editor.

=== The server script ===

The first script will be called in this example: srv

nano /opt/armagetronad/scripts/srv
That creates a text file called srv in the scripts directory. Write the following lines in the file:

#!/bin/bash

screen -S $1 -X logtstamp on # print timestamps in log file
screen -S $1 -X logfile /opt/armagetronad/logs/$1_%d%m%Y-%c.log # create a logfile in the logs subfolder
screen -S $1 -X log on # Turn on logging for the server window
while true; do # start a loop to allow server restart if it crashes

# runs the actual server. By default, the binary is called armagetronad-dedicated and is located in the prefix/bin directory. In this example, it is in /opt/armagetronad/bin directory.
/opt/armagetronad/bin/armagetronad-dedicated --configdir /opt/armagetronad/servers/$1/settings --vardir /opt/armagetronad/servers/$1/var

# Shows the errors and indicates that the server has crashed, and then, waits 5 seconds before restarting the server, allowing you to quit with CTRL-C
echo "Server has crashed. It will restart immediately..., press CTRL-C to cancel"
sleep 5

done # end the loop
To save the file, press CTRL-X and Y to confirm. You have now a file called srv in /opt/armagetronad/scripts.

=== the global script ===

Create the second script. I called it start: <code> nano /opt/armagetronad/scripts/start</code>

#!/bin/bash

# If you run the script with a parameter (server name), only that server will be start. Otherwise, all servers in the /opt/armagetronad/servers directory will be started

if [ "$1" != "" ]; then
screen -S $1 -X quit # Kill the window if it exists already, avoiding to run the same server twice
screen -dmS $1 /opt/armagetronad/scripts/srv $1 # start a GNU screen window with the specified server inside
else
for f in $(ls /opt/armagetronad/servers/.) # start a loop running the following command for any existing folders in the /opt/armagetronad/servers folder
do
screen -S $f -X quit # Kill the window if it exists already, avoiding to run the same server twice
screen -dmS $f /opt/armagetronad/scripts/srv $f # start a GNU screen window with the server inside for each server folder
done # ends the loop
fi
Save it and exit the same way as before.

Don't forget to set both files with execute permissions:
<code>chmod +x srv start</code>

=== Starting all servers ===

To make your servers start at boot, edit the /etc/rc.local file and add the "start" script at the end of <code>/opt/armagetronad/scripts/start</code>

If you want to manually start all servers, just run the <code>./start</code> script.

=== Starting a single specific server ===

If you want to start (or restart) a single server, just run
./start servername

== Server management ==

=== GNU screen ===

GNU screen is a great tool. As explained above, it allow a multi-windowed environement on the simple terminal. And even better, the windows stay alive, evening when you disconnect from the server. You can find everything about GNU screen by typing <code>man screen</code> on a terminal.

=== Listing the running servers ===

To see the existing windows, meaning here, the running servers, type <code>screen -ls</code>. It will gives you a list of running windows.

=== Accessing and leaving a server console ===

To attach to a window, type <code>screen -r servername</code>. You will be in the server console. You can then do all the command you would usually do there. Remote moderation, server adjustment, and so on.

To detach, but keep the server running, press CTRL-a d (control key + low case A, then low case D to detach). You can find all GNU screen key combinations by reading <code>man screen</code>.

=== Killing a server ===

To kill a server, attach to its window, and press CTRL-C. This will kill the script, and the window. Then press ESC to exit the dead window. An alternate way is to run
screen -S servername -X quit
This will kill and end the window and the server inside.

=== Log files ===

Everytime the <code>srv</code> script is run, a new logfile will be created in the /opt/armagetronad/logs folder. Keep an eye on log sizes. You don't want to run out of disk space because of Armagetron Advanced, do you ?

=== Test the server autorestart ===

If you want to try if the server restarts when it crash, do not press CTRL-C into the window. CTRL-C kill the script, therefore it will not be able to restart. Instead, run the <code>quit</code> command inside the server console. It will close the server, and you will be able to see the message, and the server restarting.

== Credits ==

This article has been written by Superkikim. These scripts and setup details are used to run the "FAST TRACK" servers.

== VPS packs to install ==

<code>yum groupinstall "Development Tools"<br>
yum install libxml2-devel</code>

Install BZR<br>
<code>su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm'<br \>
su -c 'yum install bzr'</code>
<br>
Compiling Zthreads<br>
<code>
CXXFLAGS=-fpermissive ./configure --prefix=/usr<br>
make<br>
make install<br>
ldconfig</code>

Running Multiple Servers on a single Linux computer

2010-03-13T22:29:34Z

Epsy: Undo revision 23049 by Superkikim (Talk) - Almost qualifies as vandalism.

== Introduction ==

If you like to experiment new settings, it might be that you come with a set of interesting servers. A shame if you cannot run them all at the same time. Here is how you can achieve this on a Linux server. Please refer to the lag and bandwidth chapters in the wiki before to run multiple servers. If you run too many, you might end with a very bad gameplay.

This chapter will present you an easy way to run multiple servers on a single Linux computer, using GNU screen.

== Server installation ==

First of all, you have to install the Armagetron Advanced Dedicated Server from source, not using the provided install script. This will allow to manage at will the settings and var directories. To do so, download the latest source package, and untar it in a temporary folder.

<code>bzr branch lp:armagetronad/0.2.8</code>

In the "configure" command, the prefix will be the application directory. I have choose to install it in /opt/armagetronad/. Make your own choice:

./configure --prefix=/opt/armagetronad/ --disable-glout --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts

Authentication:

./configure --prefix=/etc/arma --disable-glout --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts --enable-armathentication

Then, compile and install:
./bootstrap.sh
make
make install

Now, armagetron advanced dedicated is installed in the /opt/armagetronad/ folder.

== Preparing the servers ==

=== The tree ===

CD to /opt/armagetronad/
cd /opt/armagetronad/

Create the following subdirectories:

mkdir servers 'This folder will be used to store server configurations
mkdir logs 'This one will be used to save the server logs
mkdir scripts 'And this one will be used to same the scripts we will see below

We have now to create our servers. To do so, go to the servers directory you have created earlier, and for each server, create a subfolder with a one-word name for the server, and two subfolders: var and settings. For exemple:

cd /opt/armagetronad/servers

To create a server called server1:

mkdir server1
mkdir server1/settings
mkdir server1/var
then copy your config files in the settings subfolder.

You can then create a second server, and more...

mkdir server2
mkdir server2/settings
mkdir server2/var
and so on...

=== The setting files ===

For each server, do not forget to create a "server_info.cfg" file (search the wiki about it), and to change the port number. Port can be from 4534 to 4540, meaning you can safely run up to 7 servers on the same computer, depending obviously on the settings of each servers, and the bandwidth they need.

We assume that you know enough about Server Administration to understand the above explainations. This article is about Advanced Server Administration, isn't it ?

== The scripts ==

Now you have to create the scripts to launch and log all your servers. To allow managing each server separately, we will use GNU Screen. GNU screen is a terminal window manager. If it is not install on your server, you can get it with the usual installation tool (yum install screen, apt get screen, etc...). Again... advanced.... We assume you know how to install applications on linux and therefore, we assume GNU screen has been installed

You have to create two scripts. The first one will run a server and start logging the window in which the server has started. The second one will execute the first one for each folder in the /opt/armagetronad/servers folder. It will create a window for each of them. Therefore, if you don't want a server to run, you will have to temporarily move the server folder out from the /opt/armagetronad/servers directory.

Save the scripts in the /opt/armagetronad/scripts directory. I use nano which is an easy text editor.

=== The server script ===

The first script will be called in this example: srv

nano /opt/armagetronad/scripts/srv
That creates a text file called srv in the scripts directory. Write the following lines in the file:

#!/bin/bash

screen -S $1 -X logtstamp on # print timestamps in log file
screen -S $1 -X logfile /opt/armagetronad/logs/$1_%d%m%Y-%c.log # create a logfile in the logs subfolder
screen -S $1 -X log on # Turn on logging for the server window
while true; do # start a loop to allow server restart if it crashes

# runs the actual server. By default, the binary is called armagetronad-dedicated and is located in the prefix/bin directory. In this example, it is in /opt/armagetronad/bin directory.
/opt/armagetronad/bin/armagetronad-dedicated --configdir /opt/armagetronad/servers/$1/settings --vardir /opt/armagetronad/servers/$1/var

# Shows the errors and indicates that the server has crashed, and then, waits 5 seconds before restarting the server, allowing you to quit with CTRL-C
echo "Server has crashed. It will restart immediately..., press CTRL-C to cancel"
sleep 5

done # end the loop
To save the file, press CTRL-X and Y to confirm. You have now a file called srv in /opt/armagetronad/scripts.

=== the global script ===

Create the second script. I called it start: <code> nano /opt/armagetronad/scripts/start</code>

#!/bin/bash

# If you run the script with a parameter (server name), only that server will be start. Otherwise, all servers in the /opt/armagetronad/servers directory will be started

if [ "$1" != "" ]; then
screen -S $1 -X quit # Kill the window if it exists already, avoiding to run the same server twice
screen -dmS $1 /opt/armagetronad/scripts/srv $1 # start a GNU screen window with the specified server inside
else
for f in $(ls /opt/armagetronad/servers/.) # start a loop running the following command for any existing folders in the /opt/armagetronad/servers folder
do
screen -S $f -X quit # Kill the window if it exists already, avoiding to run the same server twice
screen -dmS $f /opt/armagetronad/scripts/srv $f # start a GNU screen window with the server inside for each server folder
done # ends the loop
fi
Save it and exit the same way as before.

Don't forget to set both files with execute permissions:
<code>chmod +x srv start</code>

=== Starting all servers ===

To make your servers start at boot, edit the /etc/rc.local file and add the "start" script at the end of <code>/opt/armagetronad/scripts/start</code>

If you want to manually start all servers, just run the <code>./start</code> script.

=== Starting a single specific server ===

If you want to start (or restart) a single server, just run
./start servername

== Server management ==

=== GNU screen ===

GNU screen is a great tool. As explained above, it allow a multi-windowed environement on the simple terminal. And even better, the windows stay alive, evening when you disconnect from the server. You can find everything about GNU screen by typing <code>man screen</code> on a terminal.

=== Listing the running servers ===

To see the existing windows, meaning here, the running servers, type <code>screen -ls</code>. It will gives you a list of running windows.

=== Accessing and leaving a server console ===

To attach to a window, type <code>screen -r servername</code>. You will be in the server console. You can then do all the command you would usually do there. Remote moderation, server adjustment, and so on.

To detach, but keep the server running, press CTRL-a d (control key + low case A, then low case D to detach). You can find all GNU screen key combinations by reading <code>man screen</code>.

=== Killing a server ===

To kill a server, attach to its window, and press CTRL-C. This will kill the script, and the window. Then press ESC to exit the dead window. An alternate way is to run
screen -S servername -X quit
This will kill and end the window and the server inside.

=== Log files ===

Everytime the <code>srv</code> script is run, a new logfile will be created in the /opt/armagetronad/logs folder. Keep an eye on log sizes. You don't want to run out of disk space because of Armagetron Advanced, do you ?

=== Test the server autorestart ===

If you want to try if the server restarts when it crash, do not press CTRL-C into the window. CTRL-C kill the script, therefore it will not be able to restart. Instead, run the <code>quit</code> command inside the server console. It will close the server, and you will be able to see the message, and the server restarting.

== Credits ==

This article has been written by Superkikim. These scripts and setup details are used to run the "FAST TRACK" servers.

== VPS packs to install ==

<code>yum groupinstall "Development Tools"<br>
yum install libxml2-devel</code>

Install BZR<br>
<code>su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm'<br \>
su -c 'yum install bzr'</code>
<br>
Compiling Zthreads<br>
<code>
CXXFLAGS=-fpermissive ./configure --prefix=/usr<br>
make<br>
make install<br>
ldconfig</code>