Free rush software for linux

Create your own Viking chieftain (or chieftess), sail on quests to foreign places, challenge other online players to battle and then go spend your loot on more Viking gear!

Enhancements:

• Number of players on each island shown on the Hall map.
• Players can create their own rooms in the Hall.
• The Lur Blaster will no longer lose energy if he is stunned while playing a tune.
• Initial cease-fire period reduced in treasure games to avoid tower axemen rushing.

Requirements: Java 2 Standard Edition Runtime Environment

Rush 2005 is a football game using SDL.

Rush 2005 is a BSD-licensed project to create an American football game for Windows and Linux in the tradition of Tecmo Bowl and NFL Blitz, built using the cross-platform SDL game programming library.

TTraffic project is a Tcl/Tk version of the game Rush Hour created by Binary Arts Coporation.

The goal is to remove the red car from the grid through the slot on the right. To do this you, have to slide the other cars out of the way.

TTraffic is inspired by GTraffic, the Gnome version Rush Hour.

TTraffic comes with about 15.000 puzzles ranging from intermediate to expert. These puzzles were automatically created by the program gtlevel.

TTraffic has been tested on Linux, Macintosh, Windows and Windows NT.

Glotski project is a sliding block puzzle game.
Glotski is a game in which you drag blocks around until you attain inner peace or reach the desired goal, whichever comes first.
Its a very generalized version of "Rush Hour" , and also resembles the game Klotski.
Enhancements:
- Interface spruced up, with menu, status line
- Added Goal window to show you what youre supposed to do
- Many bugs fixed (Undoing previous goals, correct Gnome setup)
- Still to do: add ability to resize, add ability to use pixmaps for pieces, perhaps add some antialiased effects (i.e. transparent drag), make some UI tweaks for better Gnome compliance

PyTraffic is a computer version of the board puzzle Rush Hour invented by the famous puzzle designer Nob Yoshigahara and commercialized by Binary Arts Corporation.
The goal of PyTraffic project is to remove the red car out of the grid through the slot on the right. To do this you have to slide the other cars out of the way. PyTraffic is written in the scripting language Python.
Playing the game on a real board is much more fun than playing it on the computer (ask my daughter!). So after having used PyTraffic you may consider buying the real thing.
Main features:
- PyTraffic comes with about 19.000 puzzles ranging in difficulty from "Intermediate" to "Expert".
- In addition it is possible to play "Trivial" and "Easy" levels which are generated on the fly. These are suitable for small children. My six year old daughter Sarah routinely does "Easy" puzzles.
- PyTraffic has a help facility which is able to find the best move in every position. It is available through a button on the toolbar.
- PyTraffic comes with several "themes". Some of the themes have a 3D-look. Making your own themes is not very hard.

a2b project is an abstract train game.
You guide trains to their destination without letting them collide with each other.
Each game is played on a set of tracks on which trains run at regular intervals. You click-pick a train and accelerate, brake or stop as necessary to safely guide it to its destination.
As trains are continously launched, more than 1 train will want to use the same section of a track potentially leading to a collision.
You resolve this by making a train wait while you rush another train or even cancel a train by sending it back to its base.
When you despatch 100 trains, a level is complete. 2 more tracks are added to the network and the game continues.
a2b controls:
- Click on or near a train to select it. Only 1 train can be selected at anytime.
- Press UP arrow key to accelerate the selected train.
- Press DOWN arrow key to brake (and reverse) the selected train.
- Press LEFT or RIGHT arrow key to stop the selected train.
- You can use W, S, A and D instead of UP, DOWN, LEFT and RIGHT arrow keys.
- Right click to pause the game.
- ESC to abort or quit the game.
- Use the Level Browser at the bottom of the main menu to choose a level to play.

rndCiv (Random Civ) are randomized rulesets for Freeciv.

If you play freeciv a lot, youll probably start to find that the games start to become the same, they blur into each other and after a while even though you love the game it starts to become boring and too easy.

Well i did, each game becomes a rush to The Republic, Gunpowder and Steam Engine. And one reason for that is that the techtree becomes totally sussed out. But techtrees are arbitrary anyway, and in another slightly different world they would be different. Sure you can download mod packs, but the problem reappears, after a while you learn their techtree, and youre back to square one.

rndCiv, is a solution to this problem. What rndCiv does is blend different genres together to produce unique (but still playable) techtrees. Its not random like Monarchy and Radio lead to Genetic Engineering, that would be silly. Its random like, Sailing could come from Boating, Map Making, Seafaring, Astronomy, or Craftsmanship. So pick two and get on with it.

Because the Techs, Units, Buildings and Governments are bundled into different generas, then you can get rndCiv to build a techtree (with related Units, Buildings & Governments) for whatever set of generas youd like to play with. Its a Meta-Modpack.

This code is beta, it works, it occasionally crashes the server (so save often), it also crashes the client (when you look up the help system for some units - weird), and its rules need to be fine-tuned.

Quick Start:

For a quick intro, try this command

./rndCiv.pl random4

then read the rulesets in the ./ouput dir

what i do, is symlink the output dir to freeciv/data/rnd and set rulesetdir to rnd

The ruleset.summary file gives a qick overview of the ruleset.

The techtree.dot file can be fed into the dot graph generator....

dot -Tps -o techtree.ps techtree.dot
gv techtree.ps

Then start civ..

./civ --tiles=rnd

and when in the civ server control mode, set the rule dir

/rulesetdir rnd

add other game options to suit, and start

PyRPM is an experimental project to look at rpm package management. It is a python module and a collection of scripts that provide similar functionality as rpm, yum and co. It is written from ground up and is implemented only in python. PyRPM project mainly deals with rpm packages, the rpm database rpmdb in /var/lib/rpm, comps.xml files and yum repositories (called repo data).
The reason for this project was to have a codebase with which we can test and verify rpm, rpmdb and yum itself and experiment with new features and implementations very quickly. Python is Red Hats in-house defacto standard, so using python to do rapid prototyping was only logical.
The code itself is still very small and modular. Were constantly looking to improve the code, make it more production ready and remove duplicate functionality. Results from this project back to rpm and co are very important for us to improve the current available Linux tools and not rush with only adding another project for this. Next to working on good algorithms and sane implementations, most code is backed up with verify and testing scripts.
Warning
The PyRPM project is by no means meant to be a full replacement of rpm or yum. In its current state we feel confident that in general it wont break anything, but the code isnt production quality yet.
The check scripts can be safely used as they wont modify anything on your system, so feel free to use them at your convenience.
We personally have been using the yum replacement very extensively and even used it to update our own systems, but thats not even remotely a guarantee that it will work on your machine. It has only been run by a few people until now.
Using it to set up buildroots on the other hand should be very safe as this all happens in a very contained environment (sandbox principle).
Please let us know of any problems you encounter, if possible with some reproducible test cases so we can figure out what might have happened.
Main features:
- Stable and reliable dependency resolver with efficient algorithms:
- Due to the easy nature of python being a rapid prototyping language and the modular design of pyrpm we were able to test and write several generations of dependency resolvers and over time optimize and improve the reliability of it to a point where we are very confident that the results are what a user would expect.
- Handling of multilib systems:
- This is connected to the previous feature. Multilib systems are generally a lot trickier to handle than single arch systems. The algorithms used in pyrpm try to make intelligent choices as to which packages should be installed resp. how packages should be updated.
- Ordering of all packages in a transaction:
- In order for a whole transaction to work reliable it is not enough to just order the installs and updates but also the erase operations properly. In pyrpm we are handling all operations and order them in a way that honors all requirements correctly, even for erases.
- Smart like package selection:
- In pyrpm we are able to make package selections similar to the SMART package manager by trying to downgrade packages or even remove them if dependencies cant be resolved at all. The semi automatic removal is of course optional and not enabled by default.
- Very easy to use scripts to setup changeroots:
- Using pyrpmkickstart you can easily use a typical anaconda kickstart file to do an automated install either on a disk, partition, diskimage or even simple changeroots.