Armagetron Advanced - User contributions [en]

Double Binding

2011-10-29T01:21:30Z

Jonathan: *Snicker*

In Armagetron, a player may bind more than one key to a turn direction. For example, binding two keys for a left turn, and then pressing them both simitaniously will result in a quick one-eighty turn-around. Double-binding has a long and glorious history smattered with a fair bit of controversy along the way.

== History ==

[[Image:Db_common_setup.png|thumb|right|An example DB setup]]

The earliest known double binder is Locutus. His reasoning was that since he had a bit of carpal tunnel syndrome, it was easier to play the game if he bound two or more keys to the same actions. So when he started doing it, it was to deal with a condition that might otherwise be considered disabling. You know, kinda like having one of those doughnut pillows to drive.

From there, it started spreading to younger more able-bodied individuals who wanted to exploit it to get the other guy. On the older servers, it wasn't a large problem because if you turned around too quickly against a wall, your cycle bounced.

After a certain period of time, another player by the name of Digital Logic popularized the phrase "Double binding is a crutch of the weak", talked a bunch of trash on the forums, and then ran away when the inevitable challenge came. We had the tournament anyway, it was a lot of fun. [http://forums.armagetronad.net/viewtopic.php?t=1018&highlight=model Here's the original thread]

=== 180s in 0.2.7.1 ===

[[image:dbindforweaksSMALL.png|right|thumb]]

The double-edged sword that is Armagetron Advanced 0.2.7.1 had a fix for the bounce bug. It also had some refactoring of rubber code. The end result was that it was now possible for all players to turn around quickly against any given wall many times in a row. The double-binding crowd jumped all over it and created a situation many older players considered almost unbearable.

[[Image:doublebinding.jpg|thumb|left|An example of double binding]]

[[Category:Game Concepts]]

== Triple Binding ==

In addition to double binding, players can also bind as many times as they want which leads to triple binding which is great for making "knots".

== Quaternion Binding ==

Armagetron works using complex numbers. On the standard grid, when you turn, your direction is multiplied with i or –i. You must step aside some distance to turn around. A recent approach uses j and k offered by quaternions to literally get around it. Instead of stepping into i, you would step into one of the other imaginary dimensions. However, you would leave the grid in the process, precluding others from hitting your walls.

A slightly more fruitful and mathematically sensible approach is negative binding, which makes you double back into your own wall. Understandably, it's still not the paragon multi-complex-binders are looking for, although it appears to be the limit of their ideal as sidestep distance goes to zero. Possibly, this confused ideal is related to the misunderstanding of quaternions. Indeed, quaternions might have been picked because it was thought nobody (at least within their clique) would be able to understand the flaws. Investigation is ongoing.

Authentication for Players

2011-10-20T14:47:11Z

Jonathan: /* What you need */ More spam using sneaky CSS link hiding

{{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://trongame.de/forum @pru]
* [http://deathbydistraction.net/forums @dbd]

They're tied to theirs 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 <full account name>", 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.

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}}

Competition Hub

2011-10-20T14:02:58Z

Jonathan: Three-month-old spam! Make sure to undo all edits when blocking a spammer.

{{PlayerTbl}} 
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.

=Current/Upcoming Competition=
{{:CTFtourney/Blurb}} 
{{:CarCurrus/Blurb}} 
{{:Ladle/Blurb}} 

=Suspended/Delayed Tournaments=
{{:HRT/Blurb}} 
{{:WarSumoTournament/Blurb}} 
{{:SBT/Blurb}} 

=Old tournaments=
{{:Rddf/Blurb}} 
{{:Wildcat_Tournament_september_2011/Blurp}} 
{{:IllegalExit/Blurb}} 
{{:EZDF/Blurb}} 
{{:TL/Blurb}} 
{{:Onslaught/Blurb}} 
{{:Fortress_Brawl/Blurb}} 
{{:Sumo1v1Blurb}} 
{{:USvsEU/blurb}} 
{{:Crosseyed&PainlessBlurb}} 
{{:IFC_Blurb}} 
{{:Bowl/Blurb}} 
{{:Kings_of_the_Grid_Blurb}}
{{:FFFBlurb}} 
{{:AFL_Blurb}} 
{{:AVE Fort/Blurb}} 
{{:TiltBlurb}}

Sandbox

2011-07-15T16:53:16Z

Jonathan: Test

'''[[Speeders|SP]]'''
# PsYkO (PsYkO@forums)
# Flex (Flex@forums)
# Delta
# Oblivion
# Insanity
# Omega
# Demon
# Sasha
# cyclo
# prestige
# envy
# Distort

----

{{Ladle Server |Blah|[[User:Nemostultae|Nemostultae]], free kill|Antarctica|Permanently fortress|generalconsumption.org:4534}}

=== Teams List ===

The Challenge Board is '''unlocked'''.

{| border="2" cellpadding="2" style="text-align:left"
! Team Name || Players || Extras
|-
| '''[http://twisted-rats.co.cc/forum Twisted Rats]''' || Corn, CuRbSidE, Durka, Goodygumdrops, JJBean, man2d, SageLord, W33D ... ||
|-
| '''[http://speederclan.5.forumer.com/ ~*The SpeediKs*~]''' || k3nNiK, DelTiK, DeMoNiK, OmEgiK, OblivioniK, PsYkOtiK, fr34kiK, <y<lo, InsanitiK, MagiK, Sasha, DiStOrTiK ... ||
|-
| '''[http://crazy-tronners.com Crazy Tronners]''' || emmy, emphasis, K-Yo, Puuquie, $afari$kater, SeBoL158, $ø1, Woned, Ady-Lucifer, Speed, Tadd, ky13, Punk ... ||
|-
| '''[http://lagtest.net Wild West]''' || Destiny, Shock, Spook, Monkey.D.Luffy, Levi, Punish, Kira, Compguygene, Ethan, ID Killer, ID Steam ... ||
|-
| '''[[Manic Tentacles|Manic Tentacles]]''' || aok_yoshy, Desolate, happen, Mâdé, m0th, orly?, pike, PlayerNuby, Slëëpy, woorm.bot ... ||
|-
| '''[[Plus]]''' || 2020, 1200, Concord, noob_saibot, Radian, sine.wav, teen, whatup, Teen Saibot ... ||
|-
| '''[http://mister.roflforum.net/ Mister]''' || MrMufo, MrJoker, MrChicho,MrRAm,MrNoName,MrS Kilizyaya,MrAlakasam ... ||
|-
| '''[http://nightwalkers.info/ Night Walkers]''' || Zurd, Beanie, Bye, SmoothIce, Arilou, Hi, murder, Pipe ... ||
|-
| '''[[Team_wiki_page|Bebe's Boobs Destroy Society]]''' || Flex, MaZuffeR, Luzifer, madmax, Lackadaisical, Pavelo, Your_mom, dlh, akira_arma ... ||
|-
| '''[http://xclan.armagetron.co.uk/ ¦×¦]''' || Black_hat, Cid, epsy, FoFo, Hoax, Liza, Lizmatic, Radian, Raiden, Roterbaron, Sticky, Subzero, Viper ... ||
|-
| '''[[Fast Fruits|Fast Fruits]] (Open Team)''' || PinkTomato, Ashitaka, Hay-Lin, 0-->, fingerbib, F!Paperclip, noob13, vipe ... ||
|-
| '''[http://ds.experimentalworks.net/ ~DS~]''' || Cruz, Zion, Sunny, G5, Fabi, Plage, Alien, Mesc, Gonz, Bizz, Novo, Dvd ... ||
|-
| '''[http://www.trongame.de/ PLZ RES US!]''' || CCC; Hell-lo; AI-Têam; Mako~X; «:ß:» tågs; uffie; Word; pixie) [http://wiki.armagetronad.net/index.php?title=PLZ_RES_US! teamname: Prude Floyds] ||
|-
| '''[http://arrow-net.tf -»]''' || Members added later ||
|-
|}

asdf is nearly a permutation of sand

== Some heading ==
<pre> sandbox--test out the formatting here
o ____ :::::::::::::::::: :::::::::::::::::: __|-----|__
Y_,_|[]| --++++++ |[][][][][][][][]| |[][][][][][][][]| | [] [] |
{|_|_|__|;|______|;|________________|;|________________|;|_________|;
/oo--OO oo oo oo oo oo oo oo oo oo oo oo oo
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</pre>

=== A sub-heading ===
* Bullet point
* Another
** How about this?
* No.
* Test

Some <code>code text</code>. Yes, it worked.

Math doesn't work right now, apparently I have to upgrade the server. Go ahead and use regular math formatting according to MediaWiki, and don't worry if you can't read it right now. I'll take care of it.

<math>sqrt(x^2 + y^2)</math>

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AA0000; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! Quarter Finals !! Semi Finals !! Finals !! Winner
|-
|1st Seed
| rowspan="2" | 1st/8th
| rowspan="4" | 1st/8th/3rd/6th
| rowspan="8" | WINNER
|-
|8th Seed
|-
|3rd Seed
| rowspan="2" | 3rd/6th
|-
|6th Seed
|-
|4th Seed
| rowspan="2" | 4th/5th
| rowspan="4" | 4th/5th/2nd/7th
|-
|5th Seed
|-
|2nd Seed
| rowspan="2" | 2nd/7th
|-
|7th Seed
|}
I dont seem to be able to make a new page so ive just placed this here till there is a [[THE SPOON PLAYOFFS]] page.
--[[User:Lackadaisical|Lackadaisical]] 13:26, 17 April 2006 (CDT)
:Luci fixed it, the page is now available: [[Playoffs (The Spoon)]] --[[User:Wrtlprnft|Wrtlprnft]] 19:40, 18 April 2006 (CDT)

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AA0000; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! colspan="2" | Quarter Finals !! colspan="2" | Semi Finals !! colspan="2" | Final !! Winner
|-
|?? || '''N/A'''
| rowspan="2" | ?? || rowspan="2" | nyp
| rowspan="4" | ??/CT/LM || rowspan="4" | nyp
| rowspan="8" | WINNER
|-
| style="border-bottom:3px double" | N/A || style="border-bottom:3px double" | N/A
|-
|CT || nyp
| rowspan="2" style="border-bottom:3px double" | CT/LM || rowspan="2" style="border-bottom:3px double" | nyp
|-
| style="border-bottom:3px double" | LM || style="border-bottom:3px double" | nyp
|-
|NI || nyp
| rowspan="2" | NI/MBC || rowspan="2" | nyp
| rowspan="4" | NI/MBC/AW/FE || rowspan="4" | nyp
|-
| style="border-bottom:3px double" | MBC || style="border-bottom:3px double" | nyp
|-
|AW || nyp
| rowspan="2" | AW/FE || rowspan="2" | nyp
|-
|FE || nyp
|}

[[image:test.PNG|thumb|100px|Drawing skills.]]

[data:text/plain,Boo! Not working] :-(
[http://tinyurl.com/2tugf6 TinyURL] (which adds 5 bytes to the URL and lots of overhead) to the rescue!

<math>
$-b \pm \sqrt{b^2 - 4ac} \over 2a$
</math>

<div id="googlecal" style="">[http://www.google.com/calendar/embed?src=davefancella.com_vlfi4psoqnf7ff07vlpdl6dmdk%40group.calendar.google.com view calendar]</div>

&wpTextbox1=hi+i+suck%2E

{{Bug|123}}

User:Wrtlprnft

2008-10-08T07:59:07Z

Jonathan: Baaaad wrtl ;-)

<div style="background:#eee; border:1px solid #444; margin: 1em; padding: .5em">'''This page layout was first used by [[User:Jonathan|Jonathan]]. Just him. On the whole web. He should patent it! ''Well, it was just granted, and I'm suing you now! —[[User:Jonathan|Jonathan]]'''''</div>

Well, I don't know exactly what to put onto this page, noone will read it anyways... But here we go:

== Contact ==

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

== Things in Armagetron Advanced you can blame me for ==

* I'm hosting the [[Servers#Race_Server|original race server]] as well as some other temporary servers. If you see someone doing things they're not supposed to on there, please [[#Contact|tell me]].
* I implemented the new [[Cockpit Tutorial|Cockpit file format]], anything related to that, bugs or just cool files, goes to me.
* There's a console and chat history in all versions since 0.2.8.1, and all versions since 0.3.0 have tab completion as well. 0.3.1 will save the history to a file and allow you to search in it by pressing CTRL-R while being in chat/console mode.
* I added some latin-1 characters to the font files in 0.2.8.0 and implemented a totally new font system in 0.3.0 using FTGL. The default font is also by me using the old bitmap fonts as a base.
* The [http://beta.armagetronad.net/resource-browser/resource resource browser] is also mine.
* Many smaller additions/fixes, I can't list them all here.

== Pages on the wiki with a major contribution by me ==

* [[Cockpit Tutorial]]
* [[Cockpits list]]
* [[Making Maps Switch Randomly]]
* [[Moviepacks list]]

== Other users with a similar page layout ==

* [[User:Jonathan|Jonathan]]
* [[User:Your_mom|Your_mom]]
* [[User:Lucifer|Lucifer]]
* [[User:Epsy|Epsy]]

<div style="position:absolute;top:.4em;left: 10em;font-size:2em;font-family:serif;color:red;">—wrtlpwnd |me| SCNR</div>

Server Administration Guide

2008-10-08T07:48:57Z

Jonathan: /* Test the Server */ It's now clearer that there's a space in "cd "

Setting up a server for Armagetron Advanced isn't terribly difficult, but there are a few things you need to consider when you do it. Taking a few minutes to figure out what you're trying to do will save you a whole lot of headache/heartache later on when people start playing your server.

== Starting out ==

Before you consider what OS you're going to use, what version of the game to run, and so forth, you should figure out a few basic parameters of the server. Here are some you should consider.

=== Private or Public? ===
The setting <code>TALK_TO_MASTER</code> is off by default. To make your server public (available on the master server list), you must turn on this setting. If it is off, players will only be able to connect to your server through the [[Server Bookmarks]] using your IP address. If you are connected to the internet through a router, normally used so that multiple computers can share the same internet connection, you will also need to open a port.

More information on both of these topics is available below.

=== Moderated? ===

Armagetron Advanced supports a limited but expanding set of in game administration commands(in 0.2.8, it will be a fairly comprehensive set). The catch is that you can only have one administration password. So in order to make moderators on your server, all you have to do is give out the administration password.

The alternative is to use the voting features that are intended to allow players to moderate the server as they see fit.

You can go either way, of course. It's entirely up to you.

=== Round or Match ===

There are plenty of ways to setup scoring on a server. A common setting is one point for each kill. While this scoring method encourages competitive play, it's not always desirable. On some servers, just surviving to the end of the round is quite an accomplishment, and you may wish to reward players for doing so. Too much of a reward will encourage players to just screw around instead of fighting.

You should also consider if you even want the standard gladiator-style fighting. It's certainly possible to set up scoring to allow for different games, such as [[Roulette]], and to encourage different playing styles. So just take a few minutes to think about it. It'll pay off in the end, because the default game server settings aren't necessarily the most popular scoring rules, and unless you really want the default scoring, you could lose most of your audience in the first two hours of operation if you didn't think about scoring.

== Requirements ==

=== If you fall short ===

If you cannot meet the requirements to host a server yourself (or simply don't want to leave your computer on 24/7), don't despair! There are companies that specialize in hosting colocated servers-- you can use many of them (such as [http://www.sevenl.net/ SevenL] or [http://www.vr.org VR Hosted]) to host an Armagetron Advanced server. If you don't have the expertise or want to bother with maintaining a full Linux server, you can get hosting specifically for Armagetron from [http://lightfoot.dashjr.org Lightfoot Hosting] or [http://flynnsarcade.net Flynn's Arcade] without needing to setup anything.

=== Hardware ===

Hardware requirements are fairly small. The game itself will only need around 10MB of RAM or so, more for more players. So whatever the minimal requirements for your target operating system will usually suffice. It is important to make sure that the game will not have any of its parts swapped to disk, just like with any other server, but memory usage is minimal.

CPU requirements are also pretty slim. Again, whatever the requirements for your target operating system will likely suffice. A common number provided for a server CPU is a 600mhz Pentium II or greater. Some popular servers have run on as little as 800mhz AMD Duron! Starting in 0.2.7.1, it is possible to limit the framerate of the simulation itself. This gives several important traits to the game. First, it makes it play nicely even on a computer that runs other tasks (such as a web server). It also provides for more stable gameplay. Finally, it allows you to tailor the simulation for your hardware, so on a smaller CPU, you should consider limiting the framerate of the simulation to improve gameplay.

=== Network ===

The size and speed of your network connection is more than likely going to be your first and most serious performance bottleneck. Generally you'll want to consider that each player connected requires about 6KB/second of upstream bandwidth. So for 16 players, you'll need 96 KB/sec of upstream bandwidth. This doesn't consider any other bandwidth usage on your network, such as web browsing from a different machine. Use MAX_CLIENTS to limit the number of players accordingly.

More information is given for both of these topics in the [[Advanced Server Administration Guide]].

== Setting Up ==

So now you've figured out what kind of server you want and how you want people to play on it, and you want to know how to set it up and optionally make it available on the master server browser. Setting up is fairly straightforward.

If you do not wish to bother with setting up a server yourself, and be left to simply administrate your server, [http://lightfoot.dashjr.org Lightfoot Hosting] or [http://flynnsarcade.net Flynn's Arcade] provide managed hosting for Armagetron servers-- you can just configure it how you like using a simple web interface and be ready to play.

=== Install the Server ===

First you need to install the server. It's common to think of any given "server" as a special machine built by old women in third-world countries, but actually, a "server" is just any machine that makes a "service" available to other users. In this case, you're going to install software on a computer, possibly your desktop computer, that will make a game service available for other users to use.

So first you need to acquire the package called "armagetronad-dedicated". If you're using Linux, get one that says "linux" on it. For Windows, get the one that has ".exe" on the end of it. For Mac OS X, there's one with a ".dmg" extension for you. Usually the CPU architecture and OS are embedded in the filename, so pick the right one and install it.

We won't go into too many details here about installation, consult the regular documentation for how to install the server for your architecture.

=== Test the Server ===

After installing the server, the first thing you should do is test it. So start it up. If you're in Linux, you will want to become the superuser and type, in a terminal, "/etc/init.d/armagetronad-dedicated start". If you're in Windows, find the icon in your Start menu and click it. If you're in Mac OS X, open the application Terminal which can be found in Utilities in the Applications folder. Type "<code>cd </code>" there (without the quotes, and note the space immediately after cd) and drop the folder containing the dedicated server on the window. You should now see something like "<code>cd /Users/username/Desktop/Armagetron\ Advanced\ Dedicated/ </code>" if the folder is located on your desktop. Run it by pressing enter or return. Once you're in there, run ./armagetronad-dedicated to start the server. Then fire up a client and see if you can connect to it as a LAN game (under Network Game). If you can do this, then you have successfully tested the server. Now you need to shut it down. In Windows, go to the console window for the server (it opens when you start the game) and type "QUIT". In Linux, just do "/etc/init.d/armagetronad-dedicated stop". In Mac OS X, you type "quit" in the Terminal window like in Windows, after which you can close the Terminal window.

== Public Servers ==

If you want to host a server at home. You have to open UDP port 4534 in your firewall and possibly forward the port from your router to the PC running ArmagetronAd (and is hosting a game).

=== Firewalls ===
*Windows XP: Either your firewall will ask you if you want ArmagetronAd to open port 4534. You can also follow [http://support.microsoft.com/default.aspx?scid=kb;en-us;308127 these instructions] use name: "Armagetron Server" the port is UDP 4534 (leave TCP blank).
*ZoneAlarm: TODO: popular? should it be added ?
*Mac OS X: Go to System Preferences ? Sharing ? Firewall. One way to let all traffic through is turning it off, but you may not want to do that. If you decide to leave/turn it on, look for a button labeled “Advanced…”. If it exists, go there and ensure “Block UDP Traffic” is not checked. If it doesn't exist you have an old version that never blocks any UDP. For the curious: this is a limited GUI to ipfirewall.
*Linux: TODO Lucifer ? Link to a site ?

=== Port forwarding ===

If you have a router with [http://en.wikipedia.org/wiki/Network_address_translation NAT], you'll want to forward a port to your server so others can reach it. Armagetron uses the UDP port from configuration option SERVER_PORT, which is 4534 by default. You'll probably want a forwarding entry that looks like:
* Local/internal address: <your server's IP address>
* Protocol: UDP
* Local/internal port: <SERVER_PORT>
* Remote/external port: anything should work, but <SERVER_PORT> is common.

It is important that your server's IP address never changes. You can manually choose an address outside the address pool used by DHCP, or an address that is unlikely to be assigned (e.g. if the lowest available address is always assigned, you can use an address ending with 100), or disable DHCP altogether and configure everything manually. [http://www.portforward.com/ http://www.portforward.com/] has more info on that.

If you can't figure it out, consult your router's manual. You can also look for help at the aforementioned [http://www.portforward.com/ http://www.portforward.com/], which has tutorials for many routers, and a forum. It doesn't have an Armagetron entry (yet), but it has been found that [http://www.portforward.com/english/applications/port_forwarding/F-22Lightning3/F-22Lightning3index.htm F-22 Lightning 3's] port range contains Armagetron's default port, so if you're absolutely clueless you can go with that.

==== Dynamic external IP addresses ====

If you have a dynamic external IP address, you can use a service like DynDNS's [http://www.dyndns.com/services/dns/dyndns/ Dynamic DNS] to map a name to your IP address. When your IP address changes, a small updater program will send the new address to DynDNS and update the address associated with the name. You should set the setting SERVER_DNS to the name you registered to ensure clients and the master servers can keep track of you when your IP address changes.

=== Secure the Server ===

There isn't really a lot to do here, but you should consider how you want to secure the machine. If you think it will be necessary to ban certain players, then a firewall is your only option. Since ArmagetronAd 0.2.8.x you are able to ban IPs.
For older versions you can use a firewall that allows you to deny connections from users by IP address. It's not foolproof, but it's the only thing possible until we have player authentification.

Contrarily, if you do not want internet players to be able to use your server, you will need to make sure your router prevents such players but making the port mentioned above inaccessible through the router.

== [[Configuration Files]] ==

At this point you should have a good idea of what kind of server you're going to run and you should also have a working server running, but you don't yet have the server you set out to build. Now you need to configure the server itself.

The server is very flexible. As of the 0.2.8 release, you have pretty complete control over the simulation, and you also have some settings that you can configure the game rules a bit. So now all you need to do is make the settings, right? Wrong. :) First you need to understand how the settings are loaded and in what order.

=== Examples ===

Note: These examples first appeared in one of the release candidates for 0.2.8. Depending on what version you install, you may not have all of them, or even any of them. The final 0.2.8 release will have them for all platforms, however.

Several example files are provided to help you get set up and running quickly. These files contain snippets of settings that range from simple adjustments to cycle physics to more complex snippets that encapsulate complete game rules. So if you've played a server that you really enjoy and you'd like to use it as a base to build your own server, you can look to see if any of the example snippets provide the settings you're wanting.

Some of the snippets are named from the servers they came from. When you see this, it is because the file contains a fairly complete set of settings to make a server exactly like the server where the settings originated. Others are named after a specific action. These may have originated in a server, or they may not have originated in a server. If they came from a server, you can read the comments in the file to see which server they came from.

Each example snippet is built with the intention of being included in your <code>settings_custom.cfg</code> file so you don't have to copy and paste the contents in order to use them. Be warned, however, that the example snippet you've picked may be changed in an upgrade. This will happen periodically when the game engine changes in a way that renders the settings snippet in a different fashion than it was intended, and the changes will be made to attempt to bring that file back to the same feel of play as it originally had. If you want to use those upgrades to your benefit, then you can and should go ahead and include the snippet file as shown. If you want to insulate your server from such upgrades, then you'll need to copy and paste the contents of the file into your own <code>settings_custom.cfg</code>.

Examples:

To make a fortress server, add this line to <code>settings_custom.cfg</code>:

<code>INCLUDE examples/fortress_soccer.cfg</code>

To add a death zone to your server, you can add this line:

<code>INCLUDE examples/death_zone.cfg</code>

To add a single-use booster in place of the brake, you can use:

<code>INCLUDE examples/single_use_turbo.cfg</code>

Some of the example files may modify the same settings that others modify. When two examples conflict in this fashion, the one that is listed last will override all others. So place the one you wish to have persist at the end.

If you'd like to taylor the settings after you've included them, place your own settings after the relevant include lines. In fact, you should place all of your additional settings after all includes in order to ensure that no new included file will override your own settings.

=== Making your own Settings ===

The most common settings to change affect game logic, scoring, and some basic simulation such as cycle speed, acceleration, and so forth.

==== Simulation Settings ====
;EXPLOSION_RADIUS
:Blast radius of cycle explosions. Set to 0 to have no explosion radius (obviously).
;WALLS_LENGTH
:Cycle trail length. Set to -1 to have infinite trails.
;WALLS_STAY_UP_DELAY
:Cycle trail stay up this long after the cycle's destruction, measured in seconds.
;SPEED_FACTOR
:Cycle speed factor. Increase this by two to double the speed
;CYCLE_RUBBER
:This affects grinding. Higher numbers allow players to get closer to walls before crashing. It's intended to be used solely to correct for lag, but it's usually not used that way.

==== Map Settings ====
;ARENA_AXES
:Sets the number of possible driving directions (used only when map is axes-independent, otherwise the map overwrite this value)
;MAP_FILE
:This describe how to retreive a map. It uses a special syntax to allow to describe the location of the map on the local disk and a possible list of network based location, such as web url, where to retreive the file. The syntax is "[./][directory[/directory[...]]]/filename [(fulluri[; fulluri[; fulluri[...]]])]". By default, missing files are looked up by the client on the central resource repository. If one of more URI are given in the MAP_FILE, they will be queried before going to the resource repository.

==== Game Rules ====

;SCORE_WIN
:Points you gain for being last one alive. Also known as "camping points"
;SCORE_SUICIDE
:Points you gain for every stupid death (race into the rim/your own wall). It is added, so negative numbers are appropriate here unless you want to reward people for being stupid.
;SCORE_KILL
:Points you gain for everyone racing into your wall.
;SCORE_DIE
:Points you gain for every time you race into someone else's wall. Like SCORE_SUICIDE, you should make this a negative number unless you want to reward people for sucking.

;LIMIT_SCORE
:Score limit. When a player reaches this score, the match ends and that player wins. Ties are resolved by playing another round until one player has more points than the rest.
;LIMIT_ROUNDS
:Max number of rounds to play. When this is reached, the highest-scoring player is named the winner.
;LIMIT_TIME
:Max time (in minutes). When this is reached, the highest-scoring player is named the winner of the match.

Here is a pretty common setup:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 10
LIMIT_ROUNDS 40
LIMIT_TIME 30
</pre>

This is the scoring system used on servers like Swampland, the old Tigers Network servers, and the goshdarn clones that are floating around. It basically means you have to get 10 points by killing other players to win the match. Breakfast in Hell used a variation:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 1000
LIMIT_ROUNDS 40
LIMIT_TIME 7
</pre>

You still had to kill people to win, but the match was limited to 7 minutes. After 7 minutes, a winner was declared. The Crack Pipe still uses these settings at the time of writing but may change in the future.

'''This isn't a complete list!'''

There are a whole slew of configuration items available. Since the config items are the same as console commands, you can see a pretty complete list on the [[Console Commands]] page.

== Finishing Up ==

The last thing you need to figure out is usually the first thing you know. Do you want this server to be known by the master server? If so, you need to add this line to your settings_custom.cfg:

<code>
TALK_TO_MASTER 1
</code>

Note: in previous versions, this was the default, but as of 0.2.8, the default will be to not talk to master. You will have to manually set that, so make it the last thing you do before starting the server up for play.

You will also likely need to set <code>DEDICATED_IDLE</code> to 0. If you're in Linux and you're using the init script, then you probably don't have to worry about it, because the init script will restart the server automatically. But if you're not in Linux, you'll need to place this in your settings_custom.cfg:

<code>
DEDICATED_IDLE 0
</code>

For instructions on server-restarting on Mac OS X and Linux/UNIX systems go to [[Server_auto_restart]].

If you want your server to be known on the internet, you will probably need to open a port in your router. The default port is 4534, and you need to open it for "udp". Instructions on how to configure this on your router are beyond the scope of this document, you should consult your owner's manual for further information.

Of course, when that's all done, you need to start the server. Use the same procedure already referenced.

== Conclusion ==

This article is the basic "How to setup a game server" article. After reading through this article and getting your server running, the best thing you can do is to play your server for awhile, talk to other administrators, and so forth. Find out what people want, or figure out what you want. Tweak your settings however you'd like, it's your server. When you feel like you've got the hang of running a server, check out the [[Advanced Server Administration Guide]] for more cool things you can do with your server.

In the meantime, have fun!

[[Category:Server/config]]

Gentoo Portage Overlay

2008-02-25T23:39:02Z

Jonathan: Too much spam

== Prerequisites ==
=== Setup layman ===
To install and use Portage overlays, you must first install and configure layman:
emerge layman
echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf
Before you can use layman, you need to fetch its list of overlays:
layman -L
You may also want to read [http://www.gentoo.org/proj/en/overlays/userguide.xml the Gentoo Overlays Users' Guide] for more information on layman, including how to update your overlays.

== Adding the Armagetron overlay ==
layman -a armagetron

== Installing Armagetron Advanced ==
=== USE flags ===
Several USE flags exist for Armagetron packages:
* debug: Enabled debug mode. This may disable certain features, and enable debugging artifacts.
* dedicated: Builds the dedicated server
* moviepack: Installs graphics making Armagetron look more like the movie TRON
* moviesounds: Installs sound files from the movie TRON. You can set LINGUAS="es -en" to get sounds from the Spanish movie instead.
* opengl: Builds the regular game client; default unless USE=dedicated

=== Packages ===
* armagetronad: Releases of Armagetron Advanced. If you set ~arch keyword, you will be able to install experimental releases.

== Updating the overlay ==
You can sync just your Armagetron overlay via layman:
layman -s armagetron
Or sync all your overlays at the same time:
layman -S

PlayingGettingStarted

2008-02-25T23:38:16Z

Jonathan: Reverted edits by RacviOulae (Talk); changed back to last version by Jonathan

{{Sections}} 

This document attempts to give the minimal set of knowledge required for a player to enjoy the game.

= Getting ready to play =
Once you start ArmagetronAd, the game will be launched in fullscreen. To be able to follow this document, press "f" to toggle between fullscreen and windowed mode.

== Select your preferred languages ==
Once the game is started, you will be asked to select your preferred language. Use the right and left arrows to change it. The secondary language is used when a translated text cannot be found in the primary language. Once selected, use the up and down arrows to move to Accept and press return.

== Hardware detection ==
A screen indicate the 3D hardware found. It us usually properly detected, so feel free to press return to continue. Even if not detected properly, you will still be able to play the game.
You should now be at the main menu, labeled "Armagetron Advance" with the items "Game", "Player Setup", "System Setup", "About" and "Exit Game". Remember this menu, it will be the navigation reference.

== How to move in the game ==
Before launching into play, here is the minimal keys you will need to know:
*To turn left, press either z, y or w
*To turn right, press x
*While playing, you can always activate the menu by pressing ESC. To stop playing, navigate to "Leave Grid"
*To navigating back to the main menu after leaving the grid, press ESC once more.
On most keyboard on the world, it should allow you to use the left most letter on the bottom row of your keyboard to turn left, and the second left most key to turn right.

== Start playing ==
In its basic form, the game will present you with battling AI. Avoid colliding with the various walls and use the trace you leave behind you to trap and kill the AI. After a few battles, leave the grid and return to this document.
To start playing, from the main menu:
*Select the first item, labeled "Game", and press enter.
*Select the first item, labeled "Local Game", in the new menu, and press enter.

= Rubber and Grinding =
Battling AI at near constant speed is quite a challenge, but barely allows to overtake a fleeting enemy or to seal another in a closed area for them to die. These strategies and more are enabled through the usage of rubber and the technique of grinding. Together, they constitute the base of the play.

== [[Rubber]] ==
Rubber allows you to press yourself to a wall, preventing you from crashing into it for a very short period.

Rubber allows a cycle to near itself to a wall, as if a cushion was laid before it. Press too hard on the cushion and you hit the wall. Turn while you are pressing on it, and you will yourself tightly placed against the wall, leaving little place for someone to follow.

Each time a cycle uses this cushion, its rubber reserve are consumed. If it reaches its limit, it hits the wall it was pressing on. Coming to a wall at greater speed with consume rubber faster, as pressing to end up tighter with the wall. Normally the cycle will regenerate its own rubber reserve with time.

== Grinding ==
Running a cycle parallel to nearby traces and sometimes walls will accelerate the cycle. The closer you are, the greater the acceleration you get. Useful when attempting to overtake an enemy. Driving between 2 traces will provide greater acceleration.

Use your gained speed advantage promptly, as with time your cycle will return to its regular speed. Each turn you make will further slow you.

== Learning Rubber and Grinding ==
The default setting of the game give very little rubber. To help you experiment with rubber, we will raise its limit. We will also lower the basic speed for the cycle so you can more carefully observe how rubber is consumed and practice grinding walls.

To change game settings, the console is used. The console is a simple text input field that allows you to redefine all the parameters of the game. It is accessible both during play and in any menu. To activate the console, press either the ^ key or the ` key. The text "Con:" should appear the bottom of the screen. There, type the parameter to affect followed by the value desired. The console is case insensitive, so typing "Cycle_speed 10", "cycle_speed 10" or CYCLE_SPEED 10" will produce the same result.

Now activate the console and write, without the quotes:
"cycle_speed 10"
This will reduce the speed at which the cycle tend to move, giving you more time to think and maneuver. Feel free to adjust to your preference.

The rubber meter is presented on the lower left part of the screen when you are playing. Note that by default the bar goes from 0 to 1, quite a small reserve of rubber. To change this, you will need to pass the command "cycle_rubber" (without the quotes) followed by a number.

Activate the console and write, without the quotes:
"cycle_rubber 10"
This will raise the rubber available to all the cycles. Feel free to adjust to your preference.

Once you have changed the cycle_speed and cycle_rubber settings, practice pressing your cycle agains traces and wall, and getting acceleration by grinding them. In the basic setup, no acceleration is gained from grinding the outer rim even though rubber is consumed when you press on it. Experiment and learn from those settings, but do not to used to them. Such a generous amount of rubber is not often seen on multi-player games.

It is to be noted that setting changes through the use of the console are not saved. When restarting the game, the original values will be restored.

=Zones=
Zones are the game elements used in ArmagetronAd. As zones can offer perculiar behavior, this section will give you a rough introduction to them.

== Win and Death Zones ==
The win and death zones offers instant win and instant death to any cycle who enters them.

To try them, you will be required to load a new map. To do this, from the console type map_file followed by the name of the map to be used. In this instance, the file name is AATeam/demo/win-1.aamap.xml, so at the console, type "map_file AATeam/demo/win-1.aamap.xml", without the quotes. If you dont have this map already on your system, the game will attempt to download it automatically, so you should probably be connected to Internet when you attempt this.

On the next round, the arena should hold a green win zone and a red death zone. Experiment with either zones. Note that for your convenience that there are no AI, as they are too subject to the zones. Also, your trace is not of a finite length, allowing you move freedom of movement.

== Conquest Zones ==
Zones can be configured so it is not the action of entering them that produce the effect, but rather by the cycle being inside the zone, often or a certain amount of time.

Using the console, type "map_file AATeam/demo/conquest-a-1.aamap.xml". This will load a map containing a single zone. You have to pass a total of 12 seconds in it in total to conquer it. As you conquer it, you should see it turning faster and faster onto itself, giving you a visual representation of the state of the conquest. Once conquered, the zone collapse and the round is won.

Now load the map named "AATeam/demo/conquest-b-1.aamap.xml". This time, your conquest of the zone gets eroded with time, meaning that if a partially conquered zone is left alone for a while, it will return to its original status and you will have to re start the conquest. Do not worry, the conquest rate is in your favor at a rate of 4:1. It would take 4 seconds outside of the zone to loose the conquest generated from 1 second inside the zone. Experiment with this zone until you are comfortable with the conquest and decay concepts. Note that when totally left alone, the zone simply turn at its lowerst original rate, indicating that the conquest of this zone has been reset to nothing.

This time the zone is configured in a way that it is the natural decay of the zone that conquers it. Left alone, the zone will naturally conquer itself and you will lose. To prevent this, passing time inside the zone will actually annulate the decay. Again, the odds are in your favor in a 4:1 rate. Each second passed inside will annulate 4 seconds of natural decay. So keep on your guards and do not wander too far. This map is named "AATeam/demo/conquest-c-1.aamap.xml".

In multi-player setups, the following names can be encountered:
- Fortress: Each team have to defend their own zone while trying to conquer the enemy's. The decay usually move the status of the zone toward non conquered.
- Sumo: Multiple zones surimposed with decay set to conquer the zone. Each player has to fight the other players for some space under the common zones in to prevent his own zone of being conquered, or face certain death.

= Multi player =
Beside rudimentary AI, the ArmagetronAd games allow you to compete again other player on the same computer, on a LAN or over Internet.

== Connecting to a LAN server ==
For the main menu, navigate to "Game". There select "Network Game" and then "LAN Game". The game will query the local network (LAN) for any server, and present them in a list.

It is possible to use the client to host a server. From the list of local servers, click on "Host Game" and then "Host Network Game". Your copy of ArmagetronAd will allow you to server as a server for other to connect to, while letting you join in the action. The server will run until you exit the menu.

== Connecting to an Internet server ==
For the main menu, navigate to "Game". There select "Network Game" followed by "Internet Game". The application will start querying different servers from all around the world and present you with a list of servers with a few details. It is strongly advised that you read the short description presented for each server at the bottom of your screen. It often gives you valuable information about the server you are about to join.

Selecting one will connect you to it. More information might be presented to you during the connection operation. Read it carefully as it often describe the type of game you are about to try. And dont forget to communicate with the other players present using the chat capacity of the game, available on the 's' key.

Internet access is of course required for this.

== Type of play ==
The dynamic of the game will be decided by the settings in use. These settings and resulting combinations are too various to cover here. Also, when connecting to a LAN based server or an Internet based one, the server will decide of the configuration.

One rough categorization is possible: Free for all versus Team Play.

When in doubt, do not hesitate to communicate with the other players. Chat capacity is associated with the key 's'.

=== Free for all ===
In this type of play, all the players compete against each others. It is left to you to make the best use of your cunning, reflexes, experience and even ad-hoc alliances to raise yourself to the top.

=== Team Play ===
In this type of play, cooperation between members of a team will usually produce better results than having everybody trying to accomplish the same goals. Often, individualism will actually harm your team mates, and incite their fury toward you. Be observant when joining a server, your team mates might be relying on you and ignoring them might cause great troubles.

Ladle-4/Challenge Board

2008-02-25T23:38:15Z

Jonathan: Reverted edits by RicdeLouol (Talk); changed back to last version by Your mom

{{Ladle-4}}

The Challenge Board is designed to make the pairing of teams easier. '''The challenge board is now locked.'''

The following list is the definitive schedule. There is a choice of servers to allow predominantly American teams an opportunity to play in a low-ping grid.

=== Quarter Finals 7.30pm GMT ===
* Team 1 challenges Team 2 on Z-man's Tournament Fortress
* Team 3 challenges Team 4 on AST Fortress
* Team 5 challenges Team 6 on Wildwest - Fortress (bugfarm)
* Team 7 challenges Team 8 on LOD Lords of Destruction Fortress Server

=== Semi Finals 8.15pm GMT ===
* Team 1/2 challenges Team 3/4 on AST Fortress
* Team 5/6 challenges Team 7/8 on LOD Fortress

=== Finals 9pm GMT ===
* Team 1/2/3/4 challenges Team 5/6/7/8 on AST Fortress

Server allocation depends on what servers are available on the night. Check the discussion page to see recent availability of servers providing Standard Fortress Settings, and feel free to propose alternatives. Ultimately, Team-Captains will decide.

=== Challenge Board ===

* Team 1 is... [[We Pwn Noobs|WPN]]
* Team 2 is... [[Tronic Monkeys]]
* Team 3 is...
* Team 4 is... [[Holers]]
* Team 5 is... [[SteveTaylor]]
* Team 6 is... [[Wraith Squadron]]
* Team 7 is... proN00bz
* Team 8 is... .Tronners in pyjamas|

The Challenge Board is locked. Only WPN is either Team 1 or Team 3... flipping a coin... heads for team 1... done -- heads, so WPN is Team 1, and Team 4, Holers, get a bye in the quarters and their first game is in the semi's.

=== Provisional Brackets ===

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! colspan="2" | Quarter Finals !! colspan="2" | Semi Finals !! colspan="2" | Final !! | Winner
|-
| colspan="2" style="border-bottom:3px double" | 7:30 PM GMT || colspan="2" style="border-bottom:3px double" | 8:15 PM GMT || colspan="2" style="border-bottom:3px double" | 9:00 PM GMT || style="border-bottom:3px double" |
|-
|WPN || 2
| rowspan="2" | wpn || rowspan="2" | 0
| rowspan="4" | ho || rowspan="4" | 0
| rowspan="8" | proNoobz
|-
|tm || 0
|-
|none || N/A
| rowspan="2" | ho || rowspan="2" | 2
|-
|ho || '''bye'''
|-
|st || 2
| rowspan="2" | st || rowspan="2" | 0
| rowspan="4" | pN || rowspan="4" | 2
|-
|ws || 0
|-
|pN || bye
| rowspan="2" | pN || rowspan="2" | 2
|-
|TiP || n/s
|}

This will be filled out throughout the competition

{{Ladle-4}}

AFL Rules

2008-02-25T18:29:56Z

Jonathan: note to self: don't look only at recent diffs

{{AFLTbl}}

For judges, and players who'd like to know how these rules will be used, we have a separate document for [[AFL_Rule_Interpretation|interpreting the rules]].

Also, [[Game Procedure]] tells players how to play an actual game.

== Teams ==

# Teams need a team name, and a team name-tag which will be inserted in the name of the player during games.
# Teams can consist of up to but not exceeding ten members.
# Teams are responsible for their own organization. Lack of organization can well end up in forfeiture of a game, so make sure that you stay on point and organized.
# Every team will make a roster, which will not change over the course of the season.
# Teams can drop players from their teams at any time during the regular season. Teams must notify a judge of drops before the next game.
# To add a new player to a team, the team must get approval of a judge.
# After the playoffs begin, no new players can be added, and a drop requires league approval (approval of a judge).
# Teams will consist of a team captain and up to nine other members
# Teams can contact the league for whatever reason through the #afl or #armagetron channels on irc.freenode.net or on the armagetron forums at forums.armagetron.net. Due to the potential for time-wasting conflict, we will not accept references to something he or she said on this or that server or so and so's forum for the purposes of mediation. The AFL pages on wiki.armagetronad.net will keep current contact information for all league contacts.

== Servers ==

# The behavior of all servers participating in the AFL will be exactly the same, and settings will be provided by the league to the server admins.
# Servers will use rules approved by the league. We'd like to allow cycle_rubber modifications within reason to correct for lag, but due to the widespread notion that rubber has nothing to do with lag, we can't make this allowance. Help change the mistaken widespread notion!
# Teams must choose a server to be their "home server." We recommend teams choose a server where their team has a low ping as a whole and with an administrator that is friendly to the team. Ideally, teams would provide their own home servers, but due to the bandwidth and performance requirements, the league is attempting to provide servers for teams to choose from.

== Games ==

# In games, teams can have a maximum of five players on the grid. Teams that show up with less than 5 will be expected to play with what they bring, or forfeit. Teams that show up with more than 5 will be allowed to use their extras as alternates and make substitutions. However, at no point can more than 5 teammates appear in the round. If this should happen, the extra player should kill himself within seconds of the round starting, or else the round will be declared invalid, possibly the match declared invalid, or some other really nasty penalty will be given. The league's approved settings should reduce/eliminate the risk of a team playing over 5 players accidentally, but it cannot eliminate the risk of a team starting a round with only 4. Tough luck.
# Each game will have a home team and a visiting team, as in professional sports.
# A game will consist of three matches played at the home team's declared server.
# The winner of the game is the first team to reach two match wins. If this should be the first two matches, playing the third match is optional, but allowed if time permits.
# For a match to be considered as being conducted as a league match, there must be a recording made with either the latest release of 0.2.8 or the latest 0.3.x release (currently 0.3.0). While any version is allowed for play, a recording made from the trunk will not be considered as having met this requirement. We are studying whether or not a server-side recording is to be accepted.

== Season ==

# Matches will generally be played on Tuesdays UTC, and Sundays will be used as an alternative day in case of complications with Tuesday, but we can't guarantee the matches will always be scheduled on those days. Check your schedule.
# Over the course of the season, each team will play each other twice, one game played at their declared home server and one game played at their opponent's declared home server.
# Teams will be ranked during the season according to their win-loss record. Any ties brought about by this system will be resolved by head to head results.
# The final rankings of the season will be used to seed teams in postseason play.

== PostSeason (Your chance to win a chip!) ==

# To qualify for the post-season, a team must consist of at least 60% of the roster that existed at the time of their second game in the regular season.
# The postseason will consist of a series of one-off elimination games in a bracket-tournament setting.
# Teams will be seeded according to the final season rankings.
# Teams will play at the declared home server of the higher seeded team or an available quality neutral league server.
# Teams will be eliminated in every round of the tournament, leading up to a game between two final teams, which will be the championship game, and the winner of this game will be declared champion. Should the playoffs contain 8 teams or more, the top 4 positions will be determined, otherwise only the championship game will be played.

== Rewards ==

# The prize for winning the championship game will be some t-shirts with a to-be-determined graphic by DrJoeTron. Note: this does not apply the the Summer 07 season.

== Sportsmanship ==

# Don't be a douche. We'll look at the recordings, and we'll know, and you'll know, and we'll tell your mother.
# Also, some really bad sportsmanship can entail severe penalties, like forfeiture of the game, suspension of a player, and even suspension of a team.
# Bad sportsmanship can be considered any of the following:
#* Insulting the opposing team
#* Declaring the game to be a bad game due to the fact that your team lost. While it may be true that it was a bad game, it's still bad sportsmanship to raise a fuss about it. If you truly believe the game was bad, speak to a judge about it to resolve the problem.
#* Core dumping a player's own teammates
#* Refusing to play competitively
#* Quitting a game because the player's team is losing.
#* Anything else your PE teacher told you was bad sportsmanship.
# Penalties for bad sportsmanship will be assessed based on degree of infraction, rate of infractions, and so forth. Basically, you might get away with something once when the judges sympathize with you, but don't expect it to happen a lot. The point is to have fun, and you should behave in a manner that is conducive to everybody having fun, not just you.

Assemble

2008-02-25T18:28:47Z

Jonathan: REALLY cleaned now

{{:TiltBlurb}}
----
----
{| border="2" cellpadding="2" style="text-align:center"
! || EST || PST || GMT
|-
| '''Quarter Finals''' || 7:00pm || 4:00 pm || 12:00 am
|-
| '''Semi Finals''' || 8:00 pm || 5:00 pm || 1:00 am
|-
| '''Finals''' || 9:00 pm || 6:00 pm || 2:00 am
|-
|}
----

== Tilt Assemble ==
'''Sign Ups for Tilt 1 begin Sunday, September 30, 2007.

***Please Create a Team Name, It makes the bracketing a lot easier to follow.

* Team 1 is... -=XXX=- Porn Team - {Mist, Teatime, Tyler, Speed}
* Team 2 is...
----
* Team 3 is...
* Team 4 is...
----
* Team 5 is... <2nd> Second Place Team - PsYkO
* Team 6 is...
----
* Team 7 is...
* Team 8 is...

'''Sign Ups are closed at 6 PM EST time on the day of the Tilt'''
----
----
----

== Quarter Final Bouts ==

* SpeederS ServeR will host the battle between Team 1 and Team 2.
* High Rubber Tilt (Manta) will host the battle between Team 3 and Team 4.
* .Humility & honor'h will host the battle between Team 5 and Team 6.
* -=}ID< -=}Immortal Dynasty< will host the battle between Team 7 and Team 8.

== Semi Final Bouts ==

* SpeederS ServeR will host the battle for the top bracket.
* .Humility & honor'h server will host the battle for the bottom bracket.

== The Final Tilt ==

* The host server for the Final Tilt will rotate between SpeederS ServeR and .Humility & honor'h Server

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:00 PM EST || style="border-bottom:3px double" | 8:00 PM EST || style="border-bottom:3px double" | 9:00 PM EST
|-
| style="border-bottom:0px" | Team 1
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 2 || style="border-bottom:0px" | []
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Team 3 || style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@High Rubber Tilt (Manta)''' || style="border-left:0px" | 0-0 || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 4 || style="border-bottom:0px" | || style="border-bottom:0px" | []
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ SpeederS ServeR''' || style="border-left:0px" | 0-0
|-
| style="border-bottom:0px" | Team 5 || style="border-top:0px" | ||style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ .Humility & honor'h server ''' || style="border-left:0px" | 0-0|| style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 6 || style="border-bottom:0px" | []
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ .Humility & honor'h server''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Team 7 || style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ -=}ID< -=}Immortal Dynasty<''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 8
|}

'''TILT 3 WINNER -=xXx=- Porn Team !'''

== Servers and Server Settings ==

'''I have successfully averaged the servers to make the fairest server possible. A server that can be adapted to easily by those who favor the SP/ID settings or those who favor the iZm/H'h settings. Make sure when you do test these settings that there is no deathzone!'''

*BUG_COLOR_OVERFLOW 1

*CAMERA_SERVER_CUSTOM_TURN_SPEED_180 4
*CYCLE_ACCEL 41
*CYCLE_BRAKE 155
*CYCLE_BRAKE_DEPLETE .4
*CYCLE_BRAKE_REFILL 1
*CYCLE_DELAY 0.008
*CYCLE_DELAY_TIMEBASED 0
*CYCLE_RUBBER_MINDISTANCE_UNPREPARED 0.005
*CYCLE_RUBBER_MINADJUST 0.08
*CYCLE_RUBBER_MINDISTANCE_LEGACY 0
*CYCLE_RUBBER_MINDISTANCE_RESERVOIR 0.005
*CYCLE_RUBBER_MINDISTANCE_RATIO 9.99868e-05
*CYCLE_RUBBER_TIME 1
*CYCLE_RUBBER_TIMEBASED 1
*CYCLE_SOUND_SPEED 30
*CYCLE_TURN_SPEED_FACTOR 0.98
*CYCLE_WALLS_STAY_UP_DELAY 2
*CYCLE_SPEED 35
*WALLS_LENGTH 2000
*REAL_ARENA_SIZE_FACTOR 1
*VOTING_TIMEOUT 60
*VOTING_TIMEOUT_PER_VOTER 15
*WIN_ZONE_MIN_ROUND_TIME 9000
---
*TEAMS_MAX 2
*TEAMS_MIN 2
*AUTO_TEAM 1
*TEAM_MAX_PLAYERS 4
*TEAM_MIN_PLAYERS 1
*TEAM_BALANCE_WITH_AIS 0
*ALLOW_TEAM_NAME_COLOR 0
*ALLOW_TEAM_NAME_PLAYER 1
---
*SCORE_KILL 0
*SCORE_DIE 0
*SCORE_SUICIDE 0
*SCORE_WIN 1
*SCORE_DEATHZONE -1
---
*SP_SIZE_FACTOR -1
*SP_WALLS_LENTH 2800
*LIMIT_ROUNDS 30
*LIMIT_SCORE 5

== Past Tilts ==

'''[[Pilot Tilt|Pilot Tilt]] [[Tilt2|Tilt 2]]'''

Tilt Schedule

2008-02-25T18:26:56Z

Jonathan: or, looking at dates, we missed some edits

{{:TiltBlurb}}

== Tilt Schedule ==

'''Tilt 3 -> Sunday, December 9, 2007'''
----
'''Tilt 4 -> Sunday, January 14, 2008'''
----
'''Tilt 5 -> Sunday, February 11, 2008'''
----
'''Tilt 6 -> Sunday, March 11, 2008'''

Ladle-13/Results

2008-02-25T18:26:31Z

Jonathan: multiple diffs only show up as one at recent changes?

{{Ladle-12}}

Write a report on your games, exciting play, team-tactics... and also include any feedback on how to improve the tournament!

== Feedback for the Thirteenth Ladle ==

Remember to sign with <nowiki>~~~~</nowiki>

...

=== Results and recordings(with 0.2.8.2.1) on Z-Man's Ladle, too scared/lazy to create a table: ===

oops vs. CT: 1:2, [http://armagetron.kicks-ass.net/~manuel/armarecordings/armarecordings/ladle_13/quarter2.zip quarter2.aaarec]

x vs. TKR: 2:1, [http://armagetron.kicks-ass.net/~manuel/armarecordings/armarecordings/ladle_13/semi1.zip semi1.aarec]

x vs CT: 3:2, [http://armagetron.kicks-ass.net/~manuel/armarecordings/armarecordings/ladle_13/final2.zip final2.aarec]

[[User:Z-man|Z-Man]]

== Previous Winners ==

The [[Ladle-12/Results|Twelfth Tronic Ladle]] was won by [http://www.xclan.net.tf/ -¦x¦-] on Sunday 3rd of June 2007.

The [[Ladle-11/Results|Eleventh Tronic Ladle]] was won by Fogies with Wheelchairs on Sunday 6th May

The [[Ladle-10/Results|Tenth Tronic Ladle]] was won by [http://tui.owns.it TuI ~ Tronners Under the Influence] on Sunday 1st April

The [[Ladle-9/Results|Ninth Tronic Ladle]] was won by [[Team somethingsomething]] on Sunday 4th March

The [[Ladle-8/Results|Eighth Tronic Ladle]] was won by [http://tui.owns.it TuI ~ Tronners Under the Influence] on Sunday 4th February

The [[Ladle-7/Feedback|Seventh Tronic Ladle]] was won by Speeders on Sunday 7th January

The [[Ladle-6/Feedback|Sixth Tronic Ladle]] was won by [[Team somethingsomething]]

The [[Ladle-5/Feedback|Fifth Tronic Ladle]] was won by [[Tronic Monkeys]] in a closely fought final on 5th November 2006

The [[Ladle-4/Feedback|Fourth Tronic Ladle]] was won by proN00bz on 1st October 2006.

The First [[4 Team Fortress Tourney 1|4 Team Fortress Tournament (4TFT)]] was won by [http://crazy-tronners.com Crazy Tronners (CT)] on Sunday, September 17th, 2006

The [[Ladle-3/Feedback|Third Tronic Ladle]] was won by [[Ladle Winners|Anarchic Wanderers]] on 3rd September 2006.

The First [[International_Tron_World_Cup|Tron World Cup]] took place in July and August 2006 and was won by the United Kingdom. Full scores of the matches are available on the [http://lod.bigreddesign.co.uk/twc/ Official TWC Site]

The [[Ladle-2/Feedback|Second Tronic Ladle]] was won by [[Ladle Winners|Anarchic Wanderers]] on 29th August 2006.

The [[Ladle-1/Feedback|First Tronic Ladle]] was a fortress tournament with seven teams and was won by [[Ladle Winners|Shadow League]] on 1st July 2006.

The [[THE SPOON|Tronic Spoon]] was a fortress tournament of 87 players arranged into 8 and was won by [[Team somethingsomething]] in March 2006.
|}

{{:Ladle/Feedback}}

{{:Ladle/Results}}

Project Documentation

2008-02-25T18:25:53Z

Jonathan: ssppaamm

This is for all of our procedural and decision-making documentation. So when a large decision is made, or a controversial decision, you should find what amounts to a paper trail of the process of making the decision here. Expect numerous links to forum posts. :) Also, svn commit rules and so forth is here.

== [http://waterfall.davefancella.com Waterfall] ==

For developers with access: [http://buildbot.davefancella.com Protected Buildbot]

The waterfall is a report that tells us where the build works and where it doesn't. It's powered by buildbot, but the builds themselves are run on different machines than the report.

Here's how it works. Whenever someone does some work and commits it to the repository, the buildbot sees it and some time after the repository has been committed to, it will start up a build of the affected branch or the trunk, whatever is appropriate. All platforms will be built, and whoever's made commits will be tracked.

Here's how you use it:

If you're one of the developers that isn't here all the time, and you return to work on your pet project, look at the waterfall and hopefully you will see the latest code builds. If that's the case, fine, jump in and start hacking, and make sure when you're done and ready to go on another hiatus, the waterfall shows everything builds. This helps you to prevent the rest of the team from waiting through your hiatus to build again because they can't figure out wtf you did. :) If it's not the case that the waterfall shows all builds currently successful, you can go back through the history until you find one that did work (hopefully the one before the current one!) and work off of that.

If you're here all the time, and you break the build, we get to lombast you for it. Besides that, it gives you good access to build information for other platforms, therefore giving each of us a real shot at fixing problems on other platforms. For most platform problems we have, this should be enough to distribute the load of supporting all these platforms. Some platform problems will still require those developers who work on those platforms to deal with it, such as adding bison and ruby support to the windows build, to pick a recent example. You can also do what philippe can do if you find the current trunk won't build: go through the history to a build that does work and work from that. This is obviously not an acceptable solution if you happen to be responsible for the build being broken in the first place. :)

Information on how you can add a node to the compiler farm controlled by the buildbot is available on the [[Development Docs]] page.

== [[Government]] ==

The as yet unwritten government page.

== For Developers ==

If you need to add documentation to this page, please edit this page and provide the link. Periodically, Lucifer or another admin will go through and archive old pages by simply moving the link to an as yet unmade archive listing. So this page should contain current documentation.

AFL Awards

2008-02-25T18:25:29Z

Jonathan: spamspamspam?

{{AFLTbl}}

There are a few awards that can be won in the Armagetron Fortress League. Here is the canonical list and a description. Rules on qualifying for the awards and how to win them are either here or on linked pages.

== AFL Champions ==

This is the award given to the team that wins the tournament. It is indexed by season and year, such as Summer 2007 Champions, or Spring 2008 Champions. All a team has to do to win this award is not lose a single game during the playoffs.

== Most Valuable Player ==

There are two versions of this award. There is a per-game version and a seasonal version.

=== Game ===

The most valuable player for the game will be selected by the players who played the game. They will each vote on the participant they thought did the most to help their team win. Obviously he should be on the winning team, and the phrase "most valuable" assumes he helped the winning team. You can win the award by consistently working hard to help your team, or possibly by being the important catalyst that allowed your team to win at a critical moment (such as by holing the enemy's defense in the last round, winning the match and the game all at once).

Winning this award nominates you automatically for the seasonal MVP award.

=== Season ===

The MVP for the season will be selected by voting by all participants during the regular season. This award does not include the playoffs! It is generally expected that this award will be given before the playoffs even begin. Participants will vote on the MVP for the season, but they can only vote for people who were nominated by winning the MVP award for a game. How the votes will be tallied has yet to be determined.

PlayingGettingStarted

2008-02-25T18:25:12Z

Jonathan: many times spam?

Development Docs

2008-02-25T18:24:26Z

Jonathan: Reverted edits by Noc4tLaorb (Talk); changed back to last version by Your mom

{{Sections}} 

This is documentation for developers or for people who just want to hack on the code. It is not intended to replace the automatic API documentation generated by doxygen (we do have a doxyfile, right?), but is intended to supplement those documents with additional information that may not necessarily appear in the API docs. It is also not intended as a substitute for good commenting tactics. And finally, it is a place to put planning documentation (like the stuff Philippe writes), proposals, RFC-type material, and so forth. But not the roadmap, we use Sourceforge's tracker for that.

== Documentation ==

* [[Wiki Structuring Project]]
* [[Wiki Development Project]]

== Building the Game ==

Building Armagetron Advanced boils down to 4 basic steps. The steps themselves are each highly platform-dependent, but the four steps are the same everywhere. Each step differs further in whether or not you're building from a branch or the trunk, and each branch may differ. Finally, each step differs depending on if you're building a source release or from version control. Here we'll concern ourselves with building the trunk only. Releases should include their own build instructions.

# Install the development environment
# Satisfy dependencies
# Unpackage source/source checkout from version control
# Build a distribution

Platform-specific instructions (they should all follow the four step structure given, that's why it's there!):

* [[Windows Development]]
* Linux
* Mac OS X

todo: the linux and mac os x pages

== Other useful hacker documentation ==

* [[Windows Development System]]
* [[Working with SVN]]
* [[Cross-compiler]]
* [[Used Libraries]]
* [[Working with SVK]]
* [http://wrtlprnft.ath.cx/doxy/html/ Doxy]

== Stuff That's Current ==

* [[Config Item Purposes]]
* [[Debug Recording]]
* [[Error Handling]]
* [[List of nDescriptors]]
* [[Project Dependency Structure]]
* [[Adding a buildslave]]

== Stuff in SVN HEAD ==

* [[Embedded Web Server]]
* [[Map/Config Rotation]]
* [[Particle System]]
* [[Joda's Team Code]]
* [[New Sound Engine]]
* [[Spawn points]]
* [[Zones v2]]

* [[Cockpit Tutorial]] | [[Cockpits list]]
* [[vValue]]

== Data File Handling ==

* [[Config Files]]
* [[Resource System]]
* [[Statistical Collections Database]] (fancy way of saying "stat files")

== Source Control ==

* [[Bazaar]] and how we use it

== Stuff That's Real but doesn't fit above ==

* [[Experimental Map Features]]
* [[Send DTD on the resource repository through ssh]]—only of interest for people on the development team

== Wishlist, or Stuff that's planned ==

(Might not be planned, but this is it)

* [[Goals]]
* [[Scripted GUI Notes]]
* [[Authentication]]
* [http://forums.armagetronad.net/viewtopic.php?t=986 Reshaping the Arena]
* [http://forums.armagetronad.net/viewtopic.php?t=1742 Map format]

== History ==

This is stuff that's of historical significance to the project. It's very difficult to remember where you're going if you don't remember where you came from, right? This is technical stuff. Community history should have its own section.

* [[What Went Wrong in Armagetron]]

{{Sections}} 
{{Category:Development}}

Assemble

2008-02-25T18:24:24Z

Jonathan: 2x spam

boracroorboc
climonlaelv
{{:TiltBlurb}}
----
----
{| border="2" cellpadding="2" style="text-align:center"
! || EST || PST || GMT
|-
| '''Quarter Finals''' || 7:00pm || 4:00 pm || 12:00 am
|-
| '''Semi Finals''' || 8:00 pm || 5:00 pm || 1:00 am
|-
| '''Finals''' || 9:00 pm || 6:00 pm || 2:00 am
|-
|}
----

== Tilt Assemble ==
'''Sign Ups for Tilt 1 begin Sunday, September 30, 2007.

***Please Create a Team Name, It makes the bracketing a lot easier to follow.

* Team 1 is... -=XXX=- Porn Team - {Mist, Teatime, Tyler, Speed}
* Team 2 is...
----
* Team 3 is...
* Team 4 is...
----
* Team 5 is... <2nd> Second Place Team - PsYkO
* Team 6 is...
----
* Team 7 is...
* Team 8 is...

'''Sign Ups are closed at 6 PM EST time on the day of the Tilt'''
----
----
----

== Quarter Final Bouts ==

* SpeederS ServeR will host the battle between Team 1 and Team 2.
* High Rubber Tilt (Manta) will host the battle between Team 3 and Team 4.
* .Humility & honor'h will host the battle between Team 5 and Team 6.
* -=}ID< -=}Immortal Dynasty< will host the battle between Team 7 and Team 8.

== Semi Final Bouts ==

* SpeederS ServeR will host the battle for the top bracket.
* .Humility & honor'h server will host the battle for the bottom bracket.

== The Final Tilt ==

* The host server for the Final Tilt will rotate between SpeederS ServeR and .Humility & honor'h Server

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:00 PM EST || style="border-bottom:3px double" | 8:00 PM EST || style="border-bottom:3px double" | 9:00 PM EST
|-
| style="border-bottom:0px" | Team 1
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 2 || style="border-bottom:0px" | []
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Team 3 || style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@High Rubber Tilt (Manta)''' || style="border-left:0px" | 0-0 || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 4 || style="border-bottom:0px" | || style="border-bottom:0px" | []
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ SpeederS ServeR''' || style="border-left:0px" | 0-0
|-
| style="border-bottom:0px" | Team 5 || style="border-top:0px" | ||style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ .Humility & honor'h server ''' || style="border-left:0px" | 0-0|| style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 6 || style="border-bottom:0px" | []
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ .Humility & honor'h server''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Team 7 || style="border-top:0px" | []
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ -=}ID< -=}Immortal Dynasty<''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 8
|}

'''TILT 3 WINNER -=xXx=- Porn Team !'''

== Servers and Server Settings ==

'''I have successfully averaged the servers to make the fairest server possible. A server that can be adapted to easily by those who favor the SP/ID settings or those who favor the iZm/H'h settings. Make sure when you do test these settings that there is no deathzone!'''

*BUG_COLOR_OVERFLOW 1

*CAMERA_SERVER_CUSTOM_TURN_SPEED_180 4
*CYCLE_ACCEL 41
*CYCLE_BRAKE 155
*CYCLE_BRAKE_DEPLETE .4
*CYCLE_BRAKE_REFILL 1
*CYCLE_DELAY 0.008
*CYCLE_DELAY_TIMEBASED 0
*CYCLE_RUBBER_MINDISTANCE_UNPREPARED 0.005
*CYCLE_RUBBER_MINADJUST 0.08
*CYCLE_RUBBER_MINDISTANCE_LEGACY 0
*CYCLE_RUBBER_MINDISTANCE_RESERVOIR 0.005
*CYCLE_RUBBER_MINDISTANCE_RATIO 9.99868e-05
*CYCLE_RUBBER_TIME 1
*CYCLE_RUBBER_TIMEBASED 1
*CYCLE_SOUND_SPEED 30
*CYCLE_TURN_SPEED_FACTOR 0.98
*CYCLE_WALLS_STAY_UP_DELAY 2
*CYCLE_SPEED 35
*WALLS_LENGTH 2000
*REAL_ARENA_SIZE_FACTOR 1
*VOTING_TIMEOUT 60
*VOTING_TIMEOUT_PER_VOTER 15
*WIN_ZONE_MIN_ROUND_TIME 9000
---
*TEAMS_MAX 2
*TEAMS_MIN 2
*AUTO_TEAM 1
*TEAM_MAX_PLAYERS 4
*TEAM_MIN_PLAYERS 1
*TEAM_BALANCE_WITH_AIS 0
*ALLOW_TEAM_NAME_COLOR 0
*ALLOW_TEAM_NAME_PLAYER 1
---
*SCORE_KILL 0
*SCORE_DIE 0
*SCORE_SUICIDE 0
*SCORE_WIN 1
*SCORE_DEATHZONE -1
---
*SP_SIZE_FACTOR -1
*SP_WALLS_LENTH 2800
*LIMIT_ROUNDS 30
*LIMIT_SCORE 5

== Past Tilts ==

'''[[Pilot Tilt|Pilot Tilt]] [[Tilt2|Tilt 2]]'''

AFL Rules

2008-02-25T18:24:09Z

Jonathan: 2x spam

erc4tdronboc
{{AFLTbl}}

For judges, and players who'd like to know how these rules will be used, we have a separate document for [[AFL_Rule_Interpretation|interpreting the rules]].

Also, [[Game Procedure]] tells players how to play an actual game.

== Teams ==

# Teams need a team name, and a team name-tag which will be inserted in the name of the player during games.
# Teams can consist of up to but not exceeding ten members.
# Teams are responsible for their own organization. Lack of organization can well end up in forfeiture of a game, so make sure that you stay on point and organized.
# Every team will make a roster, which will not change over the course of the season.
# Teams can drop players from their teams at any time during the regular season. Teams must notify a judge of drops before the next game.
# To add a new player to a team, the team must get approval of a judge.
# After the playoffs begin, no new players can be added, and a drop requires league approval (approval of a judge).
# Teams will consist of a team captain and up to nine other members
# Teams can contact the league for whatever reason through the #afl or #armagetron channels on irc.freenode.net or on the armagetron forums at forums.armagetron.net. Due to the potential for time-wasting conflict, we will not accept references to something he or she said on this or that server or so and so's forum for the purposes of mediation. The AFL pages on wiki.armagetronad.net will keep current contact information for all league contacts.

== Servers ==

# The behavior of all servers participating in the AFL will be exactly the same, and settings will be provided by the league to the server admins.
# Servers will use rules approved by the league. We'd like to allow cycle_rubber modifications within reason to correct for lag, but due to the widespread notion that rubber has nothing to do with lag, we can't make this allowance. Help change the mistaken widespread notion!
# Teams must choose a server to be their "home server." We recommend teams choose a server where their team has a low ping as a whole and with an administrator that is friendly to the team. Ideally, teams would provide their own home servers, but due to the bandwidth and performance requirements, the league is attempting to provide servers for teams to choose from.

== Games ==

# In games, teams can have a maximum of five players on the grid. Teams that show up with less than 5 will be expected to play with what they bring, or forfeit. Teams that show up with more than 5 will be allowed to use their extras as alternates and make substitutions. However, at no point can more than 5 teammates appear in the round. If this should happen, the extra player should kill himself within seconds of the round starting, or else the round will be declared invalid, possibly the match declared invalid, or some other really nasty penalty will be given. The league's approved settings should reduce/eliminate the risk of a team playing over 5 players accidentally, but it cannot eliminate the risk of a team starting a round with only 4. Tough luck.
# Each game will have a home team and a visiting team, as in professional sports.
# A game will consist of three matches played at the home team's declared server.
# The winner of the game is the first team to reach two match wins. If this should be the first two matches, playing the third match is optional, but allowed if time permits.
# For a match to be considered as being conducted as a league match, there must be a recording made with either the latest release of 0.2.8 or the latest 0.3.x release (currently 0.3.0). While any version is allowed for play, a recording made from the trunk will not be considered as having met this requirement. We are studying whether or not a server-side recording is to be accepted.

== Season ==

# Matches will generally be played on Tuesdays UTC, and Sundays will be used as an alternative day in case of complications with Tuesday, but we can't guarantee the matches will always be scheduled on those days. Check your schedule.
# Over the course of the season, each team will play each other twice, one game played at their declared home server and one game played at their opponent's declared home server.
# Teams will be ranked during the season according to their win-loss record. Any ties brought about by this system will be resolved by head to head results.
# The final rankings of the season will be used to seed teams in postseason play.

== PostSeason (Your chance to win a chip!) ==

# To qualify for the post-season, a team must consist of at least 60% of the roster that existed at the time of their second game in the regular season.
# The postseason will consist of a series of one-off elimination games in a bracket-tournament setting.
# Teams will be seeded according to the final season rankings.
# Teams will play at the declared home server of the higher seeded team or an available quality neutral league server.
# Teams will be eliminated in every round of the tournament, leading up to a game between two final teams, which will be the championship game, and the winner of this game will be declared champion. Should the playoffs contain 8 teams or more, the top 4 positions will be determined, otherwise only the championship game will be played.

== Rewards ==

# The prize for winning the championship game will be some t-shirts with a to-be-determined graphic by DrJoeTron. Note: this does not apply the the Summer 07 season.

== Sportsmanship ==

# Don't be a douche. We'll look at the recordings, and we'll know, and you'll know, and we'll tell your mother.
# Also, some really bad sportsmanship can entail severe penalties, like forfeiture of the game, suspension of a player, and even suspension of a team.
# Bad sportsmanship can be considered any of the following:
#* Insulting the opposing team
#* Declaring the game to be a bad game due to the fact that your team lost. While it may be true that it was a bad game, it's still bad sportsmanship to raise a fuss about it. If you truly believe the game was bad, speak to a judge about it to resolve the problem.
#* Core dumping a player's own teammates
#* Refusing to play competitively
#* Quitting a game because the player's team is losing.
#* Anything else your PE teacher told you was bad sportsmanship.
# Penalties for bad sportsmanship will be assessed based on degree of infraction, rate of infractions, and so forth. Basically, you might get away with something once when the judges sympathize with you, but don't expect it to happen a lot. The point is to have fun, and you should behave in a manner that is conducive to everybody having fun, not just you.

AFL Servers

2008-02-25T18:24:06Z

Jonathan: Reverted edits by ChiboRelra (Talk); changed back to last version by Jonathan

{{AFLTbl}}

Here is a list of servers available for the league. If you'd like to contribute a server, please add yourself to the list.

== Servers Available ==

{|- style="width: 100%;" border="1" cellpadding="5" cellspacing="0"
|- style=" background: lightgray;"
| '''Server''' || '''Location''' || '''Administrator'''
|-
| Swamplords AFL Server || Austin, TX || [[User:Lucifer|Lucifer]]
|-
| Z-Man's AFL Server (custom connect to l23.thp.uni-koeln.de:4540) || Cologne, Germany || [[User:Z-man|Z-Man]]
|-
| Wild West =AFL Fortress=||Texas||Manta & [[User:Durka|Durka]]
|-
| Fallin' Angels AFL Server || Some fancy place || '''Spidey, Ant, Wizzee'''
|-
| Fortress Test Server/Ladle Cafe (home server for ¦x¦ AFL team)|| Germany || Rain's Server, RA for AFL by Rico
|-
| Crazy Tronners AFL || Germany || CT's server (PTA or Ed)
|}

== For Administrators ==

To facilitate administration, we ask that you share with team captains who wish to declare your server as their home server the admin password for your server. Obviously you should change the password to the one you intend to share before the game, and change it back to your private password after the game. However, we also prefer servers to be setup within our own network of game servers, thus they will not show in the master server list. It would also be nice if you make your servers available 24/7 like you do your regular server, so that teams can practice. Ideally, the teams who call your server home are teams that consist mostly of players that regularly play your server and already have established good relations with you.

More information on how we'd like servers to be administered for the league will appear here as it becomes available, however you do not *have* to provide a separate server for the competition. To help out, all you really need to do is make sure the server you are contributing will run the appropriate settings for the games when they are scheduled, and that it will be available for the games it is scheduled for.

Ladle/Guidelines

2008-02-25T18:24:05Z

Jonathan: Reverted edits by RoaceLbasa (Talk); changed back to last version by Your mom

{{:Ladle/Blurb}}

== Stages ==

=== Stage 1 ===
'''Team-Captains visit the [[Ladle/Challenge Board]] to establish provisional playoffs.'''

Again, this is only provisional. Only the Team-Captain is authorised to place your team on the board. S/He may alter this whenever they wish, and this may mean some jostling since placement not only determines who your team goes up against in the first and subsequent rounds, but also which servers you will be playing in. Inform your Team-Captain of your preferences, your favourite servers, and consider ping, stability, and general conditions. '''The cut off for the provisional placement of teams is 00.00am GMT on the day of the event.''' This will allow time for admin to copy out the provisional bracket list, and allows all players to know who they are expected to play and where well before time. The most important thing for players to do is '''elect a Team-Captain who you can trust''', who listens to everyone in the team, who is capable of communicating with other team-captains, and can follow the procedure to the letter on the night. You may also wish to elect a stand-in in-case the Team-Captain can't make it.

=== Stage 2 ===
'''Team-Captains register at [[IRC Channel|IRC Armagetron]] at 7pm gmt, then teams play the best of 3 matches.'''

Before the first round, all Team-Captains should familiarise themselves with IRC using one of the web interfaces such as [http://www.armagetron.nixda.net/cgi-bin/irc.cgi?adv=1 '''Joda's web interface'''] or [http://www.irc4u.com/?irc_server=irc.freenode.org%3A6667&irc_channel=%23armagetron%2C+%23arma-ladle '''Wrtlprnft's interface'''] or [http://durdur.freehostia.com/irc/ladle.html '''Durka's IRC Applet''']. Useful instructions include '''/nick <your name>''' and '''/join #arma-ladle'''. Last minute alterations to brackets should be decided upon, and once confirmed, all players can view the brackets on the wiki at the Challenge Board. Team-Captains return to their teams and confirm who they are playing and where.

The Final is at 9pm GMT, Semi's at 8.15pm GMT, Quarter's at 7.30pm GMT, and previous rounds every 45mins for as many rounds as required. The Challenge Board has the details of who and where players should be assembled, in case there are problems with IRC chatrooms, or players need to take a leak, etc. Do not listen to random people appearing and changing plans suddenly. Stick to the script -- it has taken a month of preparation to write it...

Administration will record results on the brackets as they come in. '''The brackets should be followed''', unless Team-Captains have legitimate reason to alter the course of progress. The only thing to be decided, if there is any question, is the server. When approaching the final, teams will rightly wish to play on servers which favour them. This must ultimately be resolved by the Team-Captains involved.

On the games on Z-Man's Ladle Frotress, team management is available; designated team captains can choose to lock their teams themselves so no random people can join, can then invite their players without hoping the admin does an ALLOW_TEAM_CHANGE_PLAYER command in time, and substitute players can already participate in team chat. [[Authentication for Players#Benefits|More on that here]].

=== Stage 3 ===
'''Winners are celebrated, participants are congratulated, and game-analysis, results and feedback are welcomed!'''

Hurrah! Well done! Feedback is welcome to improve the system for the next time. Reports on game play, video's, etc, also invests more value in the game.

== Guidelines ==

The following guidelines for all players may prove useful:
*Only Team-captains should alter the provisional play-offs in the Challenge Room. A spot switching has to be in agreement between both teams interested.
*During the event, do not listen to anyone external to your team; rely on your Team-captain for information as to who you are playing and where.
*Regarding ping, make sure your team-captain is aware of your server preference when s/he enters your team in the Challenge Board.
*Regarding imbalanced teams... anything less than a full of team of 8 is your problem... an obliging opponent may reduce their numbers if they wish...
*If opponents don't turn up on time, they forfeit, unless again a team wishes to delay the start... though this causes problems for subsequent timing...
*Regarding new players turning up: server admins can make their server private, lock it once all players are in, or kick new players immediately

If you wish to discuss any of the stages, add to the guidelines or contribute to the rules, please click on the discussion tab above.

{{:Ladle/Blurb}}

[[Category:Events]]

High Rubber Tilt

2008-02-25T18:24:03Z

Jonathan: Reverted edits by BocdrOnrac (Talk); changed back to last version by Rain

{{:TiltBlurb}}

== Objective ==

Short and simple: To give players an opportunity to play and/or organize a tournament that strikes their fancy. Not all players are mystified by zones.

== Blue Prints ==

* Each team must come to the [[Assemble|Assemble]] page, edit their name into the appropriate team. If your clan or team is not registered, you need to do so before you edit in your name. If you are the team captain, make sure you write (Team Captain) after your name.
* You can sign up as many people as you want for your team, there is no limit. You play 8v8 in the ladle, but due to lengthy circumstances, each team will be only allowed to participate 4 players to play in each match. If the other team does not have 4 players, you can still play. It is infinitely easier to win a math in high rubber when you are against 1 v 4 odds than it is in fortress.
* To clarify for Kryalot (Very good name to pick), you must sign up AT LEAST 4 players. But if 4 players do not show, then you may play 4v3, 4v2, etc.
* To further clarify for Kryalot, PsYkO organizes the tournament.
* '''NEW SCORING''' - For each kill, the individual will get 0 points (previously 1), for each team win, the team will get 1 point (previously 1). A team will win a match when they gather 5 points (5 round wins)
* There are many different ways to trap someone in high rubber, and some aren't viewed very highly among the high rubber "elders." These include camping, cornering, sealing, speeding, or wall-whoring. However, in this particular tournament, you are allowed to do all of them. Just like in fortress you can hole or take the win zone. Nevertheless, the worst thing to do is to camp, if you do camp expect some foul words to come your way on the Back Talk page.

'''New Rules/Clarifications'''

*Instant Kills - Instant kills can be decided to count/not count if the players decide on it. The decision is decided by 50%+ of the vote. Listed are the pros and cons:

Not counting instant kills

* There is no difficulty keeping track of the score
* Prevents people from trying to gain an advantage by raising their ping and speeding
* Prevents people from having to react to people trying to gain that advantage (or whom just have high ping)

For counting instant kills

* It's easier to not keep track of if some kills didn't count.

Counting Rounds - The scoring will be the same, Each kill gets their team 1 point, each win gets their team 1 point.

Team Restrictions - A team must signup 4 members. During the tournament, teams must compete with equal numbers (2v2 or 3v3 etc). If needed, you can use people who weren't signed up in time, or are signed up on a different team. No solo teams and team signups are under the control of the organizer.

Spectators -
The only people allowed to be in the game are:
All of the players on the team.
The admin of the game, and the admin of the tournament (PsYkO)
A team representative, if the team wins their match, and plays the team of the match being held. Say Team 1 wins, and they play the winner of team 3 and 4 in the semi finals. The captain of team 1 can join the battle between team 3 and team 4.

[[Category:Tilt]]

Installing the Game

2008-02-20T17:53:20Z

Jonathan: Reverted edits by RaczeLacel (Talk); changed back to last version by Rain

{{Sections}} 

Armagetron Advanced is available for a number of different operating systems, and sources are also available if needed.

== Where to Download Armagetron Advanced ==

The very latest installation packages for Armagetron can be found under the DOWNLOADS section of the [http://www.armagetronad.net/ Main Project Website]. The 'Automatic Download Assistance' section on this page should point you to the correct package for your Operating System.

Dedicated Server packages are also available from the aforementioned page.

== Installing the Game ==

=== for Windows ===

Please see the [[Windows Installation]] page.

=== for Gentoo Linux ===

Please see the [[Gentoo Portage Overlay]] page.

=== for Mac OS X ===

Please see the [[Mac OS X Installation]] page.

== Setting up a Server ==

Please see the [[Server Administration]] section.

Back Talk

2008-02-20T14:53:40Z

Jonathan: Reverted edits by BorozElrel (Talk); changed back to last version by Rain

{{:TiltBlurb}}

= Tilt Back Talk =

;PsYkO
:Please write pretty much anything you want below either about your experience of the event or how we can make it better for next time. Any information or ideas that you have are CRUCIAL for a successful run of any kind of tournament.

;Oblivion
: err.. nobody knew about this tilt :P

== Previous Back Talks ==

[[Pilot_Back_Talk|Pilot Back Talk]] [[Back_Talk_1|Tilt Back Talk 1]] [[Back_Talk_2|Tilt Back Talk 2]]

Competition Hub

2008-02-20T14:53:38Z

Jonathan: Reverted edits by SiterOrcac (Talk); changed back to last version by 2020

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.
 
{|- border="1" cellpadding="5" cellspacing="0"
| style="background:lightgray; width: 100%" | '''Current Competitions'''
| rowspan="4" style="vertical-align: top" | <calendar />
|-
{{:Ladle/Blurb}}
----
{{:AFL_Blurb}}
----
{{:AVE Fort/Blurb}}
----
{{:TSTBlurb}}
----
{{:TiltBlurb}}
----
{{:IFC_Blurb}}

----

|-
| style="background:lightgray" | '''Suspended/Delayed Tournaments'''
|-
|
[[4 Team Fortress Tourney 2|4 Team Fortress Tournament #2]] - Possibly never going to take place
----
{{:Kings_of_the_Grid_Blurb}}
|-
| style="background:lightgray" colspan="2" | '''Earlier Competitions...'''
|-
| colspan="2" |

The [[Ladle-13/Results|Thirteenth Tronic Ladle]] was won by [http://www.xclan.armagetron.co.uk -¦x¦-] on Sunday 3rd February 2008

The [[Ladle-12/Results|Twelfth Tronic Ladle]] was won by [http://www.xclan.armagetron.co.uk -¦x¦-] on Sunday 3rd June 2007

The [[Ladle-11/Results|Eleventh Tronic Ladle]] was won by Fogies with Wheelchairs on Sunday 6th May 2007

IRC Channel

2008-02-20T14:53:35Z

Jonathan: Reverted edits by PasboCpasc (Talk); changed back to last version by Your mom

We have an [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC (click here if you don't know what IRC is)] channel on freenode that gets some traffic. There's a fair amount of development talk there, but there's plenty more to be had.

== Joining the IRC Channel ==

Pick your favorite [http://en.wikipedia.org/wiki/List_of_IRC_clients IRC client] and connect to freenode. You can connect to the server irc.freenode.net, then join #armagetron using the user interface of your IRC client or the command "/join #armagetron"

Alternatively use an easy web interface such as [http://www.armagetron.nixda.net/cgi-bin/irc.cgi?adv=1 Joda's web interface], [http://www.irc4u.com/?irc_server=irc.freenode.org%3A6667&irc_channel=%23armagetron%2C+%23arma-ladle the irc4u interface], [http://durdur.freehostia.com/irc/arma-irc.html Durka's IRC Web Applet], [http://durdur.freehostia.com/irc/arma.html Durka's CGI:IRC Chat] or [http://java.freenode.net/index.php?nick=Program&channel=armagetron this Java Applet run by Freenode].

Once there, you'll find plenty to talk about, I'm sure. There is one thing you should not do, however: enter the channel, say "hi!", maybe ask a question, and leave after a minute of getting no response. If there is no discussion currently going on, everyone has their chat windows in the background and simply won't notice you in time. Have some patience.

== The Armabot ==

There's a bot there that gives some additional features. For a list of stuff, type:

#list

Then, for example for the Weather module, do:

#list Weather

This combination will register you as a user of the bot and give you access to more features, such as a welcome message (herald):

<nowiki>/msg armabot register <username> <password></nowiki>

After registering you need to identify to armabot using

<nowiki>/msg armabot identify <username> <password></nowiki>

You can leave a note for another user like this:

#message Lucifer_arma You're a prick

When the other user comes into the channel and says something armabot will automatically deliver the notes as private messages. To see which users have notes waiting to be delivered use

#notes

You can also get RSS feeds, math calculations and conversions, coin-flipping, and other neat things. It's intended that we'll provide a module to query servers and see who's playing where, but that's not yet implemented. You can get a list of servers and the number of users playing there with the command #armaservers (somehow unreliable, but usually it works) or get help on a console command in arma using #armaconfig.

So have fun with it!

Outcome

2008-02-20T14:53:34Z

Jonathan: Reverted edits by EltraCgetb (Talk); changed back to last version by Jonathan

{{:TiltBlurb}}
== Tilt 2 Outcome ==
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:00 PM EST || style="border-bottom:3px double" | 8:00 PM EST || style="border-bottom:3px double" | 9:00 PM EST
|-
| style="border-bottom:0px" | Diztruktive ßeauty
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" | Forfeit
|-
| style="border-top:0px" | HeLL'z ReBeLs || style="border-bottom:0px" | [HeLL'z ReBeLs]
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | <2nd> || style="border-top:0px" | [<2nd>]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@High Rubber Tilt (Manta)''' || style="border-left:0px" | Forfeit || style="border-left:0px" | 2-0
|-
| style="border-top:0px" | Assasinators || style="border-bottom:0px" | || style="border-bottom:0px" | ['''<2nd>''']
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ SpeederS ServeR''' || style="border-left:0px" | 2-1
|-
| style="border-bottom:0px" | Team 5 || style="border-top:0px" | ||style="border-top:0px" | [xD]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ .Humility & honor'h server ''' || style="border-left:0px" | 0-0|| style="border-left:0px" | 2-1
|-
| style="border-top:0px" | xD || style="border-bottom:0px" | [xD]
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ .Humility & honor'h server''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | MexicanDawgFighters || style="border-top:0px" | [MexicanDawgFighters]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ -=}ID< -=}Immortal Dynasty<''' || style="border-left:0px" | 2-0
|-
| style="border-top:0px" | Destroyers
|}

'''Winner is Second Place Team'''

== Tilt 1 Outcome ==

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:00 PM EST || style="border-bottom:3px double" | 8:00 PM EST || style="border-bottom:3px double" | 9:00 PM EST
|-
| style="border-bottom:0px" | Dream's Team
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" | 2-1
|-
| style="border-top:0px" | Obli's Team || style="border-bottom:0px" | [Obli's Team]
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Relentless Honor || style="border-top:0px" | [Relentless Honor]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@High Rubber Tilt (Manta)''' || style="border-left:0px" | 0-0 || style="border-left:0px" | 2-0
|-
| style="border-top:0px" | BYE || style="border-bottom:0px" | || style="border-bottom:0px" | ['''Obli's Team''']
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ SpeederS ServeR''' || style="border-left:0px" | 2-0
|-
| style="border-bottom:0px" | Second Place Team || style="border-top:0px" | ||style="border-top:0px" | [Second Place Team]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ .Humility & honor'h server ''' || style="border-left:0px" | 2-0 || style="border-left:0px" | 2-1
|-
| style="border-top:0px" | Jellyfish Revenge || style="border-bottom:0px" | [Second Place Team]
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ .Humility & honor'h server''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Renegades || style="border-top:0px" | [Renegades]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ -=}ID< -=}Immortal Dynasty<''' || style="border-left:0px" | 2-1
|-
| style="border-top:0px" | Team 8
|}

''' Winner is Obli's Team '''

== Pilot Tilt Outcome ==

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:00 PM EST || style="border-bottom:3px double" | 8:00 PM EST || style="border-bottom:3px double" | 9:00 PM EST
|-
| style="border-bottom:0px" | [http://speederclan.5.forumer.com ~*SP*~ Elders]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | Team 2 || style="border-bottom:0px" | [http://speederclan.5.forumer.com ~*SP*~ Elders]
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ SpeederS ServeR ''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | Buc Team || style="border-top:0px" | [ Team Unoriginal Name ]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@Server.iZm''' || style="border-left:0px" | Forfeit || style="border-left:0px" | 2-0
|-
| style="border-top:0px" | [Team Unoriginal Name] || style="border-bottom:0px" | || style="border-bottom:0px" | [http://speederclan.5.forumer.com ~*SP*~ Elders]
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ SpeederS ServeR''' || style="border-left:0px" | 0-0
|-
| style="border-bottom:0px" | [Legitimate Skills] || style="border-top:0px" | ||style="border-top:0px" | [ ]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | ''' @ .Humility & honor'h server ''' || style="border-left:0px" | 0-2 || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | [http://hnhclan.30.forumer.com .Humility & Honor.]|| style="border-bottom:0px" | [http://hnhclan.30.forumer.com .Humility & Honor.]
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ .Humility & honor'h server''' || style="border-left:0px" |
|-
| style="border-bottom:0px" | [http://speederclan.5.forumer.com ~*SP*~ Newbies] || style="border-top:0px" | [http://speederclan.5.forumer.com ~*SP*~ Newbies]
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ -=}ID< -=}Immortal Dynasty<''' || style="border-left:0px" | 0-0
|-
| style="border-top:0px" | [Solo]
|}

'''Winner: No winner due to Server issues. Honarable mention to H'h and ~*SP*~ Elders for winning their matches.

Servers

2008-02-20T14:53:32Z

Jonathan: Reverted edits by DardrOncar (Talk); changed back to last version by PasroLrolc

copasac
borelchierbo
This is a list of current servers, in alphabetical order. To see a list of old servers that no longer exist but were interesting enough to write about, visit the page about [[Old Servers]].

== [http://crazy-tronners.com/portal.php Crazy Tronners Wild Servers] ==

Nice fortress servers with completly different [http://crazy-tronners.com/ladders_new.php ladder system]. Over 90 various maps are rotating in 12 rounds at [http://crazy-tronners.com/servers.php?map=wild Crazy Tronners Wild Fortress] (CTWF). [http://crazy-tronners.com/servers.php?map=cat CTWCatfight] (1v1) and [http://crazy-tronners.com/servers.php?map=dog CTWDogfight] (2v2) are fortresses with custom maps (fake walls, speed hells, chico's rides, race, octagons and many many more) greate for challanges. All placed in Europe.

== ~|DarkSyndicate|~ Arena ==

High rubber Settings

The right place to test your skills. Fast server with high rubber settings. The 100mbit connection did the rest to make the server that popular. Specifications:

*server running armagetron 0.2.8.2
*standard arena
*walls last until you die
*explosions on a wall make gaps to get through
*no winzone activated
*server admins are ~|DS|~segv

== Flynn's Arcade - .:Avl:. Clan Server==

Flynn's Arcade aims to be similar to the actual movie game grid, with emphasis on maneuvering skill, not just speed and rubber (although high speeds are quite possible). Settings include relatively low rubber, moderate speed and acceleration, infinite walls, and a turbo instead of brakes on one server, and good brakes and slow speed on the other server. Brake server is sometimes used for clan training. Servers are run by .:Avl:.C10ud:. (formerly ianthetechie). Homepage is http://flynnsarcade.net/

== [[GP-Clan server]] ==

Low rubber, not infinite, rim makes speed.
Fun to test your LR skills.

== [[Ion]] ==

Ion is a test server hosted by zero. It allows players to test out new server settings and maps without having to use their own server. For more information, please contact [[User:zero]].

== [[MicroBusCity]] ==

This server has long walls and high speeds. There are moderate brakes here. This server is a standard gladiatorial-style arena where you are expected to kill or be killed. Server settings change at the end of every month, but MBC is always winzone-friendly.

== Norms Place ==

A classic style server with friendly people. This server combines the best aspects of classic and fast play minus any bugs or much hated lag. To be among the best here you need skill and a range of strategies; however all are welcome whatever your ability.
For server stats, FAQ and links visit [http://normsplace.de]

== Race Server ==

This is the first server of its kind, but the setup is simple: You all start at about the same position of a long narrow alley with many obstacles in it. Whoever arrives first at the other end and hits the winzone there gets declared the winner — if anyone makes it there, that is. Many different obstacles that are tricky to escape, small killzones, sticky rim walls, a passage where the alley gets even narrower or splits, killzone- only rounds, the ability to lay mines to get rid of your followers and the turbo make this server an experience you don't want to miss!

== [[RaceToWinzone]] ==

You drive on the server a genuine running — head at head — with a speed from 0 to > 700. Obstacles will try you there to stop. The level are labyrinth-well-behaved however without erring courses. One must also never the way seeks to separate to simply only loose-race. There are different types of level. Times an obstacle run, times goes it through narrow tunnels, times must you try between the barks to drive. Adrenalin impacts are guaranteed.

== Race From Death Zone ==

Similar to any race server, get to the end first, and hit the win zone. Just here, if you slow down, or make a wrong turn, you smash into the death zone, that is quickly expanding behind you.
With an arrange of different maps and brake to boost, it is a very fun server.
To see server stats and maps, visit [http://www.freewebs.com/racefromdeathzone Race From Death Zone Website]
This server is run by Aang.

== :(SX):_OZZY ==

Small grid, high speed. It is also a standard gladiatorial-style arena. This server is run by Swampy.

== [[Swampland]] ==

This server offers shorter walls and moderately high wall acceleration. It is also a standard gladiatorial-style arena. This server is run by Swampy.

== The Lobster Cage and The Lobster Tub==

The Lobster Cage consists of a Medium/Small Grid, Endless Walls, Moderate Speeds, with Moderate Acceleration. Rubber Is slightly above average. The Lobster Tub is a combination of the server settings of In Limbo, Shrunkland, and The Lobster Cage to make one pretty swanky server. Both have a single use turbo instead of a brake. They also are the first official Armagetron servers to have their own Public Teamspeak Server.

These servers are ran by Dr Joe Tron(Lobster Cage/Tub) and Gomes(Teamspeak Server)

== [[~"XzL.Clan Server]] ==

This server is similar to MicroBusCity. It has high speed, non-infinite walls, and the scoring is based upon core dumps making this server more challenging. This server also has a quickly expanding deathzone that loves to eat your lightcycle.

== | Nano's Playground | ==

A very unique server with several different settings configs. Currently this includes classic nano (default), snake hunt mode (fighting style gameplay with very short tails), brake boost chico, trapdoor madness (very high wallshrink), tail madness (very high NEGATIVE wallshrink), and Durka Durka Nano Land (a midget version of DDL)

== Wild West Servers: ==
''Sumo, Team Sumo, Sumo Treasure Island, Fortress, Fortress Shootout, Wild Fortress
Capture the Flag, Capture the Flag Shooting, CTF Labryth, Multi-Mode, Cockpit''

A set of low rubber servers to meet many style preferences. These servers are hosted in Atlanta, Georgia on Dual AMD MP 2800+ CPUs. For server stats, who's playing, and forums visit http://www.lagtest.net

Ladle-11/Results

2008-02-20T14:53:29Z

Jonathan: 2x spam

taelmonc4
{{Ladle-11}}

Write a report on your games, exciting play, team-tactics... and also include any feedback on how to improve the tournament!

== Feedback for the Eleventh Ladle ==

;Rico

:First 2 rounds went well, Â¦xÂ¦ played quite well together as a team and we defeated TM in round 1, where 2020 had to go find some other players to help out at the last minute. That ended up 2-0, but then when it came to the second round we only had 6 players, and DS/oops had 8. 2020 and wrtlprnft helped us out, big thanks to them. We got through that, also 2-0.

:We then had to wait about 6 hours for the final, due to the TuI vs Mr Men match being delayed. When the Mr Men all arrived, they had 7 players, so wrtlprnft left and 2020 continued to help us out. During all this time as the server wasnt locked, random people kept joining and screwing up the teams, meaning the final got delayed even moreso. We went down 1-0 in the first match which was really close, like 100-94. Similar story in match 2, however subz' ping started going crazy due to other downloads through his router - thats why he left, as theres no point playing when you cant do anything with 600 ping. Being one-man down, we then lost the 2nd match to a quite similar score.

:It was here that some of things began to piss me off. As it was best of 5, there was one person playing as "Mr x", saying some things like, don't worry only one more match to go before we get out of here, in a really arrogant tone which pissed me off, as if to imply we wouldnt even stand a chance of winning one match (we didnt, but thats not the point). Then, considering who the players were (I found out after) I was even more shocked. Probably a team of the best euro players there is, and I was holed in practically every round. Now Ive got no problem with holing, but when its about 4 vs me and you just torpedo its fucking ridiculous. Considering the skill level of the players were against me they shouldnt have even needed to hole.

:I dont feel like we were defeated in the final, more just holed the fuck out of to try get everything over as quickly as possible.

;Lackadaisical

:We started as team 7, and tui was team 8 so we expected to start playing in the quarterfinals like the challengeboard said, but for one reason or another Durka had decided to start in semi's, which made our team and a big part of tui show up 45 minutes too early. This led to a lot of irritation and confusion (like random people shouting 'this match it starts!' even though we already waited 30 minutes and we knew durka would show up in another 15). Ofcourse durka didn't officially know who we were but he could've posted something on the forums, it would've saved us alot of misery. I'm just glad our team showed enough patience, I can't image the hell that would've broken loose if we would've forced tui to play at the assigned time.

:About Mr. x's comments: It's not something I would do, but it's 'just' trashtalk, during the heat of the battle people do it to stir the enemy up, get them out of focus. I guess you could say it's part of the game, plus you can always silence trashtalkers. That's what a big part of our team did. And I don't really see a big difference between what Mr. x said and what some people from |x| said to Omega when he showed up after the finals. Or maybe implying someone sucks is worse than just plainly saying it.

:I'm not sure what to say about the whole holing thing that hasn't been said already, but even some of the 'best'players agree that there are defs that are pretty much impossible to break.

;PsYkO

:Hi.

:Well, it was a fun ladle. Got a headache for about the 4th straight ladle due to playing TuI (You should feel lucky that you played against us then TuI, Rico) TuI played remarkedly well, probably the best they have ever played imo while I think we were a bit too confident. 1st match was a blow out, 2nd match was like 90-82 or something in our favor and TuI came back to win it 104-100 . And then the 3rd match was like 100-80 I think. I was defense and let me tell you, even in an American server, and I am an American I felt slides nearly once going around the zone (and I go around fast) which would kill me everytime if I did not expect it. I got penetrated about 3 to 4 times because I froze up for a second which left a gap leading to a victory for them. Knowing this, I can't imagine what all the euro players had to deal with. orange, red, and gold were fantastic sweepers. I normally hate sweepers but they made my job easy ;). The finals were a bit lopsided. Just knowing a few we had a damn good team going from playing in crappy conditions to semi-crappy conditions which will make you play better. (If you run long enough with 10 pound weights on your ankles, when you take them off your legs will run faster)

:Every ladle it seems there are complaints. Winzone this, holing that, trash talk blah. You don't have to see the winners as the best team, but you should see them as the team that played the best, this time. And then of course make it your duty to own them in the next ladle =D

;Rico

:Lack - I didnt see anything said to omega, who was it by? This was plainly because by the end of match 2 there were only about 5 people I hadnt silenced after getting pissed with Mr X and a number of others, including at least two members of my own team I think.

:Grats anyway, hopefully next ladle all the server will be private so theres no problems with random people joining. Maybe we could also start up a discussion about some new settings to rework some of the parts of the game which make people unhappy/pissed off, etc etc etc.

:Oh, and a big thanks to Legit and 2020 for helping us out this Ladle, and also to wrtlprnft who played for us vs oops + DS.

;PsYkO

:Dunno who it was by it was just shit talk against SP. I think everyone could care less including me but Lack is just saying that whatever X was saying was minor in comparison.

;Rico

:Okiedoke.

;[[User:Durka|Durka]]

:Please correct me if I'm wrong, but I'm pretty sure that 2020 has always said, that if there are only 2 teams on one side of the bracket (in this case TuI and FWW), then the first round is skipped. His reasoning for this was so that the winning team didn't have to wait 45 minutes in between the semi's and finals. This would also allow the entire competition for that team (in this case FWW) to only last 1:30 straight minutes rather than play for 45, break for 45, play again for 45. So, I was just going on past experiences. Sorry for the confusion.

:As for the matches, indeed, FWW got too cocky and we caught them by surprise the 2nd match. As usual, we (or I guess I) weren't prepared seeing as I got 1 round of warmup after rushing home. Then again, everyone was pissed off and wanted to start. Another problem I can see was the player limit. We were expecting FWW to show up with 5 players since they had only signed up with 5, but oh well. So, we ended up filling the server with 16 players. The big problem was, I was locked out and spammed my teammates aim/msn to tell them to get rid of one of our teammates so I could join. Then, we started playing and we had 8 players, but we did not know that Luzifer and Sky were locked out of the server. Then garisimo's connection dropped after the 3rd round or so. By that time, I'm guessing, Luzi and Sky had probably stopped trying to connect to the server. So, we ended up playing 7 on 8 vs FWW.

:This doesn't happen in Cafe of Z-Man's server since they allow 32 clients, we got to fix that for Wild West.

:Holes, heh, I've gotten holed everytime I've played the Ladle, so for FWW to hole me constantly over 3 matches wasn't surprising, but one thing really pissed me off. It was 4 on 2 (we had 2) and my defense was pretty big and my sweeper (don't remember who it was) was doing a great job. Then, I see their defense and sweeper attack. They grind eachother the length of the grid and torpedo into my defense. You can say that's good strategy, but, if a team has to torpedo me to win, it pretty much takes the fun out of it. Especially since this was near the beginning of the 3rd match. So instead of us getting a possible 10 points for winning the round, they get 10. Basically a 20 point swing. Then we /team messaged each other saying, "Hole them!" but then we all decided not to since we thought it showed poor sportsmanship.

:All in all, it was fun playing against a team consisting of: Lackadaisical, madmax, MaZuffeR, eggcozy, newbÃe, pavelo, PsYkO, & wHaTuP.

:Great competition and looking forward for a rematch.

;PsYkO
:It seemed to us that the ladle starts at 8:30 GMT and first bracket starts at 8:30 GMT, not 9:15. All of us seemed ready at around 8:45GMT but we were missing an admin. Correct me if I'm wrong but it was 8v8 throught he middle of round 2, and start of round 3 it was 8v8 again, I'm sure me and you should know this best because at the start of every round I'm circling and looking at how many from each team are alive. About you expecting 5 cuz only 5 were signed up. This is a bit sticky. See we did only have 5 signed up because it states that for a person to sign up they have to come to the challenge board and sign themselves up. This isn't strictly enforced but I can tell you that TuI also had 5 members, one hour later had like 10-12 members signed up =D lol. Holes are part of the game, I get holed by every single team in the ladle.
:The Reservoir Dogs will maybe make a return sometime in the future, but not for a whiiillleee.

;~ X ~
:Haha, I just loved the laddle. Before it started, everyone was saying we going to be playing against some of the 'best' European players (FFW), so we should practice as much as we can. Ha, what a joke that was! Rather than showing experience and their skills,which I was so looking forward to, it ended up as an opposite. The first two matches were great, the opposite team was doing incredible job, before I guess we pissed them off and caught them by surprise by winning the 2nd match. After that the whole hell turned lose. There wasn't no more competition, there was only one way one and one way only, HOLING! It seemed that our defense started screaming "DEF DOWN" more often every single match till the end. There was no more challenge left in the game except figuring on how to prevent our self's from getting holed. After a few rounds in game, the team also decides, why try to break a defense if we could just torpedo (in the middle of the game). Now that was a main highlight I'm guessing. Kind of guessing they really NEEDED to win no matter what at that point. There was no skills involved afterwards, only non-stop irritating holing. Sure I guess people say holes are part of the game and you should hole, but most do show some kind of decency of actually trying to win. I never saw any challenge we were suppose to have fighting against some of the most experienced players on tron, or maybe I'm just wrong, being one of the best players you got to be best at holing the other team, who knows, but I'm finding out more and more things. Instead I did figured out one thing during this laddle, is the next time we fighting some of the so called overrated 'best' players of tron, is to be prepared for non stop holing.

; egg
:Playing anonymous seems to lend itself more to all the name calling. In the final, I didn't even know who Mr. X and Mr. Blue was on my own team. Anonymity needs to be taken out of tourneys at some point in the distant future.
:I'm sure everything has been said already in arguments about holing ... maybe the team who is being holed should just not die. I'm sure thats been said.
:TUI is a good team, but their whole focus is on defense. There were times when they had 3 and we had 2, or just 2 on 2, and all they wanted to do was defend till we had one left. My connection was awful, the server was to put it nicely, not so great, and I was not in a position to do anything close to walls, but TUI insisted on playing turtle, putting me with my crappy connection up against two with American connections. They deserved every hole they received.
:
:In the future, remind me not to play on a team with even one player who thinks double grinding is a good thing. There was one on our team who insisted on being 2 or 3 and insisted on DG.
:Team Something Something is still the best team ever :-D

; PsYkO
:I've never won anything on this game where the opponent has admitted defeat =_= Ok TuI you are the best clan and best ladle team, you guys are teh pwn

;~ X ~
:Jeez, you the most irritating person I ever came across on Tron, are you trying or that's just your nature being an asshole?

;PsYkO
:Jeez, I'm sorry that you can't even say that a team of 8 of probably the best 10 fortress players isn't better than TuI. So you think I'm irritating huh? Now you know how most of the fortress player feels about TuI players. There are those that think I'm a great guy, those that think I'm a complete dick. The same goes for you or anyone else pretty much in the world.

;JJBean
: Psyko I still think it's funny you and whatup ditched your 'elite' speeders clan to play with the foggies. But it's even funnier that your 'elite' speeders clan couldn't even beat half of the oops clan and the other half rubber players. WD on the win, also wd to sp for being so awsomely good.

;PsYkO
:Considering I organized our team and I told k3nny (our ladle organizer) well in advance that i was going to play for another team, I hardly call that ditching, but hey you can try and convince some of them that.. Yes SP lost, but so did you. Correct me if I'm wrong but in the same round? And before that losing a 2v1 by basically 100-0 if it wasn't for a suicide. Hardly in a position to run your mouth JJ.

;2020
:Good games. Best ladle for me for a long time... Enjoyed the first game and thanks to rico of |x| i got to play in their team in the semi and final. Nice analysis rico, though i must admit, opponents chatting and bawking is expected in a high-testosterone environment; such chat comes with the game... and holing is allowed, we just didn't cover defence well... Rico: as a captain, you are superb, and it was a pleasure to work in a team, positive comments by flex, humour from subz...
:lacka says it all...
:psyko's right too: best team on the night, though i am waiting for a team to dominate who are full of average players but they play as a unit...
:durka is right too too: normally we skip the quarters if the semi is empty... but this does need to be communicated between captains, players, etc... as for holing -- guys, it is part of the game, it is not a game fault... it might be a low-honour technique, but in game-ware, anything within the rules goes...
:hehehe as for the rest of it, it is a competition, and none of us like to lose hehehe

;Hoax
: egg "in the future, remind me not to play on a team with even one player who thinks double grinding is a good thing. There was one on our team who insisted on being 2 or 3 and insisted on DG."
:Thats funny because I remember when I was first playing fortress, the worst abuse I ever received was from you. This was because I was '''not''' double grinding. I also dont get the obsession with name alliases either when we are all in a tournament. Rico pretty much summed it up. Credit to wrtl 2020 & legit for playing for us also.

;Egg
: Hoax, you are wrong. I don't know who you are thinking of, but I have never in my life told anyone they should double grind. I have always thought that it hurts the team more than it helps. Usually the only players I have "abused" are players who DG poorly with the result of killing me when I am center.
:"Obsession" is a strong word regarding my thoughts on anonymity. Just an opinion. I like to know who individual players are on my team and the other team (more important for the team I am on). You don't see players in the World Cup or the World Series deciding they want to be called W30wN3DU. I guess it's probably something that can not be changed with 13 year olds and online play though.

== Previous Winners ==

The [[Ladle-11/Results|Eleventh Tronic Ladle]] was won by Fogies with Wheelchairs on Sunday 6th May

The [[Ladle-10/Results|Tenth Tronic Ladle]] was won by [http://tui.owns.it TuI ~ Tronners Under the Influence] on Sunday 1st April

The [[Ladle-9/Results|Ninth Tronic Ladle]] was won by [[Team somethingsomething]] on Sunday 4th March

The [[Ladle-8/Results|Eighth Tronic Ladle]] was won by [http://tui.owns.it TuI ~ Tronners Under the Influence] on Sunday 4th February

The [[Ladle-7/Feedback|Seventh Tronic Ladle]] was won by Speeders on Sunday 7th January

The [[Ladle-6/Feedback|Sixth Tronic Ladle]] was won by [[Team somethingsomething]]

The [[Ladle-5/Feedback|Fifth Tronic Ladle]] was won by [[Tronic Monkeys]] in a closely fought final on 5th November 2006

The [[Ladle-4/Feedback|Fourth Tronic Ladle]] was won by proN00bz on 1st October 2006.

The First [[4 Team Fortress Tourney 1|4 Team Fortress Tournament (4TFT)]] was won by [http://crazy-tronners.com Crazy Tronners (CT)] on Sunday, September 17th, 2006

The [[Ladle-3/Feedback|Third Tronic Ladle]] was won by [[Ladle Winners|Anarchic Wanderers]] on 3rd September 2006.

The First [[International_Tron_World_Cup|Tron World Cup]] took place in July and August 2006 and was won by the United Kingdom. Full scores of the matches are available on the [http://lod.bigreddesign.co.uk/twc/ Official TWC Site]

The [[Ladle-2/Feedback|Second Tronic Ladle]] was won by [[Ladle Winners|Anarchic Wanderers]] on 29th August 2006.

The [[Ladle-1/Feedback|First Tronic Ladle]] was a fortress tournament with seven teams and was won by [[Ladle Winners|Shadow League]] on 1st July 2006.

The [[THE SPOON|Tronic Spoon]] was a fortress tournament of 87 players arranged into 8 and was won by [[Team somethingsomething]] in March 2006.
|}

{{:Ladle/Feedback}}

{{:Ladle/Results}}

Server Administration

2008-02-20T01:37:12Z

Jonathan: Reverted edits by EltsiTlidr (Talk); changed back to last version by TadarOlori

baspasel
trcovarcn
{{Sections}} 

Here you will find various guides to creating and administering game servers.

== [[Server Administration Guide]] ==

Basic guide for setting up a game server. This is your first and hopefully last, resource when you decide to run your first Armagetron Advanced game server. It will walk you through setting up the server, making it available on the internet, basic game and physics settings, and it will set you loose. You should at least read it, even if some of the material strikes you as being particularly basic. It is intended to be used by a fairly computer-literate person who has very little or no knowledge of server operations of any sort.

== [[Advanced Server Administration Guide]] ==

So you've been running a server for awhile and now you'd like to do more with it? Maybe you've found that there are some punk-ass players out there that you really want to kick off your server? Maybe your players are asking for more, and you're saying "Hell yeah!" but you don't know what to actually do about it?

== [[Remote Moderation]] ==

So you want your server moderated but you have to explain how to kick and ban remotely to everyone that you want to help moderate it. Well, send them to this page!

== [[Console Commands]] ==

A complete list of console commands.

== Making the server run as a service in Windows NT (2000/XP) ==
This is probably one of the easiest things to do for amateur admins. You start by editing the config files located usually (C:) Drive under Program Files and inside the Armagetron Dedicated Server folder. Once you alter those to your liking, create a shortcut on the desktop for the armagetron dedicated server.exe file. Click it ands you should have DOS prompt window show up that spews out text about what is exactly happening to and inside the server, you can mimimize it and not worry about it hanging for freezing. This is probably one of the easiest ways to run a server. '''Except that this isn't running as a service.'''

'''Drawbacks of running a server with Windows:''' Due to the intense graphics the GUI windows uses. The computer may sturr up some lag for players. It is highly suggestive that if you run a windows server, make sure you have a higher end model computer and a fast connection.
*TODO: Check if [http://www.codeproject.com/system/xyntservice.asp| XYNTservice] can be integrated into the code or used to run win32 dedis as services. Is the absense of a server console a problem ? the server does not have a console as it's run under another users accounts and there is no way in windows (AFAIK) to access it. We might send a message to the service ? --[[User:Joda|Joda]] 10:56, 19 March 2007 (CDT)

{{Sections}}

AVE2

2008-02-20T01:37:10Z

Jonathan: Reverted edits by LiracBocer (Talk); changed back to last version by Jonathan

{|- style="width: 100%"
| style="background: lightgray;" |'''AVE Fort''' |[[AVE| Home ]] |[[AVE_Schedule| Calender]] | [[AVE2| Sign Up]] | [[AVE3| Rules]] | [[AVE4 | Teams]] '''Signing up''': At The moment there is no deadline, but it is possible to pre-signup already '''If you sign up for the tourney there is the possiblity that you don't play, these choices are made between the Team-Leaders''' '''Please post your name within the correct continent, if we find out you didn't you could be banned, post also 
* Nickname
* Aliases
* E-Mail
* Country
* Europe/America
* Position (Sweeper, Attacker, Midfielder, Defender)
* Do you want to become and team leader Yes/No'''
 '''Sign-ups will be proccesed at [http://eva-tron.net.tc/ This Site]'''

AVE4

2008-02-20T01:37:09Z

Jonathan: Reverted edits by RolnoOrbas (Talk); changed back to last version by Rain

{|- style="width: 100%"
| style="background: lightgray;" |'''AVE Fort''' |[[AVE| Home ]] |[[AVE_Schedule| Calender]] | [[AVE2| Sign Up]] | [[AVE3| Rules]] | [[AVE4 | Teams]]

AFL Spring 2007 Playoffs

2008-02-20T01:37:02Z

Jonathan: 2x spam

olotrnod
{{AFLTbl}}

Here's all the information for the Spring 2007 Playoffs.

== Brackets ==

Home teams are listed first.

{{:AFL_playoffs_results_table}}

The playoffs will proceed as follows:

First round will have 6 teams playing. These will be played the same as the games in the regular season, best 2 of 3. (Technically we're first-past-the-post here since the third match is optional if one of the teams wins the first two matches) These games will have the higher-ranked team as the home team and will be played on their server.

Second round will have 4 teams playing. The 3 that advanced plus the team that sat out the first round. Each game will be first-past-the-post, and the post is 3. So the first team to win 3 matches in a game wins the series and advances, the other team loses. These games will flip-flop servers. First match will be played at the higher-ranked team's home server, second match will be played at the other team's, and then back again, and so forth, until there's a winner. Please don't get lost switching servers. You guys do this all the time, so it shouldn't be that hard.

Third round is the Championship. This game will have the post at 4 and could be a very long game. At the end of the second round, if both teams that advance desire, the championship can be rescheduled for up to one week from then. If there is disagreement, the game will be played immediately following the second round (with a little break if need be). This game has several playable options. It can be flip-flopped as the last game. It can be played in its entirety at the FA AFL Server, or if z-man's willing, it can be played in its entirety at his server. Also, if wrtlpwned is willing, it can be played in its entirety on Fort Cafe. The two lucky teams will decide, and if they can't agree, it will be flip-flopped by default.

== MVP Nominations ==

The following players are automatically nominated for the Most Valuable Player award. Please begin voting! All votes must be signed, or it can't count. Remember, only people who played during the season can vote, and the only way we can verify that fact is if the votes themselves are signed. Sign with <nowiki>~~~~</nowiki> if you are a user here, or else just write your name. You must have played at least one game to be able to vote.

The votes will be tallied. In order to win, a player must receive 2/3 of the votes cast. If a player hasn't received a 2/3 majority, then the lowest ranked player will be removed and a second round of votes will be cast. This is similar to instant run-off voting, which may be the voting method in your country. We will continue voting until someone wins 2/3 of the total votes cast, or until everyone is eliminated except one person, whichever comes first.

=== Round 1 Voting ===

==== Subzero ====

==== Luzifer ====
--- owned
 --- [[User:Durka|Durka]] 18:11, 10 August 2007 (PDT)
 --- Phantom
 --- [[User:PsYkO|PsYkO]]
 --- newbie

==== apparition ====

[[User:Epsy|Epsy]] 09:40, 10 August 2007 (PDT) aka fuck that capital letter

==== whatup ====

==== Gluggsel ====

==== FoFo ====
-''Ã¥ppÃ¥ritiÃ¸n''

-''Legit'' - Gayfo for president!

-''Rico'' - croissants ftw!

-''Hoax'' - raise a white flag for Fo!

-''$ubzero'' - FoFo smells and is gay :D <3

==== epsy ====

==== $ativa ====

==== Legit ====

Server Administration Guide

2008-02-12T15:05:13Z

Jonathan: /* Test the Server */ OS X start

eldrontar
Setting up a server for Armagetron Advanced isn't terribly difficult, but there are a few things you need to consider when you do it. Taking a few minutes to figure out what you're trying to do will save you a whole lot of headache/heartache later on when people start playing your server.

== Starting out ==

Before you consider what OS you're going to use, what version of the game to run, and so forth, you should figure out a few basic parameters of the server. Here are some you should consider.

=== Private or Public? ===
The setting <code>TALK_TO_MASTER</code> is off by default. To make your server public (available on the master server list), you must turn on this setting. If it is off, players will only be able to connect to your server through the [[Server Bookmarks]] using your IP address. If you are connected to the internet through a router, normally used so that multiple computers can share the same internet connection, you will also need to open a port.

More information on both of these topics is available below.

=== Moderated? ===

Armagetron Advanced supports a limited but expanding set of in game administration commands(in 0.2.8, it will be a fairly comprehensive set). The catch is that you can only have one administration password. So in order to make moderators on your server, all you have to do is give out the administration password.

The alternative is to use the voting features that are intended to allow players to moderate the server as they see fit.

You can go either way, of course. It's entirely up to you.

=== Round or Match ===

There are plenty of ways to setup scoring on a server. A common setting is one point for each kill. While this scoring method encourages competitive play, it's not always desirable. On some servers, just surviving to the end of the round is quite an accomplishment, and you may wish to reward players for doing so. Too much of a reward will encourage players to just screw around instead of fighting.

You should also consider if you even want the standard gladiator-style fighting. It's certainly possible to set up scoring to allow for different games, such as [[Roulette]], and to encourage different playing styles. So just take a few minutes to think about it. It'll pay off in the end, because the default game server settings aren't necessarily the most popular scoring rules, and unless you really want the default scoring, you could lose most of your audience in the first two hours of operation if you didn't think about scoring.

== Requirements ==

=== If you fall short ===

If you cannot meet the requirements to host a server yourself (or simply don't want to leave your computer on 24/7), don't despair! There are companies that specialize in hosting colocated servers-- you can use many of them (such as [http://www.sevenl.net/ SevenL] or [http://www.vr.org VR Hosted]) to host an Armagetron Advanced server. If you don't have the expertise or want to bother with maintaining a full Linux server, you can get hosting specifically for Armagetron from [http://lightfoot.dashjr.org lightfoot.dashjr.org] without needing to setup anything.

=== Hardware ===

Hardware requirements are fairly small. The game itself will only need around 10MB of RAM or so, more for more players. So whatever the minimal requirements for your target operating system will usually suffice. It is important to make sure that the game will not have any of its parts swapped to disk, just like with any other server, but memory usage is minimal.

CPU requirements are also pretty slim. Again, whatever the requirements for your target operating system will likely suffice. A common number provided for a server CPU is a 600mhz Pentium II or greater. Some popular servers have run on as little as 800mhz AMD Duron! Starting in 0.2.7.1, it is possible to limit the framerate of the simulation itself. This gives several important traits to the game. First, it makes it play nicely even on a computer that runs other tasks (such as a web server). It also provides for more stable gameplay. Finally, it allows you to tailor the simulation for your hardware, so on a smaller CPU, you should consider limiting the framerate of the simulation to improve gameplay.

=== Network ===

The size and speed of your network connection is more than likely going to be your first and most serious performance bottleneck. Generally you'll want to consider that each player connected requires about 6KB/second of upstream bandwidth. So for 16 players, you'll need 96 KB/sec of upstream bandwidth. This doesn't consider any other bandwidth usage on your network, such as web browsing from a different machine. Use MAX_CLIENTS to limit the number of players accordingly.

More information is given for both of these topics in the [[Advanced Server Administration Guide]].

== Setting Up ==

So now you've figured out what kind of server you want and how you want people to play on it, and you want to know how to set it up and optionally make it available on the master server browser. Setting up is fairly straightforward.

If you do not wish to bother with setting up a server yourself, and be left to simply administrate your server, [http://lightfoot.dashjr.org lightfoot.dashjr.org] provides managed hosting for Armagetron servers-- you can just configure it how you like using a simple web interface and be ready to play.

=== Install the Server ===

First you need to install the server. It's common to think of any given "server" as a special machine built by old women in third-world countries, but actually, a "server" is just any machine that makes a "service" available to other users. In this case, you're going to install software on a computer, possibly your desktop computer, that will make a game service available for other users to use.

So first you need to acquire the package called "armagetronad-dedicated". If you're using Linux, get one that says "linux" on it. For Windows, get the one that has ".exe" on the end of it. For Mac OS X, there's one with a ".dmg" extension for you. Usually the CPU architecture and OS are embedded in the filename, so pick the right one and install it.

We won't go into too many details here about installation, consult the regular documentation for how to install the server for your architecture.

=== Test the Server ===

After installing the server, the first thing you should do is test it. So start it up. If you're in Linux, you will want to become the superuser and type, in a terminal, "/etc/init.d/armagetronad-dedicated start". If you're in Windows, find the icon in your Start menu and click it. If you're in Mac OS X, open the application Terminal which can be found in Utilities in the Applications folder. Type "cd " there (without the quotes) and drop the folder containing the dedicated server on the window. You should now see something like "cd /Users/username/Desktop/Armagetron\ Advanced\ Dedicated/ " if the folder is located on your desktop. Run it by pressing enter or return. Once you're in there, run ./armagetronad-dedicated to start the server. Then fire up a client and see if you can connect to it as a LAN game (under Network Game). If you can do this, then you have successfully tested the server. Now you need to shut it down. In Windows, go to the console window for the server (it opens when you start the game) and type "QUIT". In Linux, just do "/etc/init.d/armagetronad-dedicated stop". In Mac OS X, you type "quit" in the Terminal window like in Windows, after which you can close the Terminal window.

== Public Servers ==

If you want to host a server at home. You have to open UDP port 4534 in your firewall and possibly forward the port from your router to the PC running ArmagetronAd (and is hosting a game).
=== Firewalls ===
*Windows XP: Either your firewall will ask you if you want ArmagetronAd to open port 4534. You can also follow [http://support.microsoft.com/default.aspx?scid=kb;en-us;308127 these instructions] use name: "Armagetron Server" the port is UDP 4534 (leave TCP blank).
*ZoneAlarm: TODO: popular? should it be added ?
*Mac OS X: Go to System Preferences â Sharing â Firewall. One way to let all traffic through is turning it off, but you may not want to do that. If you decide to leave/turn it on, look for a button labeled âAdvancedâ¦â. If it exists, go there and ensure âBlock UDP Trafficâ is not checked. If it doesn't exist you have an old version that never blocks any UDP. For the curious: this is a limited GUI to ipfirewall.
*Linux: TODO Lucifer ? Link to a site ?

=== Port forwarding ===

If you have a router with [http://en.wikipedia.org/wiki/Network_address_translation NAT], you'll want to forward a port to your server so others can reach it. Armagetron uses the UDP port from configuration option SERVER_PORT, which is 4534 by default. You'll probably want a forwarding entry that looks like:
* Local/internal address: <your server's IP address>
* Protocol: UDP
* Local/internal port: <SERVER_PORT>
* Remote/external port: anything should work, but <SERVER_PORT> is common.

It is important that your server's IP address never changes. You can manually choose an address outside the address pool used by DHCP, or an address that is unlikely to be assigned (e.g. if the lowest available address is always assigned, you can use an address ending with 100), or disable DHCP altogether and configure everything manually. [http://www.portforward.com/ http://www.portforward.com/] has more info on that.

If you can't figure it out, consult your router's manual. You can also look for help at the aforementioned [http://www.portforward.com/ http://www.portforward.com/], which has tutorials for many routers, and a forum. It doesn't have an Armagetron entry (yet), but it has been found that [http://www.portforward.com/english/applications/port_forwarding/F-22Lightning3/F-22Lightning3index.htm F-22 Lightning 3's] port range contains Armagetron's default port, so if you're absolutely clueless you can go with that.

==== Dynamic external IP addresses ====

If you have a dynamic external IP address, you can use a service like DynDNS's [http://www.dyndns.com/services/dns/dyndns/ Dynamic DNS] to map a name to your IP address. When your IP address changes, a small updater program will send the new address to DynDNS and update the address associated with the name. You should set the setting SERVER_DNS to the name you registered to ensure clients and the master servers can keep track of you when your IP address changes.

=== Secure the Server ===

There isn't really a lot to do here, but you should consider how you want to secure the machine. If you think it will be necessary to ban certain players, then a firewall is your only option. Since ArmagetronAd 0.2.8.x you are able to ban IPs.
For older versions you can use a firewall that allows you to deny connections from users by IP address. It's not foolproof, but it's the only thing possible until we have player authentification.

Contrarily, if you do not want internet players to be able to use your server, you will need to make sure your router prevents such players but making the port mentioned above inaccessible through the router.

== [[Configuration Files]] ==

At this point you should have a good idea of what kind of server you're going to run and you should also have a working server running, but you don't yet have the server you set out to build. Now you need to configure the server itself.

The server is very flexible. As of the 0.2.8 release, you have pretty complete control over the simulation, and you also have some settings that you can configure the game rules a bit. So now all you need to do is make the settings, right? Wrong. :) First you need to understand how the settings are loaded and in what order.

=== Examples ===

Note: These examples first appeared in one of the release candidates for 0.2.8. Depending on what version you install, you may not have all of them, or even any of them. The final 0.2.8 release will have them for all platforms, however.

Several example files are provided to help you get set up and running quickly. These files contain snippets of settings that range from simple adjustments to cycle physics to more complex snippets that encapsulate complete game rules. So if you've played a server that you really enjoy and you'd like to use it as a base to build your own server, you can look to see if any of the example snippets provide the settings you're wanting.

Some of the snippets are named from the servers they came from. When you see this, it is because the file contains a fairly complete set of settings to make a server exactly like the server where the settings originated. Others are named after a specific action. These may have originated in a server, or they may not have originated in a server. If they came from a server, you can read the comments in the file to see which server they came from.

Each example snippet is built with the intention of being included in your <code>settings_custom.cfg</code> file so you don't have to copy and paste the contents in order to use them. Be warned, however, that the example snippet you've picked may be changed in an upgrade. This will happen periodically when the game engine changes in a way that renders the settings snippet in a different fashion than it was intended, and the changes will be made to attempt to bring that file back to the same feel of play as it originally had. If you want to use those upgrades to your benefit, then you can and should go ahead and include the snippet file as shown. If you want to insulate your server from such upgrades, then you'll need to copy and paste the contents of the file into your own <code>settings_custom.cfg</code>.

Examples:

To make a fortress server, add this line to <code>settings_custom.cfg</code>:

<code>INCLUDE examples/fortress_soccer.cfg</code>

To add a death zone to your server, you can add this line:

<code>INCLUDE examples/death_zone.cfg</code>

To add a single-use booster in place of the brake, you can use:

<code>INCLUDE examples/single_use_turbo.cfg</code>

Some of the example files may modify the same settings that others modify. When two examples conflict in this fashion, the one that is listed last will override all others. So place the one you wish to have persist at the end.

If you'd like to taylor the settings after you've included them, place your own settings after the relevant include lines. In fact, you should place all of your additional settings after all includes in order to ensure that no new included file will override your own settings.

=== Making your own Settings ===

The most common settings to change affect game logic, scoring, and some basic simulation such as cycle speed, acceleration, and so forth.

==== Simulation Settings ====
;EXPLOSION_RADIUS
:Blast radius of cycle explosions. Set to 0 to have no explosion radius (obviously).
;WALLS_LENGTH
:Cycle trail length. Set to -1 to have infinite trails.
;WALLS_STAY_UP_DELAY
:Cycle trail stay up this long after the cycle's destruction, measured in seconds.
;SPEED_FACTOR
:Cycle speed factor. Increase this by two to double the speed
;CYCLE_RUBBER
:This affects grinding. Higher numbers allow players to get closer to walls before crashing. It's intended to be used solely to correct for lag, but it's usually not used that way.

==== Map Settings ====
;ARENA_AXES
:Sets the number of possible driving directions (used only when map is axes-independent, otherwise the map overwrite this value)
;MAP_FILE
:This describe how to retreive a map. It uses a special syntax to allow to describe the location of the map on the local disk and a possible list of network based location, such as web url, where to retreive the file. The syntax is "[./][directory[/directory[...]]]/filename [(fulluri[; fulluri[; fulluri[...]]])]". By default, missing files are looked up by the client on the central resource repository. If one of more URI are given in the MAP_FILE, they will be queried before going to the resource repository.

==== Game Rules ====

;SCORE_WIN
:Points you gain for being last one alive. Also known as "camping points"
;SCORE_SUICIDE
:Points you gain for every stupid death (race into the rim/your own wall). It is added, so negative numbers are appropriate here unless you want to reward people for being stupid.
;SCORE_KILL
:Points you gain for everyone racing into your wall.
;SCORE_DIE
:Points you gain for every time you race into someone else's wall. Like SCORE_SUICIDE, you should make this a negative number unless you want to reward people for sucking.

;LIMIT_SCORE
:Score limit. When a player reaches this score, the match ends and that player wins. Ties are resolved by playing another round until one player has more points than the rest.
;LIMIT_ROUNDS
:Max number of rounds to play. When this is reached, the highest-scoring player is named the winner.
;LIMIT_TIME
:Max time (in minutes). When this is reached, the highest-scoring player is named the winner of the match.

Here is a pretty common setup:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 10
LIMIT_ROUNDS 40
LIMIT_TIME 30
</pre>

This is the scoring system used on servers like Swampland, the old Tigers Network servers, and the goshdarn clones that are floating around. It basically means you have to get 10 points by killing other players to win the match. Breakfast in Hell used a variation:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 1000
LIMIT_ROUNDS 40
LIMIT_TIME 7
</pre>

You still had to kill people to win, but the match was limited to 7 minutes. After 7 minutes, a winner was declared. The Crack Pipe still uses these settings at the time of writing but may change in the future.

'''This isn't a complete list!'''

There are a whole slew of configuration items available. Since the config items are the same as console commands, you can see a pretty complete list on the [[Console Commands]] page.

== Finishing Up ==

The last thing you need to figure out is usually the first thing you know. Do you want this server to be known by the master server? If so, you need to add this line to your settings_custom.cfg:

<code>
TALK_TO_MASTER 1
</code>

Note: in previous versions, this was the default, but as of 0.2.8, the default will be to not talk to master. You will have to manually set that, so make it the last thing you do before starting the server up for play.

You will also likely need to set <code>DEDICATED_IDLE</code> to 0. If you're in Linux and you're using the init script, then you probably don't have to worry about it, because the init script will restart the server automatically. But if you're not in Linux, you'll need to place this in your settings_custom.cfg:

<code>
DEDICATED_IDLE 0
</code>

If you want your server to be known on the internet, you will probably need to open a port in your router. The default port is 4534, and you need to open it for "udp". Instructions on how to configure this on your router are beyond the scope of this document, you should consult your owner's manual for further information.

Of course, when that's all done, you need to start the server. Use the same procedure already referenced.

== Conclusion ==

This article is the basic "How to setup a game server" article. After reading through this article and getting your server running, the best thing you can do is to play your server for awhile, talk to other administrators, and so forth. Find out what people want, or figure out what you want. Tweak your settings however you'd like, it's your server. When you feel like you've got the hang of running a server, check out the [[Advanced Server Administration Guide]] for more cool things you can do with your server.

In the meantime, have fun!

[[Category:Server/config]]

PlayingGettingStarted

2008-01-11T15:41:54Z

Jonathan: Reverted edits by VialdArcac (Talk); changed back to last version by Jonathan

AFL Calendar

2008-01-11T15:41:49Z

Jonathan: Reverted edits by 222.190.96.195 (Talk); changed back to last version by Jonathan

{{AFLTbl}}

This is the entire calendar for the AFL and contains everything currently scheduled.

'''''All times listed are London time, not UTC! London Time is currently UTC+1 because of daylight savings.'''''

<div id="googlecal" style="">[http://www.google.com/calendar/embed?src=davefancella.com_vlfi4psoqnf7ff07vlpdl6dmdk%40group.calendar.google.com view calendar]</div>

You can also get this calendar in some other ways:

* [http://www.google.com/calendar/feeds/davefancella.com_vlfi4psoqnf7ff07vlpdl6dmdk%40group.calendar.google.com/public/basic XML]
* [http://www.google.com/calendar/ical/davefancella.com_vlfi4psoqnf7ff07vlpdl6dmdk%40group.calendar.google.com/public/basic.ics ICAL] - For embedding into your own calendar program.

AFL Contact

2008-01-11T15:41:46Z

Jonathan: Reverted edits by 222.190.96.195 (Talk); changed back to last version by Jonathan

{{AFLTbl}}

The Armagetron Fortress League is organized and administered by a group of volunteers for your enjoyment. This page serves to both give credit to those people and give a way to contact them.

== Contact Methods ==

The best way to contact us is by visiting the irc channel #afl on freenode.

If you don't have an irc client, you can just use this nice link provided by Durka (warning: requires Java):

http://durdur.freehostia.com/irc/afl.html

Other than that, you may use the user pages here for the people listed, or PM them through the [http://forums.armagetronad.net forums]. You should generally find the person most apt for the problem. For example, if you think that a game you just played contained serious violations, you want a Judge.

== Judges ==

Judges are the people who make mediation decisions. When a question of interpretation of the rules comes up, it's a Judge who answers. When a game requires review for any reason, a Judge is required to do that. Once a Judge gives an answer, if you disagree with that judge, you can appeal exactly one time. Judges that are with us from season to season also band together to make policy decisions and the like. Basically, if you imagine the organization as a hierarchical tree of authority, judges are the top. The organization isn't setup that way, however, so use the tree model only as an aid to finding the right person to talk to. You can't go wrong talking to a judge, he'll at least refer you to the right person.

* Lucifer [http://forums.armagetronad.net/profile.php?mode=viewprofile&u=233 contact]
* DrJoeTron
* kamp

== Server Administrators ==

The following people administer the league's servers. Issues with specific servers should be brought to their attention. Administrators have three and only three responsibilities: make sure their server is running when a game is scheduled to play on it, make sure their server is using the approved league settings, and make sure there is someone available with the admin password during the game. The first is solved by running it 24/7 and has the added benefit of letting teams that claim it as home use it for practice. The second is solved by downloading and installing the league rule zip file. The third is best solved by giving both team captains the password, and optionally changing it after the game. Optionally, if giving team captains isn't an option, the server admin can show up and do it himself or have someone he trusts show up to do it, or find some other way to make it done (a really liberal poll setting will work too).

* [[User:Z-man|z-man]]
* Lucifer
* Rico
* Manta
* Durka

== Organizers ==

These people have helped organize the league. They are listed last, but not least, primarily to prevent you from having to scroll down a long list of people to find the person you need to contact for current questions and issues. Organizers may or may not stay with the league from season to season, and their primary purpose is to provide useful input to make sure we're thorough in setting up. Because of their work helping to setup, if you can't get the ear of one of the above listed persons, you might try one of these guys down here. They can at least help you get into contact with the right person for your problem, and in many cases they can help you resolve it.

* Lucifer
* kamp
* DrJoeTron
* ghableska
* Luke-Jr
* Vanhayes
* wrtlprnft
* Lackadaisical
* madmax
* Durka

Tilt Schedule

2008-01-11T15:41:44Z

Jonathan: Reverted edits by 198.173.203.7 (Talk); changed back to last version by Jonathan

Extending Armagetron Advanced

2008-01-11T15:41:26Z

Jonathan: Reverted edits by 84.2.38.30 (Talk); changed back to last version by Jonathan

{{Sections}} 

People like to extend and hack on Armagetron Advanced. Normally they just make moviepacks, sometimes they make other things. Maybe you'd like to make something but you just don't know where to start or what to do. These pages should give you some help in that pursuit.

==[[Customizing the game|Customizing the Game]]==
Learn how and what to do!

== [[Map Making]] ==

How to make maps. Also, how to make fun maps. You'll find some other resources here, such as links to all existing graphical map editors and so forth. Everything you need to know to make a killer map, that is.

==[[Cockpit Tutorial]]==

How to make cockpits. After you added yours to [[Resource repository]], add it here: [[Cockpits list]]

== [[Model Formats]] ==

If you want to make a new model, you're going to need to know what formats are supported by what parts of the code and where to put them. This is part of making a moviepack, but deserves its own separate discussion.
ok

== [[Textures]] ==

How do you make textures? Where do you put them? What possibilities are there that are known? You'll have to dream up new possibilities yourself.

== [[Moviepacks]] ==

Wrapping it all up, put your model and textures into a moviepack! Here are directions on how to do exactly that and distribute it.

== [[Code hacks]] ==

What code hacks are available? If you've got a compiler available and a little bit of programming abilities, there are plenty of fun things you can do to the game directly. Who knows? Do something cool and put it here and it might make it into a future version of the game.

{{Sections}}

AFL Previous

2008-01-10T08:53:40Z

Jonathan: Reverted edits by 211.233.78.237 (Talk); changed back to last version by Jonathan

{{AFLTbl}}

Here's information of historical interest to anybody interested in the history of the Armagetron Fortress League.

== July, 2007 ==

* [[AFL_Schedule|Schedule]]
* [[AFL_Spring_2007_Results|Regular Season Results]]
* [[AFL_Spring_2007_Playoffs|Postseason]]

Ladle Brackets

2008-01-10T06:08:53Z

Jonathan: Reverted edits by 80.250.210.12 (Talk); changed back to last version by Jonathan

{{Ladle}}
There has to be some kind of organization before the tournament so I made these brackets really quickly according to the [[Challenge Board]].

== Quarter Finals ==
;<nowiki>7:30</nowiki> pm GMT
;Best of 3 Matches

AW
:vs
WS
*(on Wild West - Fortress (Ladle))

LOL
:vs
WPN
*(on U.S. Fortress)

SL
:vs
CT
*(on Bugfarm - LoD Server)

== Semi Finals ==
;<nowiki>8:15 pm</nowiki> GMT
;Best of 3 Matches

Winner of AW vs WS
:vs
Winner of LOL vs WPN
*(on U.S, Fortress)

Winner of SL vs CT
:vs
~bye~

== Finals ==
;<nowiki>9:00 pm</nowiki> GMT
;Best of 5 Matches

Winner of AW/WS vs LOL/WPN
:vs
Winner of SL vs CT
*(on U.S. Fortress/Bugfarm - LoD Server)

Gentoo Portage Overlay

2008-01-10T06:08:43Z

Jonathan: Reverted edits by 80.250.210.12 (Talk); changed back to last version by Jonathan

AVE3

2008-01-10T06:08:17Z

Jonathan: Reverted edits by 80.250.210.12 (Talk); changed back to last version by Jonathan

{|- style="width: 100%"
| style="background: lightgray;" |'''AVE Fort''' |[[AVE| Home ]] |[[AVE_Schedule| Calender]] | [[AVE2| Sign Up]] | [[AVE3| Rules]] | [[AVE4 | Teams]] 
* Rule 1: The teams may not contain more then 3 players from one clan.
* Rule 2: The teams may not containt more then Players from one country.
* Rule 3: If an player doesn't show up there is no replacement allowed.
* Rule 4: If an server admin decides that you are spoiling the match you will be banned.
* Rule 5: Every team will be allowed up to 8 people
* Rule 6: If an player will not be able to play notify us at the forums atleast 2 days before the match
* Rule 7: All teams will have 1 Leader and one Co-Leader no more, no less
* Rule 8: Behave at all costs, it is able to get a ban when your'e spoiling the game

AVE Schedule

2008-01-10T06:08:06Z

Jonathan: Reverted edits by 147.46.7.54 (Talk); changed back to last version by Jonathan

{|- style="width: 100%"
| style="background: lightgray;" |'''AVE Fort''' |[[AVE| Home ]] |[[AVE_Schedule| Calender]] | [[AVE2| Sign Up]] | [[AVE3| Rules]] | [[AVE4 | Teams]]

Server Administration

2008-01-10T06:07:44Z

Jonathan:

{{Sections}} 

Here you will find various guides to creating and administering game servers.

== [[Server Administration Guide]] ==

Basic guide for setting up a game server. This is your first and hopefully last, resource when you decide to run your first Armagetron Advanced game server. It will walk you through setting up the server, making it available on the internet, basic game and physics settings, and it will set you loose. You should at least read it, even if some of the material strikes you as being particularly basic. It is intended to be used by a fairly computer-literate person who has very little or no knowledge of server operations of any sort.

== [[Advanced Server Administration Guide]] ==

So you've been running a server for awhile and now you'd like to do more with it? Maybe you've found that there are some punk-ass players out there that you really want to kick off your server? Maybe your players are asking for more, and you're saying "Hell yeah!" but you don't know what to actually do about it?

== [[Remote Moderation]] ==

So you want your server moderated but you have to explain how to kick and ban remotely to everyone that you want to help moderate it. Well, send them to this page!

== [[Console Commands]] ==

A complete list of console commands.

== Making the server run as a service in Windows NT (2000/XP) ==
This is probably one of the easiest things to do for amateur admins. You start by editing the config files located usually (C:) Drive under Program Files and inside the Armagetron Dedicated Server folder. Once you alter those to your liking, create a shortcut on the desktop for the armagetron dedicated server.exe file. Click it ands you should have DOS prompt window show up that spews out text about what is exactly happening to and inside the server, you can mimimize it and not worry about it hanging for freezing. This is probably one of the easiest ways to run a server. '''Except that this isn't running as a service.'''

'''Drawbacks of running a server with Windows:''' Due to the intense graphics the GUI windows uses. The computer may sturr up some lag for players. It is highly suggestive that if you run a windows server, make sure you have a higher end model computer and a fast connection.
*TODO: Check if [http://www.codeproject.com/system/xyntservice.asp| XYNTservice] can be integrated into the code or used to run win32 dedis as services. Is the absense of a server console a problem ? the server does not have a console as it's run under another users accounts and there is no way in windows (AFAIK) to access it. We might send a message to the service ? --[[User:Joda|Joda]] 10:56, 19 March 2007 (CDT)

{{Sections}}

Playing the Game

2008-01-10T06:07:29Z

Jonathan:

{{Sections}} 

This is a page to talk about stuff for players. I didn't write anything because I know you all are just dying to write all your secrets in this wiki. ;)

= [[The Object of the Game]] =

A brief introduction to Armagetron Advanced.

= For Beginners =

== [[The Basics]] ==

A guide for players new to the game that want to improve their abilities.
Start playing with the basic moves. Those are Left, Right and Brake. When you are good at that, you can start thinking about adding bindings to your settings so you can make 180° turns.

== [[Building Your Skillset]] ==

A top-level how-to that explains the base set of skills needed and gives some pointers on how to develop those skills. By focusing on skills and leaving tactical discussions to other articles, a new player will have a way to evaluate their overall progress in the game.
Play opponents who are better than yourself so you learn from them. It might be frustrating if you lose all the time but don't worry... Every kill is a lesson

== [[Teamplay]] ==

Learning to play in a team. Also, why good behavior is important in this and any other internet activity.

= Game Concepts =

A discussion of important game concepts.

== [[Rubber]] ==

What is rubber, anyway? I have a gauge for it, but what does it mean?

== [[Scale]] ==

What is the scale of the arena? How fast am I really going? How long are my walls, if not infinite?

= Tricks and Tactics =

== [[Player Tricks]] ==

A page that discusses specific tricks or moves. Tactical discussions aren't to be found here, this is all special moves that get you points!

== [[Single Player Tactics]] (Against AIs) ==

My best advice is to box them in. Once you have done that the AI cant get out unless your wall dissapears.

== [[Multi-Player Tactics]] ==

Via internet or LAN.
Play real life opponents from all over the world.
Think about attacking while defending or vice versa...
Try to outsmart your opponent or just surprise him.
Make traps, speedkills,...
To learn about these thing you might consider to spectate a match or play it.

Also, read [[Advanced_Tactics]].

== [[Team Tactics]] ==

For all types of game, here's what you need to know to win or lose without pissing off your teammates.

== [[:Category:Fortress_Tactics|Fortress Tactics]] ==

This is different enough from [[Team Tactics]] to get its own page. Most team tactics apply here, but fortress tactics put a whole new take on things.

== [[Animated Tactics]] ==

Watch and Learn!

= [[Moviepacks_list|Moviepacks]] =

A canonical list of moviepacks and other modifications available.

= [[Grid Games]] =

Sometimes players like to play games that are a bit different than the regular game. Maybe you've seen it and you thought they were camping? Maybe you've tried to play along and had a spot of trouble? Read here to find out all about it.

= [[Game Variations]] =

These are settings that allow for different game play styles or modes.
Click on the title for further details.

= [[Chat Features]] =

Page about chat features that come with 0.2.8.0 servers.

= [[Camping]] =

Camping is a skill you need to learn...
Camping is being caught in a box where you cant get out from, you twist and turn to stay alive. If the game has infinite walls its just staying alive. But if the walls aren't infinite you can camp so long till you find a way out.
Camping is not the same as escaping.

= [[Clan]] =
Sometimes good players team-up and start (gangs) groups. Some examples: {USA}, Death By Distraction, Status Clan, Speeders, Xlz, DarkSyndicates, Lords Of Destruction, Stealth, Six Dragons, NiNja, Noob, NoClan, AST, Global Players, Avalanche, ... Most clans have minimum standards of behavior and ability that must be met before a new player can join them. Check with the clan you're specifically interested in before attempting to join a clan.

There is also a growing group of players that dislike clans for various reasons. Ironically, many of these players have been offered to join various clans and turned the offer(s) down.

= [[Lag]] =

Lag is a myth, but heres some information on how you can minimize it.

= [[Frames Per Second]] =

FPS is the number of frames pass your screen in 1 sec.
It is possible to play with an FPS around 40 or higher. Anything lower makes your screen go shaky.
The more moves you and/or other players make the faster the FPS goes down. ( for more exp. players: i'm talking about digging and multiple bindings.)

= [[Console]] =

Using the console.

Press the tilde key.

= [[Effects and Display]] =

A guide to video effects and display.

= [[Customizing the game]] =

Changing the look and feel of the game: installing [[Moviepacks]], changing cycle colors etc.

= [[Playing Maps]] =

Your complete guide to installing a map into Armagetron Advanced and configuring the game to play it for you. It does not include how to make a map, you'll need to saunter over to [[Extending Armagetron Advanced]] for that.

{{Sections}}

Development Docs

2008-01-10T06:07:14Z

Jonathan: Reverted edits by 211.38.131.22 (Talk); changed back to last version by Jonathan

{{Sections}} 

This is documentation for developers or for people who just want to hack on the code. It is not intended to replace the automatic API documentation generated by doxygen (we do have a doxyfile, right?), but is intended to supplement those documents with additional information that may not necessarily appear in the API docs. It is also not intended as a substitute for good commenting tactics. And finally, it is a place to put planning documentation (like the stuff Philippe writes), proposals, RFC-type material, and so forth. But not the roadmap, we use Sourceforge's tracker for that.

== Documentation ==

* [[Wiki Structuring Project]]

== Building the Game ==

Building Armagetron Advanced boils down to 4 basic steps. The steps themselves are each highly platform-dependent, but the four steps are the same everywhere. Each step differs further in whether or not you're building from a branch or the trunk, and each branch may differ. Finally, each step differs depending on if you're building a source release or from version control. Here we'll concern ourselves with building the trunk only. Releases should include their own build instructions.

# Install the development environment
# Satisfy dependencies
# Unpackage source/source checkout from version control
# Build a distribution

Platform-specific instructions (they should all follow the four step structure given, that's why it's there!):

* [[Windows Development]]
* Linux
* Mac OS X

todo: the linux and mac os x pages

== Other useful hacker documentation ==

* [[Windows Development System]]
* [[Working with SVN]]
* [[Cross-compiler]]
* [[Used Libraries]]
* [[Working with SVK]]
* [http://wrtlprnft.ath.cx/doxy/html/ Doxy]

== Stuff That's Current ==

* [[Config Item Purposes]]
* [[Debug Recording]]
* [[Error Handling]]
* [[List of nDescriptors]]
* [[Project Dependency Structure]]
* [[Adding a buildslave]]

== Stuff in SVN HEAD ==

* [[Embedded Web Server]]
* [[Map/Config Rotation]]
* [[Particle System]]
* [[Joda's Team Code]]
* [[New Sound Engine]]
* [[Spawn points]]
* [[Zones v2]]

* [[Cockpit Tutorial]] | [[Cockpits list]]
* [[vValue]]

== Data File Handling ==

* [[Config Files]]
* [[Resource System]]
* [[Statistical Collections Database]] (fancy way of saying "stat files")

== Stuff That's Real but doesn't fit above ==

* [[Experimental Map Features]]
* [[Send DTD on the resource repository through ssh]]—only of interest for people on the development team

== Wishlist, or Stuff that's planned ==

(Might not be planned, but this is it)

* [[Goals]]
* [[Scripted GUI Notes]]
* [[Authentication]]
* [http://forums.armagetronad.net/viewtopic.php?t=986 Reshaping the Arena]
* [http://forums.armagetronad.net/viewtopic.php?t=1742 Map format]

== History ==

This is stuff that's of historical significance to the project. It's very difficult to remember where you're going if you don't remember where you came from, right? This is technical stuff. Community history should have its own section.

* [[What Went Wrong in Armagetron]]

{{Sections}} 
{{Category:Development}}

PlayingGettingStarted

2008-01-10T06:07:09Z

Jonathan:

Extending Armagetron Advanced

2008-01-10T06:06:57Z

Jonathan:

Server Administration Guide

2008-01-10T06:06:21Z

Jonathan:

Setting up a server for Armagetron Advanced isn't terribly difficult, but there are a few things you need to consider when you do it. Taking a few minutes to figure out what you're trying to do will save you a whole lot of headache/heartache later on when people start playing your server.

== Starting out ==

Before you consider what OS you're going to use, what version of the game to run, and so forth, you should figure out a few basic parameters of the server. Here are some you should consider.

=== Private or Public? ===
The setting <code>TALK_TO_MASTER</code> is off by default. To make your server public (available on the master server list), you must turn on this setting. If it is off, players will only be able to connect to your server through the [[Server Bookmarks]] using your IP address. If you are connected to the internet through a router, normally used so that multiple computers can share the same internet connection, you will also need to open a port.

More information on both of these topics is available below.

=== Moderated? ===

Armagetron Advanced supports a limited but expanding set of in game administration commands(in 0.2.8, it will be a fairly comprehensive set). The catch is that you can only have one administration password. So in order to make moderators on your server, all you have to do is give out the administration password.

The alternative is to use the voting features that are intended to allow players to moderate the server as they see fit.

You can go either way, of course. It's entirely up to you.

=== Round or Match ===

There are plenty of ways to setup scoring on a server. A common setting is one point for each kill. While this scoring method encourages competitive play, it's not always desirable. On some servers, just surviving to the end of the round is quite an accomplishment, and you may wish to reward players for doing so. Too much of a reward will encourage players to just screw around instead of fighting.

You should also consider if you even want the standard gladiator-style fighting. It's certainly possible to set up scoring to allow for different games, such as [[Roulette]], and to encourage different playing styles. So just take a few minutes to think about it. It'll pay off in the end, because the default game server settings aren't necessarily the most popular scoring rules, and unless you really want the default scoring, you could lose most of your audience in the first two hours of operation if you didn't think about scoring.

== Requirements ==

=== If you fall short ===

If you cannot meet the requirements to host a server yourself (or simply don't want to leave your computer on 24/7), don't despair! There are companies that specialize in hosting colocated servers-- you can use many of them (such as [http://www.sevenl.net/ SevenL] or [http://www.vr.org VR Hosted]) to host an Armagetron Advanced server. If you don't have the expertise or want to bother with maintaining a full Linux server, you can get hosting specifically for Armagetron from [http://lightfoot.dashjr.org lightfoot.dashjr.org] without needing to setup anything.

=== Hardware ===

Hardware requirements are fairly small. The game itself will only need around 10MB of RAM or so, more for more players. So whatever the minimal requirements for your target operating system will usually suffice. It is important to make sure that the game will not have any of its parts swapped to disk, just like with any other server, but memory usage is minimal.

CPU requirements are also pretty slim. Again, whatever the requirements for your target operating system will likely suffice. A common number provided for a server CPU is a 600mhz Pentium II or greater. Some popular servers have run on as little as 800mhz AMD Duron! Starting in 0.2.7.1, it is possible to limit the framerate of the simulation itself. This gives several important traits to the game. First, it makes it play nicely even on a computer that runs other tasks (such as a web server). It also provides for more stable gameplay. Finally, it allows you to tailor the simulation for your hardware, so on a smaller CPU, you should consider limiting the framerate of the simulation to improve gameplay.

=== Network ===

The size and speed of your network connection is more than likely going to be your first and most serious performance bottleneck. Generally you'll want to consider that each player connected requires about 6KB/second of upstream bandwidth. So for 16 players, you'll need 96 KB/sec of upstream bandwidth. This doesn't consider any other bandwidth usage on your network, such as web browsing from a different machine. Use MAX_CLIENTS to limit the number of players accordingly.

More information is given for both of these topics in the [[Advanced Server Administration Guide]].

== Setting Up ==

So now you've figured out what kind of server you want and how you want people to play on it, and you want to know how to set it up and optionally make it available on the master server browser. Setting up is fairly straightforward.

If you do not wish to bother with setting up a server yourself, and be left to simply administrate your server, [http://lightfoot.dashjr.org lightfoot.dashjr.org] provides managed hosting for Armagetron servers-- you can just configure it how you like using a simple web interface and be ready to play.

=== Install the Server ===

First you need to install the server. It's common to think of any given "server" as a special machine built by old women in third-world countries, but actually, a "server" is just any machine that makes a "service" available to other users. In this case, you're going to install software on a computer, possibly your desktop computer, that will make a game service available for other users to use.

So first you need to acquire the package called "armagetronad-dedicated". If you're using Linux, get one that says "linux" on it. For Windows, get the one that has ".exe" on the end of it. For Mac OS X, there's one with a ".dmg" extension for you. Usually the CPU architecture and OS are embedded in the filename, so pick the right one and install it.

We won't go into too many details here about installation, consult the regular documentation for how to install the server for your architecture.

=== Test the Server ===

After installing the server, the first thing you should do is test it. So start it up. If you're in Linux, you will want to become the superuser and type, in a terminal, "/etc/init.d/armagetronad-dedicated start". If you're in Windows, find the icon in your Start menu and click it. Then fire up a client and see if you can connect to it as a LAN game (under Network Game). If you can do this, then you have successfully tested the server. Now you need to shut it down. In Windows, go to the console window for the server (it opens when you start the game) and type "QUIT". In Linux, just do "/etc/init.d/armagetronad-dedicated stop".

== Public Servers ==

If you want to host a server at home. You have to open UDP port 4534 in your firewall and possibly forward the port from your router to the PC running ArmagetronAd (and is hosting a game).
=== Firewalls ===
*Windows XP: Either your firewall will ask you if you want ArmagetronAd to open port 4534. You can also follow [http://support.microsoft.com/default.aspx?scid=kb;en-us;308127 these instructions] use name: "Armagetron Server" the port is UDP 4534 (leave TCP blank).
*ZoneAlarm: TODO: popular? should it be added ?
*Mac OS X: Go to System Preferences → Sharing → Firewall. One way to let all traffic through is turning it off, but you may not want to do that. If you decide to leave/turn it on, look for a button labeled “Advanced…”. If it exists, go there and ensure “Block UDP Traffic” is not checked. If it doesn't exist you have an old version that never blocks any UDP. For the curious: this is a limited GUI to ipfirewall.
*Linux: TODO Lucifer ? Link to a site ?

=== Port forwarding ===

If you have a router with [http://en.wikipedia.org/wiki/Network_address_translation NAT], you'll want to forward a port to your server so others can reach it. Armagetron uses the UDP port from configuration option SERVER_PORT, which is 4534 by default. You'll probably want a forwarding entry that looks like:
* Local/internal address: <your server's IP address>
* Protocol: UDP
* Local/internal port: <SERVER_PORT>
* Remote/external port: anything should work, but <SERVER_PORT> is common.

It is important that your server's IP address never changes. You can manually choose an address outside the address pool used by DHCP, or an address that is unlikely to be assigned (e.g. if the lowest available address is always assigned, you can use an address ending with 100), or disable DHCP altogether and configure everything manually. [http://www.portforward.com/ http://www.portforward.com/] has more info on that.

If you can't figure it out, consult your router's manual. You can also look for help at the aforementioned [http://www.portforward.com/ http://www.portforward.com/], which has tutorials for many routers, and a forum. It doesn't have an Armagetron entry (yet), but it has been found that [http://www.portforward.com/english/applications/port_forwarding/F-22Lightning3/F-22Lightning3index.htm F-22 Lightning 3's] port range contains Armagetron's default port, so if you're absolutely clueless you can go with that.

==== Dynamic external IP addresses ====

If you have a dynamic external IP address, you can use a service like DynDNS's [http://www.dyndns.com/services/dns/dyndns/ Dynamic DNS] to map a name to your IP address. When your IP address changes, a small updater program will send the new address to DynDNS and update the address associated with the name. You should set the setting SERVER_DNS to the name you registered to ensure clients and the master servers can keep track of you when your IP address changes.

=== Secure the Server ===

There isn't really a lot to do here, but you should consider how you want to secure the machine. If you think it will be necessary to ban certain players, then a firewall is your only option. Since ArmagetronAd 0.2.8.x you are able to ban IPs.
For older versions you can use a firewall that allows you to deny connections from users by IP address. It's not foolproof, but it's the only thing possible until we have player authentification.

Contrarily, if you do not want internet players to be able to use your server, you will need to make sure your router prevents such players but making the port mentioned above inaccessible through the router.

== [[Configuration Files]] ==

At this point you should have a good idea of what kind of server you're going to run and you should also have a working server running, but you don't yet have the server you set out to build. Now you need to configure the server itself.

The server is very flexible. As of the 0.2.8 release, you have pretty complete control over the simulation, and you also have some settings that you can configure the game rules a bit. So now all you need to do is make the settings, right? Wrong. :) First you need to understand how the settings are loaded and in what order.

=== Examples ===

Note: These examples first appeared in one of the release candidates for 0.2.8. Depending on what version you install, you may not have all of them, or even any of them. The final 0.2.8 release will have them for all platforms, however.

Several example files are provided to help you get set up and running quickly. These files contain snippets of settings that range from simple adjustments to cycle physics to more complex snippets that encapsulate complete game rules. So if you've played a server that you really enjoy and you'd like to use it as a base to build your own server, you can look to see if any of the example snippets provide the settings you're wanting.

Some of the snippets are named from the servers they came from. When you see this, it is because the file contains a fairly complete set of settings to make a server exactly like the server where the settings originated. Others are named after a specific action. These may have originated in a server, or they may not have originated in a server. If they came from a server, you can read the comments in the file to see which server they came from.

Each example snippet is built with the intention of being included in your <code>settings_custom.cfg</code> file so you don't have to copy and paste the contents in order to use them. Be warned, however, that the example snippet you've picked may be changed in an upgrade. This will happen periodically when the game engine changes in a way that renders the settings snippet in a different fashion than it was intended, and the changes will be made to attempt to bring that file back to the same feel of play as it originally had. If you want to use those upgrades to your benefit, then you can and should go ahead and include the snippet file as shown. If you want to insulate your server from such upgrades, then you'll need to copy and paste the contents of the file into your own <code>settings_custom.cfg</code>.

Examples:

To make a fortress server, add this line to <code>settings_custom.cfg</code>:

<code>INCLUDE examples/fortress_soccer.cfg</code>

To add a death zone to your server, you can add this line:

<code>INCLUDE examples/death_zone.cfg</code>

To add a single-use booster in place of the brake, you can use:

<code>INCLUDE examples/single_use_turbo.cfg</code>

Some of the example files may modify the same settings that others modify. When two examples conflict in this fashion, the one that is listed last will override all others. So place the one you wish to have persist at the end.

If you'd like to taylor the settings after you've included them, place your own settings after the relevant include lines. In fact, you should place all of your additional settings after all includes in order to ensure that no new included file will override your own settings.

=== Making your own Settings ===

The most common settings to change affect game logic, scoring, and some basic simulation such as cycle speed, acceleration, and so forth.

==== Simulation Settings ====
;EXPLOSION_RADIUS
:Blast radius of cycle explosions. Set to 0 to have no explosion radius (obviously).
;WALLS_LENGTH
:Cycle trail length. Set to -1 to have infinite trails.
;WALLS_STAY_UP_DELAY
:Cycle trail stay up this long after the cycle's destruction, measured in seconds.
;SPEED_FACTOR
:Cycle speed factor. Increase this by two to double the speed
;CYCLE_RUBBER
:This affects grinding. Higher numbers allow players to get closer to walls before crashing. It's intended to be used solely to correct for lag, but it's usually not used that way.

==== Map Settings ====
;ARENA_AXES
:Sets the number of possible driving directions (used only when map is axes-independent, otherwise the map overwrite this value)
;MAP_FILE
:This describe how to retreive a map. It uses a special syntax to allow to describe the location of the map on the local disk and a possible list of network based location, such as web url, where to retreive the file. The syntax is "[./][directory[/directory[...]]]/filename [(fulluri[; fulluri[; fulluri[...]]])]". By default, missing files are looked up by the client on the central resource repository. If one of more URI are given in the MAP_FILE, they will be queried before going to the resource repository.

==== Game Rules ====

;SCORE_WIN
:Points you gain for being last one alive. Also known as "camping points"
;SCORE_SUICIDE
:Points you gain for every stupid death (race into the rim/your own wall). It is added, so negative numbers are appropriate here unless you want to reward people for being stupid.
;SCORE_KILL
:Points you gain for everyone racing into your wall.
;SCORE_DIE
:Points you gain for every time you race into someone else's wall. Like SCORE_SUICIDE, you should make this a negative number unless you want to reward people for sucking.

;LIMIT_SCORE
:Score limit. When a player reaches this score, the match ends and that player wins. Ties are resolved by playing another round until one player has more points than the rest.
;LIMIT_ROUNDS
:Max number of rounds to play. When this is reached, the highest-scoring player is named the winner.
;LIMIT_TIME
:Max time (in minutes). When this is reached, the highest-scoring player is named the winner of the match.

Here is a pretty common setup:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 10
LIMIT_ROUNDS 40
LIMIT_TIME 30
</pre>

This is the scoring system used on servers like Swampland, the old Tigers Network servers, and the goshdarn clones that are floating around. It basically means you have to get 10 points by killing other players to win the match. Breakfast in Hell used a variation:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 1000
LIMIT_ROUNDS 40
LIMIT_TIME 7
</pre>

You still had to kill people to win, but the match was limited to 7 minutes. After 7 minutes, a winner was declared. The Crack Pipe still uses these settings at the time of writing but may change in the future.

'''This isn't a complete list!'''

There are a whole slew of configuration items available. Since the config items are the same as console commands, you can see a pretty complete list on the [[Console Commands]] page.

== Finishing Up ==

The last thing you need to figure out is usually the first thing you know. Do you want this server to be known by the master server? If so, you need to add this line to your settings_custom.cfg:

<code>
TALK_TO_MASTER 1
</code>

Note: in previous versions, this was the default, but as of 0.2.8, the default will be to not talk to master. You will have to manually set that, so make it the last thing you do before starting the server up for play.

You will also likely need to set <code>DEDICATED_IDLE</code> to 0. If you're in Linux and you're using the init script, then you probably don't have to worry about it, because the init script will restart the server automatically. But if you're not in Linux, you'll need to place this in your settings_custom.cfg:

<code>
DEDICATED_IDLE 0
</code>

If you want your server to be known on the internet, you will probably need to open a port in your router. The default port is 4534, and you need to open it for "udp". Instructions on how to configure this on your router are beyond the scope of this document, you should consult your owner's manual for further information.

Of course, when that's all done, you need to start the server. Use the same procedure already referenced.

== Conclusion ==

This article is the basic "How to setup a game server" article. After reading through this article and getting your server running, the best thing you can do is to play your server for awhile, talk to other administrators, and so forth. Find out what people want, or figure out what you want. Tweak your settings however you'd like, it's your server. When you feel like you've got the hang of running a server, check out the [[Advanced Server Administration Guide]] for more cool things you can do with your server.

In the meantime, have fun!

[[Category:Server/config]]