LVL Format - Revision history

CypherJF: minor punctuation change

2007-10-20T20:56:54Z

minor punctuation change

← Older revision		Revision as of 20:56, 20 October 2007
Line 18:		Line 18:
	</pre>		</pre>

	The x and y must not exceed 1023. The maximum file size of a LVL with Continuum 38, 39, 40 will support is 1,000,000 bytes. Otherwise the player will receive a "File write error"		The x and y must not exceed 1023. The maximum file size of a LVL with Continuum 38, 39, 40 will support is 1,000,000 bytes. Otherwise the player will receive a "File write error" and the client will crash.

	== Tileset ==		== Tileset ==

CypherJF: added max file size support for Continuum

2007-10-20T20:56:34Z

added max file size support for Continuum

← Older revision		Revision as of 20:56, 20 October 2007
Line 18:		Line 18:
	</pre>		</pre>

	The x and y must not exceed 1023.		The x and y must not exceed 1023. The maximum file size of a LVL with Continuum 38, 39, 40 will support is 1,000,000 bytes. Otherwise the player will receive a "File write error"

	== Tileset ==		== Tileset ==

CypherJF: fixed spellings

2007-09-30T00:26:40Z

fixed spellings

← Older revision		Revision as of 00:26, 30 September 2007
Line 1:		Line 1:
	Most .lvl files in current use follow this format. Some .lvl files, however, are [[Extended LVL]] maps. The format is reverse ~~compatable~~, so there's no way to tell if you have a regular or extended .lvl file from inside the game. The way you can tell the difference is:		Most .lvl files in current use follow this format. Some .lvl files, however, are [[Extended LVL]] maps. The format is reverse compatible, so there's no way to tell if you have a regular or extended .lvl file from inside the game. The way you can tell the difference is:

	If the map does not have a tileset bitmap appended to it (first two bytes are not 'BM') and the first four bytes are 'elvl' then you have an Extended LVL file.		If the map does not have a tileset bitmap appended to it (first two bytes are not 'BM') and the first four bytes are 'elvl' then you have an Extended LVL file.

	If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are ~~guarenteed~~ to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].		If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guaranteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].

	This regular format is also described in http://www.rarefied.org/subspace/lvlformat.html		This regular format is also described in http://www.rarefied.org/subspace/lvlformat.html

Samapico: /* Special Objects */

2007-09-04T17:58:28Z

Special Objects

← Older revision		Revision as of 17:58, 4 September 2007
Line 39:		Line 39:
	*Another small asteroid (was originally a large asteroid).		*Another small asteroid (was originally a large asteroid).
	*A space station (6x6 tiles).		*A space station (6x6 tiles).
	*A ~~worm hole~~ (5x5 tiles).		*A wormhole (5x5 tiles).

	== Extra Tiles ==		== Extra Tiles ==

BaK: /* Tileset */ grammar

2006-10-09T06:38:00Z

Tileset: grammar

← Older revision		Revision as of 06:38, 9 October 2006
Line 29:		Line 29:
	[[Image:TilesetDescription.PNG\|Tileset With Descriptions]]		[[Image:TilesetDescription.PNG\|Tileset With Descriptions]]

	Note that although you might have a good looking soccer goal or flag tile, it will not show up in the game. This is because there is a custom [[animation]] for these two tiles. You can find and edit these tiles by looking at Continuum\graphics\goal.bm2 and Continuum\graphics\flag.bm2. You can have other users use your custom goal or flag animation by including your new animations in a [[LVZ]] File.		Note that although you might have a good looking soccer goal or flag tile, it will not show up in the game. This is because there is a custom [[animation]] for these two tiles. You can find and edit these tiles by looking at Continuum\graphics\goal.bm2 and Continuum\graphics\flag.bm2. You can have other users use your custom goal or flag animation by including your new animations in an [[LVZ]] File.

	== Special Objects ==		== Special Objects ==

Mine GO BOOM: Reverted edit of Zc321, changed back to last version by Smong

2005-11-30T07:53:26Z

Reverted edit of Zc321, changed back to last version by Smong

← Older revision		Revision as of 07:53, 30 November 2005
Line 1:		Line 1:
	~~apple cows~~		Most .lvl files in current use follow this format. Some .lvl files, however, are [[Extended LVL]] maps. The format is reverse compatable, so there's no way to tell if you have a regular or extended .lvl file from inside the game. The way you can tell the difference is:

			If the map does not have a tileset bitmap appended to it (first two bytes are not 'BM') and the first four bytes are 'elvl' then you have an Extended LVL file.

			If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].

			This regular format is also described in http://www.rarefied.org/subspace/lvlformat.html

			Basically it is a bitmap with tile data appended to it.
			Each tile is represented in this format: (little endian)
			<pre>
			struct
			{
			unsigned long x : 12;
			unsigned long y : 12;
			unsigned long tile : 8;
			};
			</pre>

			The x and y must not exceed 1023.

			== Tileset ==
			This is an uncompressed bitmap image (typically 256-color) 304x160 [[Pixels \| pixels]], making each [[Tiles \| tile]] 16x16 pixels.

			[[Image:Tileset.jpg\|Tileset]]

			When editing maps with a tileset, there are different types of tiles, outlined below:

			[[Image:TilesetDescription.PNG\|Tileset With Descriptions]]

			Note that although you might have a good looking soccer goal or flag tile, it will not show up in the game. This is because there is a custom [[animation]] for these two tiles. You can find and edit these tiles by looking at Continuum\graphics\goal.bm2 and Continuum\graphics\flag.bm2. You can have other users use your custom goal or flag animation by including your new animations in a [[LVZ]] File.

			== Special Objects ==
			These are special animated objects. The most popular map editor, [[SSME]], calls these 'Special Objects' and changes the mouse pointer to a stamper.

			There are five objects available:
			*A small asteroid.
			*A medium asteroid (2x2 tiles).
			*Another small asteroid (was originally a large asteroid).
			*A space station (6x6 tiles).
			*A worm hole (5x5 tiles).

			== Extra Tiles ==
			There are some types, which are not meant to be part of typical mapmaking programs, but have been discovered and may have uses.

			Tile: Description
			*191: Invisible on screen, visible on radar, ships can go through them, items bounce off it, 'thors' go through it. (If you 'launch' an item while in it, the item will float suspended in space).
			*192-215: Invisible on screen, visible on radar, solid block (like any other tile).
			*216: A small asteroid, nothing not previously known about this.
			*217: A medium asteroid, nothing not previously known about this.
			*218: Another small asteroid, just the same as the other one, except the graphics are a little different(?)
			*219: A space station, nothing not previously known about this.
			*220: A wormhole, nothing not previously known about this.
			*221-240: Invisible on screen, visible on radar, solid block (like any other tile).
			*241: Invisible on screen, visible on radar, ship can go through it but Items disappear when they touch it.
			*242: Invisible on screen, invisible on radar, warps your ship on contact, items bounce off it, 'thors' disappear on contact.
			*243-251: Invisible on screen, invisible on radar, solid block (like any other tile).
			*252: Visible on screen (animated enemy brick), invisible on radar, items go through it, your ship gets warped after a random amount of time (0-2 seconds) while floating on it.
			*253: Visible on screen (animated team brick), invisible on radar, items go through it, so does your ship.
			*254: Invisible on screen, invisible on radar, items go through it, so does your ship. Possibly the internal representation of fly under tiles. You can't brick or mine while on it.
			*255: Visible on screen (animated prize), invisible on radar, items go through it, so does your ship. This is a prize, but it doesn't show up on radar, and no matter how many times you fly over it, you will never pick it up, ever.

			[[Category: Formats]]
			[[Category: Map]]

Zc321 at 07:31, 30 November 2005

2005-11-30T07:31:37Z

← Older revision		Revision as of 07:31, 30 November 2005
Line 1:		Line 1:
	Most .lvl files in current use follow this format. Some .lvl files, however, are [[Extended LVL]] maps. The format is reverse compatable, so there's no way to tell if you have a regular or extended .lvl file from inside the game. The way you can tell the difference is:		apple cows

	~~If the map does not have a tileset bitmap appended to it (first two bytes are not 'BM') and the first four bytes are 'elvl' then you have an Extended LVL file.~~

	If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].

	~~This regular format is also described in http://www.rarefied.org/subspace/lvlformat.html~~

	~~Basically it is a bitmap with tile data appended to it.~~
	~~Each tile is represented in this format: (little endian)~~
	~~<pre>~~
	~~struct~~
	{
	~~unsigned long x : 12;~~
	~~unsigned long y : 12;~~
	~~unsigned long tile : 8;~~
	};
	~~</pre>~~

	~~The x and y must not exceed 1023.~~

	~~== Tileset ==~~
	~~This is an uncompressed bitmap image (typically 256-color) 304x160 [[Pixels \| pixels]], making each [[Tiles \| tile]] 16x16 pixels.~~

	~~[[Image:Tileset.jpg\|Tileset]]~~

	~~When editing maps with a tileset, there are different types of tiles, outlined below:~~

	~~[[Image:TilesetDescription.PNG\|Tileset With Descriptions]]~~

	Note that although you might have a good looking soccer goal or flag tile, it will not show up in the game. This is because there is a custom [[animation]] for these two tiles. You can find and edit these tiles by looking at Continuum\graphics\goal.bm2 and Continuum\graphics\flag.bm2. You can have other users use your custom goal or flag animation by including your new animations in a [[LVZ]] File.

	~~== Special Objects ==~~
	~~These are special animated objects. The most popular map editor, [[SSME]], calls these 'Special Objects' and changes the mouse pointer to a stamper.~~

	~~There are five objects available:~~
	*A small asteroid.
	*A medium asteroid (2x2 tiles).
	*Another small asteroid (was originally a large asteroid).
	*A space station (6x6 tiles).
	*A worm hole (5x5 tiles).

	~~== Extra Tiles ==~~
	~~There are some types, which are not meant to be part of typical mapmaking programs, but have been discovered and may have uses.~~

	~~Tile: Description~~
	*191: Invisible on screen, visible on radar, ships can go through them, items bounce off it, 'thors' go through it. (If you 'launch' an item while in it, the item will float suspended in space).
	*192-215: Invisible on screen, visible on radar, solid block (like any other tile).
	*216: A small asteroid, nothing not previously known about this.
	*217: A medium asteroid, nothing not previously known about this.
	*218: Another small asteroid, just the same as the other one, except the graphics are a little different(?)
	*219: A space station, nothing not previously known about this.
	*220: A wormhole, nothing not previously known about this.
	*221-240: Invisible on screen, visible on radar, solid block (like any other tile).
	*241: Invisible on screen, visible on radar, ship can go through it but Items disappear when they touch it.
	*242: Invisible on screen, invisible on radar, warps your ship on contact, items bounce off it, 'thors' disappear on contact.
	*243-251: Invisible on screen, invisible on radar, solid block (like any other tile).
	*252: Visible on screen (animated enemy brick), invisible on radar, items go through it, your ship gets warped after a random amount of time (0-2 seconds) while floating on it.
	*253: Visible on screen (animated team brick), invisible on radar, items go through it, so does your ship.
	*254: Invisible on screen, invisible on radar, items go through it, so does your ship. Possibly the internal representation of fly under tiles. You can't brick or mine while on it.
	*255: Visible on screen (animated prize), invisible on radar, items go through it, so does your ship. This is a prize, but it doesn't show up on radar, and no matter how many times you fly over it, you will never pick it up, ever.

	~~[[Category: Formats]]~~
	~~[[Category: Map]]~~

Smong: /* Extra Tiles */ seems someone was too liberal with uppercase letters (fixed)

2005-09-11T17:49:51Z

Extra Tiles: seems someone was too liberal with uppercase letters (fixed)

← Older revision		Revision as of 17:49, 11 September 2005
Line 45:		Line 45:

	Tile: Description		Tile: Description
	*191: Invisible on screen, ~~Visible~~ on radar, ~~Ships~~ can go through them, ~~Items~~ bounce off it, ~~Thors~~ go through it. (If you "launch" an item while in it, the item will float suspended in space).		*191: Invisible on screen, visible on radar, ships can go through them, items bounce off it, 'thors' go through it. (If you 'launch' an item while in it, the item will float suspended in space).
	*192-215: Invisible on screen, ~~Visible~~ on radar, ~~Solid~~ block (like any other tile).		*192-215: Invisible on screen, visible on radar, solid block (like any other tile).
	*216: A small asteroid, nothing ~~special~~ about this.		*216: A small asteroid, nothing not previously known about this.
	*217: A medium asteroid, nothing ~~special~~ about this.		*217: A medium asteroid, nothing not previously known about this.
	*218: Another small asteroid, just the same as the other one, except the graphics are a little different(?)		*218: Another small asteroid, just the same as the other one, except the graphics are a little different(?)
	*219: A ~~spacestation~~, nothing ~~special~~ about this.		*219: A space station, nothing not previously known about this.
	*220: A wormhole, nothing ~~special~~ about this.		*220: A wormhole, nothing not previously known about this.
	*221-240: Invisible on screen, ~~Visible~~ on radar, ~~Solid~~ block (like any other tile).		*221-240: Invisible on screen, visible on radar, solid block (like any other tile).
	*241: Invisible on screen, ~~Visible~~ on radar, ~~Ship~~ can go through it but Items disappear when they touch it.		*241: Invisible on screen, visible on radar, ship can go through it but Items disappear when they touch it.
	*242: Invisible on screen, ~~Invisible~~ on radar, ~~Warps~~ your ship on contact, items bounce off it, ~~Thors~~ disappear on contact!		*242: Invisible on screen, invisible on radar, warps your ship on contact, items bounce off it, 'thors' disappear on contact.
	*243-251: Invisible on screen, ~~Invisible~~ on radar, ~~Solid~~ block (like any other tile).		*243-251: Invisible on screen, invisible on radar, solid block (like any other tile).
	*252: Visible on screen (~~Animated NME~~ brick), ~~Invisible~~ on radar, ~~Items~~ go through it, your ship gets warped after a random amount of time (0-2 seconds) while floating on it.		*252: Visible on screen (animated enemy brick), invisible on radar, items go through it, your ship gets warped after a random amount of time (0-2 seconds) while floating on it.
	*253: Visible on screen (~~Animated Team~~ brick), ~~Invisible~~ on radar, ~~Items~~ go through it, so does your ship.		*253: Visible on screen (animated team brick), invisible on radar, items go through it, so does your ship.
	*254: Invisible on screen, ~~Invisible~~ on radar, ~~Items~~ go through it, So does your ship~~. Not sure what its used for, but it seems you cant brick while on/near it~~. Possibly the internal representation of fly under tiles.		*254: Invisible on screen, invisible on radar, items go through it, so does your ship. Possibly the internal representation of fly under tiles. You can't brick or mine while on it.
	*255: Visible On screen (~~Animated Prize~~), ~~Invisible~~ on radar, ~~Items~~ go through it, So does your ~~Ship~~. This is a prize, but it doesn't show up on radar, and no matter how many times you fly over it, you will never pick it up, ever.		*255: Visible on screen (animated prize), invisible on radar, items go through it, so does your ship. This is a prize, but it doesn't show up on radar, and no matter how many times you fly over it, you will never pick it up, ever.

	[[Category: Formats]]		[[Category: Formats]]
	[[Category: Map]]		[[Category: Map]]

Smong: added link back in

2005-06-09T12:58:48Z

added link back in

← Older revision		Revision as of 12:58, 9 June 2005
Line 4:		Line 4:

	If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].		If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].

			This regular format is also described in http://www.rarefied.org/subspace/lvlformat.html

	Basically it is a bitmap with tile data appended to it.		Basically it is a bitmap with tile data appended to it.

BaK: removed broken link

2005-06-09T10:09:37Z

removed broken link

← Older revision		Revision as of 10:09, 9 June 2005
Line 4:		Line 4:

	If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].		If the map does have a tileset bitmap (first two bytes are 'BM') then check the bfReserved1 field of the BITMAPFILEHEADER. If it is 49720, and the bfSize is not 49718, you are guarenteed to either have an eLVL file, or a corrupt file. For more information see the [[ELVL Format]].

	~~This regular format is also described in http://www4.ncsu.edu/~rniyenga/subspace/old/lvlformat.html~~

	Basically it is a bitmap with tile data appended to it.		Basically it is a bitmap with tile data appended to it.