Map structure - Revision history

UniqueGeek: Redirect

2017-10-14T21:03:42Z

Redirect

UniqueGeek at 23:54, 2 February 2017

2017-02-02T23:54:46Z

← Older revision		Revision as of 23:54, 2 February 2017
Line 1:		Line 1:
	~~[[Category:ROM Hacking]]~~		== Map Structure ==
	~~[[Category:Structures]]~~

	== ~~'''~~Map Structure~~'''~~ ==

	Maps in Pokemon Diamond and Pearl are stored in fielddata\landdata directory. [[List of Maps]]		Maps in Pokemon Diamond and Pearl are stored in fielddata\landdata directory. [[List of Maps]]
Line 28:		Line 25:
	\|}		\|}

	== ~~'''FIRST PART- MOVEMENT PERMISSION'''~~ ==		== First Part: Movement Permission ==

	First part represents movement permission.		First part represents movement permission.
Line 322:		Line 319:
	\|}		\|}

	== ~~'''SECOND PART-~~ 3D ~~OBJECTS '''~~ ==		== Second Part: 3D Objects ==

	In this parts we find 3d objects that are showed in the map.		In this parts we find 3d objects that are showed in the map.
Line 356:		Line 353:
	For more information, go to [[Model list]]		For more information, go to [[Model list]]

	== ~~'''THIRD PART-~~ NSBMD ~~MODEL MAP '''~~ ==		== Third Part: NSBMD Model Map ==
	The NSBMD format will have its own page.		The NSBMD format will have its own page.
	[[NSBMD]]		[[NSBMD]]

	== ~~'''FOURTH PART-~~ BDHC ~~'''~~ ==		== Fourth Part: BDHC ==
	Currently the BDHC is known to have two parts. The first part controls base height of entire map. The second part only exists in maps with changes in height (e.g. stairs).		Currently the BDHC is known to have two parts. The first part controls base height of entire map. The second part only exists in maps with changes in height (e.g. stairs).

	[[Category:Technical References]]		[[Category:Technical References]]
	[[Category:Structures]]		[[Category:Structures]]
			[[Category:ROM Hacking]]
			[[Category:Gen 4]]
			[[Category:Game Data]]

Alpha: Added missing 0a-0f values

2015-05-17T06:48:02Z

Added missing 0a-0f values

← Older revision		Revision as of 06:48, 17 May 2015
Line 62:		Line 62:
	{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"		{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"
	\|- style="background: #ccc;" align="center"		\|- style="background: #ccc;" align="center"
	! Hex Value ~~(decimal)~~		! Hex Value
	! Movement type		! Movement type
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
Line 76:		Line 76:
	\|04-09		\|04-09
	\| Free passage		\| Free passage
			\|- style="background: #eee;" align="center"
			\|0A
			\| Cave Encounter
			\|- style="background: #eee;" align="center"
			\|0B
			\| Plains Encounter
			\|- style="background: #eee;" align="center"
			\|0C-0F
			\| Free Passage
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\|10-12		\|10-12

Alpha: Reverted edits by Atofeqoly (Talk) to last version by CuleX

2010-11-27T04:46:48Z

Reverted edits by Atofeqoly (Talk) to last version by CuleX

Show changes

Atofeqoly at 09:27, 24 November 2010

2010-11-24T09:27:27Z

Show changes

CuleX: Four part -> Fourth part; added to Technical References and Structures

2010-04-30T13:08:20Z

Four part -> Fourth part; added to Technical References and Structures

← Older revision		Revision as of 13:08, 30 April 2010
Line 351:		Line 351:
	[[NSBMD]]		[[NSBMD]]

	== '''~~FOUR~~ PART- BDHC ''' ==		== '''FOURTH PART- BDHC ''' ==
	Currently the BDHC is known to have two parts. The first part controls base height of entire map. The second part only exists in maps with changes in height (e.g. stairs).		Currently the BDHC is known to have two parts. The first part controls base height of entire map. The second part only exists in maps with changes in height (e.g. stairs).

			[[Category:Technical References]]
			[[Category:Structures]]

Alpha: /* FIRST PART- MOVEMENT PERMISSION */

2009-11-01T07:28:28Z

FIRST PART- MOVEMENT PERMISSION

← Older revision		Revision as of 07:28, 1 November 2009
Line 32:		Line 32:
	First part represents movement permission.		First part represents movement permission.
	It's length depends from maps and is characterized by a sequence of		It's length depends from maps and is characterized by a sequence of
	00 XX ~~00 XX 00~~ XX ...		XX YY XX YY ...

	Here's a table of the ~~moveability~~ hex bytes:		XX = special permissions

			YY = movement flag

			Here's a table of the movement flags represented as hex bytes:

	{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"		{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"
Line 41:		Line 45:
	! Movement type		! Movement type
	! Game		! Game
	\|- style="background: #~~e00~~;" align="center"		\|- style="background: #eee;" align="center"
	\| 00		\| 00
	\| Any Movement		\| Any Movement
	\| HGSS/ DPPt		\| HGSS/ DPPt
	\|- style="background: #~~e00~~;" align="center"		\|- style="background: #eee;" align="center"
	\| 04		\| 04
	\| No special permissions		\| No special permissions
	\| HGSS		\| HGSS
	\|- style="background: #~~e00~~;" align="center"		\|- style="background: #eee;" align="center"
	\| 80		\| 80
	\| No movement		\| No movement
	\| HGSS/ DPPt		\| HGSS/ DPPt
	\|}		\|}
	Here's a table of ~~movements~~ hex bytes:		Here's a table of special permissions represented as hex bytes:

	{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"		{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"

Alpha: /* FIRST PART- MOVEMENT PERMISSION */

2009-11-01T07:23:42Z

FIRST PART- MOVEMENT PERMISSION

← Older revision		Revision as of 07:23, 1 November 2009
Line 34:		Line 34:
	00 XX 00 XX 00 XX ...		00 XX 00 XX 00 XX ...

	Here's a table of ~~movements~~ hex ~~byte~~		Here's a table of the moveability hex bytes:

	{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"		{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"
	\|- style="background: #ccc;" align="center"		\|- style="background: #ccc;" align="center"
	! Hex Value ~~(decimal)~~		! Hex Value
	! Movement type		! Movement type
			! Game
			\|- style="background: #e00;" align="center"
			\| 00
			\| Any Movement
			\| HGSS/ DPPt
			\|- style="background: #e00;" align="center"
			\| 04
			\| No special permissions
			\| HGSS
	\|- style="background: #e00;" align="center"		\|- style="background: #e00;" align="center"
	\| 80		\| 80
	\| No ~~passage~~		\| No movement
			\| HGSS/ DPPt
			\|}
			Here's a table of movements hex bytes:

			{\| border="1" style="border: 1px solid #999; border-collapse: collapse;"
			\|- style="background: #ccc;" align="center"
			! Hex Value (decimal)
			! Movement type
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\| 00		\| 00
Line 291:		Line 308:
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\|}		\|}


	== '''SECOND PART- 3D OBJECTS ''' ==		== '''SECOND PART- 3D OBJECTS ''' ==

Alpha: /* Map Structure */

2009-11-01T04:19:39Z

Map Structure

@@ Line 8: / Line 8: @@
 Each map is divided in four parts
-The first 16 bytes give the sizes of each section (4 bytes each).
+The first 0x10 bytes give the sizes of each section as such:
 == '''FIRST PART- MOVEMENT PERMISSION''' ==

Alpha: /* FOUR PART- BDHC */

2009-05-26T19:53:25Z

FOUR PART- BDHC

← Older revision		Revision as of 19:53, 26 May 2009
Line 314:		Line 314:

	== '''FOUR PART- BDHC ''' ==		== '''FOUR PART- BDHC ''' ==
			Currently the BDHC is known to have two parts. The first part controls base height of entire map. The second part only exists in maps with changes in height (e.g. stairs).