Lich:A beginner's guide to the Lich mapdb - Revision history

HOST-GSKEBECHET: Adding 3rd-party template to lich script page. Removing duplicate category.

2023-05-30T14:30:26Z

Adding 3rd-party template to lich script page. Removing duplicate category.

← Older revision		Revision as of 09:30, 30 May 2023
Line 1:		Line 1:
			{{3rd-party}}
	<div class="alert alert-danger"><big><center>'''NEVER UPLOAD ANYTHING TO THE MAPDB WITHOUT CAREFULLY CHECKING YOUR WORK!'''</center></big></div>		<div class="alert alert-danger"><big><center>'''NEVER UPLOAD ANYTHING TO THE MAPDB WITHOUT CAREFULLY CHECKING YOUR WORK!'''</center></big></div>

Line 165:		Line 166:

	[[Category:Guides]]		[[Category:Guides]]
	[[Category:Third-Party Software]]

HOST-GSKEBECHET: HOST-GSKEBECHET moved page A beginner's guide to the Lich mapdb to Lich:A beginner's guide to the Lich mapdb: Renaming article to conform with updated guidelines for articles associated with Lich scripts. This will need to be updated with the f...

2023-05-23T15:34:21Z

HOST-GSKEBECHET moved page A beginner's guide to the Lich mapdb to Lich:A beginner's guide to the Lich mapdb: Renaming article to conform with updated guidelines for articles associated with Lich scripts. This will need to be updated with the f...

← Older revision	Revision as of 10:34, 23 May 2023
(No difference)

GS4XANLIN at 23:34, 8 April 2022

2022-04-08T23:34:44Z

Show changes

GS4XANLIN: /* What is a room? */

2022-04-08T23:14:34Z

What is a room?

@@ Line 17: / Line 17: @@
 <pre{{log2|margin-right=60%}}>
 @image_coords=[197, 175, 233, 211]
 @image="wl-wehnimers-1264234799.png"
 @timeto={"226"=>0.2, "294"=>0.2, "224"=>0.2}
 @location="the town of Wehnimer's Landing"
 </pre>

WINTERDAWN: /* check_location */ more info

2021-12-08T20:35:21Z

check_location: more info

← Older revision		Revision as of 15:35, 8 December 2021
Line 108:		Line 108:

	===check_location===		===check_location===

	This is used to indicate an error and is either true or nil. It defaults to nil and is toggled to true when using Map.current_or_new and the room already exists in the database. A room with this set to true needs to be looked into for duplicates, and when the issue is resolved, the remaining room needs to have this manually set to nil.
			Value: either true or nil

			This is used primarily for when two separate rooms have the same description. A good example might be a locker in Solhaven compared to a locker in Wehnimer's Landing. When check_location is set to true then that room will do a further check of where you are by determining your general location, instead of matching on the description alone.

			This can also be used to determine that there is an error with the room, usually with location and/or duplication. When a room is initially mapped the value defaults to nil, but when Map.current_or_new is used and there are discrepancies, then it will get toggled to true. A good example of this happening would be a room that exists in the database already, but the location value is wrong. This might cause Lich not to display the ID, amongst other issues, and thus give indication the room is not in the database. The trap is blindly creating a new database entry, but further investigation would show the location value is wrong. However, check_location being set to true would give followup issues that might yield awareness of the true issue.

			If there are no duplicate entries in the database, and everything appears proper, check_location would need to be manually set back to nil as a final step.

	===timeto===		===timeto===

WINTERDAWN: /* timeto */

2021-12-08T20:22:47Z

timeto

← Older revision		Revision as of 15:22, 8 December 2021
Line 111:		Line 111:

	===timeto===		===timeto===
	Type: ~~Haash~~		Type: Hash

	<pre{{log2\|margin-right=60%}}>		<pre{{log2\|margin-right=60%}}>

WINTERDAWN: /* check_location */ added information about what this is for and what to do with it

2021-12-08T07:01:21Z

check_location: added information about what this is for and what to do with it

← Older revision		Revision as of 02:01, 8 December 2021
Line 108:		Line 108:

	===check_location===		===check_location===
			This is used to indicate an error and is either true or nil. It defaults to nil and is toggled to true when using Map.current_or_new and the room already exists in the database. A room with this set to true needs to be looked into for duplicates, and when the issue is resolved, the remaining room needs to have this manually set to nil.
	???

	===timeto===		===timeto===

WHIGHTCNIGHT: /* Resources */

2020-11-17T17:28:28Z

Resources

← Older revision		Revision as of 12:28, 17 November 2020
Line 146:		Line 146:

	==Resources==		==Resources==
		⚫	*[https://elanthipedia.play.net/Lich_mapping_reference DragonRealm's Wiki Lich MapDB Reference Page]: A more up-to-date reference guide to editing and updating the mapdb

	*[http://forum.gsplayers.com/showthread.php?57828-lrn2map lrn2map thread]: ~~The most authoritative~~ information on the mapdb from Tillmen.		*[http://forum.gsplayers.com/showthread.php?57828-lrn2map lrn2map thread]: Original information on the mapdb from Tillmen
⚫	*[https://elanthipedia.play.net/Lich_mapping_reference DragonRealm's Wiki Lich MapDB Reference Page]: A ~~decent~~ ~~write-~~up

	[[Category:Guides]]		[[Category:Guides]]

RADDAFISKIE: removed - 'work in progress' notice... it's a wiki... everything is a work in progress

2019-03-04T15:56:27Z

removed - 'work in progress' notice... it's a wiki... everything is a work in progress

← Older revision		Revision as of 10:56, 4 March 2019
Line 1:		Line 1:
	<div class="alert alert-danger"><big><center>'''NEVER UPLOAD ANYTHING TO THE MAPDB WITHOUT CAREFULLY CHECKING YOUR WORK!'''</center></big></div>		<div class="alert alert-danger"><big><center>'''NEVER UPLOAD ANYTHING TO THE MAPDB WITHOUT CAREFULLY CHECKING YOUR WORK!'''</center></big></div>
	{{Work-in-progress}}

	The '''Lich map database''' ('''mapdb''') is an important part of [[Lich (software)\|Lich]] used for automated travel and other tasks related to room properties. It is distinct from the [[Script Go2\|go2]] script, but in general both of these two require the other for normal use. This article aims to provide a general introduction to the mapdb at a level appropriate for basic usage as well as getting started wtih modifications.		The '''Lich map database''' ('''mapdb''') is an important part of [[Lich (software)\|Lich]] used for automated travel and other tasks related to room properties. It is distinct from the [[Script Go2\|go2]] script, but in general both of these two require the other for normal use. This article aims to provide a general introduction to the mapdb at a level appropriate for basic usage as well as getting started wtih modifications.

DAID: /* Introduction */ note

2018-09-13T23:40:09Z

Introduction: note

← Older revision		Revision as of 18:40, 13 September 2018
Line 10:		Line 10:
	One is a database (mapdb) and the other is a script (go2). To exemplify their differences, consider that [[Prime]], [[Platinum]], and [[Shattered]] all have different mapdbs, but they can commonly share the same version of the go2 script. The databases cannot be shared across instances because the actual rooms and layouts are not 100% identical between them; they can, however, share the logic used by go2 to perform operations on the mapdb and issue instructions to the game server for movement and other tasks.		One is a database (mapdb) and the other is a script (go2). To exemplify their differences, consider that [[Prime]], [[Platinum]], and [[Shattered]] all have different mapdbs, but they can commonly share the same version of the go2 script. The databases cannot be shared across instances because the actual rooms and layouts are not 100% identical between them; they can, however, share the logic used by go2 to perform operations on the mapdb and issue instructions to the game server for movement and other tasks.

	The mapdb is a file with a record for each unique room it knows about. At ~~present~~, the file is about 20 MB in size containing information about nearly 30,000 rooms. These files are kept under lich/data/GSIV/map-##########.dat (for the Prime instance), where the long number is an identifying hash which is updated automatically in an incremental fashion. Although the hashes do not proceed linearly in mapdb number (e.g. 1, 2, 3, 4), a smaller hash is always an older version of the mapdb than a newer hash.		The mapdb is a file with a record for each unique room it knows about. At the time of writing (check History), the file is about 20 MB in size containing information about nearly 30,000 rooms. These files are kept under lich/data/GSIV/map-##########.dat (for the Prime instance), where the long number is an identifying hash which is updated automatically in an incremental fashion. Although the hashes do not proceed linearly in mapdb number (e.g. 1, 2, 3, 4), a smaller hash is always an older version of the mapdb than a newer hash.

	This article will focus on the mapdb from the perspective of not only its use with go2, but other scripts such as [[Script_Narost\|narost]] and ones that sort rooms by nearest location and tags (e.g., zzherb).		This article will focus on the mapdb from the perspective of not only its use with go2, but other scripts such as [[Script_Narost\|narost]] and ones that sort rooms by nearest location and tags (e.g., zzherb).