Free survival software for linux

Invasion Battle of Survival us a futuristic real-time strategy game.
Bos Wars is a futuristic real-time strategy game. It is possible to play against human opponents over LAN, internet, or against the computer. It successfully runs under Linux and MS Windows. It should run on BSD, MacOS/X, MacOS/Darwin and BeOS.
Defend against your enemies and keep your economy running.
Bos Wars aims to create a completly original and fun open source RTS game.
Enhancements:
- The project changed its name into Bos Wars.
- The engine got merged into Bos Wars in order to ease and speed up the development.
- Support Lua 5.1

Foundation project is a real-time multi-player space conquest game.
OpenGL hardware support is recommended. Goals include researching new technology, colonizing distant planets, and fighting intense 3D fleet battles for survival.
Main features:
- colonization
- production of new units, facilities and ships
- research new technology to give you an edge
- space battles
Enhancements:
- more high-level network code (can now transfer fleet info)
- can now build ships
- wont crash if youre not connected to a server but try send a msg
- texture caching system
- fixed check for if a planet is building a certain structure
- slight changes to planetview and fleetview layout
- added more components to fleetview
- moved id to platform class, fleets and planets now both have IDs
- fleet movement mostly complete, still have to deal with deleting fleets
- fixed production bug, need resources now

Zombie Master project is a multiplayer survival horror FPS/RTS mod for Half-Life 2. A team of FPS-playing humans attempts to complete map-specific objectives while an RTS player controls the zombie horde with only one goal: death to all humans.
He is the Zombie Master.
Enhancements:
- [fix] Weapons were sometimes hard to pick up
- [fix] Fast shooting exploits in shotgun and rifle
- [tweak] Health indication in player identification display
- [tweak] ZM resource limit server setting zm_resource_limit (default 4000)
- [fix] Team changes (including to spectator after death) had erratic results
- [feature] Muting players
- [tweak] Weapon flags failed to reset in some situations after forcehuman/forcemaster team switching
- [fix] ZM preference window came up when the ZM camera toggled
- [fix] Zombie spawns could still be clicked when inactive
- [fix] Voting for roundrestart could be spammed
- [fix] DOTD chalkboard weirded out
- Plus minor fixes to the maps.
As usual, if your game goes horridly wrong after patching, try reinstalling with the 1.1.2 full installer.
UPDATE: If you experience the spectator bug after patching to 1.1.2, it is recommended you do a clean install using the full 1.1.2 installer.

IGE - Outer Space is an on-line strategy game with SciFi theme.

IGE - Outer Space is an on-line strategy game which takes place in the dangerous universe. You must become the commander of many stars, planets, and great fleets and you will struggle for survival with other commanders.

Outer Space communicates with the server in the same way as your browser, but you will need a special client to play it. Using this client you can create an account on the server and you can start to explore the world of the Outer Space.

wmlife is a program launcher dockapp.

Wmlife is a dock app running Conways Game of Life (and program launcher). Life is played on a grid of square cells where a cell can be either live or dead. In the rules, you count the number of live neighbours for each cell to determine whether a cell lives or dies;

Birth A dead cell with exactly three live neighbours becomes a live cell.

Survival A live cell with two or three live neighbours stays alive.
Overcrowding / Loneliness In all other cases, a cell dies or remains dead.
Normally Life is implemented on an infinite board but due to size restraints wmlife implements the grid as a torus. In a torus, the grid wraps at the edges from top to bottom and left to right.

Evocosm is a C++ Framework for Evolutionary Computing library.
Evocosm is a set of classes that abstract the fundamental components of an evolutionary algorithm. Ill list the components here with a bit of introduction; you can review the details of the classes by downloading the code archives or by reviewing the online documentation (see the menu at the articles beginning for code and documentation links.)
All class documentation was generated from source code comments using doxygen. These docs have not been thoroughly proofread, so they may contain a few typos and minor errors. Self-publishing has taught me the value of a good proofreader.
Evolutionary algorithms come in a variety of shapes and flavors, but at their core, they all share certain characteristics: populations that reproduce and mutate through a series of generations, producing future generations based on some measure of fitness. An amazing variety of algorithms can be built on that general framework, which leads me to construct a set of core classes as the basis for future applications.
The classes include:
Random Numbers
Evocosm relies on the code in The Twisted Road to to Randomness for random number generation. The Mersenne Twister algorithm is particularly well-suited to evolutionary algorithms, based on its long period, granularity, "randomness", and speed. As of the 2.1.0 release of libevocosm, the mtprng class resides in libcoyote, and not libevocosm as it did earlier. This means that any program using libevocosm must also link against libcoyote.
Validation
To validate function arguments, Evocosm uses the code I describe in Beyond Assert; this code is part of libcoyote. Any program using libevocosm must also link against libcoyote.
Floating- Point Chromosomes
Evcosom supports the crossover and mutation of IEEE-754 floating-point numbers, using an algorithm I invented in the mid-1990s. This topic is covered in detail here.
Roulette Wheels
The roulette_wheel class implements the concept of a "software roulette wheel" for Evocosm. This is a tool for natural selection, wherein the fitness of an organism determines the width of its "slot" on an imaginary roulette wheel.
Organisms
Think of an "organism" as an answer to a problem posed by a fitness landscape; "genes" define its behavior and an associated fitness value is assigned by an evocosm during testing. Evocosm provides the freedom to define organisms as almost anything: bit strings, floating-point numbers, finite state machines, LISP programs, or external robots controlled via radio waves. In A Complexity of Options, I used an Evocosm-derived GA to determine the gcc options that produce the faster code.
Fitness Landscapes
A "fitness landscape" defines the environment where organisms "live" or a problem that they are tested against. The landscape is intimately tied to the nature of the organism; think of an organism as a potential solution to a problem implemented by the landscape. A floating-point organism, for example, could be tested by a fitness landscape that represents a function to be maximized. Or, an organism describing the shape of wing could be tested by a landscape that simulates a wind tunnel.
Evocosms
The evocosm class binds a population of organisms to a set of objects that define the rules of survival and reproduction. An evocosm will have one or more populations, which will evolve against population-unique and shared (common) fitness landscapes; breeding is controlled by a set of class objects from the following classes.
Fitness Scaling
As a population converges on an "answer", the difference between fitness values often becomes very small; this prevents the best solutions from having a significant advantage in reproduction. Fitness scaling solves this problem by adjusting the fitness values to the advantage of the most-fit chromosomes. Evocosm includes a variety of fitness scaling algorithms.
Migration
A migrator removes individuals (via "emigration") from a population of organisms, transferring them to another population (via "immigration"). The only concrete implementation of this interface is random_pool_migrator, which defines a specific number of organisms that may migrate from each population to another. When creating a random_pool_migrator, specify the number of organisms that can migrate from each population. Migration is, of course, meaningless in any application that has only one population.
Selecting Survivors
A selector decides which organisms survive from one generation to the next. Some evolutionary algorithms will not use a selector; other will. In general, it is effective to keep the "best" organisms from one generation to the next, so that good genes do not become lost at random. This is, of course, an improvement on nature, where being "the best" doesnt guarantee survival.
Reproduction
In most cases, a reproducer generates new organisms using parents selected (by fitness) from an existing population. In some singular (and probably rare) cases, a reproducer might generate new, random organisms in order to keep diversity high. Reproduction techniques can include crossover and asexual, sexual and (my favorite) try-sexual models.
Mutation Operators
A mutator applies mutations (random, usually small changes) to a set of organisms. Mutation is highly dependent on the type of organism. In traditional genetic algorithms, a mutation flips one or more bits in an integer (i.e., chromosome). Evolving a path for the Traveling Salesman Problem involves complex mutations that maintain valid permutations of destination points; in the case of floating-point numbers, Ive provided utilities for mutating and crossing IEC-60559 (IEEE- 754) float and double types.
Enhancements:
- Minor bugfixes, code cleanups, and changes to pseudo-random number generators.
- Now includes Visual Studio 2005 projects along with GNU build files.