Free call of combat software for linux

Castle-combat is a clone of the old DOS game Rampart.

Up to four players build castle walls, place cannons inside these walls, and shoot at the walls of their enemy(s).

If a player cant build a complete wall around one of his castles, he loses. The last surviving player wins.

Realms of Rivalry is an online tactical rpg. Play short skirmishes in random-generated game worlds.
The game can be summarized as an online graphical turn-based strategy/rpg game where you can play short tactical skirmishes with 2-4 players in small random-generated game worlds. The game is free and can be played either as an applet or downloadable client.
The time-limited turns (30-90 secs) give the game a semi-realtime feel, and the game has sometimes been characterized as "chess on steroids".
Main features:
- Community friendly game lobby where you can chat with others and join realms.
- Up to 4 players simultaneously battling on the same realm.
- Players control teams of 3 characters: Warrior, Archer and Mage.
- Time-limited turn-based gameplay.
- Random-generated game worlds (realms).
- CPU controlled monsters.
- Several weapons, armor, traps and other items.
- Occlusion calculation used in combat situations.
- Interrupts.
- Different types of terrain.
- Buy & sell items at vendors.
- Monster respawning.
- Ingame chat.
- Detailed end-of-game summary panel.
Explore the map and kill creatures to obtain weapons, potions, runes, traps and more to aid you in your quest for domination!
The game development has been very "test-driven" in the sense that the game quickly was made playable and that features and changes were added and removed continuously during development. This hopefully improves gameplay, but of course at the expense of dramatically increased development time.
Realms of rivalry was never intended to "soothe the masses", but were made entirely to match the game that we ourselves would like to play - something we have done for many, many hours :-) But of course, some of you might enjoy this game aswell, and that is why we decided to share it with you!.

ffcall is a foreign function call libraries.

This is a collection of four libraries which can be used to build foreign function call interfaces in embedded interpreters.

The four packages are:

avcall

calling C functions with variable arguments

vacall

C functions accepting variable argument prototypes

trampoline

closures as first-class C functions

callback

closures with variable arguments as first-class C functions (a reentrant combination of vacall and trampoline)

Call Of Duty 2 Linux Multiplayer Server Code is a COD2 linux server.

!! IMPORTANT !!

Call of Duty 2 Linux Server is NOT SUPPORTED by Activision Customer Support. Please do not call with any questions related to this free beta product. There are other channels to aid you listed at the bottom of this document.

Introduction

This document explains how to install the Call of Duty 2 Linux server version 1.0. Installation from scratch and upgrading an existing installation are both covered.

Usage is very similar to Call of Duty and United Offensive... many of the console commands, command lines, and cvars are identical, so if you are comfortable maintaining dedicated servers for those games, you will find this process familiar.

MOD USERS: PLEASE READ...

It is recommended that any user modifications that have been installed to the Call of Duty 2 directory be removed before installing this package. These modifications are not supported by Activision and may not be compatible with some of the new features that are included. When installing or upgrading a server, if problems or unexpected behavior arise, your first step in troubleshooting should be to do a clean install with the original data files.

IF YOU HAVE A PROBLEM WITH "LIBSTDC++.SO.5" ...

(This is a frequent-enough problem to merit discussion in the introduction.)

If you are reading this, its probably because you tried to start your Linux server and saw this message:

./cod2_lnxded: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

COD2 is a C++ program built with gcc 3.3.4, which means it needs a system library specific to gcc 3.3. Older Linux systems wont have this installed, and were starting to see newer Linux distributions that dont have this either, since they are supplying an incompatible gcc 3.4 version. The good news is that you can drop the needed library into your system without breaking anything else.

Here is the library you need, if your Linux distribution doesnt supply it:

http://icculus.org/updates/cod/gcc3-libs.tar.bz2

You want to unpack that somewhere that the dynamic linker will see it (if you are sure it wont overwrite any files, you can even use /lib).

The brave can put it in the same directory as the game and run the server like this:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. ./cod2_lnxded

Now the server will start.

Upgrading from 1.0 to Linux 1.0a.

Just stop the game server, replace cod2_lnxded on your server with the version included in this package, and restart the game server. 1.0a is just a minor hotfix and requires no other code changes.

As the hotfix is Linux-specific there is no Windows version of 1.0a.

Installation From Scratch

- Get the retail Call of Duty 2 disc(s) (there may be multiple discs depending on what edition of the game you have obtained, or perhaps a single DVD-ROM disc).
- Copy the contents of disc ones "Setup/Data" directory to wherever you want to install the Call of Duty 2 Linux server. There should be a "localization.txt" file in the root of this directory, and a "Main" Subdirectory. Each additional disc should be opened and the contents of each "Data" folder should be copied over to the existing Main folder. When you have copied everything, the final installation size is around 3.5 gigabytes.
- Alternately, you may install on Windows and copy the installed game to your Linux system, but many will opt to skip this step since the data files are uncompressed and easily accessible on the discs. Final installation size is around 3.5 gigabytes.
- Unpack this archive in the root of the newly-copied tree, so "cod2_lnxded" is in the same directory as "localization.txt". Unlike the original Call of Duty, there are not seperate .so files like "game.mp.i386.so", so dont be concerned when you dont see them.
- Now, run the server:
cd /where/i/copied/callofduty2
./cod2_lnxded

- When you see "--- Common Initialization Complete ---", the game server has started, but you need to start a map before the server will accept connections. At this point, type:

map mp_leningrad

("mp_leningrad" being a given maps name).

- Now you should see your server in the in-game browser. You will now want to customize your server, but that is beyond the scope of this document.

TurboCall is an extension which adds a phone call function to your browser.
Select any phone number on any web page, or click on a phone number in your contact list in the integrated panel, and you will receive an incoming call from the desired destination number within seconds.
Main features:
- No obligation to subscribe after trial period
- Use your regular landline or cell phone
- Low international rates!
- Accessible worldwide
- Store your personal contact list
- No connection fee, no maintenance fee!

Python Call Graph (pycallgraph) is a Python library that creates call graphs for Python programs

pycallgraph is quite new. It seems to work well and I will most likely improve it in the near future!

Sys::AlarmCall is a package to handle the logic in timing out calls with alarm() and an ALRM handler, allowing nested calls as well.

SYNOPSIS

use Sys::AlarmCall;

$result = alarm_call($timeout1,$func1,@args1);
@result = alarm_call($timeout2,$func2,@args2);

Sys::AlarmCall provides a straightforward function call to use the alarm handler. It also handles the logic which allows nested time out calls if timeout calls are run thorugh the alarm_call() functions.

The main advantages of Sys::AlarmCall are that:

1. simple calls, e.g.

@result = &func(@args); #Normal function call with &
$result = func(@args);; #Normal function call
@result = &$code_reference(@args);
@result = $obj->func(@args); #Object method call

become simple calls:

@result = alarm_call($timeout,&func,@args);
$result = alarm_call($timeout,func,@args);
@result = alarm_call($timeout,$code_reference,@args);
@result = alarm_call($timeout,->func,$obj,@args);