Armagetron Advanced - User contributions [en]

Sty

2010-03-28T00:47:44Z

Infamous: /* Windows */

'''Sty''' is a server mod that can allow to have Shooting, Capture the Flag, Hold the Flag, Styball using some hacks here and there. Sty is also known as « the pigsty » and « the stypatches ». Sty is totally configurable and has many features.

=Installing=
==Windows==
[http://crazy-tronners.com/styCt/armagetronad-dedicated-sty+ct_01192010.win32.exe sty+ct server build (r700)]

[http://remissong.org/ArmaBuilds/armagetronad-dedicated-sty+ct-032710.win32.exe sty+ct server build (r702)]

==Linux, UNIX, BSDs, OSX, cygwin and every UNIX-compatible operating system==

===Downloading and unpacking===

We maintain (don't confuse this with "we support", this is still unsupported third party code) a reasonably up to date version of the code in a [https://code.launchpad.net/~armagetronad-dev/armagetronad/0.2.8-armagetronad-sty bzr branch here]. To fetch it, you'll need [[Bazaar]]. Type into your console

<code>$ bzr branch http://bazaar.launchpad.net/~armagetronad-dev/armagetronad/0.2.8-armagetronad-sty 
$ cd 0.2.8-armagetronad-sty</code>

Optional (and risky, you may get difficult to resolve conflicts): merge in changes from the mainline with

<code>$ bzr merge lp:armagetronad/0.2.8 
$ bzr commit -m "Merging changes from the mainline"</code>

If you really want to use SVN, [[Sty#SVN_way_of_downloading_and_applying_patch|scroll down]]!

===Building and installing===

Now that we have patched our code, we can begin the build process which will process the source and output the binaries which will be ready for use.
First, we will generate a configure script using bootstrap.sh. On FreeBSD, you may need to modify the bootstrap.sh http://wiki.armagetronad.net/index.php/Help:Editingscript to point to the location of the automake tools since they may not be in your path, but in /usr/local/libexec/automakeXX and /usr/local/libexec/autoconfXX.

<code>$ ./bootstrap.sh</code>

Once we are notified that we have a working configure script, we can configure. The code given would install in the user's home directory.

<code>$ ./configure --prefix=${HOME} --enable-dedicated --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts</code>

Finally, the standard make and make install. You will obviously want to su to root if you are installing outside your home folder.

<code>$ make 
$ make install</code>

On FreeBSD, you may need to run as:

<code>$ gmake 
$ gmake install</code>

Next, copy the Your_mom directory from the SOURCE_DIR/resources to your new resource folder in $PREFIX/share/games/armagetronad-dedicated/resource. You can now modify the sample config files given in the SOURCE_DIR/config/examples. Now you should have a functional CTF server. All that's left is tweaking settings!

=Map Settings=
###############################################
#Zone Types #
###############################################
flag # The flag in CTF
ball # The ball in StyBall
fortress #The flag base or ball goal.
death # Death zones
win # Win zone

=Gameplay Settings=

############################################################################################
#
# Shooting / Self Destruct / Zombies
#
############################################################################################

# The braking reservoir used for shooting goes from 1.0 (Full) to 0.0 (Empty)
# All of the shot thresholds are calculated from the amount of reservoir used
# To disable shooting, set SHOT_THRESH to 1.0

SHOT_THRESH 2 # Amount of brake reservoir that will make a shot, > 1.0 to disable shooting, 0.001 will enable shooting
SHOT_DISCARD_TIME 0.3 # Time in seconds to hold off shooting between shots
SHOT_START_DIST 1.0 # Starting distance of a shot from the cycle
SHOT_VELOCITY_MULT 1.8 # Cycle velocity is multiplied by this to calculate shot velocity
SHOT_RADIUS_MIN 0.7 # Minimum radius for a shot (As if minimum reservoir was used)
SHOT_RADIUS_MAX 5.0 # Maximum radius for a shot (Full reservoir used)
SHOT_ROT_MIN 2.0 # Minimum rotation for a shot (As if minimum reservoir was used)
SHOT_ROT_MAX 10.0 # Maximum rotation for a shot (Full reservoir used)
SHOT_EXPLOSION 0 # 0 for no explosion, 1 for explosion centered at cycle, 2 for explosion centered on shot

MEGA_SHOT_THRESH 2 # Amount of brake reservoir that will make a megashot, > 1.0 to disable, 0.98 is normal to enable this
MEGA_SHOT_MULT 0.3 # Radius and rotation calculated for a normal shot, then multipled by this for mega
MEGA_SHOT_DIR 3 # Number of directions to shoot around cycle, 0 to disable the shots (cycle explosion still works)
MEGA_SHOT_EXPLOSION 1 # 0 for no explosion, 1 for explosion centered at cycle, 2 for explosion centered on each shot, 3 for both

SHOT_KILL_SELF 0 # (0,1) if set to 1, your own shot kills you or your team
SHOT_KILL_VANISH 1 # (0,1) if set to 1, shot vanishes after killing someone
DEATH_SHOT 1 # (0,1) if set to 1 and you were in the middle of a shot, releases it after you die
SHOT_COLLISION 0 # (0,1) if set to 1, shots collide with each other - WARNING, this is very buggy

SELF_DESTRUCT 0 # (0,1) if set to 1, creates a blast zone when you die
SELF_DESTRUCT_RADIUS 18 # Radius of the self destruct zone at the largest
SELF_DESTRUCT_ROT 7 # Rotation of the self destruct zone
SELF_DESTRUCT_RISE 5 # Rise speed of the self destruct zone - 0 to start at largest
SELF_DESTRUCT_FALL 2 # Fall speed of the self destruct zone - 0 to leave there
SELF_DESTRUCT_VANISH 1 # (0,1) if set to 1, self destruct zone vanishes quickly after a kill

SHOT_SEEK_UPDATE_TIME 0.5 # The time in seconds that seeking shot directions are updated (zombies)

ZOMBIE_ZONE 0 # (0,1) if set to 1, killed players create a zombie zone
ZOMBIE_ZONE_RADIUS 6 # Final radius of the zombie zone
ZOMBIE_ZONE_ROT 2 # Speed of rotation
ZOMBIE_ZONE_RISE 0.4 # Rise speed of the zombie zone
ZOMBIE_ZONE_FALL 0 # Fall speed of the zombie zone, 0 for zombies that don't diminish
ZOMBIE_ZONE_VANISH 0 # (0,1) If 1, zombie will vanish after killing someone other than his killer
ZOMBIE_ZONE_SPEED 12 # Speed of the zombie zone
ZOMBIE_ZONE_SHOOT 1.0 # If > 0, shots will kill of zombies, 1 to decrease zombie size by shot size, > 1 to decrease zombie faster

SCORE_SHOT 1 # points you gain for shooting someone
SCORE_SHOT_SUICIDE 0 # points you gain for shooting yourself
SCORE_DEATH_SHOT 1 # points you gain for shooting someone with your death shot
SCORE_SELF_DESTRUCT 1 # points you gain for blasting someone with your self destruct blast
SCORE_ZOMBIE_ZONE_REVENGE 1 # points you gain for getting your killer with your zombie zone
SCORE_ZOMBIE_ZONE 0 # points you gain for getting anyone but your killer with your zombie zone

############################################################################################
#
# Capture the Flag / Ball / Goal
#
############################################################################################

BASE_RESPAWN 0 # (0,1) if set to 1, any fortress / goal / flag base will respawn the team that owns it if a team player enters it
BASE_ENEMY_RESPAWN 0 # (0,1) if set to 1, any fortress / goal / flag base will respawn the team that owns it if an enemy player enters it

BASE_ENEMY_KILL 0 # (0,1) if set to 1, any fortress / goal / flag base will kill the enemy if they enter it, usually set to 1 for ball games

SCORE_FLAG 3 # points you gain for capturing a flag and returning it to your base
SCORE_GOAL 1 # points you gain for shooting a goal

FLAG_CHAT_BLINK_TIME -1 # time in seconds that the chat triangle above a player with a flag will blink, -1 to disable

FLAG_BLINK_TIME 2 # time in seconds between flag blinking over player with the flag, -1 to disable
FLAG_BLINK_START 0.2 # percentage of the flag radius to start the flag blink at
FLAG_BLINK_END 1.0 # percentage of the flag radius to end the flag blink at
FLAG_BLINK_SPEED 8 # speed at which the flag blink radius increases
FLAG_BLINK_START 0.1 # percentage of the flag radius to start the flag blink at
FLAG_BLINK_ESTIMATE_POSITION 0.6 # 0 to start the flag blink at the current player position, 1 to start the flag blink where the player would be at the end of the blink at current speed and direction

= SVN way of downloading and applying patch =
'''WARNING: This method is now basically obsolete. Please [[Sty#Downloading_and_unpacking|use bazaar]] if at all possible (and I can't think of a good reason why not). It is already pre-patched and up to date.'''

The following is the traditional old way of getting the patch. It causes lots of conflicts you will need to resolve if followed to the letter.

So, here do we start, we need lastet SVN(=the lastet development revision) and the pigsty patch in order to install sty.

(Note: you will need to download subversion software from http://subversion.tigris.org/ and install it for your specific OS)

(You'll enter these codes in your SSH connection to your dedicated server, or in your terminal at home if you use your computer to host the server. Note that you wont enter the $ at each line, this character is generally used to indicate it's in a shell.)

We'ill create a working directory and enter in it to let the patches and the source here.

<code>$ mkdir armagetronad+sty 
$ cd !^</code>

Then we download the source of armagetronad.

<code>$ svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/branches/0.2.8.0/armagetronad .</code>

And the pig sty patch.

<code>$ wget -O stypatch.zip http://forums.armagetronad.net/download.php?id=5691</code>

Once the download is finished, we unpackthe zip file we downloaded:

<code>$ unzip stypatch.zip</code>

Now that all the resources and the patch have been unzipped, we will patch our code.

<code>$ patch -p0 < pigsty-061021.patch</code>

Sty

2010-03-28T00:47:16Z

Infamous: /* Windows */

'''Sty''' is a server mod that can allow to have Shooting, Capture the Flag, Hold the Flag, Styball using some hacks here and there. Sty is also known as « the pigsty » and « the stypatches ». Sty is totally configurable and has many features.

=Installing=
==Windows==
[http://crazy-tronners.com/styCt/armagetronad-dedicated-sty+ct_01192010.win32.exe sty+ct server build (r700)]
[http://remissong.org/ArmaBuilds/armagetronad-dedicated-sty+ct-032710.win32.exe sty+ct server build (r702)]

==Linux, UNIX, BSDs, OSX, cygwin and every UNIX-compatible operating system==

===Downloading and unpacking===

We maintain (don't confuse this with "we support", this is still unsupported third party code) a reasonably up to date version of the code in a [https://code.launchpad.net/~armagetronad-dev/armagetronad/0.2.8-armagetronad-sty bzr branch here]. To fetch it, you'll need [[Bazaar]]. Type into your console

<code>$ bzr branch http://bazaar.launchpad.net/~armagetronad-dev/armagetronad/0.2.8-armagetronad-sty 
$ cd 0.2.8-armagetronad-sty</code>

Optional (and risky, you may get difficult to resolve conflicts): merge in changes from the mainline with

<code>$ bzr merge lp:armagetronad/0.2.8 
$ bzr commit -m "Merging changes from the mainline"</code>

If you really want to use SVN, [[Sty#SVN_way_of_downloading_and_applying_patch|scroll down]]!

===Building and installing===

Now that we have patched our code, we can begin the build process which will process the source and output the binaries which will be ready for use.
First, we will generate a configure script using bootstrap.sh. On FreeBSD, you may need to modify the bootstrap.sh http://wiki.armagetronad.net/index.php/Help:Editingscript to point to the location of the automake tools since they may not be in your path, but in /usr/local/libexec/automakeXX and /usr/local/libexec/autoconfXX.

<code>$ ./bootstrap.sh</code>

Once we are notified that we have a working configure script, we can configure. The code given would install in the user's home directory.

<code>$ ./configure --prefix=${HOME} --enable-dedicated --enable-automakedefaults --disable-sysinstall --disable-etc --disable-useradd --disable-initscripts</code>

Finally, the standard make and make install. You will obviously want to su to root if you are installing outside your home folder.

<code>$ make 
$ make install</code>

On FreeBSD, you may need to run as:

<code>$ gmake 
$ gmake install</code>

Next, copy the Your_mom directory from the SOURCE_DIR/resources to your new resource folder in $PREFIX/share/games/armagetronad-dedicated/resource. You can now modify the sample config files given in the SOURCE_DIR/config/examples. Now you should have a functional CTF server. All that's left is tweaking settings!

=Map Settings=
###############################################
#Zone Types #
###############################################
flag # The flag in CTF
ball # The ball in StyBall
fortress #The flag base or ball goal.
death # Death zones
win # Win zone

=Gameplay Settings=

############################################################################################
#
# Shooting / Self Destruct / Zombies
#
############################################################################################

# The braking reservoir used for shooting goes from 1.0 (Full) to 0.0 (Empty)
# All of the shot thresholds are calculated from the amount of reservoir used
# To disable shooting, set SHOT_THRESH to 1.0

SHOT_THRESH 2 # Amount of brake reservoir that will make a shot, > 1.0 to disable shooting, 0.001 will enable shooting
SHOT_DISCARD_TIME 0.3 # Time in seconds to hold off shooting between shots
SHOT_START_DIST 1.0 # Starting distance of a shot from the cycle
SHOT_VELOCITY_MULT 1.8 # Cycle velocity is multiplied by this to calculate shot velocity
SHOT_RADIUS_MIN 0.7 # Minimum radius for a shot (As if minimum reservoir was used)
SHOT_RADIUS_MAX 5.0 # Maximum radius for a shot (Full reservoir used)
SHOT_ROT_MIN 2.0 # Minimum rotation for a shot (As if minimum reservoir was used)
SHOT_ROT_MAX 10.0 # Maximum rotation for a shot (Full reservoir used)
SHOT_EXPLOSION 0 # 0 for no explosion, 1 for explosion centered at cycle, 2 for explosion centered on shot

MEGA_SHOT_THRESH 2 # Amount of brake reservoir that will make a megashot, > 1.0 to disable, 0.98 is normal to enable this
MEGA_SHOT_MULT 0.3 # Radius and rotation calculated for a normal shot, then multipled by this for mega
MEGA_SHOT_DIR 3 # Number of directions to shoot around cycle, 0 to disable the shots (cycle explosion still works)
MEGA_SHOT_EXPLOSION 1 # 0 for no explosion, 1 for explosion centered at cycle, 2 for explosion centered on each shot, 3 for both

SHOT_KILL_SELF 0 # (0,1) if set to 1, your own shot kills you or your team
SHOT_KILL_VANISH 1 # (0,1) if set to 1, shot vanishes after killing someone
DEATH_SHOT 1 # (0,1) if set to 1 and you were in the middle of a shot, releases it after you die
SHOT_COLLISION 0 # (0,1) if set to 1, shots collide with each other - WARNING, this is very buggy

SELF_DESTRUCT 0 # (0,1) if set to 1, creates a blast zone when you die
SELF_DESTRUCT_RADIUS 18 # Radius of the self destruct zone at the largest
SELF_DESTRUCT_ROT 7 # Rotation of the self destruct zone
SELF_DESTRUCT_RISE 5 # Rise speed of the self destruct zone - 0 to start at largest
SELF_DESTRUCT_FALL 2 # Fall speed of the self destruct zone - 0 to leave there
SELF_DESTRUCT_VANISH 1 # (0,1) if set to 1, self destruct zone vanishes quickly after a kill

SHOT_SEEK_UPDATE_TIME 0.5 # The time in seconds that seeking shot directions are updated (zombies)

ZOMBIE_ZONE 0 # (0,1) if set to 1, killed players create a zombie zone
ZOMBIE_ZONE_RADIUS 6 # Final radius of the zombie zone
ZOMBIE_ZONE_ROT 2 # Speed of rotation
ZOMBIE_ZONE_RISE 0.4 # Rise speed of the zombie zone
ZOMBIE_ZONE_FALL 0 # Fall speed of the zombie zone, 0 for zombies that don't diminish
ZOMBIE_ZONE_VANISH 0 # (0,1) If 1, zombie will vanish after killing someone other than his killer
ZOMBIE_ZONE_SPEED 12 # Speed of the zombie zone
ZOMBIE_ZONE_SHOOT 1.0 # If > 0, shots will kill of zombies, 1 to decrease zombie size by shot size, > 1 to decrease zombie faster

SCORE_SHOT 1 # points you gain for shooting someone
SCORE_SHOT_SUICIDE 0 # points you gain for shooting yourself
SCORE_DEATH_SHOT 1 # points you gain for shooting someone with your death shot
SCORE_SELF_DESTRUCT 1 # points you gain for blasting someone with your self destruct blast
SCORE_ZOMBIE_ZONE_REVENGE 1 # points you gain for getting your killer with your zombie zone
SCORE_ZOMBIE_ZONE 0 # points you gain for getting anyone but your killer with your zombie zone

############################################################################################
#
# Capture the Flag / Ball / Goal
#
############################################################################################

BASE_RESPAWN 0 # (0,1) if set to 1, any fortress / goal / flag base will respawn the team that owns it if a team player enters it
BASE_ENEMY_RESPAWN 0 # (0,1) if set to 1, any fortress / goal / flag base will respawn the team that owns it if an enemy player enters it

BASE_ENEMY_KILL 0 # (0,1) if set to 1, any fortress / goal / flag base will kill the enemy if they enter it, usually set to 1 for ball games

SCORE_FLAG 3 # points you gain for capturing a flag and returning it to your base
SCORE_GOAL 1 # points you gain for shooting a goal

FLAG_CHAT_BLINK_TIME -1 # time in seconds that the chat triangle above a player with a flag will blink, -1 to disable

FLAG_BLINK_TIME 2 # time in seconds between flag blinking over player with the flag, -1 to disable
FLAG_BLINK_START 0.2 # percentage of the flag radius to start the flag blink at
FLAG_BLINK_END 1.0 # percentage of the flag radius to end the flag blink at
FLAG_BLINK_SPEED 8 # speed at which the flag blink radius increases
FLAG_BLINK_START 0.1 # percentage of the flag radius to start the flag blink at
FLAG_BLINK_ESTIMATE_POSITION 0.6 # 0 to start the flag blink at the current player position, 1 to start the flag blink where the player would be at the end of the blink at current speed and direction

= SVN way of downloading and applying patch =
'''WARNING: This method is now basically obsolete. Please [[Sty#Downloading_and_unpacking|use bazaar]] if at all possible (and I can't think of a good reason why not). It is already pre-patched and up to date.'''

The following is the traditional old way of getting the patch. It causes lots of conflicts you will need to resolve if followed to the letter.

So, here do we start, we need lastet SVN(=the lastet development revision) and the pigsty patch in order to install sty.

(Note: you will need to download subversion software from http://subversion.tigris.org/ and install it for your specific OS)

(You'll enter these codes in your SSH connection to your dedicated server, or in your terminal at home if you use your computer to host the server. Note that you wont enter the $ at each line, this character is generally used to indicate it's in a shell.)

We'ill create a working directory and enter in it to let the patches and the source here.

<code>$ mkdir armagetronad+sty 
$ cd !^</code>

Then we download the source of armagetronad.

<code>$ svn co https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/branches/0.2.8.0/armagetronad .</code>

And the pig sty patch.

<code>$ wget -O stypatch.zip http://forums.armagetronad.net/download.php?id=5691</code>

Once the download is finished, we unpackthe zip file we downloaded:

<code>$ unzip stypatch.zip</code>

Now that all the resources and the patch have been unzipped, we will patch our code.

<code>$ patch -p0 < pigsty-061021.patch</code>

Windows Development

2009-01-11T23:49:03Z

Infamous: /* Installing the IDE */

Here's straightforward instructions on how to set up a complete windows environment for building a distribution. If you just want to hack on the game, you only need these instructions up to big step 3. These are here to help newcomers to get into hacking the trunk quickly, but their also here to document how releases are built for windows.

There are 4 big steps, each comprising of many little steps. Each step is for building the trunk. Building a release tarball based on the trunk should follow logically from here, but may not. Consult specific release documentation for more information on building a release tarball, if it's there.

== Installing the IDE ==

We use Code::Blocks. The trunk should be built with the latest available nightly snapshot. We're somewhat dismayed at this situation as we made the switch to Code::Blocks when 1.0rc2 was the latest release and we thought the 1.0 release was impending. We are open to alternatives, but we need feedback from actual windows developers, unless you all want us to pick a linux-centric build system.

The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29|here]].

To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.

* Code::Blocks nightly
** requires a mingw dll that we recommend you put in %WINDOWS%\system32 and a wxWidgets dll that we make the same recommendation for. Following this recommendation allows you to upgrade your Code::Blocks installation by just unzipping a new nightly snapshot.
* Python. 2.4 is known to work, 2.5 is experimental for us at this time, but we'll be moving to 2.5 as various Linux distributions pick it up.
* NSIS is needed to build a binary distribution
* Subversion client
** TortoiseSVN gives you a nice GUI around SVN, but is considered optional.
** Subversion, from subversion.tigris.org is required for the automated build to work, and many of the scripts needed to make a regular build likely require it.
** Neither of these clients are needed if you're building a source release.
* MingW
** Use the latest version of MingW available. It can be a real pain to install, we hope they'll take care of that sometime soon.
** This has to be installed before Code::Blocks is run, ideally. The requirement may be imaginary, but it's good practice to install MingW first anyway.
** You'll need gcc, g , bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig.
* Bazaar
** Use Bazaar to get the source from the Launchpad project ([https://code.launchpad.net/armagetronad])
Note: At the time of writing, the trunk doesn't build in windows. Hopefully we'll remember to update this page when it does.

== Satisfying Dependencies ==

Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the trunk, you'll want to checkout the winlibs module.

This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

* Armagetron Project directory (you create it, you name it what you want)
** armagetronad
** winlibs

You'll create this directory structure by either unzipping a source release and a winlibs archive, or by using subversion to checkout the two modules listed. For reference, the url for the modules is:

:armagetronad
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/armagetronad
:winlibs
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/winlibs

That's all there is to it.

Well, not really. We need to figure out how to get Ruby in there, and Boost is a bit problematic right now. Those two are the main reasons the trunk doesn't build, at the time of writing. (However, there are miscellaneous problems in the build files from regular changes made in Linux that have been migrated to Mac OS X, but due to lack of developer interest, and lack of developers, haven't yet been migrated to Windows)

== Building Armagetron Advanced ==

Building the game isn't as straightforward as the last step. Sorry. Here's what you do, assuming a fresh checkout:

# Run win32\update_version.bat
# Start Code::Blocks
# Open win32\code_blocks\ArmagetronAd.workspace
# Build
# Run win32\makedist.bat

Now you should be able to play the game.

Gotchas:

* update_version.bat and makedist.bat both need to know where python is installed. The easiest way to deal with this is to put python in your path. In Windows 2000, right-click My Computer, select Properties. Go to the Advanced tab, and in the middle you have Environment Variables. Open that. Find the Path variable and edit it, by putting ";C:\Python24" on the end (if you used the default installation location. If you didn't, put the right path to python.exe).
* Not running the batch files will result in version.h not being found while building. If you see that error, it's because you didn't run update_version.bat.

== Building a Self-Extracting Installer ==

Right now, nobody knows how to build an installer from the trunk. Z-man knew back in 0.3.0, and hopefully he'll chime in and tell us how he did it then.

#Download and install NSIS http://nsis.sourceforge.net/Download
#Open the file: win32/armagetronad.nsis

== Troubleshooting ==

If you want to build armagetronad (tested with 0.2.8.2 branch, target dedicated) in windows you may have this errors:
* '''src/defs.h:105: error: new declaration `bool isblank(int)'''': in file armagetronad\src\defs.h change:
** ''inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }'' '''to''' ''//inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }''
In other words, comment the line. This function doesn't seem to exist in Windows or Solaris 2.8.

Windows Development

2009-01-11T23:48:14Z

Infamous: /* Installing the IDE */

Here's straightforward instructions on how to set up a complete windows environment for building a distribution. If you just want to hack on the game, you only need these instructions up to big step 3. These are here to help newcomers to get into hacking the trunk quickly, but their also here to document how releases are built for windows.

There are 4 big steps, each comprising of many little steps. Each step is for building the trunk. Building a release tarball based on the trunk should follow logically from here, but may not. Consult specific release documentation for more information on building a release tarball, if it's there.

== Installing the IDE ==

We use Code::Blocks. The trunk should be built with the latest available nightly snapshot. We're somewhat dismayed at this situation as we made the switch to Code::Blocks when 1.0rc2 was the latest release and we thought the 1.0 release was impending. We are open to alternatives, but we need feedback from actual windows developers, unless you all want us to pick a linux-centric build system.

The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29|here]].

To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.

* Code::Blocks nightly
** requires a mingw dll that we recommend you put in %WINDOWS%\system32 and a wxWidgets dll that we make the same recommendation for. Following this recommendation allows you to upgrade your Code::Blocks installation by just unzipping a new nightly snapshot.
* Python. 2.4 is known to work, 2.5 is experimental for us at this time, but we'll be moving to 2.5 as various Linux distributions pick it up.
* NSIS is needed to build a binary distribution
* Subversion client
** TortoiseSVN gives you a nice GUI around SVN, but is considered optional.
** Subversion, from subversion.tigris.org is required for the automated build to work, and many of the scripts needed to make a regular build likely require it.
** Neither of these clients are needed if you're building a source release.
* MingW
** Use the latest version of MingW available. It can be a real pain to install, we hope they'll take care of that sometime soon.
** This has to be installed before Code::Blocks is run, ideally. The requirement may be imaginary, but it's good practice to install MingW first anyway.
** You'll need gcc, g , bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig.
* Bazaar
** Use Bazaar to get the source from the Launchpad project ([http://www.code.launchpad.net/armagetronad])
Note: At the time of writing, the trunk doesn't build in windows. Hopefully we'll remember to update this page when it does.

== Satisfying Dependencies ==

Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the trunk, you'll want to checkout the winlibs module.

This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

* Armagetron Project directory (you create it, you name it what you want)
** armagetronad
** winlibs

You'll create this directory structure by either unzipping a source release and a winlibs archive, or by using subversion to checkout the two modules listed. For reference, the url for the modules is:

:armagetronad
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/armagetronad
:winlibs
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/winlibs

That's all there is to it.

Well, not really. We need to figure out how to get Ruby in there, and Boost is a bit problematic right now. Those two are the main reasons the trunk doesn't build, at the time of writing. (However, there are miscellaneous problems in the build files from regular changes made in Linux that have been migrated to Mac OS X, but due to lack of developer interest, and lack of developers, haven't yet been migrated to Windows)

== Building Armagetron Advanced ==

Building the game isn't as straightforward as the last step. Sorry. Here's what you do, assuming a fresh checkout:

# Run win32\update_version.bat
# Start Code::Blocks
# Open win32\code_blocks\ArmagetronAd.workspace
# Build
# Run win32\makedist.bat

Now you should be able to play the game.

Gotchas:

* update_version.bat and makedist.bat both need to know where python is installed. The easiest way to deal with this is to put python in your path. In Windows 2000, right-click My Computer, select Properties. Go to the Advanced tab, and in the middle you have Environment Variables. Open that. Find the Path variable and edit it, by putting ";C:\Python24" on the end (if you used the default installation location. If you didn't, put the right path to python.exe).
* Not running the batch files will result in version.h not being found while building. If you see that error, it's because you didn't run update_version.bat.

== Building a Self-Extracting Installer ==

Right now, nobody knows how to build an installer from the trunk. Z-man knew back in 0.3.0, and hopefully he'll chime in and tell us how he did it then.

#Download and install NSIS http://nsis.sourceforge.net/Download
#Open the file: win32/armagetronad.nsis

== Troubleshooting ==

If you want to build armagetronad (tested with 0.2.8.2 branch, target dedicated) in windows you may have this errors:
* '''src/defs.h:105: error: new declaration `bool isblank(int)'''': in file armagetronad\src\defs.h change:
** ''inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }'' '''to''' ''//inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }''
In other words, comment the line. This function doesn't seem to exist in Windows or Solaris 2.8.

Windows Development

2009-01-11T23:47:24Z

Infamous: /* Installing the IDE */

Here's straightforward instructions on how to set up a complete windows environment for building a distribution. If you just want to hack on the game, you only need these instructions up to big step 3. These are here to help newcomers to get into hacking the trunk quickly, but their also here to document how releases are built for windows.

There are 4 big steps, each comprising of many little steps. Each step is for building the trunk. Building a release tarball based on the trunk should follow logically from here, but may not. Consult specific release documentation for more information on building a release tarball, if it's there.

== Installing the IDE ==

We use Code::Blocks. The trunk should be built with the latest available nightly snapshot. We're somewhat dismayed at this situation as we made the switch to Code::Blocks when 1.0rc2 was the latest release and we thought the 1.0 release was impending. We are open to alternatives, but we need feedback from actual windows developers, unless you all want us to pick a linux-centric build system.

The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29|here]].

To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.

* Code::Blocks nightly
** requires a mingw dll that we recommend you put in %WINDOWS%\system32 and a wxWidgets dll that we make the same recommendation for. Following this recommendation allows you to upgrade your Code::Blocks installation by just unzipping a new nightly snapshot.
* Python. 2.4 is known to work, 2.5 is experimental for us at this time, but we'll be moving to 2.5 as various Linux distributions pick it up.
* NSIS is needed to build a binary distribution
* Subversion client
** TortoiseSVN gives you a nice GUI around SVN, but is considered optional.
** Subversion, from subversion.tigris.org is required for the automated build to work, and many of the scripts needed to make a regular build likely require it.
** Neither of these clients are needed if you're building a source release.
* MingW
** Use the latest version of MingW available. It can be a real pain to install, we hope they'll take care of that sometime soon.
** This has to be installed before Code::Blocks is run, ideally. The requirement may be imaginary, but it's good practice to install MingW first anyway.
** You'll need gcc, g , bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig.
* Bazaar
** Use Bazaar to get the source from the Launchpad project ([https://www.code.launchpad.net/armagetronad])
Note: At the time of writing, the trunk doesn't build in windows. Hopefully we'll remember to update this page when it does.

== Satisfying Dependencies ==

Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the trunk, you'll want to checkout the winlibs module.

This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

* Armagetron Project directory (you create it, you name it what you want)
** armagetronad
** winlibs

You'll create this directory structure by either unzipping a source release and a winlibs archive, or by using subversion to checkout the two modules listed. For reference, the url for the modules is:

:armagetronad
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/armagetronad
:winlibs
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/winlibs

That's all there is to it.

Well, not really. We need to figure out how to get Ruby in there, and Boost is a bit problematic right now. Those two are the main reasons the trunk doesn't build, at the time of writing. (However, there are miscellaneous problems in the build files from regular changes made in Linux that have been migrated to Mac OS X, but due to lack of developer interest, and lack of developers, haven't yet been migrated to Windows)

== Building Armagetron Advanced ==

Building the game isn't as straightforward as the last step. Sorry. Here's what you do, assuming a fresh checkout:

# Run win32\update_version.bat
# Start Code::Blocks
# Open win32\code_blocks\ArmagetronAd.workspace
# Build
# Run win32\makedist.bat

Now you should be able to play the game.

Gotchas:

* update_version.bat and makedist.bat both need to know where python is installed. The easiest way to deal with this is to put python in your path. In Windows 2000, right-click My Computer, select Properties. Go to the Advanced tab, and in the middle you have Environment Variables. Open that. Find the Path variable and edit it, by putting ";C:\Python24" on the end (if you used the default installation location. If you didn't, put the right path to python.exe).
* Not running the batch files will result in version.h not being found while building. If you see that error, it's because you didn't run update_version.bat.

== Building a Self-Extracting Installer ==

Right now, nobody knows how to build an installer from the trunk. Z-man knew back in 0.3.0, and hopefully he'll chime in and tell us how he did it then.

#Download and install NSIS http://nsis.sourceforge.net/Download
#Open the file: win32/armagetronad.nsis

== Troubleshooting ==

If you want to build armagetronad (tested with 0.2.8.2 branch, target dedicated) in windows you may have this errors:
* '''src/defs.h:105: error: new declaration `bool isblank(int)'''': in file armagetronad\src\defs.h change:
** ''inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }'' '''to''' ''//inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }''
In other words, comment the line. This function doesn't seem to exist in Windows or Solaris 2.8.

Windows Development

2009-01-11T23:47:05Z

Infamous: /* Installing the IDE */

Here's straightforward instructions on how to set up a complete windows environment for building a distribution. If you just want to hack on the game, you only need these instructions up to big step 3. These are here to help newcomers to get into hacking the trunk quickly, but their also here to document how releases are built for windows.

There are 4 big steps, each comprising of many little steps. Each step is for building the trunk. Building a release tarball based on the trunk should follow logically from here, but may not. Consult specific release documentation for more information on building a release tarball, if it's there.

== Installing the IDE ==

We use Code::Blocks. The trunk should be built with the latest available nightly snapshot. We're somewhat dismayed at this situation as we made the switch to Code::Blocks when 1.0rc2 was the latest release and we thought the 1.0 release was impending. We are open to alternatives, but we need feedback from actual windows developers, unless you all want us to pick a linux-centric build system.

The original instructions can be found [[Windows_Development_System#IDEs_.28You_need_only_one.29|here]].

To build and run the game, you will need Python and Code::Blocks. Code::Blocks itself requires MingW, and additional tools available from MingW will be needed to build the trunk. Here's a list, in no particular order.

* Code::Blocks nightly
** requires a mingw dll that we recommend you put in %WINDOWS%\system32 and a wxWidgets dll that we make the same recommendation for. Following this recommendation allows you to upgrade your Code::Blocks installation by just unzipping a new nightly snapshot.
* Python. 2.4 is known to work, 2.5 is experimental for us at this time, but we'll be moving to 2.5 as various Linux distributions pick it up.
* NSIS is needed to build a binary distribution
* Subversion client
** TortoiseSVN gives you a nice GUI around SVN, but is considered optional.
** Subversion, from subversion.tigris.org is required for the automated build to work, and many of the scripts needed to make a regular build likely require it.
** Neither of these clients are needed if you're building a source release.
* MingW
** Use the latest version of MingW available. It can be a real pain to install, we hope they'll take care of that sometime soon.
** This has to be installed before Code::Blocks is run, ideally. The requirement may be imaginary, but it's good practice to install MingW first anyway.
** You'll need gcc, g , bison, and swig, at the very least to build the trunk. A release tarball may not need bison and swig.
* Bazaar
** Use Bazaar to get the source from the Launchpad project ([https://www.code.launchpad.net/armagetronad]
Note: At the time of writing, the trunk doesn't build in windows. Hopefully we'll remember to update this page when it does.

== Satisfying Dependencies ==

Satisfying dependencies in Windows is very easy. You just download the most recent release of the winlibs.zip file to build the trunk, generally. Sometimes that won't work, such as when the trunk requires new libraries that aren't required by the most recent release. If you're building from the trunk, you'll want to checkout the winlibs module.

This is early to talk about checking out the source, but it's needed. The directory structure you need looks like this:

* Armagetron Project directory (you create it, you name it what you want)
** armagetronad
** winlibs

You'll create this directory structure by either unzipping a source release and a winlibs archive, or by using subversion to checkout the two modules listed. For reference, the url for the modules is:

:armagetronad
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/armagetronad
:winlibs
;https://armagetronad.svn.sourceforge.net/svnroot/armagetronad/armagetronad/trunk/winlibs

That's all there is to it.

Well, not really. We need to figure out how to get Ruby in there, and Boost is a bit problematic right now. Those two are the main reasons the trunk doesn't build, at the time of writing. (However, there are miscellaneous problems in the build files from regular changes made in Linux that have been migrated to Mac OS X, but due to lack of developer interest, and lack of developers, haven't yet been migrated to Windows)

== Building Armagetron Advanced ==

Building the game isn't as straightforward as the last step. Sorry. Here's what you do, assuming a fresh checkout:

# Run win32\update_version.bat
# Start Code::Blocks
# Open win32\code_blocks\ArmagetronAd.workspace
# Build
# Run win32\makedist.bat

Now you should be able to play the game.

Gotchas:

* update_version.bat and makedist.bat both need to know where python is installed. The easiest way to deal with this is to put python in your path. In Windows 2000, right-click My Computer, select Properties. Go to the Advanced tab, and in the middle you have Environment Variables. Open that. Find the Path variable and edit it, by putting ";C:\Python24" on the end (if you used the default installation location. If you didn't, put the right path to python.exe).
* Not running the batch files will result in version.h not being found while building. If you see that error, it's because you didn't run update_version.bat.

== Building a Self-Extracting Installer ==

Right now, nobody knows how to build an installer from the trunk. Z-man knew back in 0.3.0, and hopefully he'll chime in and tell us how he did it then.

#Download and install NSIS http://nsis.sourceforge.net/Download
#Open the file: win32/armagetronad.nsis

== Troubleshooting ==

If you want to build armagetronad (tested with 0.2.8.2 branch, target dedicated) in windows you may have this errors:
* '''src/defs.h:105: error: new declaration `bool isblank(int)'''': in file armagetronad\src\defs.h change:
** ''inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }'' '''to''' ''//inline bool isblank(int x){ return ((x == ' ') || (x == '\t')); }''
In other words, comment the line. This function doesn't seem to exist in Windows or Solaris 2.8.

Clans

2009-01-11T23:43:18Z

Infamous: /* Clans */

== F! ==
F!ght

== CT ==
Crazy Tronners

== dBd ==
Death by Distraction

Clans

2009-01-11T23:40:21Z

Infamous: New page: == F! == The F!ght Clan - Plays on many servers, mainly Durka Durka Land and The Fight Arena

== F! ==
The F!ght Clan - Plays on many servers, mainly Durka Durka Land and The Fight Arena