Region Files - Revision history

imported>Perny: Make the format's legacyness more clear

2024-08-28T15:29:43Z

Make the format's legacyness more clear

← Older revision		Revision as of 15:29, 28 August 2024
Line 1:		Line 1:
	The ~~latest version of~~ the ~~Minecraft game uses a new, more efficient~~ format for storing ~~a worlds chunk data,~~ based on ~~work~~ by Scaevolous.		The Region file format is the binary file format for storing Java Edition chunks from Beta 1.3 to release 1.2. This format was based on a mod developed by Scaevolous.

	== Background & Reasoning ==		== Background & Reasoning ==

imported>Oq: info

2024-08-09T10:45:39Z

info

← Older revision		Revision as of 10:45, 9 August 2024
Line 38:		Line 38:
	In the official client and server, each region is stored within the folder <code>region</code> within the level folder. The naming scheme for region files is very simple. For example, given the filename <code>r.8.20.mcr</code>, <code>r</code> is a meaningless prefix found on all region files, <code>8</code> is the <code>X</code> coordinate of the region, and <code>20</code> is the <code>Z</code> coordinate of the region.		In the official client and server, each region is stored within the folder <code>region</code> within the level folder. The naming scheme for region files is very simple. For example, given the filename <code>r.8.20.mcr</code>, <code>r</code> is a meaningless prefix found on all region files, <code>8</code> is the <code>X</code> coordinate of the region, and <code>20</code> is the <code>Z</code> coordinate of the region.

	The region <code>X</code> and <code>Z</code> can be found simply by dividing the chunks <code>X</code> or <code>Z</code> by 32, and then [http://en.wikipedia.org/wiki/Floor_and_ceiling_functions flooring] the result. Here's an example in python, where given a chunk at <81, -39>, the region filename can be found:		The region <code>X</code> and <code>Z</code> can be found simply by right shifting the chunk <code>X</code> or <code>Z</code> position by 5 or by dividing the chunks <code>X</code> or <code>Z</code> by 32, and then [http://en.wikipedia.org/wiki/Floor_and_ceiling_functions flooring] the result. Here's an example in python, where given a chunk at <81, -39>, the region filename can be found:

	<pre>>>> import math		<pre>>>> import math

imported>Mudkipdev: Wtf

2024-07-30T01:01:36Z

Wtf

← Older revision		Revision as of 01:01, 30 July 2024
Line 1:		Line 1:
	The latest version of the Minecraft game uses a new, more efficient ~~(but still poor)~~ format for storing a worlds chunk data, based on work by Scaevolous.		The latest version of the Minecraft game uses a new, more efficient format for storing a worlds chunk data, based on work by Scaevolous.

	== Background & Reasoning ==		== Background & Reasoning ==

imported>MMK21: /* Background & Reasoning */ Worlds can be arbitrarily tall now

2023-04-03T13:01:13Z

Background & Reasoning: Worlds can be arbitrarily tall now

← Older revision		Revision as of 13:01, 3 April 2023
Line 23:		Line 23:
	\|-		\|-
	! Chunk		! Chunk
	\| A single section of the level that is 16 by 16 blocks, and ~~128 blocks~~ high.		\| A single section of the level that is 16 by 16 blocks, and as high as the world's build limit
	\|-		\|-
	! Region		! Region
Line 30:		Line 30:
	! Level		! Level
	\| A (realistically, but not technically) unlimited collection of ''chunks'' stored in ''regions'' that make up a single playable world.		\| A (realistically, but not technically) unlimited collection of ''chunks'' stored in ''regions'' that make up a single playable world.
	\|}		\|}

	== Specification ==		== Specification ==

imported>Dolphin2410: chuck -> chunk

2022-08-24T08:31:16Z

chuck -> chunk

← Older revision		Revision as of 08:31, 24 August 2022
Line 85:		Line 85:
	<pre>def chunk_location(l):		<pre>def chunk_location(l):
	"""		"""
	Returns the offset (in bytes) and size (in bytes) of the ~~chuck~~ for		Returns the offset (in bytes) and size (in bytes) of the chunk for
	the given location.		the given location.
	"""		"""

imported>Trashpanda at 08:48, 10 February 2022

2022-02-10T08:48:45Z

← Older revision		Revision as of 08:48, 10 February 2022
Line 117:		Line 117:
	\|}		\|}
	There are two possible values for the compression scheme. If it is a <code>1</code>, the following chunk is compressed using [[wikipedia:gzip\|gzip]]. If it's a <code>2</code>, the following chunk is compressed with [[wikipedia:zlib\|zlib]]. In practice, you will only ever encounter chunks compressed using zlib.		There are two possible values for the compression scheme. If it is a <code>1</code>, the following chunk is compressed using [[wikipedia:gzip\|gzip]]. If it's a <code>2</code>, the following chunk is compressed with [[wikipedia:zlib\|zlib]]. In practice, you will only ever encounter chunks compressed using zlib.

			The length includes the compression scheme byte.

	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

imported>KurtThiemann: fixed location table python example (again)

2019-08-13T20:54:52Z

fixed location table python example (again)

← Older revision		Revision as of 20:54, 13 August 2019
Line 88:		Line 88:
	the given location.		the given location.
	"""		"""
	offset = ((l >> 8) & ~~0xFF) + ((l >> 16) & 0xFF) + ((l >> 24) & 0xFF~~)		offset = ((l >> 8) & 0xFFFFFF)
	size = l & 0xFF		size = l & 0xFF

imported>KurtThiemann: Well, let's take 4 bytes and right shift them 32 bits...

2019-05-25T22:50:52Z

Well, let's take 4 bytes and right shift them 32 bits...

← Older revision		Revision as of 22:50, 25 May 2019
Line 88:		Line 88:
	the given location.		the given location.
	"""		"""
	offset = ((l >> 8) & 0xFF) + ((l >> 16) & 0xFF) + ((l >> 32) & 0xFF)		offset = ((l >> 8) & 0xFF) + ((l >> 16) & 0xFF) + ((l >> 24) & 0xFF)
	size = l & 0xFF		size = l & 0xFF

imported>Metalim: /* File Names */

2017-07-28T00:43:08Z

File Names

← Older revision		Revision as of 00:43, 28 July 2017
Line 39:		Line 39:
	The region <code>X</code> and <code>Z</code> can be found simply by dividing the chunks <code>X</code> or <code>Z</code> by 32, and then [http://en.wikipedia.org/wiki/Floor_and_ceiling_functions flooring] the result. Here's an example in python, where given a chunk at <81, -39>, the region filename can be found:		The region <code>X</code> and <code>Z</code> can be found simply by dividing the chunks <code>X</code> or <code>Z</code> by 32, and then [http://en.wikipedia.org/wiki/Floor_and_ceiling_functions flooring] the result. Here's an example in python, where given a chunk at <81, -39>, the region filename can be found:

	<pre>>>> import math >>> region_xz = lambda x,z: (math.floor(x / 32), math.floor(z / 32)) >>> region_xz(81,-39) (2.0, -2.0)		<pre>>>> import math
			>>> region_xz = lambda x,z: (math.floor(x / 32), math.floor(z / 32))
			>>> region_xz(81,-39)
			(2.0, -2.0)
	</pre>		</pre>

imported>Endorphinex: /* File Names */

2016-06-27T15:37:37Z

File Names

← Older revision		Revision as of 15:37, 27 June 2016
Line 52:		Line 52:
	So, this chunk would reside in <code>r.-4.0.mcr</code>.		So, this chunk would reside in <code>r.-4.0.mcr</code>.

	Simple to use tool made in ~~Java~~ is available for download [http://www.mediafire.com/download/mb2cfs8iae977hn/MC_Region_Calculator.jar here].		Simple to use tool for calcualting region filenames made in java is available for download [http://www.mediafire.com/download/mb2cfs8iae977hn/MC_Region_Calculator.jar here].

	=== Structure ===		=== Structure ===