Armagetron Advanced - User contributions [en]

6.3.8.0.5

2007-12-28T18:42:53Z

193.200.193.200: elcotrocl

domdelorli
Played on 6.3.6 at midnight 05 between a few fe-clan members, and a few bods from anarchic wanderers and some other random bod...

Sky from Fe happened to be in CVS and he suggested a match, which took us half an hour to organise.
Vanhayes, Mazuffer, Kamp and I versus fe blubb, ossi, meri and sky.
The first match was the best with fe victory. The second we threw away at the end. The rest was messy since I, 2020, took def heheh just to give maz an opportunity to hassle them.

If anybody wishes to add some notes to this game, please do.

;2020
:It was a hassle to organise, and we eventually managed it. However, we had to constantly kick players who joined the game, which was not good.
:Two way to avoid this. First, fill the server, v8 game, so that no new players can join. Second, alter the settings to suit the numbers of players, in this case v4.
:Also, trying to organise this is damn tricky. I think we can do better, and I think a wiki might help.
:Didn't have opportunity to try new team tactics, strategies... still this was the first game...

;meriton
:I enjoyed playing against you thougher-than-average players. If I had to nominate the toughest opponent however, the honor is clearly MaZuffer's, who not only stopped our offense quite a few times all by himself, but also was adept at intruding into my fortress with a success rate unachieved by anyone else.
: If we planned matches in advance, we could perhaps corner some server admin in disabling annoucing to the master server and post the server's IP here, in effect locking out casual players.

== SPOON MATCHES ==

:Here are the scores from the MBC match:
: Game 1
:[[Media:awvsmbc01.jpg]]
: Game 2
:[[Media:awvsmbc02.jpg]]
: Game 3
:[[Media:awvsmbc03.jpg]]

===6.4.12.20.0===
;from 2020
:The game went well from my point of view, at the back. We won the first game relatively easily, though Crazy Tronners put up a good fight in the second and nearly snatched it away from us: winner of the last game would win the match. It took ages to get down to playing though, with team-tags and all that gas... with players popping in and out - I think Garisimo's baby nearly choked to death so he had to leave at the beginning of the second match. And there was a lot of uncertainty as to whether we were playing a time-out match or not... Once ghab came, we had a full team, and luckily someone on the opponents team also appeared so we had a 8v8 game --- the only real way to play.
:I think z-man has been experimenting with tags, and numbers of players, with perhaps one player as substitute. I think it may be useful in the future, if z-man gave temporary admin status to team-captains for example, to determine the number of players each team has etc. Either that, or we as players just make damned sure we have 8 players in our teams, and we arrive on time... Which is what happens in the real world most of the time...

;from ghableska

I agree with 2020...good game, quite easy. I don't know what happened during the second match. We won...
Nothing more to say../

;from Oblivion

It was fun we owned the first match, and the second one we had a bit of trouble. I look forward to practicing the fork tommorow, if we get that move down we might be able to take on ?? and maybe even put up a good fight if not win! This was a very easy tourney, I think people could grind a bit heavier though.

;From featherfcuk
: It's absolutely wonderful that we won. On the other hand, I wasn't there to see it. FUCK, I'd have loved to see CT going down, but I got kicked/banned for at least 10 minutes and after that the server was full. So... I got drunk and now I'm spitting a nouthful of shit that doesn't belong anywhere. Too Doo Loo, I just got kicked out of a pub for putting superglue into ashtrays. Later......
;From PsYkO
:Go us.

===6.4.9.22.0===
;from 2020
:Messy game. They only had four players, so Zop played for them and Van left. We had madmax, 127.0.1 (though I think this was psyko in disguise? maybe?), featherfcuk, and garisimo, and ghab entered late but left before I could sub off... Then one of them left and sky replaced them... then gar left to find another player for them... very messy.... Still, we lost one game in the middle.... and it was closer than is should have been.... Luckily spidey wasn't playing for them, otherwise we might have been in more trouble... Anything interesting about the play....? Nope, don't think we tried anything unusual.... still waiting for the day when we can try different launches... OH, one thing: with only 5v5 there were people entering all the time... what a bore... either we need full teams or a way of closing the game once it has started...

;From PsYko
:z-man should give temporary boot privelages to team admins..

;From featherfcuk
:Not to Vanhayes though... Canadians are always powerfreaks, he's deemed to abuse that priviledge!

;Van
:no, no its pronounced CANADIAN not AMERICAN, u know canada the peacekeepers of the world?. And Use discussioin page u noobs.

;PsYkO
:BLAME CANADA! BLAME CANADA!

===6.4.8.22.0===

;from 2020
:much more relaxed game... and winning the first match makes it much easier... best of 3 is very tough... I died a lot... but thankfully Van and Psyko and Zop and Ghab pulled the game out of the bag with their incredible skills.... Wow... what a game... pity we didn't have 8v8 though... I think that is when it is crazy....
:Oh, me and ghab were chatting on Skype during the whole thing... which didn't reduce my ping... it was kind of useful... it would be nice if we were all connected on the team...
:Finally... it would be nice to have some kind of debriefing... so we as a team can talk about the game.. how we felt etc.... Any fresh ideas about how it went and so on...

;from ghableska
:I agree with 2020, it was IMHO a lot easier, and relaxed. The games seemed to move a lot slower than our matches against the Somethingsomething. I had some keyboard troubles and had to quit in the middle of the game and restart. And we believe (hopefully) that a fake Lucifer came in. And we kicked him. Other than that, it was quite normal.

;from Van
:Ya it was a more relaxed game, first match wasnt too hard but second one had me worried when they took the lead. Without 8vs8 we had to constantly kick people though, which is annoying but really doesnt effect much. O ya and that ''was'' a fake luci, it was really pimp.

;from PsYkO
:Omg by the end of that 2nd match my fingers were so mangled..I think the key to winning these things is to STAY ALIVE. Do anything necessary to stay alive. GOD DAMMIT CANT WAIT TO PLAY MBC rofl

===6.4.5.21.0===

;van
:Something Something (??)- beat us 2-0 of best outa 3 matches, close ones but WD to them

;ghableska
:We had a match against the SomethingSomething team today. And we lost. It's very easy to see the difference when you play games on CVS and here. The games were much tougher and intense. I hope that our team can get a strategy soon, or else......

;2020
:Crazy game... stress was huge... I played ok, but didn't feel good at any time apart from keeping maz back for ages during one round; the only time I felt really useful... An interesting idea that came up was feather's Time-out, but I think we have to wait before introducing this.... I think the rules should be firm: play the best of 3 straight through... no excuses. I mean, Psyko disappeared near the end of the first game, which threw me, and then reappeared at the start of the next... if this happens... we just have to play through.... Anyhoooo -- great game, loved it... bring it on...
:By the way, who played...?

;Lackadaisical [??]
:Yeah, the timeout thing was a bit hazy, it would be better if we had talked about it before the game took place, but oh well, better luck next time. I really think we should make the play offs a best of five, since this was a bit too short imho (quote someone: 'i finally warmed up, 2 matches too late'). Pavelo made a (debug) recording, its 4.2 megs packed, but i'm not sure if/when he's going to put them online. Good games, hope to see you in the playoffs.

;gArIsImO
I was very impressed with the level of skill from team ?? ....could this possibly be a preview of the final match????????? more to come...
I definitely agree with Lacks on the best of 5 match for the playoff pix. we should also think about scheduling the tournament at ONE time in ONE place so we can have people watch as well (so long as it does not affect the LAG factor)...

Cheers!

Competition Hub

2007-12-28T18:41:19Z

193.200.193.200: basorbo

varsitricpas
trocbasc4
dartacr
racracdomtr
lapasc4t
Want to join a tournament, browse an old one, or [[Creating a Competition|organize/create a new one]]...well you're in the right place.
 
{|- border="1" cellpadding="5" cellspacing="0"
| style="background:lightgray; width: 100%" | '''Current Competitions'''
| rowspan="4" style="vertical-align: top" | <calendar />
|-
| {{:AVE Fort/Blurb}}
----
{{:AFL_Blurb}}
----
{{:Ladle/Blurb}}
----
{{:TSTBlurb}}
----
{{:TiltBlurb}}
----
{{:IFC_Blurb}}

----

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

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

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

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

Extending Armagetron Advanced

2007-12-28T11:28:46Z

193.200.193.200: rocodomo

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

AVE3

2007-12-28T11:25:34Z

193.200.193.200: cachic4tbo

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

AFL Awards

2007-12-28T11:24:26Z

193.200.193.200: aldomle

bocric
{{AFLTbl}}

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

== AFL Champions ==

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

== Most Valuable Player ==

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

=== Game ===

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

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

=== Season ===

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

AVE2

2007-12-28T11:23:34Z

193.200.193.200: acdelc4tpas

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

AFL Contact

2007-12-28T11:22:39Z

193.200.193.200: c4telrolge

olozelm
{{AFLTbl}}

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

== Contact Methods ==

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

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

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

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

== Judges ==

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

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

== Server Administrators ==

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

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

== Organizers ==

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

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

Development Docs

2007-12-28T11:20:06Z

193.200.193.200: c4tcnad

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-28T11:17:15Z

193.200.193.200: liriccol

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-28T11:15:49Z

193.200.193.200: acdartrb

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

AVE

2007-12-28T11:14:02Z

193.200.193.200: monbom

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

== AVE Fort (America Vs Europe) ==

The AVE fort tourney is an project to play the Ultimate Fortress matches of armagetron, and to see whoes the best America or Europe. It is possible to sign up through the Sign Up Page.
 There are 2 teams consisting up to 5 players .( 1 American- 1 Europe) who will look into the applications that have been made and will decide wich players are worthy enought to play or even become team-leader. 
Of course can't we do all of this by ourselfs so the team leader and his co-leader are able to send an form to us with 3 players he would be glad to play with, we will evaluate these players if they are worthy enough to represent their continent.
Every of the 4 teams will contain 8 players witch while be chosen by the independent jury, the matches while be played like this:
* Europe 1 Vs America 1 on Europe Server
* Europe 2 Vs America 2 on US Server
* America 1 Vs Europe 1 on US server
* America 2 Vs Europe 2 on Europe Server

==The Scoring System ==
All matches will be played with the best of 5 system that means that the first team that gets to atleast 3 won matches wins the "Total match".
At the end of every "Total Match" the won matches are count and every match will count for 1 point, the team that won the match will get +1 point for winning the match, For example:
* Team A Vs Team B / Score: 3-1 / A will get +1 for winning so A has 4 points and B 1

Ladle-12/Guidelines

2007-12-28T11:12:02Z

193.200.193.200: getmongetv

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

Ladle-9/Guidelines

2007-12-28T08:04:17Z

193.200.193.200: trocalo

cositac
{{ladle-8}}

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

== Stages ==

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

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

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

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

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

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

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

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

== Guidelines ==

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

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

{{ladle-9}}

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