Be the first to post a text review of Extensible Java MUD. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Refactoring Completed

  After several weeks of um-ing and ah-ing I have moved classes around into new packages, hopefully making the XJMud package structure make more sense. I have also re-written all of the configuration files to use the new Preferences framework rather than the old Hashtable hacked files. The new preferences files should make creating heirarchical properties much easier to load, save and process. Sorry for the delay, any problems please, fire me an email, or write to the forums. Aidos_g

  posted by aidos_g 1871 days ago

• xjmud-olc 2004-09-27 file released: olc.zip

  posted 1871 days ago

• xjmud 2004-09-27 file released: core.zip

  posted 1871 days ago

• File released: /xjmud/2004-09-27/core.zip

  posted 1871 days ago

• xjmud-rmi 2004-09-27 file released: remote.zip

  posted 1871 days ago

• File released: /xjmud-olc/2004-09-27/olc.zip

  posted 1871 days ago

• File released: /xjmud-rmi/2004-09-27/remote.zip

  posted 1871 days ago

• GUI based OLC Preview Released

  A new package called XJMud-OLC has been added to the files section, providing the first look at the XJMud GUI based OLC (that uses the XJMud-Remote package). The GUI is very dynamic, and very very alpha. It currently only supports the adding/removing of objects, the creating of exits, and the manipulation of all Describable types. The release, although very primitive is enough to get basic region building out there so people can start work on building their games. The OLC is currently highest priority, so expect updates very frequently, and updates to the core / remote packages as soon as bugs are found / improvements required. --Aidos

  posted by aidos_g 1907 days ago

• Core / Remote Update

  The core and remote packages have been updated to include missing API functions, and to remove some more bugs from the core. The remote package now includes the concept of a security manager that works on a per-method basis. Every method that can be called remotely makes a call to RemoteSecurityManager.accept(), and if the remote access is forbidden, a remote exception is thrown. All remote access is now made through a Login module (the only object placed into the RMIRegistry), and all remote instances are on a per "remote user" basis. If the keepAlive function is not called every two minutes, the remote objects are unbound, and destroyed. These features should make the XJMud remote interface a lot more secure, and provide the ability for a much more developer friendly remote environment. Hope the new fixes and improvements are of use to everyone. -- Aidos

  posted by aidos_g 1907 days ago

• File released: /xjmud-rmi/Initial Release/xjmud-remote-0.2.zip

  posted 1907 days ago