LVZ Format - Revision history

Samapico at 21:14, 24 February 2007

2007-02-24T21:14:32Z

Cyan~Fire: a few corrections, rm redundant header

2005-03-27T06:03:45Z

a few corrections, rm redundant header

Pests: Changed cat

2005-01-13T04:15:58Z

Changed cat

Smong: made changes for ctm 37 compatibility

2005-01-12T00:21:44Z

made changes for ctm 37 compatibility

BaK: Fixed signed / unsigned variables

2005-01-11T23:14:53Z

Fixed signed / unsigned variables

BaK: elaborated more on file time

2005-01-11T23:10:54Z

elaborated more on file time

Mine GO BOOM: Converted from

 to 2005-01-11T22:08:00Z
Converted from <pre> to <table>
Show changes
Pests: category
2005-01-11T21:02:26Z
category






				
				
				
				
				
				← Older revision
				Revision as of 21:02, 11 January 2005
				
Line 238:
Line 238:
    This is not true for imageobjects.     This is not true for imageobjects.
  </pre>   </pre>
  + 
  + [[Category: Protocol]]

CypherJF: minor updates.. hopefully i didn't butcher this to death..

2005-01-11T18:39:39Z

minor updates.. hopefully i didn't butcher this to death..

CypherJF: minor updates.. hopefully i didn't butcher this to death..

2005-01-11T18:38:45Z

minor updates.. hopefully i didn't butcher this to death..

@@ Line 237: / Line 237: @@
 <tr>
 <td>i16</td>
-<td>Display Time</td>
+<td>Animation Time</td>
-<td>How long to display each frame for. '''NOTE''': This is stored in 1/100th of a second ''not'' 1/10</td>
+<td>How long does the whole animation lasts. '''NOTE''': This is stored in 1/100th of a second ''not'' 1/10</td>
 </tr>
 <tr>

@@ Line 1: / Line 1: @@
-== LVZ File format description ==
+This is a quick description of the current .lvz file format. Only Continuum .37 and higher support [[LVZ]]s. If you design a program to read or write LVZ files, please safely handle the differences of the Types for each section, since newer continuum version will add newer sections.
 The first 8 bytes of every .lvz file:
@@ Line 288: / Line 286: @@
 ==Extra information about bit ordering==
-All the data is in confusing little endian byte ordering...here's a layout of the data within each byte:
+All the data is in confusing little-endian byte ordering. Here's a layout of the data within each byte:
 <pre>MapObject:

← Older revision		Revision as of 04:15, 13 January 2005
Line 325:		Line 325:
	Also note that although ini's store the display time in 1/100th seconds for map and screenobjects... they are stored in the file as 1/10th seconds. This is not true for imageobjects.		Also note that although ini's store the display time in 1/100th seconds for map and screenobjects... they are stored in the file as 1/10th seconds. This is not true for imageobjects.

−	[[Category: ~~Protocol~~]]	+	[[Category: Formats]]

@@ Line 1: / Line 1: @@
-==LVZ File format description for Continuum 0.38==
+== LVZ File format description ==
-This is a quick description of the current .lvz format for continuum .38. Please safely handle the differences of the Types for each section, since newer continuum version will add newer sections.
+This is a quick description of the current .lvz format. Currently only Continuum .37 and higher support LVZ. Please safely handle the differences of the Types for each section, since newer continuum version will add newer sections.
 The first 8 bytes of every .lvz file:
@@ Line 74: / Line 74: @@
 '''Object section can now have two different types, though only the Screen Objects are changed'''
 Object Section always starts with this 12 byte header:

@@ Line 17: / Line 17: @@
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>Count</td>
 <td>How many compressed sections are in this .lvz.</td>
@@ Line 39: / Line 39: @@
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>Decompress Size</td>
 <td>The size of the data after it would be decompressed. This is the value you should set your out-buffer for the zlib's compression call.</td>
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>File Time</td>
 <td>This can either be a file time, if this compressed section is a file, or it could be 0. If 0, then is a special compressed section. The file time is the standard time_t format used by windows/unix (seconds since midnight, January 1st, 1970).</td>
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>Compressed Size</td>
 <td>The size of the compressed data in the .lvz. This is how many bytes you'll need to read to get your required data.</td>
@@ Line 89: / Line 89: @@
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>Object Count</td>
-<td>How many object definitions are in this Object Section.</td>
+<td>How many object (mapobject and screenobject) definitions are in this Object Section.</td>
 </tr>
 <tr>
-<td>i32</td>
+<td>u32</td>
 <td>Image Count</td>
-<td>How many image definitions are in this Object Section.</td>
+<td>How many image (imageobject) definitions are in this Object Section.</td>
 </tr>
 </table>
@@ Line 113: / Line 113: @@
 </tr>
 <tr>
-<td>i1</td>
+<td>u1</td>
 <td>Map Object</td>
 <td>A bool-like value. If true, this is a Map Object. If false, then is a Screen Object.</td>
 </tr>
 <tr>
-<td>i15</td>
+<td>u15</td>
 <td>Object ID</td>
 <td>The value for this object id, for use with *objon for example.</td>
@@ Line 133: / Line 133: @@
 </tr>
 <tr>
-<td>i8</td>
+<td>u8</td>
 <td>Image Number</td>
 <td>Which of the Image Definitions this object will use for its graphic.</td>
 </tr>
 <tr>
-<td>i8</td>
+<td>u8</td>
 <td>Layer</td>
 <td>Which layer it will be displayed on. Values for this later.</td>
 </tr>
 <tr>
-<td>i12</td>
+<td>u12</td>
 <td>Display Time</td>
 <td>How long will display for, in 1/10th of a second.</td>
 </tr>
 <tr>
-<td>i4</td>
+<td>u4</td>
 <td>Display Mode</td>
 <td>Which display mode this object uses. Values later.</td>
@@ Line 165: / Line 165: @@
 </tr>
 <tr>
-<td>i1</td>
+<td>u1</td>
 <td>Map Object</td>
 <td>A bool-like value. If true, this is a Map Object. If false, then is a Screen Object.</td>
 </tr>
 <tr>
-<td>i15</td>
+<td>u15</td>
 <td>Object ID</td>
 <td>The value for this object id, for use with *objon for example.</td>
@@ Line 195: / Line 195: @@
 </tr>
 <tr>
-<td>i8</td>
+<td>u8</td>
 <td>Image Number</td>
 <td>Which of the Image Definitions this object will use for its graphic.</td>
 </tr>
 <tr>
-<td>i8</td>
+<td>u8</td>
 <td>Layer</td>
 <td>Which layer it will be displayed on. Values for this later.</td>
 </tr>
 <tr>
-<td>i12</td>
+<td>u12</td>
 <td>Display Time</td>
 <td>How long will display for, in 1/10th of a second.</td>
 </tr>
 <tr>
-<td>i4</td>
+<td>u4</td>
 <td>Display Mode</td>
 <td>Which display mode this object uses. Values later.</td>
@@ Line 284: / Line 284: @@
-==Extra information about little/big endian bytes==
+==Extra information about bit ordering==
 All the data is in confusing little endian byte ordering...here's a layout of the data within each byte:

← Older revision		Revision as of 21:02, 11 January 2005
Line 238:		Line 238:
	This is not true for imageobjects.		This is not true for imageobjects.
	</pre>		</pre>
		+
		+	[[Category: Protocol]]

@@ Line 236: / Line 236: @@
 Also note that altough ini's store the display time in 1/100th
   seconds for map and screenobjects... they are stored in the file as 1/10th seconds.
-  This is not true for imageobjects
+  This is not true for imageobjects.
 </pre>

@@ Line 33: / Line 33: @@
 i32		File Time - This can either be a file time, if this
-                      compressed section is a file, or it could be 0. If
+                      compressed section is a file, or it could be 0.
-, then is a special compressed section. The file
+                    If 0, then is a special compressed section.
-                     time is the standard time_t format used by windows/unix.
+		    The file time is the standard time_t format used
 i32		Compressed Size - The size of the compressed data in the
@@ Line 72: / Line 73: @@
 Object Section always starts with this 12 byte header:
 -len str	Type - Can be 'CLV1' or 'CLV2'.
 i32		Object Count - How many object definitions are in this Object Section.
 i32		Image Count - How many image definitions are in this Object Section.
 *** For both of CLV1's Screen/Map object, or CLV2's Map object ***
   After the Object Section header, you would loop through the Object Count
   reading 10 bytes at a time till you hit the Object Count. Each of these
 byte sections are the Object definitions:
 i1		Map Object - A bool-like value. If true, this is a Map Object.
                      If false, then is a Screen Object.
 i15		Object ID - The value for this object id, for use with *objon
                      for example.
 i16		X Coord - The X coord value, in pixels, this object will be
                      displayed on. More info later.
 i16		Y Coord - The Y coord value, in pixels.
 i8		Image Number - Which of the Image Definitions this object will
                      use for its graphic.
 i8		Layer - Which layer it will be displayed on. Values for this later,
 i12		Display Time - How long will display for, in 1/10th of a second.
 i4		Display Mode - Which display mode this object uses. Values later.
 *** CLV2's Screen Object ***
 i1		Map Object - A bool-like value. If true, this is a Map Object.
                      If false, then is a Screen Object.
 i15		Object ID - The value for this object id, for use with *objon for example.
 u4		X Type - Which part of the screen the X coord is offset
                      from (see OffsetTypes lower down)
 i12		X Coord - The X coord value, in pixels, this object will be displayed on.
                      More info later.
 u4		Y Type - Same as for X
 i12		Y Coord - The Y coord value, in pixels.
 i8		Image Number - Which of the Image Definitions this object will use for
                      its graphic.
-i8		Layer - Which layer it will be displayed on. Values for this later,
 i12		Display Time - How long will display for, in 1/10th of a second.
 i4		Display Mode - Which display mode this object uses. Values later.
@@ Line 115: / Line 138: @@
 i16		X Count - How many columns are in this image. Used for animations.
 i16		Y Count - How many rows are in this image.
 i16		Display Time - How long to display each frame for.
-                   EDIT: This is stored in 1/100th of a second NOT 1/10
+                EDIT: This is stored in 1/100th of a second NOT 1/10
 Null-end str	File Name - This will be null ended. This is which file this image
                     uses. The file name is not required to be included with the .lvz,
@@ Line 210: / Line 236: @@
 Also note that altough ini's store the display time in 1/100th
   seconds for map and screenobjects... they are stored in the file as 1/10th seconds.
-  This is not true for imageobjects.
+  This is not true for imageobjects
 </pre>