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.
Sapidlib is developed by the LPuniversity community.
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 utilities 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 than 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.org 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.
Project information
- Maintainer:
- Sapidlib Core Developers
- Driver:
- Sapidlib Developers
- Licence:
- Simplified BSD Licence
View full history Series and milestones
trunk series is the current focus of development.
All code Code
- Version control system:
- Bazaar
- Programming languages:
- LPC, C
All questions Latest questions
All bugs Latest bugs reported
-
Bug #406082: history_d (Channel logging daemon) needs limitation in logging amounts
Reported -
Bug #369595: locate command
Reported -
Bug #334913: non-fatal error on using command relogin
Reported -
Bug #331338: trying to read sent mail fails
Reported -
Bug #245722: Remove dependency on simul-efuns {f_,}format_mixed
Reported
All blueprints Latest blueprints
-
single account for multiple characters
Registered -
Intermud 3+ Router
Registered -
Mud Package Tool
Registered -
Framework that will help detect regressions and bugs
Registered -
Develop a standardized directory hierarchy
Registered