RGN Format - Revision history

Akai: typo

2005-03-12T14:13:41Z

typo

2005-01-13T14:15:03Z

added to Formats category

2005-01-12T05:22:07Z

change 5->6 again somewhere else

2005-01-12T05:21:23Z

changed 5 to 6... i was off by 1

2005-01-12T05:19:16Z

added information about the .rgn format

2005-01-12T01:26:01Z

typo (RGN)

2005-01-12T01:20:12Z

Fixing text.

2005-01-11T17:53:41Z

deprecated, see ELVL_Format

2005-01-11T17:36:52Z

Deleting page.. (cypherjf)

2005-01-11T17:23:05Z

cypher we don't need this page. elvl covers it, .rgn files are deprecated

@@ Line 29: / Line 29: @@
 </pre>
-Now each one of these character represents 5 bits of encoded data. To encode 0 we would use 'a', to encode 1 we would use 'b'. This goes all the way up to encoding 31 which we would use '6'. You can treat each pair of letters as 10 bits put together to make a single number that is 0-1023 (convienently these are the only tile that a map can have). We could get the x by doing something like decode(g) * 32 + decode(u). decode(g) would give us 6 and decode(u) would give us 20. So the x coordinate encoded would be 6 * 32 + 20 or 212. We could similiarly find the y, width, and height of the encoded rectnagle. All these rectangles together make up the encoded region. Here is an example of a complete version 1 region file:
+Now each one of these character represents 5 bits of encoded data. To encode 0 we would use 'a', to encode 1 we would use 'b'. This goes all the way up to encoding 31 which we would use '6'. You can treat each pair of letters as 10 bits put together to make a single number that is 0-1023 (conveniently these are the only tile that a map can have). We could get the x by doing something like decode(g) * 32 + decode(u). decode(g) would give us 6 and decode(u) would give us 20. So the x coordinate encoded would be 6 * 32 + 20 or 212. We could similiarly find the y, width, and height of the encoded rectnagle. All these rectangles together make up the encoded region. Here is an example of a complete version 1 region file:
 <pre>

@@ Line 29: / Line 29: @@
 </pre>
-Now each one of these character represents 5 bits of encoded data. To encode 0 we would use 'a', to encode 1 we would use 'b'. This goes all the way up to encoding 31 which we would use '5'. You can treat each pair of letters as 10 bits put together to make a single number that is 0-1023 (convienently these are the only tile that a map can have). We could get the x by doing something like decode(g) * 32 + decode(u). decode(g) would give us 6 and decode(u) would give us 20. So the x coordinate encoded would be 6 * 32 + 20 or 212. We could similiarly find the y, width, and height of the encoded rectnagle. All these rectangles together make up the encoded region. Here is an example of a complete version 1 region file:
+Now each one of these character represents 5 bits of encoded data. To encode 0 we would use 'a', to encode 1 we would use 'b'. This goes all the way up to encoding 31 which we would use '6'. You can treat each pair of letters as 10 bits put together to make a single number that is 0-1023 (convienently these are the only tile that a map can have). We could get the x by doing something like decode(g) * 32 + decode(u). decode(g) would give us 6 and decode(u) would give us 20. So the x coordinate encoded would be 6 * 32 + 20 or 212. We could similiarly find the y, width, and height of the encoded rectnagle. All these rectangles together make up the encoded region. Here is an example of a complete version 1 region file:
 <pre>

@@ Line 20: / Line 20: @@
 </pre>
-The name is encoded after the "Name:". This is the name of the region you are about to define. After the name we have our rectangle defintions. These lines start with a '|' and then another character (space is used here). They are then followed by 8 characters (a-z, 0-5). These tell use the rectangle encoding. In the above example we have a single rectangle encoded as "gutkataj". The first two are the x encoding, and the next two y encoding of the upper left tile contained in this rectangle. The next two pairs of letters are the width and the height. So we have:
+The name is encoded after the "Name:". This is the name of the region you are about to define. After the name we have our rectangle defintions. These lines start with a '|' and then another character (space is used here). They are then followed by 8 characters (a-z, 0-6). These tell use the rectangle encoding. In the above example we have a single rectangle encoded as "gutkataj". The first two are the x encoding, and the next two y encoding of the upper left tile contained in this rectangle. The next two pairs of letters are the width and the height. So we have:
 <pre>

@@ Line 1: / Line 1: @@
-RGN Format (Region v. 1) has been deprecated.
+RGN Format (version 1) is a format which was used to encode files (ending with .RGN) containing region information. This format is now deprecated, and replaced with the  [[ELVL Format]] which contains region information inside the .lvl file. Nonetheless it may be useful to understand a version 1 region file if you come across it. [[Continuum Level / Ini Tool]] is capable of loading regions from a version 1 region file, and translating them to version 2 (eLVL) regions.
-See [[ELVL Format]] which contains region version 2 among other things.
+== The Format ==
 [[Category: Map]]

← Older revision	Revision as of 17:53, 11 January 2005
Line 1:	Line 1:
	+	The .rgn format (region version 1) has been deprecated.

	+	See [[ELVL_Format]] which contains region version 2 among other things.
	+
	+	[[Category: Map]]

← Older revision		Revision as of 17:36, 11 January 2005
Line 1:		Line 1:
−	~~cypher we don't need this page. elvl covers it, .rgn files are deprecated --smong~~	+
−	~~----~~
−	~~Todo: Add details about the format. Teaming this up w/ the [[LVL_Format]], [[ELVL_Format]] and [[LVZ_Format]] [[RGN_Format]] formats.~~

← Older revision		Revision as of 17:23, 11 January 2005
Line 1:		Line 1:
		+	cypher we don't need this page. elvl covers it, .rgn files are deprecated --smong
		+	----
	Todo: Add details about the format. Teaming this up w/ the [[LVL_Format]], [[ELVL_Format]] and [[LVZ_Format]] [[RGN_Format]] formats.		Todo: Add details about the format. Teaming this up w/ the [[LVL_Format]], [[ELVL_Format]] and [[LVZ_Format]] [[RGN_Format]] formats.