This page details the interests of the user Tricky. See here for information on the pilot Commander Tricky
|Tricky aka Ricardo|
|Name||Richard Thomas Harrison|
|Location||Bradford, West Yorkshire, UK|
|Interests||Oolite, LPMuds, Coding|
Current Windows Backdrop
- Friend or Foe OXP - an OXP that enhances ship group interaction.
- Jaguar Company adds in an Elite group of pilots to patrol the space lanes in Anarchy, Feudal and Multi-Government systems.
Maintainer of Sapidlib
Sapidlib (formerly LPUniMudlib) is a small yet powerful mudlib aimed at creating a solid, versatile, scalable mudlib solution for a variety of text-based projects including muds (a game genre, text-based MMORPG) that incorporates revolutionary and innovative features. Sapidlib is modular in design allowing developers to piece together pre-built modules and easily create their own. Sapidlib believes in striving for usability, stability, and dependability and applies these values not only via coding standards but always in project policies, practices, and procedures.
For quick reference, see the Sapidlib Project FAQ
You can often find developers hanging out on Rock the Halo: Developer Mud.
The date of the first release of Sapidlib is yet to be decided. As Sapidlib is based on LPUniMudlib, you can use the following downloads to get a feel of Sapidlib.
The latest release can be found here:
Download LPuniMudlib Alpha-0610-R7 for *NIX
Download LPuniMudlib Alpha-0607-R6 for WINDOWS
Download other Releases
Send us an e-mail if you're interested in hosting a mirror.
If you're interested in getting involved in the development of Sapidlib, you should have a good understanding and application of the LPC or C programming language. Sapidlib currently utilizes the MudOS driver officially (although it has been ported to FluffOS) and familiarity of the MudOS variant of LPC is recommended. Furthermore, Sapidlib employs the bazaar version control system for managing revisions of source code - see http://bazaar-vcs.org for details on how to get started with bzr.
Once you've gotten bazaar installed, you will want to branch the mainline (or the branch that contains the specific module you would like to work on) and then you're free to start making your additions. However, as a new developer you will not be able to push your changes to the server. You will be required to extract a patch (see bzr help diff) and file a bug requesting it be applied. Be sure to include which branch you wish it to be applied to. Your patch will be reviewed and accepted or you will be informed of what you need to do to get it accepted.
After you've made a name for yourself, you can apply for membership with the sapidlib-dev team here on launchpad which will allow you to push your changes to the server instead of having to send patches in via bug reports. Developers who show strong commitment, development skills, and work well with the team will be grant membership to sapidlib-dev-core which will allow you permission to push to our mainline series which is the series that is packaged for release.
Being a member of the official development team also has other benefits such as access to our google application platform, launchpad infrastructure, and servers. This will provide you with access to a lpuni.net e-mail address, our calendar system, shared documents, a shell account, more access to functionality on launchpad, and much more.
If you're not interested in assisting with developing the mudlib, there are other ways to contribute as well. If you're interested in developing documentation, sysadmin work, website development, or would like to help others learn how to program in LPC then there is a place for you in our project. Please feel free to contact us.
- To file a bug, visit: http://bugs.launchpad.net/sapidlib
- To file a specification, visit: http://blueprints.launchpad.net/sapidlib
- To ask a question, vsit: http://answers.launchpad.net/sapidlib
- To view our code, visit: http://code.launchpad.net/sapidlib
- Our launchpad project page can be found here: http://launchpad.net/sapidlib
- Check out the project FAQ for frequently asked questions