Free mastercraft boats software for linux

Games::Battleship::Craft is a Battleship craft class.

SYNOPSIS

use Games::Battleship::Craft;

my $craft = Games::Battleship::Craft->new(
id => T,
name => tug boat,
points => 1,
)

$points_remaining = $craft->hit;

A Games::Battleship::Craft object represents the profile of a Battleship

PUBLIC METHODS

new %ARGUMENTS

id => $STRING

A scalar identifier to use to indicate position on the grid. If one is not provided, the uppercased first name character will be used by default.

Currently, it is required that this be a single uppercase letter (the first letter of the craft name, probably), since a hit will be indicated by "lowercasing" this mark on a player grid.

name => $STRING

A required attribute provided to give the craft a name.

points => $NUMBER

An attribute used to define the line segment span on the playing grid.

position => [$X, $Y]

The position of the craft bow ("nose") on the grid.

Currently, the craft is assumed to have a horizontal or vertical alignment. Soon there will be diagonal positioning...

hit

$points_remaining = $craft->hit;

Increment the crafts hit attribute value and return whats left of the craft (total point value minus the number of hits).

Bloboats project is a boat racing game in the spirit of Elasto Mania or X-Moto, introducing a handful of elements from Super Mario Bros-like games.

The objective of Bloboats is to reach MS Enterprise as fast as possible to save if from
the hands of the terrible Tentacle Monsters of an Unknown Master and the same time beat your friend and laugh at his or her puny time.

The journey starts from a place called Tutorial, somewhere in the United States, and somehow the player ends up in the famous HV-Arena of Helsinki. During the trip a number of MS Enterprises are saved, luckily, from the hands of the terrible Tentacle Monsters of an Unknown Master, who actually is your dad. Or then aint.

Nasal is a language that I wrote for use in a personal project. Ostensibly it was because I was frustrated with the dearth of small-but-complete embeddable scripting languages, but of course I really wrote it because it was fun.
It is still young and incomplete in a few places, but is under active development and has been integrated as the extension language for the FlightGear simulator.
Documentation is still sparse. There is a design document available, which talks at length about the "whys" behind the design of Nasal and includes documentation for the built-in library functions.
More useful to the experienced programmer is the tutorial-style sample code, which explains and demonstrates all the syntax features of the language.
Like perl, python and javascript, nasal uses vectors (expandable arrays) and hash tables as its native data format. This is a well-understood idiom, and it works very well. I felt no need to rock the boat here.
Like perl, and unlike everything else, nasal combines numbers and strings into a single "scalar" datatype. No conversion needs to happen in user code, which simplifies common string handling tasks.
Like perl, but unlike python, hash keys must by scalars in nasal. Python supports a "tuple" constant type that can be used as well, but there is no equivalent in nasal (you cant use vectors as keys because they might change after the insertion).
Like perl and python, nasal uses a # character to indicate and end-of-line comment. There is no multiline begin/end comment syntax as in Javascript.
Like perl, nasal functions do not have named parameters. They get their arguments in a vector named "arg", and can extract them however they like. Unlike perl, Nasal takes advantage of this feature to do away with function "declaration" entirly; see below.
Like python, there is no hidden local object scope in a function call. The object on which a method was called is available to a function as a local variable named "me" (python calls this "self" by convention, but because nasal has no declared function arguments, there is no opportunity to change it).
Like perl, "objects" in nasal are simply hash tables. Looking an item up by name in a hash table and extracting a symbol for an object are just different syntax for the same operation (but read on for an important exception):
a["b"] = 1 means the same thing as: a.b = 1
The above paragraph is a minor lie. The "dot" syntax is also the clue to the interpreter to "save" the left hand side as the "me" reference if the expression is used as a function/method call. That is, these expressions are not equivalent (one is a plain function call, the other a method invocation on the object "a"):
a["b"](arg1, arg2) isnt the same as: a.b(arg1, arg2)
Like javascript, nasal lacks a specific "class" syntax for OOP programming. Instead, classes are simply objects. Each object supports a "parents" member array; symbol lookup on the object at runtime bounces to the parents (and the parents parents) if the symbol is not found in the hash. The parents field is just like any other object field, you can set it however you like and even change it at runtime if you are feeling especially perverse.
Like lisp, javascript and perl, nasal supports lexical closures. This means that the local symbol namespace available to your function when it is assigned remain constant over time. If you dont know what this means, you dont need to care. It is this feature that allows functions to use variables declared in the outer scope when it is defined (e.g. seeing "module" variables).
Like all other scripting languages, functions are just symbols in a namespace, but unlike all other scripting languages, there is no function "declaration" syntax. A function is always an anonymous object (a "lambda," in the parlance), which you assign to a variable in order to use. Like so:
myfunction = func { arg[0] + 1 }
myfunction(1); # returns 2
One annoyance of this feature is that Nasal functions dont have unique internal "names". So a debugging or exception stack trace can only give you a source line number, and not a function name as reference.
Nasal has a straightforward, readable syntax which is closest to javascript among other scripting languages. Like later versions of javascript, it includes has a hash lookup syntax as well as an object field accessor syntax (that is, you can do both a.b and a["b"]).
Unlike python, nasal has a grammar which is not whitespace-sensitive. This doesnt make python hard to write, and it arguably makes it easier to read. But it is different from the way the rest of the world works, and makes python distinctly unsuitable for "inline" environments (consider PHP, Javascript, ASP or in-configuration-file scripts) where it needs to live as a plain old string inside of another programs code or data file.
Nasal garbage collects runtime storage, so the programmer need not worry about manual allocation, or even circular references. The current implementation is a simple mark/sweep collector, which should be acceptable for most applications. Future enhancements will include a "return early" capability for latency-critical applications. The collector can be instructred to return after a certain maximum delay, and be restarted later. Fancy items like generational collectors fail the "small and simple" criteria and are not likely to be included.
Like python, nasal supports exception handling as a first-class language feature, with built-in runtime-inspectable stack trace. Rather like perl, however, there is no special "try" syntax for exception handling, nor inheritance-based catching semantics. Instead, you call a "try" function on another function, and inspect the return value on your own. Code simply calls die with an argument list, which is returned from the closest enclosing try() invocation. Elaborate exception handling isnt really appropriate for embedded scripting languages. [NOTE: this isnt finished yet]
Nasal tries to be stricter than perl. Operations like converting a non-numeric string value to a number, reading or writing past the end of an array or operating on a nil reference, which are generally legal in perl, throw exceptions in nasal. Perl sometimes bends over backwards to do something "reasonable" with your instructions (e.g. whats the boolean truth value of a hash reference?); nasal doesnt try ("error: non-scalar used in boolean context at line 92")
Nasal is very small, very simple, written in ANSI C, and generally an excellent choice for embedded applications. It uses a simple and transparent syntax interpretable by a simple "bracket matching and operator precedence" parser. It does not depend on any third party libraries other than the standard C library. It does not depend on third party tools like (f)lex and yacc/bison. It builds simply and easily, supports a reasonably simple extension API and cohabitates well with other code.
Nasal makes no use of the processor stack when running recursive code. This is important for embedded languages as it provides the ability to "exit early" from a Nasal context. An outside application may have realtime constraints, and Nasal can be instructed to run for only a certain number of "cycles" before returning. Later calls will automatically pick up the interpreter state where it left off.
Nasal provides "minimal threadsafety". Multithreaded operations on Nasal objects are safe in the sense that they cannot crash or corrupt the interpreter. They are not guaranteed to be atomic. In particular, poorly synchronized insertions into containers can "drop" objects into oblivion (which is OK from an interpreter stability standpoint, since the GC will clean them up normally). Race conditions have to be the programmers problem anyway, this is just another symptom. Garbage collection will block all threads before running. [NOTE: this part is still unimplemented.]
Enhancements:
- This release contains the updates that have been available in SimGear for some time now.
- Important new functionality includes bugfixes, many performance enhancements, a declared function argument syntax, a ternary (?:) operator, indexable and mutable string objects, interpreter thread safety features, and much work to the "standard" library (including stdio, bitfields, Unix system calls, and PCRE regular expressions).

Tracksail project is a simple sailing game.

The player guides a small boat through a track while competing for the best time with other players.

It uses a client-server model.

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

Wolfpack project is a server-side Ultima Online MMORPG software.
Wolfpack is software for an Ultima Online MMORPG server. Gameplay is scripted using Python and XML. You need EAs Ultima Online to play on Wolfpack servers.
The Wolfpack project is an effort to develop and maintain an open-source Ultima Online server that is secure, stable and extensible, providing users with the ability to create their own unique shards.
Enhancements:
- ixed meditation skillcheck in mana regeneration code.
- Changed GM talk color.
- Implemented the onCheckVictim event.
- Implemented the onDoDamage event.
- Stablemasters now remove the stabled pets from the follower list.
- Corpses now decay in multis too.
- Implemented a walktest command for testing walking.
- Fixed several other walking bugs.
- Implemented onRemoteUse for checking if an object that is in the belonging
- of another char may be used. First called for the using char, then for the
- owner of the object.
- Implemented onSnooping that is called for the owner and for the player trying to
- open a container.
- Fixed shop restock.
- Fixed bug #0000364. (Vendors not selling items they bought)
- Rewrote the vendor buy handler code.
- Improved the configure script:
- Translations are disabled by default now.
- Cleaner output.
- Fixed a bug with MySQL library reporting.
- The SectorMaps singleton has been renamed to MapObjects.
- The deprecated RegionIterators have been removed.
- The SectorIterators have also been replaced with a much faster iterator.
- The new iterators dont allocate/copy memory anymore.
- The "range" lookup now looks for items within a real circle.
- Multis now have their own structure, and are now separate from items.
- Region calls now list online and offline chars in sperate lists.
- Implemented player collision stamina loss in Felucca.
- Fixed lightlevel calculation.
- Fixed the pythonscript* integer conversion warnings by using size_t instead.
- Fixed adding items to the MapObjects.
- Fixed a bug in the new ContainerCopyIterator.
- Fixed movement not correctly being sent to other characters.
- Fixed Multi Update range.
- Added .reload muls and added a broadcast message to the reload commands.
- Fixed handling of a fixed z value for spawnregions.
- Fixed an exploit (dropping without dragging first)
- Changed the semantics of onLogin/onLogout (character entering/leaving the world).
- Added onConnect/onDisconnect (socket attaching/detaching to/from a player).
- Its no longer possible to login with a char if another char in
- the same account is still online.
- Fixed a bug that would cause onLogout not to be called.
- A skill of 100% or more in Spirit Speaking now allows you to talk
- freely as a ghost and hear everything dead players have to say.
- All geometrical bodies for spawnregions now support the except="true"
- tag that makes the rectangle, circle or point not be included in finding
- a random position within the region.
- Fix with spawnregion data. UShort != UInt
- Added socket.denymove to send packets to deny movement
- Fixed a crashbug with invalid function names passed to .addtimer()
- Added the ability to make yourself visible to other players.
- Guildbutton now triggers onGuildButton(player) python event.
- Fixed bug #0000376. (Stablemasters dont take money from the bank)
- Added "Refresh Characters Maximum Values" setting. Setting this to "false"
- will disable the automatic recalculation of Maxhitpoints/Maxmana/Maxstamina.
- Added a warning in the console if translation file could not be found.
- Fixed monsters not attacking players pets.
- Fixed bug #0000363. (Pets dont attack a target if its already fighting)
- More tag documentation in the code.
- Definition Tag Cleanups.
- Using skills no longer unhides by default, unhide moved to python.
- Fixed a nasty bug in the map sector code which caused objects not
- to be in the map objects when moved between maps.
- Fixed a walking bug that caused monsters to walk trough certain objects.
- type="3" in bodyinfo.xml is now correctly interpreted by the core.
- Exploit bugfix for locked containers.
- The status only shows the gold directly in your backpack now. (performance issues)
- Added bladespirit and energyvortex ai.
- Fixed a vision range bug with walking.
- Fixed many compiler warnings for GCC 3.4 versions, and general warnings.
- Updated SQLite to 2.8.15 and defaulted SQLite to encode data with UTF-8.
- Added a new feature to random:
- This will select a random value from a random list.
- Added new features to container items (made list work as well):
-
- Disabled verdata.mul support as this is no longer included in the latest
- releases of Ultima Online. Note: Commented out the source code only.
- Implemented an onSelectAbility event for the weapon special moves.
- Corrected the NINJITSU and BUSHIDO skill ids.
- Small cleanup to wolfpack.xml: Database options follow the same option
- names are are given in account options.
- Implemented a "karmalock" property to player objects. If its True, the player will not
- gain any positive karma anymore.
- Added Commoner AI.
- Fixed mul path detection on windows in release builds.
- * Definition Changes:
- Added the mage AI to most creatures.
- Adjusted carving sheep.
- Fixed leatherworkers and tanners not buying leather and hides.
- Male NPCs now have a 75% chance of getting a beard when created.
- Made shrink potions craftable.
- Changed the color of shrink potions.
- Added Tokuno includes for regions and spawnregions.
- Removed the "Pink Spawn" from decoration.
- Fixed skeletal steeds stats and skills.
- Added stackable burned food that is used when cooking fails.
- Added ranged weapons + ammo to orc scout, ratmen archer, meer captain and juka lord.
- Added colored samurai armor.
- Reorganized base armor categories.
- New folder for defines: definitions/defines/
- Applied the index.xml branches to colored armor.
- Added lightsources to fire elementals, wisps and horde minions.
- Added bones to bone_magi and body parts to horde minions, zombies and others.
- Added colored weapons. Note: Only the metallic weapons.
- Sorted out the samurai weapons by type and fixed properties.
- Ranged weapons set to 10 instead of 12.
- Price fixes for arrows/bolts.
- Fixed potion kegs.
- Gave guards colored hair.
- NPC skill defines are now: value
- Gold now has weight.
- Corrected the bushido and ninjitsu skill ids.
- All mounts now have the event npc.mount
- * Python Script Changes:
- Fixed bug #0000369. (Equip possible although item.movable = 3)
- Fixed bug #0000361. (Pets dont follow trough gate)
- Added xoffset, yoffset and zoffset to socket.attachmultitarget. (housing.deed)
- Fixed a runebook bug. (Refuses to work when full)
- Rewrote parts of the runebook.
- Added support for creature based poison immunity.
- Added support for hit based poisoning.
- Fixed several bugs in lumberjacking.
- Chars will now get revealed when using training dummy or archery butte.
- Fixed blood created at carving not decaying for a long time.
- Fixed fishing pole not wearing out.
- Fixed gainfactor for skills always beeing 1.0
- Fixed a skill check bug with lumberjacking.
- Implemented shrink potions.
- Fixed the tooltip of alchemy tools not being resend.
- Fixed the input system trying to call not existent scripts.
- Fixed the color of shrunken pets.
- Implemented shrink command.
- Implemented telem command.
- Added onConnect to system.players
- Fixes for moongate.py
- Guild button now opens guildstone menu by default.
- Fixed resistances for dragon scale armors.
- Fixed the open door macro.
- Fixed bug #0000310. (Invis spell duration too brief, Players will now be able to use stealth
- if they are hidden by the invisibility spell, even if they dont have 80.0 Hiding )
- Fixed bug #0000321. (Info Gump not setting boolean values to True if input is 1)
- Poisoning now accepts stacked potions.
- Reorganized the potion scripts.
- Added possibility to cut bone parts into usable bones using scissors.
- Fixed potion kegs.
- Added tilecolorz command. Same as tilecolor, but limited to one z coordinate.
- Added nukez command. Same as nuke, but limited to one z coordinate.
- Added tilemove command.
- Increased energyvortex and bladespirit casting time.
- Implemented the bleeding wound system.
- Implemented the weapon special moves.
- Implemented the SelfRepair item property.
- Implemented the Enhance Potions item property.
- Implemented the Splash Damage item properties.
- Implemented the On Hit spell effect item properties.
- Implemented support for dispel difficulty/dispel focus (see playguide).
- Enabled tithing of gold, resurrection and karma locking at ankhs.
- * Misc. Changes:
- FAQ Updates.
- Now compiling with the KDE Cygwin QT version on Windows. (http://kde-cygwin.sf.net)
- Updated the gm tool a little. It now has support for the samurai empire maps.
- In addition to fixing some bugs, it also has an experimental region rectangle generator
- on the settings tab.
- * Known Issues, Bugs, and Missing Features:
- Some skills are still incomplete.
- Spawn regions are incomplete.
- We welcome donated OSI-like spawn scripts!
- Town/World regions are incomplete.
- We welcome donated OSI-like region scripts!
- Possible that a few monsters are missing and/or incomplete.
- Multis (Houses/Boats) are not currently supported.

UOX3 project is an Ultima Online Server emulator.
UOX3 stands for Ultima Offline eXperiment 3, and can basically be described as an Ultima Online server-emulator. It allows anyone and everyone to run their own private Ultima Online shard (either offline or online) which they may then use the official UO Client (or a custom one) to connect to the shard.
While one of UOX3s goals is to emulate the functionality of the official Ultima Online servers and allow anyone to run a server of their own, another is to allow its users to tweak all aspects of said functionalities, and even to create new functionality altogether - either through UOX3s complex scripting engine (based on the SpiderMonkey-implementation of JavaScript) or by editing the source-code for UOX3 directly.
UOX3 is free for everyone. Its also in most cases free to play on any UO servers set up using UOX3 - that is the moral code MOST users of UOX3 follow. Not to mention that charging people money for playing on your shard is illegal and will almost certainly bring Electronic Arts legal-team down on you.
Enhancements:
- Support for all ML weapons added to source
- Duping error involving stacks larger than 32,767 has been fixed
- Issue causing timers not to be properly reset by the JS engine fixed
- Price and description information added to item tooltips on player vendors
- "view", "status" and "dismiss" commands added for player vendors
- Various other player vendor related bugs fixed
- House placement in valid locations fixed
- Boats will now also work at water levels other than Z -5
- Characters can now fight their own pets/summons without turning criminal
- Damage output by summoned creatures fixed
- The effects of magic fields fixed
- New MOUNTID tag added to creatures DFN to allow making creatures mountable
- NPCs can now walk through player ghosts
- Player ghosts only visible in combat mode, will enter combat mode when speaking
- JS method TextMessage has two new optional parameters; allHear and txtHue.
- NPCs can no longer cast Blade Spirit/Energy Vortex, due to flagging issues
- The ever-swinging training dummies have been fixed (new ones only!)
- Bugs with the following spells were fixed: clumsy, heal, feeblemind and magic arrow
- Two new JS scripts added to UOX3: oilcloth.js and cow_tipping.js
- Functional keyrings (and scripted version of keys) added
- GOOD tags added to buyable items to make it easier to use the advanced trade system
- Several guardzones fixed
- Its now possible to fish up assorted items aside from fish