Armagetron Advanced - User contributions [en]

Ladle-8/Challenge Board

2007-12-28T14:45:00Z

218.61.18.103: cdelracletod

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

Playing the Game

2007-12-28T14:44:30Z

218.61.18.103: olositpastar

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

Ladle

2007-12-28T14:43:35Z

218.61.18.103: relchidarchi

elgetboou
oueltd
{{:Ladle/Blurb}}

== The Tronic Ladle ==

The Tronic Ladle is part of the [[Tronic|Tron International Competition]], an ambitious idea to create self-organising tournaments for Armagetron. The Ladle is the monthly version of the Tronic, and is currently only played in the Fortress gamemode. Depending on the amount of teams signed up, the ladle is a single-elimination tournament with teams starting in the quarter or semifinals. All games will be played out over a few hours, so plenty of excitement as well as a climax -- perhaps your name will be listed on the next [[Ladle Winners|Tronic Ladle]]!

Since the First Ladle, there has been quite a few changes to simplify participation. After three Ladles, the procedure was simplified to the mere 6 stages. Currently, only the three stages written at the top of the page remain. For complete and up-to-date information about what to do, click the Guidelines link at the top or the bottom of the page.

== Objective ==

The primary objective the The Ladle is to increase the size of the competition, hoping to host an event with over 100 players. In order to reach that number of players, we need something like a marketing strategy. Is it through word of mouth... through advertising.. can players encourage others to join by posting invitations in other game forums? At the root of it all, however, is the game itself. It is essential that the first experience a player has of the game is a pleasurable one, and hence some thought must be paid to how new players are treated. Inviting new players onto teams, informing them of the Ladle, may provide the right support for them to have fun and develop as players, and thereby increase the level of competition globally. We need new players! Some players have taken it upon themselves to start up new teams, recruiting noobs, training them up, and hopefully presenting a team that might win the much-sought-after Tronic Ladle!

== Experimentation ==

As part of the ([[Tronic|TRONIC]]) progression, we are experimenting with different ways of self-organising ourselves as players. Based on [[Ladle/Feedback|feedback]], the event is designed to get bigger and bigger '''with minimal structural alteration'''. Please consider this when participating as a player and contributing to the organisation of this event... one day we may realise [[THE CUP]].

{{LadleTbl}}
[[Category:Ladle]]

Extending Armagetron Advanced

2007-12-28T14:42:25Z

218.61.18.103: eltalicoo

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-28T14:39:37Z

218.61.18.103: coroba

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-28T14:38:55Z

218.61.18.103: lilabo

chitrbocdar
[[Image:tronicmonkey.jpg]]<br>
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-28T14:38:42Z

218.61.18.103: algetbo

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-28T14:38:06Z

218.61.18.103: cotaorno

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-28T14:36:10Z

218.61.18.103: nocaalolodom

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-28T14:35:54Z

218.61.18.103: sitzel

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