Talk:Standards:MMP - Revision history

Vadi at 11:01, 28 December 2025

2025-12-28T11:01:58Z

Keneanung at 12:04, 15 August 2017

2017-08-15T12:04:46Z

Keneanung at 07:40, 15 August 2017

2017-08-15T07:40:38Z

Slysven at 00:07, 15 August 2017

2017-08-15T00:07:09Z

Keneanung at 14:38, 10 August 2017

2017-08-10T14:38:12Z

Keneanung at 14:32, 10 August 2017

2017-08-10T14:32:39Z

Keneanung at 14:32, 10 August 2017

2017-08-10T14:32:17Z

Show changes

Keneanung at 15:35, 7 August 2017

2017-08-07T15:35:31Z

Slysven: /* Initial talk page creation */

2017-08-03T04:32:45Z

Initial talk page creation

New page

Currently the biggest item missing from the IRE samples (and the Mudlet interpreter) is handling of Special Exits.

I have added support for our door types (IRE MUDs do use a `door="1"` as an exit attribute and also a `hidden="1"`) so that door type "1" corresponds to our "open door" marking, "2" to "closed door" and "3" (and `hidden="1"`) to our "locked door".

Not documented here is that all of the official five (now four) IRE Mud XML files now include an "HTLMColor" attribute as well as a "Color" number attribute. Last time I checked four (now three) of them all had the same color number to HTMLcolor "names" (actually a 6 hex digit/24 bit "rrggbb" code that Qt can comprehend as a QColor::name if it is prefix with a '#' IIRC) but one use different shades of similar colours for a richer colour experience - e.g. swimmable water might be a different shade of blue to deep water as their HTMLColor attribute - but still had the same basic (16 colour) "Color" attribute for those different "environments". As for environments we do not currently capture the "Description" data and we map the colour "Color" codes to our "ColorID"s with a generated lookup table that is totally inaccessible and unmodifiable (but stored in the Mudlet binary map file format so it persists) by the end user!!!

[[User:Slysven|slysven]] ([[User talk:Slysven|talk]]) 04:32, 3 August 2017 (UTC)

← Older revision		Revision as of 11:01, 28 December 2025
Line 267:		Line 267:
	:::You're right, the "hidden" flag should hide the exit instead of the room, my fault. I will also amend the comment the door comment to be more open and we should probably have an "implementation status/notice" page where we list which standards are implemented and where/how we derive from them. We could note the additional exit values there. The same with the single area maps: we should note this on an implementation status page.		:::You're right, the "hidden" flag should hide the exit instead of the room, my fault. I will also amend the comment the door comment to be more open and we should probably have an "implementation status/notice" page where we list which standards are implemented and where/how we derive from them. We could note the additional exit values there. The same with the single area maps: we should note this on an implementation status page.
	:::--[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 07:40, 15 August 2017 (UTC)		:::--[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 07:40, 15 August 2017 (UTC)
		+
		+	Special exits are handled via a special attribute, ie:
		+	<exit special="1" command="climb tree" target="42" />
		+
		+	This is in relation to the first comment in the page.
		+	--[[User:Vadi\|Vadi]] ([[User talk:Vadi\|talk]]) 11:01, 28 December 2025 (UTC)

@@ Line 263: / Line 263: @@
 : --[[User:Keneanung|keneanung]] ([[User talk:Keneanung|talk]]) 14:32, 10 August 2017 (UTC)
-:Not sure if the "hidden" attribute is applicable to the "exit" that has it or the "room" that it goes to as you have put here.  Also I have only seen door="1" for exits - though I coded as if "0", "2" or "3" were possible and mapped hidden="1" to be the same as door="3"...  I wasn't aware of the ability to have only a portion of a map (one or more complete "areas") and Mudlet would not behave nicely with such a thing with the current XML importer (it throws away the existing map when it reads a new XML file).  IIRC Exits to rooms that are not present in the particular XML file loaded will get converted to stubs - this will be recorded both in the ''errors.txt'' log file and in a specifically crafted Room ''User Data'' entry for the starting room for the exit route. [[User:Slysven|slysven]] ([[User talk:Slysven|talk]])
+::Not sure if the "hidden" attribute is applicable to the "exit" that has it or the "room" that it goes to as you have put here.  Also I have only seen door="1" for exits - though I coded as if "0", "2" or "3" were possible and mapped hidden="1" to be the same as door="3"...  I wasn't aware of the ability to have only a portion of a map (one or more complete "areas") and Mudlet would not behave nicely with such a thing with the current XML importer (it throws away the existing map when it reads a new XML file).  IIRC Exits to rooms that are not present in the particular XML file loaded will get converted to stubs - this will be recorded both in the ''errors.txt'' log file and in a specifically crafted Room ''User Data'' entry for the starting room for the exit route. [[User:Slysven|slysven]] ([[User talk:Slysven|talk]])
-::You're right, the "hidden" flag should hide the exit instead of the room, my fault. I will also amend the comment the door comment to be more open and we should probably have an "implementation status/notice" page where we list which standards are implemented and where/how we derive from them. We could note the additional exit values there. The same with the single area maps: we should note this on an implementation status page.
+:::You're right, the "hidden" flag should hide the exit instead of the room, my fault. I will also amend the comment the door comment to be more open and we should probably have an "implementation status/notice" page where we list which standards are implemented and where/how we derive from them. We could note the additional exit values there. The same with the single area maps: we should note this on an implementation status page.
-::--[[User:Keneanung|keneanung]] ([[User talk:Keneanung|talk]]) 07:40, 15 August 2017 (UTC)
+:::--[[User:Keneanung|keneanung]] ([[User talk:Keneanung|talk]]) 07:40, 15 August 2017 (UTC)

← Older revision		Revision as of 07:40, 15 August 2017
Line 263:		Line 263:
	: --[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 14:32, 10 August 2017 (UTC)		: --[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 14:32, 10 August 2017 (UTC)

−	Not sure if the "hidden" attribute is applicable to the "exit" that has it or the "room" that it goes to as you have put here. Also I have only seen door="1" for exits - though I coded as if "0", "2" or "3" were possible and mapped hidden="1" to be the same as door="3"... I wasn't aware of the ability to have only a portion of a map (one or more complete "areas") and Mudlet would not behave nicely with such a thing with the current XML importer (it throws away the existing map when it reads a new XML file). IIRC Exits to rooms that are not present in the particular XML file loaded will get converted to stubs - this will be recorded both in the ''errors.txt'' log file and in a specifically crafted Room ''User Data'' entry for the starting room for the exit route. [[User:Slysven\|slysven]] ([[User talk:Slysven\|talk]])	+	:Not sure if the "hidden" attribute is applicable to the "exit" that has it or the "room" that it goes to as you have put here. Also I have only seen door="1" for exits - though I coded as if "0", "2" or "3" were possible and mapped hidden="1" to be the same as door="3"... I wasn't aware of the ability to have only a portion of a map (one or more complete "areas") and Mudlet would not behave nicely with such a thing with the current XML importer (it throws away the existing map when it reads a new XML file). IIRC Exits to rooms that are not present in the particular XML file loaded will get converted to stubs - this will be recorded both in the ''errors.txt'' log file and in a specifically crafted Room ''User Data'' entry for the starting room for the exit route. [[User:Slysven\|slysven]] ([[User talk:Slysven\|talk]])
		+
		+	::You're right, the "hidden" flag should hide the exit instead of the room, my fault. I will also amend the comment the door comment to be more open and we should probably have an "implementation status/notice" page where we list which standards are implemented and where/how we derive from them. We could note the additional exit values there. The same with the single area maps: we should note this on an implementation status page.
		+	::--[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 07:40, 15 August 2017 (UTC)

← Older revision		Revision as of 00:07, 15 August 2017
Line 262:		Line 262:
	: [[File:MMP-Draft-1.png]]		: [[File:MMP-Draft-1.png]]
	: --[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 14:32, 10 August 2017 (UTC)		: --[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 14:32, 10 August 2017 (UTC)
		+
		+	Not sure if the "hidden" attribute is applicable to the "exit" that has it or the "room" that it goes to as you have put here. Also I have only seen door="1" for exits - though I coded as if "0", "2" or "3" were possible and mapped hidden="1" to be the same as door="3"... I wasn't aware of the ability to have only a portion of a map (one or more complete "areas") and Mudlet would not behave nicely with such a thing with the current XML importer (it throws away the existing map when it reads a new XML file). IIRC Exits to rooms that are not present in the particular XML file loaded will get converted to stubs - this will be recorded both in the ''errors.txt'' log file and in a specifically crafted Room ''User Data'' entry for the starting room for the exit route. [[User:Slysven\|slysven]] ([[User talk:Slysven\|talk]])

@@ Line 10: / Line 10: @@
 : [[User:Keneanung|keneanung]] ([[User talk:Keneanung|talk]]) 15:35, 7 August 2017 (UTC)
-: This is the XSD file that I came up with, qhat do you think?:
+: This is the XSD file that I came up with, what do you think?:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

← Older revision		Revision as of 14:32, 10 August 2017
Line 261:		Line 261:
	: A pictorial representation would be this:		: A pictorial representation would be this:
	: [[File:MMP-Draft-1.png]]		: [[File:MMP-Draft-1.png]]
		+	: --[[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 14:32, 10 August 2017 (UTC)

← Older revision		Revision as of 15:35, 7 August 2017
Line 6:		Line 6:

	[[User:Slysven\|slysven]] ([[User talk:Slysven\|talk]]) 04:32, 3 August 2017 (UTC)		[[User:Slysven\|slysven]] ([[User talk:Slysven\|talk]]) 04:32, 3 August 2017 (UTC)
		+
		+	: There are some more features in the MMP files that are used by IRE right now. I have an XSD file ready that validates against the current files, but I'd like to add some more comments to it first before publishing it
		+	: [[User:Keneanung\|keneanung]] ([[User talk:Keneanung\|talk]]) 15:35, 7 August 2017 (UTC)