XML:AKEV: Difference between revisions

XML:AKEV (view source)

Revision as of 21:56, 17 March 2014

28 bytes added , 17 March 2014

m

copy edit

Iritscen

Bureaucrats, Interface administrators, Administrators

18,700

edits

@@ Line 225: / Line 225: @@
 |valign="top"| <Color>
 |valign="top"| color
-| Colors are stored as four value arrays: R G B [A], which means Red Green Blue and the optional Alpha channel value. Min value: 0. Max value: 255.
+| Colors are stored as four-element arrays: R G B [A], which means Red, Green, Blue, and the optional Alpha channel value. Min value: 0. Max value: 255.
-: This belongs to [[XML:ONLV#Vertex_coloring|vertex coloring]].
+: This is used for [[XML:ONLV#Vertex_coloring|vertex coloring]].
 |-
 |valign="top"| <Flags>
@@ Line 232: / Line 232: @@
 |
 : DoorFrame (invisible quad that uses the _DOOR_FRAME texture, however, this flag has no effect on the game)
-: Ghost (pathfinding volume separator, see AKVA etc)
+: Ghost (pathfinding volume separator, see AKVA, etc.)
 : StairsUp
 : StairsDown
@@ Line 247: / Line 247: @@
 : Horizontal (slope > 70°, automatic creation)
 : Vertical (slope < 70°, automatic creation)
-: GridIgnore (onisplit will ignore the object when it calculate the pathfinding grids, so the grids will be white)
+: GridIgnore (OniSplit will ignore the object when it calculates the pathfinding grids, so the grids will be white)
-: NoDecals (decals can't be applied to object, doors use this)
+: NoDecals (decals can't be applied to object; doors use this)
 : Furniture (Cntl + Shift + s: makes furniture textures red)
 : ProjectionBit0 (automatic creation)
@@ Line 257: / Line 257: @@
 |valign="top"| <ObjectId>
 |valign="top"| int32
-| [[OBD:ONOA|Object type and object id]] are merged here to one number. The value is -1 if the quad doesn't belong to an object.
+| [[OBD:ONOA|Object type and object id]] are merged here into one number. The value is -1 if the quad doesn't belong to an object.
-:Example 1: If <ObjectId> is 251658333 the converted hex value is (0)f 00 00 5d. With that you get the type 0f = console and the id 5d = 93.
+:Example 1: If <ObjectId> is 251658333, the converted hex value is (0)f 00 00 5d. With that you get the type 0f = console and the id 5d = 93.
-:Example 2: If <ObjectId> is 50331739 the converted hex value is (0)3 00 00 5b. With that you get the type 03 = door and the id 5b = 91.
+:Example 2: If <ObjectId> is 50331739, the converted hex value is (0)3 00 00 5b. With that you get the type 03 = door and the id 5b = 91.
 Types:
 : 01 - character
@@ Line 523: / Line 523: @@
 | <IDXA id="...">
 | integer
-| Instance Id. Should be 12.
+| Instance ID. Should be 12.
 |-
 | <Indices>
@@ Line 531: / Line 531: @@
 |valign="top"| <Int32>
 |valign="top"| int32
-| Stores an object Id used by BSL commands env_broken, env_shade, env_show and env_texswap. Ergo this IDXA should belong to [[OBD:IDXA_AKEV_2|AKEV 2]].
+| Stores an object ID used by BSL commands "env_broken", "env_shade", "env_show" and "env_texswap". Ergo this IDXA should belong to [[OBD:IDXA_AKEV_2|AKEV 2]].
-: ''Why can Ids appear here multiple times?'' Most objects are made of multiple triangles/quads. Probably there are as many equal Ids as an object has triangle/quads. So when you want show/hide/etc. an object, all triangles/quads will be targeted by this way.
+: ''Why can IDs appear here multiple times?'' Most objects are made of multiple triangles/quads. Probably there are as many identical IDs as an object has triangles/quads. This way, when you want show/hide/etc. an object, all of its triangles/quads will be affected.
 |}