|
Name: ColdC
Pros: Makes no assumptions about the type of game you want to make (it doesn't even assume you necessarily want to make a game). No restrictive licensing. Lends itself well to the creation of persistent virtual worlds. Disk-based memory. Objects can be reprogrammed on the fly without having to reboot and without having to destroy and reload the objects.
Cons: Spotty documentation. Be prepared to do a lot of low-level work with the core (lib) before you have anything resembling a game to work with.
License: GPL
ColdC most closely resembles the MOO programming language, but is probably just as accessible to anyone familiar with LPC. There are a couple of minimal cores available for anyone wanting to essentially build a core from scratch.
The driver handles incoming and outgoing network connections, but leaves just about everything else to the code in the core. This leaves a mud developer with a lot more work than would be required with most of the more popular LP libs, but nowhere near the level of work that would be required to develop a mud from scratch in C/C++.
|