Armagetron Advanced - User contributions [en]

Playing the Game

2007-12-29T23:20:19Z

195.229.242.57: bodaroloor

trdelcococol
roltrer
domcaltrocsi
letodeltae
varzelaczelc
letota
liorcabase
letodarcoli
laorroldo
{{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}}

Server Administration

2007-12-29T23:01:58Z

195.229.242.57: pasers

outrli
basrolli
letovar
taoloda
tacortre
basacelg
ladelcnaalel
olotrcae
bocoraclir
{{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}}

Servers

2007-12-29T22:59:54Z

195.229.242.57: coletool

acacolovie
c4touer
montroczele
elboracchir
zelcnaba
rozeldel
chibocdom
lizelde
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 Brackets

2007-12-29T14:59:58Z

195.229.242.57: boeltolob

zelolochita
{{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)

Server Administration

2007-12-29T14:48:00Z

195.229.242.57: letoracmonli

letovar
taoloda
tacortre
basacelg
ladelcnaalel
olotrcae
bocoraclir
{{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}}

Servers

2007-12-29T14:43:09Z

195.229.242.57: varcosi

c4touer
montroczele
elboracchir
zelcnaba
rozeldel
chibocdom
lizelde
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

Development Docs

2007-12-29T14:38:55Z

195.229.242.57: letotraclac

viletor
eltzelmonmo
c4tbascc
chidelouca
coutrrov
pasdelrol
{{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}}

Competition Hub

2007-12-29T14:14:09Z

195.229.242.57: olorelcnaca

chic4ta
trocro
domalolos
varsitricpas
trocbasc4
dartacr
racracdomtr
lapasc4t
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 />
|-
| {{:AVE Fort/Blurb}}
----
{{:AFL_Blurb}}
----
{{:Ladle/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-12/Results|Twelfth Tronic Ladle]] was won by [http://www.xclan.armagetron.co.uk -ÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂ¦ÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂ¦-] on Sunday 3rd June

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

PlayingGettingStarted

2007-12-29T14:09:50Z

195.229.242.57: darcnacna

rogettracalo
sitvieltboct
aclacdel
domcoco
rolaldomli
boliacrositp
delnoorracc
{{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-3/Feedback

2007-12-29T14:08:28Z

195.229.242.57: canolaboe

eroloacel

;Manta

Each ladle keeps getting better and I think we had a great turnout. It's nice to see so many different teams participating. However I'm beginning to think we should do a way with team captains deciding the matches on game day. Once again the first match started almost an hour late do to delays by team captains. And I'm not blameless here either. We really need to just go with the lineup we have already decide upon ahead of time in the challenge page. Many good players are sadly getting burned since they are told to show up at a certain time only to be informed to wait around for decisions to be made.

Also for my location the timing of this match worked out to being on a Sunday morning on one of the biggest holiday weekends of the year. Could there please be a little more consideration for players living in the Americas next time. WS was at 4 players because of this. Thank you to those who generously volunteered to help. It would also be nice to have it scheduled a few hours later on in the day but even as it is the players located in China can't easily make it.

On another point: I am beginning to think there is no fix for this issue of disparaging ping difference. After just a few weeks of hosting my own server I have noticed that most players located in Europe (but not all luckily) refuse to play on servers where they do not get a 50 ping. Their first comments are generally "this server is $@%&*, I have a 190 ping" and leave. Heck I play with 350!! of course not as well as I would like. Because of the size of the land mass many Americans average a 190 ping on THEIR OWN servers!!! I'm sadly beginning to get some VERY unfavorable impressions of certain players. And lets not forget there are some people left out not matter what such as the Chinese players. No one will play on their servers since we do nothing but bitch. but they "QUIETLY" put up with 300 - 400+ pings NO matter the server and they still play well. We could learn a lot from them.

The only way I can see to fix this advantage of pitting teams in the ladle with such different pings is for people to stop unilaterally refusing to play above a 100 ping. And the other is teams need to actively recruit members from all parts of the world. This is an internal game after all.

Sorry if I offended some people but I think this needed to be brought up and I tried not to mention any names.

---------------------

Reply to above: I don't mind a high ping, I can play with that. What i do mind is servers that have sudden lag jumps for everyone that make it luck whether you win or lose.

For the ladle: First of all, it was fun. A lot of fun, actually. One thing that annoyed me was the fact that a certain someone started taking over all organisation just an hour before the thing started. Suddenly we had two conflicting brackets (2020 already posted his version ages ago, [[Ladle Brackets]] was useless), a certain someone joining the server my team was on wanting to tell us what to do, and other things that only delayed it IMHO. Of course, that guy wasn't in IRC which would have made it easy to communcicate, but went in and out of servers just at he liked.

In the end we still got great matches (though I sucked even more than usual). I think having the wiki more organized and have one IRC channel '''all''' ladle- related people are in will prevent such conflicting information. â[[User:Wrtlprnft|Wrtlprnft]] 01:19, 4 September 2006 (CDT)

:This crazy person running back and forth was me (Durka). Either I was off on the time or you guys were, but I'm pretty sure it was me. As you say up above wrtl, you say that I started taking over all the oranization just an hour before the thing started. Well at 12:27 pm PST which is 7:27 pm GMT (3 minutes before the scheduled start) WS and WPN were gonna leave because nothing was going on. They had been waiting since around 7:15. At that moment I jumped into CT Wild Fortress and found meriton sasha wargasm and sebol and told them to go into a server to play in the ladle. I couldn't believe that 3 minutes before the Ladle 2 of the teams were just playing some CTWF and not participating in organizing the event. That match ended up working fine. Then as time passed by WS decided to go to Bugfarm - LoD server figuring that they were going to play an AW team. They went there, then about 5 minutes later some of them came back to my server asking where the hell AW was and they didn't want to keep waiting. Now 2 minutes after the start time I jumped into your server telling you guys that WS was waiting in LoD server. I kept saying it and saying it and I realized I got really annoying and left and went back to the server WPN was in. Now we were getting pissed off that we didn't know who to play. I jumped back into the server with the million AW's (by the way congrats again :D) and asked for the team captains from both teams (A and B) to come to my server. Then I left again. Thankfully, gari and lacks came to my server and I told them what was going on. A team went to LoD server and B team came to Wild West Fortress (which was the most unstable server when it came to lag...but we couldn't go to U.S. fortress because that was even more screwed up). Anyways, from that point on the Ladle worked well. SORRY FOR JUMPING INTO YOUR SERVER AND SHOUTING THINGS TO THE AW PEOPLE, but I guess you guys had the timing off. It wasn't an hour before, it was actually past the start time and people were getting annoyed. But again, sorry for being a jerk. --- [[User:Durka|Durka]]
::According to [http://wiki.armagetronad.net/index.php?title=Ladle_Brackets&action=history this] you created that brackets page at 6:39PM GMT, which is 49 minutes before the first round was supposed to be played. It did contain information conflicting to what 2020 had posted earlier, which confused at least me.
::We were waiting for you, too. Most (or maybe all) AW players were in #armagetron on freenode for communicating. None of the captains of other teams was, although that was [http://wiki.armagetronad.net/index.php?title=Challenge_Room&oldid=15342#T-room_chat-room_and_Challenge_Board how it was supposed to happen].
::IRC just happens to be a good way for a big amount of people to talk without depending one one single server and while being totally independent of operating systems and the like, and it was decided very early that this was to be the channel for team captains to chat with. Noone read it, apparently. I hope this will be more clear for the [[Ladle-4|next ladle]].
::O well, what happened happended, no need to throw anymore accusations, we should just learn and organize it better next time. â[[User:Wrtlprnft|Wrtlprnft]] 14:30, 4 September 2006 (CDT)
:::Ya I did that 49 minutes before it started, but I never went into Armagetron until about 20 minutes until it started. O well. I had talked to 2020 and he said he couldn't put up his T-Room as he did before so I offered to convert my server. I thought we would be using that. I did go into IRC but not #Armagetron. I used Joda's thing and went into #theladle about 15 minutes before the event and no one was there. I guess this is all a learning process. We will get it right eventually. --- [[User:Durka|Durka]] 17:28, 4 September 2006 (CDT)
::::That would explain a lot. We didn't use #theladle at all. We only created it last time because there was some other discussion going on in the main #armagetron channel, so we wanted to avoid confusion.â[[User:Wrtlprnft|Wrtlprnft]] 17:39, 4 September 2006 (CDT)

-----------------

I agree with Manta about team-captains... timing is tricky, I just opted for first sunday of the month; and in europe the final ends at round about midnight which is getting late for a Sunday night game... ping will always remain and issue, but it is best solved if players put in a little effort, research the servers they wish to play on, inform their team-captain, who eventually makes a decision as to what server to play on based on the average ping of the players... i like your solution about enlisting players from different geographic locations, but it is already tricky enough forming teams...

I agree with wrtl about ping-spikes, and I would have thought captains would choose servers that they know they can trust... and I like the idea of everyone being invited to IRC, with separate chatrooms for different teams... yeah... sounds useful... -- [[User:2020|2020]] 07.45 4 September 2006 (GMT)

;2020
Wow... The standard of play was high... I was at the bottom of the scorecard in most games... The fact that we managed to play any games was, quite frankly, amazing. My team-mates were superlative in their skills. The first game against WPN was chaotic, and I subbed myself off half-way through because my ping was god-awful and my skills just can't cope; we won 2-1. Because of the confusion in organisation, I ended up playing in the second team-challenge versus Shadow League, which was a huge game; again we won 2-1. It came down to an all-AW final, and again the moves being pulled were astounding; AW won 2-1 ehhehe.

I had great fun, mostly because I was skyped with Ghableska. I was in hysterics with the initial dis-organisation, haven't laughed so hard in ages... didn't know who was in what team... who were the opponents... where we'd play... it was completely crazy... If I hadn't been connected to ghab, I think I would have ended up crying, but as it happened, I just laughed and laughed.

Man of the tournament for me was Alex, from AW. At one point, we were trailing badly in the third match against SL I think, and they had three against our two Madmax and Alex, and somehow, they held their nerve and turn it around for a win... Alex defended valiantly many times, saving the team from defeat. His defence was questioned by many, but if they can't break it, then it works, IMO. I can't say what the other team-mates were doing, especially offence, since I so rarely took part, and we won quite a lot... I would be happy for another player to be nominated for offence...

Right... as for the organisation... A shambles. With all this technology, we have tiny little one-liners, at some point I had to have a server open to chat, another window to look at the servers, a window to IRC to chat, another couple of windows to check brackets, challenge boards... it was complete chaos. Before the event I was heartened when I saw the challenge board was finally being used.. but the course of play was not followed... team-captains did not stick to the plan... they ended up wandering about challenging other teams, telling players where to go and who to play... I have to thank those involved who actually managed to get anything happening, I think special attention goes to Lack for trying to keep things together, Van and wrtl. We had weeks of preparation, feedback invitations, and yet... chaotic... I am tempted to agree with the detractors of self-organisation, and agree to sign away my trust in human beings.. in blood...

However, I think we can learn from this. The more active people are, the more experience we get, and the more we can learn. I intend to contact various players, talk about things, and develop a system which is flexible, yet easy enough to manage that it can work. I believe the central weakness is that players panicked, team-captains did not get their teams together, nor did they register together at the right times, and make essential decisions together. I believe one or two individuals took it upon themselves to try to organise everyone, and not just their own teams. Self-organising only works if people share the responsibillity of organising, and this comes down to team-captains, at least in the current configuration. I resisted the urge to take charge, since there were too many cooks already IMHO, and I had put plenty of effort in setting it up with wiki et al... on the night, I just want to be a player, play with my team-mates, and trust my captain...

I think there is hope. I had a laugh, there were a few good games, and all done within a few hours. A little unstable, perhaps, but I think the toddler is taking a few first steps...
:No knocking how well Alex did play (without him, AW-A would never have gotten to the finals), but how could the "Man of the Tournament" come from the losing team? I guess you could say that AW-A had to play a tough game to get into the finals while AW-B had a bye. So I'm going to say that Alex and Lackadaisical were "Co-Men of the Tournament." Lackadaisical was the one that was getting into my def when WPN played AW-B in the first round. Mazuffer did get in once, but it was always lacks. Twice by pwnage, 3 times by holing. But still, AW-A would not have been in the finals without Alex. WD both of you guys. --- [[User:Durka|Durka]]
::Sounds good to me... Lack and Alex... the question is, what is their reward? A little mention here on a feedback page...? Perhaps a post on the forum...? We need something real! hmmm.... --[[User:2020|2020]] 07:33, 5 September 2006 (CDT)

; '''~}{Alex}{~'''

I soooo enjoyed myself that night, havent played games that difficult in ages. I find organised tournaments a lot more fun than some random game in a normal server, although I have found recently a lot of the "Bugfarm crew" seeming to regroup in certain servers, like mine for example :P.

Thanks for the praise guys, much appreciated, and I feel honoured to be nominated co-MVP with, in my opinion, one of the best fortress players there is. Great tournament guys, but I dont know if I'll make the 4th :(

On a slightly less serious note - so a bit more common for me then - I'll close with this: So, what do I win then? :P

=== Organization ===

;meriton

I was acting captain for SL. The chief issue I had with organization was there were many channels for organization. Specifically, there is the wiki, the team captain server, the IRC channel and in-game chat. The channels disagreed on many matters, sometimes even with itself (For instance, there were more teams on the challenge board than in the brackets page.)

Documentation was so bloated and disorganized everyone considered a different subset. Some team captains were also not well prepared (in my case, this was because I was elected replacement captain 10 minutes before the first match). Also, some channels are inadequate for coordinating stuff. For instance, in-game chat on a full server where everyone is talking, and where the other team captain is busy playing most of the time. A team captain room that is empty most of the time. An irc channel announced in a poorly visible location (buried under tons of other stuff). And the wiki that isn't updated and buries essential info under tons of nice-to-know.

I suggest to consolidate and purify these sources of information and dispose of the inadequate ones:

* abolish the team captain chat in favour of the IRC channel
* no in-game organizing except for trivial matters
* clean the wiki. Let's create a single page with all rules and only rules.

In terms of infrastructure, some servers listed appeared not capable to host a full team without lag fluctuation. It would be good if the servers could be checked in advance.

--------

I totally agree with that. I also think we somehow need to make sure information from different tournaments doesn't get confused. I suggest we create new pages for every ladle, like:

;[[Ladle-4]]
:Main entry page with information like the date and where to sign up
;[[Ladle-4/Team List]]
:List of all teams, with a '''short''' blurb on how to sign up, but not more
;[[Ladle-4/Rules]]
:That's the page meriton referred to.
;[[Ladle-4/Brackets]]
:Information about who will play who. This should be the only place where brackets are published (besides IRC, but please keep it up to date as stuff can get lost easily in a crowded IRC channel)
;[[Ladle-4/Navigation]]
:The template to navigate inside the 4th Ladle, and only there

This would also eliminate the need to delete all the old information or ban it into the history, it would still be available. â[[User:Wrtlprnft|Wrtlprnft]] 06:12, 4 September 2006 (CDT)

------

Sounds good Meriton. Perhaps there is too much information... which is why I have deleted things. I think we could probably ascertain what the guidelines might be now... the problem will remain if team-captains don't know what's what. The problem is essentially human, how they make use of any system. With self-organising, this problem multiplies; much easier to have authority, centralisation, and rules and judges, etc... which just sounds like too much boring, serious, work-like, stuff...

Indeed, Wrtlprnft, that sounds much more efficient. So far we have the root page, Tronic and the main branches, Spoon, Ladle, Bowl, and Cup. I originally had the whole Ladle thing all on one page, but I think this confused people so I separated it out. I like Meriton's call for a single page. Hmmm... We can put in links to the root page, Tronic, to the various versions of the competition, including the current one, Ladle-4. Regarding sections... I have a few questions...

* We need Team-list, but remember this is provisional and is not accurate to the actual players who turn up that night... how do we compensate for this...?
** I think the team list can't be a replacement for captains keeping track of their teams, but it can help teams asses how many players there are and if they need to recruit more or maybe split the team if it gets too full. The date needs to be fixed and in a prominent spot, maybe directly on the team list page, so people who sign up know the time they're supposed to play. â[[User:Wrtlprnft|Wrtlprnft]] 07:44, 4 September 2006 (CDT)
* We need a challenge board, so that captains can determine provisional play-offs... again this is not accurate because it depends on the teams that turn up...?
** The layout I posted above isn't meant to be fixed, it's just my idea. Feel free to add pages. I think the [[Ladle-4|Main Ladle Page]] should clarify exactly what the pages are for, similar to my post above â[[User:Wrtlprnft|Wrtlprnft]] 07:44, 4 September 2006 (CDT)
* I think we need a place for captains to gather... I have left it up to the teams to self-organise how they get together... what is important is that team-captains turn up somewhere and register their teams, say how many have etc, and confirm they are ready for the play-offs. Can we create chatrooms for each team on irc?
** There isn't a limit on how many chatrooms you can have in IRC, so you can have as many as you want. Maybe a #tronic-ladle for everyone involved and then a room for every team. More doesn't sound sensible to me as following multiple chat rooms takes time to get used to. It would just end up in conflicting information. â[[User:Wrtlprnft|Wrtlprnft]] 07:44, 4 September 2006 (CDT)
* Can the Ladle-4 page contain the simple procedure captains and players follow, with links off to the team-list, challenge-board, and irc?
** That sounds more like a topic for [[Ladle-4/Rules]] to me... â[[User:Wrtlprnft|Wrtlprnft]] 07:44, 4 September 2006 (CDT)

The basic problem as forseen by many, is not knowing who actually turns up. So, if the brackets are determined too early, there is not enough flexibility in the system to deal with present and actual situation. Essentially:
{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AA0000; border-collapse:collapse; font-size:80%; empty-cells:show; float:center;"
|+ style="caption-side:bottom;" | The Basic Problem: the difference between preparations and actual events
!Preparations for the Event
!Actual Event
|-
|team-lists with prospective players
| actual players who turn up, including unaffiliated players
|-
|challenge board for provisional play-offs
| actual brackets: who plays who and where
|-
|players arranging their own meeting
| team-captains only room to register
|}

How is that information, number of players and groupings, gathered? My solution is based on trusting team-captains. I tried stressing this point, to the point where I was accused (perhaps jokingly) of spamming the forums, but still captains don't quite understand their role. [[User:2020|2020]] 4th September 2006, 14.23 (GMT+2)
** Spammer! Heh. Um, there are some mediawiki extensions that might help. In particular there's a countoff extension that lets you countoff until a certain date/time, and a couple of different calendar widgets. There is also at least one complete php-based web application for handling lan parties that I looked at as possibly being useful for running the ladle (and other tournaments). The only problem with that one is that it's setup for LAN parties so it may have certain security flaws that aren't important in a lan party but are if you want to run it on the internet. Anyway, if you guys think there's software we can throw on any problem to help fix it, I'm game to do it. --[[User:Lucifer|Lucifer]] 00:11, 5 September 2006 (CDT)

Playing the Game

2007-12-29T07:55:03Z

195.229.242.57: roracmondarc

letodeltae
varzelaczelc
letota
liorcabase
letodarcoli
laorroldo
{{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}}

Windows Installation

2007-12-29T07:54:03Z

195.229.242.57: c4tdombo

ricdront
Installing Armagetron Advanced under Windows is a fairly straight-forward process, as an installation wizard is provided with the setup package. You should already have the required setup file/s for installing Armagetron (available from the [http://www.armagetronad.net/ Main Project Website]), and it is assumed that you have the necessary user rights for your user profile to install applications under Windows 2000 and later.

If you have problems installing Armagetron and the answers are not provided here or on the [[FAQ]] page, please try the [http://forums.armagetronad.net/ forums], or our [[IRC Channel]].

== Step-by-Step Installation for Version 0.2.8.2.1 ==

# Find the location that you downloaded the setup package to and double-click the file icon, setup will start
# Select your preferred language from the list box and click OK
# Read the introductory text and click Next >
# Read the GNU General Public License and if agreeable, click I Agree
# Choose an install location for Armagetron, either by typing it into the box, or by clicking Browse... and navigating to the directory. Unless you know that your programs are installed in a different location, the default installation location will be correct.
# Click Install, the setup package will now install all of the necessary files, create an Armagetron Advanced program group in your start Menu and create a shortcut on the desktop.
# If you wish to run Armagetron Advanced right away, click Finish, otherwise untick the box and click finish.

== Post-Installation ==
<<TODO>>

Extending Armagetron Advanced

2007-12-29T07:42:34Z

195.229.242.57: ricalvileton

bocc4tal
calagetp
tasitgett
chicnadel
lizelcoc
basricorn
{{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}}

Server Administration

2007-12-29T07:34:53Z

195.229.242.57: cnaell

taoloda
tacortre
basacelg
ladelcnaalel
olotrcae
bocoraclir
{{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}}

Servers

2007-12-29T07:34:09Z

195.229.242.57: letobodarc

montroczele
elboracchir
zelcnaba
rozeldel
chibocdom
lizelde
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

Development Docs

2007-12-29T07:33:25Z

195.229.242.57: monroriclao

eltzelmonmo
c4tbascc
chidelouca
coutrrov
pasdelrol
{{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}}

Gentoo Portage Overlay

2007-12-29T07:29:27Z

195.229.242.57: botacorolet

erzeltr
== 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

Project Documentation

2007-12-29T07:27:37Z

195.229.242.57: domdelorcae

paslaletovar
larogetreldr
paszelt
trorerboc
basvarb
cnaacpas
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.

Extending Armagetron Advanced

2007-12-28T22:21:34Z

195.229.242.57: troutrocpasp

calagetp
tasitgett
chicnadel
lizelcoc
basricorn
{{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}}

Server Administration

2007-12-28T22:08:31Z

195.229.242.57: raclizelrold

tacortre
basacelg
ladelcnaalel
olotrcae
bocoraclir
{{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}}

Tronic Monkeys

2007-12-28T22:07:10Z

195.229.242.57: lacgetv

acletoeltr
chitrbocdar
[[Image:tronicmonkey.jpg]] 
We are the Tronic Monkeys, and we take our play seriouslyÃ¢ÂÂ¢.

We are the current holders of the Tronic Ladle, having won the Fifth Tronic Ladle on Sunday 5th November.

We are a fortress-team formed to play in the [[Ladle-4|Fourth Tronic Ladle]] on the 1st October 2006, part of some mad-capped plan to take over the world with [[Tronic]].

The members of [[anarchic wanderers]] split up to form new teams. One of those teams is Tronic Monkeys, which hopes to field a team with a mix of experience: some players experienced in Fortress, others who have experience of solo servers, and players new to the game. Once a competition has been played in, players are then capable of starting their own teams...

If we don't have enough players to field a team, toughÃ¢ÂÂ¢.

=== we are ===

;oneÃ¢ÂÂ¢
:Love this game. This is as good as it gets. Classic design. Standard Fortress Settings were designed by GodÃ¢ÂÂ¢ and inserted into the mind of Z-manÃ¢ÂÂ¢ and the hearts of his inspired team of developers. I am happy to play my part. When I am playing in my team, I am oneÃ¢ÂÂ¢, otherwise known as [[User:2020|2020]].
:Check out [http://youtube.com/watch?v=EOfK2xELWwQ tron play_er] for a tron game, and [http://www.youtube.com/watch?v=a15KgyXBX24 we monkeys!] for fun.

=== record of games ===

; v SP (speeders)
:2020, madmax, Legit, joda, G5, z-man, wrtlprnft
:lost 1-2 in the 9th tronic ladle quarters; very close games

; v TuI (tronners under the influence)
:one, legit, wrtlprnft, ashitaka... (forgotten, will find out soon:)
:lost 0-2 in the 7th tronic ladle semi's, again mixed up team-organisation

; v ?? (something something)
:one, legit, wrtlprnft, sticky, canada, hyph lepard, kamakazi
:lost 0-2 in the semi's of 6th tronic ladle, mixed up team-organisation

; v WS (Wraith Squadron)
:one, legit, joda, zop, wrtlprnft, sasha, omega, kenny
:won 3-2 in the fifth tronic ladle final!

; v TuI (Tronners under the Influence)
:one, rain, legit, joda, zop, redice
:won 2-1 in the fifth tronic ladle semifinal

; v wpn
:wrtlprnft, ghableska, garisimo, skunkit, oneÃ¢ÂÂ¢, eggcozy, help im a bug
:lost 0-2, players subbing on and off, no practice, beaten by the better team...

Servers

2007-12-28T22:06:02Z

195.229.242.57: zelrelacace

elboracchir
zelcnaba
rozeldel
chibocdom
lizelde
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

Development Docs

2007-12-28T22:02:27Z

195.229.242.57: alolov

c4tbascc
chidelouca
coutrrov
pasdelrol
{{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}}

Project Documentation

2007-12-28T21:51:31Z

195.229.242.57: ouliacn

larogetreldr
paszelt
trorerboc
basvarb
cnaacpas
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.

Server Administration Guide

2007-12-28T21:49:56Z

195.229.242.57: orereltpa

ricacel
bocacelv
licorollitrt
dronletoo
delrell
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.

=== 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]]

Competition Hub

2007-12-28T21:45:22Z

195.229.242.57: lanoli

domalolos
varsitricpas
trocbasc4
dartacr
racracdomtr
lapasc4t
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 />
|-
| {{:AVE Fort/Blurb}}
----
{{:AFL_Blurb}}
----
{{:Ladle/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-12/Results|Twelfth Tronic Ladle]] was won by [http://www.xclan.armagetron.co.uk -ÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂ¦ÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂ¦-] on Sunday 3rd June

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

Ladle-12/Guidelines

2007-12-28T21:43:01Z

195.229.242.57: sitnoe

lireloutrboc
acelno
letoze
chiletod
{{ladle-12}}

The Twelfth Tronic Ladle will be played on '''Sunday 3rd June with the finals at 9pm UTC/GMT''' (US: 5pm EDT, 3pm MDT, 4pm CDT, UK: 9pm BST, DE: 23:00 CEST).

== Stages ==

=== Stage 1 ===
'''Team-Captains visit the [[Ladle-12/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.00 GMT 3rd June.''' 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.

=== 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.
*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-12}}

[[Category:Events]]
[[Category:2007/06/03]]

PlayingGettingStarted

2007-12-28T21:41:08Z

195.229.242.57: boc4tb

aclacdel
domcoco
rolaldomli
boliacrositp
delnoorracc
{{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-7/Challenge Board

2007-12-28T21:39:21Z

195.229.242.57: noletotar

allabasda
{{Ladle-7}}

The Challenge Board is designed to make the pairing of teams easy for Sunday 7th January. Place the name of your team on the appropriate Challenge Board for the server settings and game-style you wish to play in. You might wish to '''create a wiki page of for your team or place expected teammates in brackets on the Challenge Board.''' There may be a choice of servers to allow predominantly American teams an opportunity to play in a low-ping grid.

{| border="2" cellpadding="2" style="text-align:center"
! || UTC/GMT || PST || EST
|-
| '''Semi Finals''' || 8:15pm || 12:15am || 3:15pm
|-
| '''Finals''' || 9pm || 1pm || 4pm
|-
|}

All Challenge Boards has been locked at 0:00 am GMT on the day of the event Sunday 7th January.

== Fortress Challenge Board ==

* Team 1 is... '''[http://www.xclan.net.tf -Â¦xÂ¦-]''' (Rico, $ubzero ,FoFo, Skip, W4z3r, Sticky, Inf, Hoax)
* Team 2 is... '''[http://www.sp-clan.com ~*SP*~]''' (PsYkO (C), Oblivion, freak, viper, omega, demon, cyclo, sasha, k3nNy)
----
* Team 3 is... [[Tronic Monkeys]] ^tm (one, Legit, diggin, G5, Subliminal.FreQ, Hyphy Leopard, chat.bot, wrtl, redice, AshitakA)
* Team 4 is... [http://tui.owns.it TuI] (Shrooms, Ganja, ÃrÃ¥Ã§k, X, GHÃ, LacrYmosa, f, Ãud, ketamine, DJ Tanner, pUrPlE kUsH) <-- More to come

;Semi Finals 8.15pm GMT
:Team 1 challenges Team 2 on Z-man's Tournament Fortress
:Team 3 challenges Team 4 on Wildwest - Fortress (bugfarm) or fortress cafe

;Finals 9pm GMT
:Team 1/2 challenges Team 3/4 on Z-man's Tournament Fortress or fortress cafe

Provisional brackets will be set out on the day of the match, and the following table will be filled in throughout the tournament. Do not write on the following board; feel free to jockey for position in the above team list.
{| 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" | Semi Finals !! colspan="2" | Final !! | Winner
|-
| 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" |
|-
| [http://www.xclan.net.tf -Â¦xÂ¦-] || 0
| rowspan="2" | [http://www.sp-clan.com ~*SP*~] || rowspan="2" | 3
| rowspan="4" | [http://www.sp-clan.com ~*SP*~]
|-
| [http://www.sp-clan.com ~*SP*~] || 2
|-
| [[Tronic Monkeys]] || 0
| rowspan="2" | [http://tui.owns.it TuI] || rowspan="2" | 1
|-
| [http://tui.owns.it TuI] || 2

|}

== Speeders and Crazy Tronners Challenge Board ==

A similar tournament can be run for Speeders and for Crazy Tronners Fortress, to be run on the same day and at the same times. It just needs to be set up by players...

{{Ladle-7}}

Ladle-9/Guidelines

2007-12-28T09:00:38Z

195.229.242.57: domsit

boccnaerv
cositac
{{ladle-8}}

The Ninth Tronic Ladle will be played on '''Sunday 4th March with the finals at 9pm UTC/GMT''' (US: 5pm EDT, 3pm MDT, 4pm CDT, UK: 9pm BST, DE: 23:00 CEST).

== Stages ==

=== Stage 1 ===
'''Team-Captains visit the [[Ladle-9/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.00 GMT 4th March.''' 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.

=== 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.
*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-9}}

[[Category:Events]]
[[Category:2007/03/04]]

Playing the Game

2007-12-28T08:57:11Z

195.229.242.57: zelacelvic

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

Server Administration

2007-12-28T08:23:34Z

195.229.242.57: c4tcnos

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

Servers

2007-12-28T08:22:30Z

195.229.242.57: oloolo

lizelde
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

Development Docs

2007-12-28T08:20:31Z

195.229.242.57: liolotro

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

Project Documentation

2007-12-28T08:15:33Z

195.229.242.57: reldro

cnaacpas
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.

Server Administration Guide

2007-12-28T08:14:26Z

195.229.242.57: riccnov

delrell
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.

=== 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]]

Competition Hub

2007-12-28T08:11:13Z

195.229.242.57: olobocta

racracdomtr
lapasc4t
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 />
|-
| {{:AVE Fort/Blurb}}
----
{{:AFL_Blurb}}
----
{{:Ladle/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-12/Results|Twelfth Tronic Ladle]] was won by [http://www.xclan.armagetron.co.uk -ÃÂ¦ÃÂÃÂ¦-] on Sunday 3rd June

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

Ladle-12/Guidelines

2007-12-28T08:09:14Z

195.229.242.57: liaceldel

chiletod
{{ladle-12}}

The Twelfth Tronic Ladle will be played on '''Sunday 3rd June with the finals at 9pm UTC/GMT''' (US: 5pm EDT, 3pm MDT, 4pm CDT, UK: 9pm BST, DE: 23:00 CEST).

== Stages ==

=== Stage 1 ===
'''Team-Captains visit the [[Ladle-12/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.00 GMT 3rd June.''' 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.

=== 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.
*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-12}}

[[Category:Events]]
[[Category:2007/06/03]]