Lich mapping reference - Revision history

RANGERMAHTRA at 09:36, 7 January 2025

2025-01-07T09:36:40Z

← Older revision		Revision as of 04:36, 7 January 2025
Line 2:		Line 2:
	== Introduction to Mapping==		== Introduction to Mapping==

	''* '''Please do your research before editing the map!''' Chances are high any room that is not currently mapped has a reason why! You can open an issue on https://github.com/~~rpherbig~~/dr-scripts/issues to get rooms fixed or ask in lnet for someone to double check the rooms before doing any updating. *''		''* '''Please do your research before editing the map!''' Chances are high any room that is not currently mapped has a reason why! You can open an issue on https://github.com/elanthia-online/dr-scripts/issues to get rooms fixed or ask in lnet for someone to double check the rooms before doing any updating. *''

FREEDOMMINE: /* Introduction to Mapping */

2020-06-13T17:15:06Z

Introduction to Mapping

← Older revision		Revision as of 12:15, 13 June 2020
Line 3:		Line 3:

	''* '''Please do your research before editing the map!''' Chances are high any room that is not currently mapped has a reason why! You can open an issue on https://github.com/rpherbig/dr-scripts/issues to get rooms fixed or ask in lnet for someone to double check the rooms before doing any updating. *''		''* '''Please do your research before editing the map!''' Chances are high any room that is not currently mapped has a reason why! You can open an issue on https://github.com/rpherbig/dr-scripts/issues to get rooms fixed or ask in lnet for someone to double check the rooms before doing any updating. *''


	This guide is inspired by Tillmens posts on lrn2map: http://forum.gsplayers.com/showthread.php?57828-lrn2map (Note: ignore any mentions of mapmap, this script does not apply to Dragonrealms)		This guide is inspired by Tillmens posts on lrn2map: http://forum.gsplayers.com/showthread.php?57828-lrn2map (Note: ignore any mentions of mapmap, this script does not apply to Dragonrealms)

FREEDOMMINE: /* Introduction to Mapping */

2020-06-13T17:14:48Z

Introduction to Mapping

← Older revision		Revision as of 12:14, 13 June 2020
Line 1:		Line 1:

	== Introduction to Mapping==		== Introduction to Mapping==

			''* '''Please do your research before editing the map!''' Chances are high any room that is not currently mapped has a reason why! You can open an issue on https://github.com/rpherbig/dr-scripts/issues to get rooms fixed or ask in lnet for someone to double check the rooms before doing any updating. *''

	This guide is inspired by Tillmens posts on lrn2map: http://forum.gsplayers.com/showthread.php?57828-lrn2map (Note: ignore any mentions of mapmap, this script does not apply to Dragonrealms)		This guide is inspired by Tillmens posts on lrn2map: http://forum.gsplayers.com/showthread.php?57828-lrn2map (Note: ignore any mentions of mapmap, this script does not apply to Dragonrealms)

HAZADO22: Adding identical room mapping instructions

2019-07-23T16:04:51Z

Adding identical room mapping instructions

← Older revision		Revision as of 11:04, 23 July 2019
Line 259:		Line 259:

	</pre>		</pre>
			=== Adding identical rooms ===
			Taken from [http://forum.gsplayers.com/showthread.php?57828-lrn2map&p=1826134#post1826134]

			Fixing this sort of thing requires more knowledge of how the map database works than your standard mapping procedure. If it wasn't in River's Rest, I could run over to the room and give it a look and either fix it or give you some useful pointers, but since it's in River's Rest and I'm lazy, you're screwed.

			My assumption is that there are two rooms that are in different places but have the same room title/description/paths. There are several ways to deal with this, and they are mostly terrible.

			First, go to each of the identical rooms and type:

			<pre>
			;e echo Room.current_or_new
			</pre>

			If one of them shows up with a new room number, everything is good and right in the world (this isn't going to happen).

			Second, perhaps someone used ";mapmap fix" incorrectly (they didn't, because no one uses that, even though it's in the instructions). To check if this is the case, go to each of the identical rooms and type:

			<pre>
			;e echo Room.current.desc.length
			</pre>

			In the map database, rooms can have more than one description. This is mostly to deal with different night/day descriptions for the same room, but it can rarely have other uses. When using ";mapmap fix", the script tests existing paths to see if you end up in the expected room. If you don't, it'll ask you if the rooms are the same. If you tell it they're the same, it'll combine them so they both have the same room number. If not, it will delete the path and create a new one to the different room. Someone may have said yes when they shouldn't have, which would add two unrelated room descriptions (and/or titles/paths) to the same room id. If the above command says "1", then this is not the case. If it's more than one, then it might be the case, but I won't go into it further because it's too unlikely.

			So now we need to differentiate between the two horrible rooms. The best way to do this is with the room_objects tag. If there's something that shows up in the "You also see" line that is permanent, such as an arch or a door or something, and it's in one room but not the other, then all is good and right in the world (unlikely). Type:

			<pre>
			;e echo DRRoom.room_objs
			</pre>

			to see the exact object name, and then type:

			<pre>
			;e Room.current.room_objects = [ 'whatever' ]
			</pre>

			replacing whatever with the object name. Now, the room that has that object should keep the room number, and the room without the object should either be unknown, or might still tell you it knows the room id because of fuzzy room lookups. Either way, go to the other room and do a:

			<pre>
			;e echo Room.current_or_new
			</pre>

			and there should be two room ids. Then you can go over the whole area with a ";mapmap map" and a ";mapmap fix" and it should be good.

			If room_objects isn't an option, you can use a peer tag, which causes Lich to peer into the next room in order to discriminate between two rooms. This is nice because it lets you use either room as a target for go2, but it's terrible because it has to peer if you walk through the room with narost running.

			If the title/description/paths of each adjacent room is identical in each identical room (unlikely but actually has happened more than once), then you're stuck with treating the two rooms as one. You would need to create some creative StringProcs paths from each room to each adjacent room that will be sucessful regardless of which of identical room it's started in.

			I left out the location verb property because it sounds like these rooms are in the same location.

	=== Adding a new map image ===		=== Adding a new map image ===

KRISTENL: /* Re-routing a path by changing timeto */

2019-05-17T14:02:26Z

Re-routing a path by changing timeto

← Older revision		Revision as of 09:02, 17 May 2019
Line 53:		Line 53:
	You can change a path if there is an obstacle that you want to avoid, like a wall that might be too difficult to climb for younger adventurers!		You can change a path if there is an obstacle that you want to avoid, like a wall that might be too difficult to climb for younger adventurers!
	<pre>		<pre>
	;e ~~echo~~ Room.current.timeto["5665"] = 10.0		;e Room.current.timeto["5665"] = 10.0
	</pre>		</pre>

SORTIK: /* Update Rooms with multiple descriptions */ clarifying how to add second description to an existing room

2018-11-09T22:23:03Z

Update Rooms with multiple descriptions: clarifying how to add second description to an existing room

← Older revision		Revision as of 17:23, 9 November 2018
Line 199:		Line 199:

	This assumes you are standing in the target room with its new description and you know the roomid. You can find the roomid by going to a connecting room and looking at the room number for the direction of the room without a number.		This assumes you are standing in the target room with its new description and you know the roomid. You can find the roomid by going to a connecting room and looking at the room number for the direction of the room without a number.

			If you have not already, you need to run <pre><nowiki>;alias add ad = ;e Room[\?].description.push(XMLData.room_description)</nowiki></pre>
			then
	<pre>		<pre>
	<nowiki>;~~repo~~ checkout-mapdb</nowiki>		<nowiki>;repository checkout-mapdb</nowiki>
	<nowiki>ad roomnumber-it-should-be</nowiki>		<nowiki>ad roomnumber-it-should-be</nowiki>
	<nowiki>;~~repo~~ upload-mapdb</nowiki>		<nowiki>;repository upload-mapdb</nowiki>
	</pre>		</pre>

SZODRIN: /* Useful Aliases */

2018-09-17T01:15:22Z

Useful Aliases

← Older revision		Revision as of 20:15, 16 September 2018
Line 67:		Line 67:
	;alias add pop = ;e echo Room.current.tags.pop #deletes the last tag from the room you are in and displays it to you!		;alias add pop = ;e echo Room.current.tags.pop #deletes the last tag from the room you are in and displays it to you!
	</pre>		</pre>
			Note: Genie users must use slight variations for these commands. For instance, a comma instead of a semicolon, and double backward slashes where there is a backward slash.
			For example:
			,alias add lfr = ,e echo Room[\\?\].inspect

	=== Useful commands ===		=== Useful commands ===

HOOKERR: /* Adding a new map image */

2018-04-27T21:32:14Z

Adding a new map image

← Older revision		Revision as of 16:32, 27 April 2018
Line 261:		Line 261:
	Step 6: Add to narost (if needed or wanted)		Step 6: Add to narost (if needed or wanted)

	6a. Add the image to the map database. Narost will only display images that are already in the map database. If the image is already in the map database because it's used by other rooms, move on to 6b. If not, save the image in the lich\maps directory, go to a room that will use the image, and type ;e Room.current.image = 'filename' # substitute the actual filename of the image, including the file extension, but without the path.		6a. Add the image to the map database. Narost will only display images that are already in the map database. If the image is already in the map database because it's used by other rooms, move on to 6b. If not, save the image in the lich\maps directory, go to a room that will use the image, and type ;e Room.current.image = 'filename' # substitute the actual filename of the image, including the file extension, but without the path. Name the file is all lowercase with the formatting province-mapnumber-name-timestamp.whatever. You can get the timestamp by typing date +%s in a linux environment. If you leave a timestamp off there is no way to overwrite the map with a newer version without uploading a new file name. Make absolutely sure not to include apostrophes in the name.

	6b. Start narost in fix mode (;type ;narost fix)		6b. Start narost in fix mode (;type ;narost fix)

HOOKERR: /* Update Rooms with multiple descriptions */

2018-02-24T01:55:10Z

Update Rooms with multiple descriptions

← Older revision		Revision as of 20:55, 23 February 2018
Line 198:		Line 198:
	<pre>		<pre>
	<nowiki>;repo checkout-mapdb</nowiki>		<nowiki>;repo checkout-mapdb</nowiki>
	<nowiki>;e ~~Map.list[1263].description.push(XMLData.room_description)~~</nowiki>		<nowiki>ad roomnumber-it-should-be</nowiki>
	<nowiki>;repo upload-mapdb</nowiki>		<nowiki>;repo upload-mapdb</nowiki>
	</pre>		</pre>

HOOKERR: /* Re-routing a path by changing timeto */

2017-12-30T19:16:28Z

Re-routing a path by changing timeto

← Older revision		Revision as of 14:16, 30 December 2017
Line 53:		Line 53:
	You can change a path if there is an obstacle that you want to avoid, like a wall that might be too difficult to climb for younger adventurers!		You can change a path if there is an obstacle that you want to avoid, like a wall that might be too difficult to climb for younger adventurers!
	<pre>		<pre>
	,e echo Room.current.timeto["5665"] = 10.0		;e echo Room.current.timeto["5665"] = 10.0
	</pre>		</pre>

	=== Useful Aliases ===		=== Useful Aliases ===
	If you are using the Dependency suite of scripts, please run <code>;setupaliases</code> to install these some of these useful mapping aliases. It will not install all of them, currently.		If you are using the Dependency suite of scripts, please run <code>;setupaliases</code> to install these some of these useful mapping aliases. It will not install all of them, currently.