Timeline for Organising levels / rooms in a MUD-style text based world
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2014 at 1:31 | history | edited | Trevor Powell | CC BY-SA 3.0 | Fixed TADS code to be Tads3-legal. Improved Inform code. Because I'm OCD, apparently. Also, screenshots |
| Dec 2, 2014 at 13:44 | comment | added | DLeh | okay, I'll have to look into this. Thanks for the extra info! | |
| Dec 2, 2014 at 0:49 | comment | added | Trevor Powell | Also, I've actually been playing this game in another window. Granted it's been over three years since I originally wrote the answer, but it took me literally five minutes to download the latest version of Inform, install it, paste the code in, and now I can actually play it; wander around, pick up objects, check my inventory, save/load games, undo actions, etc. I could put it up on my web page right now, and anyone could play it. How much work do you reckon it'd take you to be able to do that with the XML version? | |
| Dec 2, 2014 at 0:18 | comment | added | Trevor Powell | It's also worth noting that the XML version is baking the cupboards' contents into the cupboards' description. That is, there's a hardcoded message for what to print when opening or looking at the (open) cupboards, which tells you that there are batteries inside. But what if the player has already taken the batteries? The XML version will tell you that there are batteries inside (because that's the only string it has available to display), while the Inform and TADS versions will tell you that the cupboards are empty. | |
| Dec 2, 2014 at 0:17 | comment | added | Trevor Powell | In addition to being much shorter, the Inform and TADS examples also support more features. For example, in both of them you can put the knife into the cupboards, which isn't supported at all in the XML version. | |
| Dec 2, 2014 at 0:15 | comment | added | Trevor Powell | But since you asked about "pitfalls and weaknesses": The Inform implementation is 19 lines long. The TADS example is 40 lines long. The XML implementation requires 126 lines (and would be even longer if it was word-wrapped at 80 columns and contained whitespace for legibility, the way that the Inform and TADS implementations do). | |
| Dec 2, 2014 at 0:10 | history | edited | Trevor Powell | CC BY-SA 3.0 | Updated samples to be complete implementations of the example XML |
| Dec 2, 2014 at 0:01 | history | edited | Trevor Powell | CC BY-SA 3.0 | Updated Inform sample to be a complete implementation of the example XML, which can trivially be pasted into Inform and run. |
| Dec 1, 2014 at 23:13 | comment | added | Trevor Powell | @DLeh The question was "I'd like to know if this method has any downfalls, and if there's a "better" or more standard way of doing it" This answer provides the better-and-more-standard-way-of-doing-it. | |
| Dec 1, 2014 at 11:02 | vote | accept | Polynomial | ||
| Dec 1, 2014 at 4:55 | comment | added | DLeh | this is very cool and informative, but imo doesn't answer the question. I was going to ask basically this exact same question. I'd like to know more about whether or not this XML is a valid approach or if there are any pitfalls or weaknesses it would have. | |
| Feb 20, 2012 at 20:23 | history | edited | Trevor Powell | CC BY-SA 3.0 | Fixed Inform sample to match the OP's map layout. Oops! |
| Nov 24, 2011 at 23:59 | history | answered | Trevor Powell | CC BY-SA 3.0 |