Zugg Software :: View topic

Newbie Joined: 30 Dec 2012 Posts: 2

This may be too ambitious of a project for what CMud is capable of, but I thought I'd run it by the experts before I spend too much time banging my head against this just to realize it's not possible.

My favorite MUD has recently open-sourced all their code, which includes SQL dumps of all their database tables. The three tables I'm interested in are "zone", "room", and "roomexit".
- Zone has one record for each zone in the game, with the important fields being a unique zone number as the primary key, and the zone name.
- Room contains one row for every room in the game, with the unique VNUM as the primary key, a room name, long description, X/Y/Z coordinates, and a foreign key to the zone number to which it belongs.
- Roomexit contains a row for every exit from every room in the game. Each row contains the VNUM of the room from which it exits, the direction of the exit, the door name if applicable, and the VNUM of the destination room.

I have all of the tables imported in to mySQL right now. Would the easiest thing be just to programmatically convert the data directly to a map database file (.mdb I think, correct?) that CMud can read? Or would I need to use CMud scripting commands (using CMud Pro 3.34) and SQL queries to create and link the rooms one by one (if that's a possibility)?

Sorry if this sounds crazy, it just seems a shame to go through and map the entire mud manually when I have all that data already at my fingertips.

Thanks!

Sorcerer Joined: 15 Apr 2011 Posts: 809

The problem with converting the data is that there's a lot more that goes into a CMUD mapper database than that. If you really want to try this, I'd suggest creating a new map, making a zone and a few rooms, then open up the database in an SQLite viewer and look at the results. It's been a while since I messed with the mapper database directly, but off the top of my head, a few tips for you:
- The three tables you'll want to look at are ObjectTbl (rooms), ExitTbl and ZoneTbl.
- All the fields you listed should have one-to-one mappings in the mapper database.
- I'm not sure how your X/Y/Z coordinate fields work, but in the mapper database, the X/Y/Z fields correspond to (I think?) pixel locations on the map canvas. I don't remember how it works exactly, but they don't change in increments of 1.
- Your exit table might work the same way, but in the mapper database, you need two rows for two-way exits. For example, an exit east from room 1 to room 2, and an exit west from room 2 to room 1.
- Directions aren't stored in the exit table by name, they're stored by an id number. IIRC there's a directions table that you can look at for the numbers.

I'm sure I (and others) will come up with more later, and feel free to post questions as you go. Good luck!

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Cmud is easily capable of this, but the major stumbling block is the map database itself. The interconnectivity of the data is so complex few, if any, users have even attempted to "reinvent the wheel" to handle all that the mapper already doe internally.

FYI, it's typically a bad idea to modify the database (in the way you'll have to to make all the changes) while cmud is using it. Your changes won't appear until you restart the session.

Newbie Joined: 30 Dec 2012 Posts: 2

Hey guys, thanks for the responses.

Sorcerer Joined: 15 Apr 2011 Posts: 809