Armagetron Advanced - User contributions [en]

Project Documentation

2007-12-29T14:20:10Z

217.172.56.174: boligetr

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

Server Administration Guide

2007-12-29T14:18:57Z

217.172.56.174: libasalrolro

cdelerva
corelchi
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]]

Ladle-7/Challenge Board

2007-12-28T22:32:13Z

217.172.56.174: lasitb

lirele
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-12/Guidelines

2007-12-28T14:30:20Z

217.172.56.174: botrocric

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-28T14:29:19Z

217.172.56.174: dronzelpas

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-8/Challenge Board

2007-12-28T14:28:20Z

217.172.56.174: domact

erchicna
{{Ladle-8}}

The Challenge Board is designed to make the pairing of teams easy for Sunday 4th February with finals at 9pm UTC. 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
|-
| '''Quarter Finals''' || 7:30pm || 11:30am || 2:30pm
|-
| '''Semi Finals''' || 8:15pm || 12:15am || 3:15pm
|-
| '''Finals''' || 9pm || 1pm || 4pm
|-
|}

All Challenge Boards will be locked at 0:00 am UTC on the day of the event Sunday 4th February.

== Fortress Challenge Board ==

* Team 1 is... [http://www.oops-clan.org Â°Â°ps] (AshitakA, Redice, Manta, Hay-Lin, ÃÃ«Â®D, Plato)
* Team 2 is [http://www.sp-clan.com ~*SP*~] (k3nNy, PsYkO, Speed!, Sasha, freaky!, Obli, viper, whatup, demon, omega, cyclo, ...)
----
* Team 3 is... '''[http://www.xclan.net.tf -Â¦xÂ¦-]''' (FoFo,Hoax,$ubzero,W4z3r,inf,Sticky)
* Team 4 is...
----
* Team 5 is...
* Team 6 is...
----
* Team 7 is... [[Tronic Monkeys]]^tm (visit wiki page to get on the team... only 2020 so far )
* Team 8 is... [http://tui.owns.it TuI] (Crack, Shrooms, Lacrymosa, X, ketamine, GHÃ, SmAcK, f, purple kush, os, djt, ... ) <-- probably it

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px black; border-collapse:collapse; font-size:95%; empty-cells:show; text-align:center;"
! | Quarter Finals !! | Semi Finals !! | Final
|-
| style="border-bottom:3px double" | 7:30 PM UTC || style="border-bottom:3px double" | 8:15 PM UTC || style="border-bottom:3px double" | 9:00 PM UTC
|-
| style="border-bottom:0px" | none
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ Z-mans Fortress''' || style="border-left:0px" | result
|-
| style="border-top:0px" | none || style="border-bottom:0px" | Â°Â°ps
|-
||| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ Z-mans Fortress''' || style="border-left:0px" | 1-2 : ~*SP*~
|-
| style="border-bottom:0px" | none || style="border-top:0px" | ~*SP*~
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ 2020 team challenge''' || style="border-left:0px" | result
|-
| style="border-top:0px" | none || style="border-bottom:0px" | || style="border-bottom:0px" | ~*SP*~
|-
| style="border-right:0px" | || style="border-left:0px; border-top:0px; border-bottom:0px" | || style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ Z-mans fortress''' || style="border-left:0px" | 1-3 : TuI -- winners of 8th tronic ladle
|-
| style="border-bottom:0px" | none || style="border-top:0px" | || style="border-top:0px" | TuI
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ wild-west fortress''' || style="border-left:0px" | result
|-
| style="border-top:0px" | none || style="border-bottom:0px" | -Â¦xÂ¦-
|-
| || style="border-top:0px; border-bottom:0px; border-right:0x" | '''@ fortress cafe''' || style="border-left:0px" | 0-2 : TuI
|-
| style="border-bottom:0px" | none || style="border-top:0px" | TuI
|-
| style="border-top:0px; border-bottom:0px; border-right:0px" | '''@ fortress cafe''' || style="border-left:0px" | result
|-
| style="border-top:0px" | none
|}

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

AFL Calendar

2007-12-28T10:16:25Z

217.172.56.174: c4torracmont

sitzelo
{{AFLTbl}}

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

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

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

You can also get this calendar in some other ways:

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

Outcome

2007-12-28T09:49:47Z

217.172.56.174: letobo

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

'''Winner is Second Place Team'''

== Tilt 1 Outcome ==

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

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

== Pilot Tilt Outcome ==

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

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

PlayingGettingStarted

2007-12-28T09:48:51Z

217.172.56.174: taalc4t

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.