Difference between revisions of "Object Data"

From wiki.vg
Jump to navigation Jump to search
(Added item frame orientation details)
(25 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== Object Data ==
+
This article documents the '''Data''' field in the [[Protocol#Spawn Object|Spawn Object]] packet. The field is of type Int, and the meaning of its contents depend on the [[Entities#Objects|type of object]] being spawned, as defined in the Type field of the same packet, and is documented below.
  
In the "Spawn Object/Vehicle" packet, additional metadata about the spawned entity may be provided.  The length and contents of this extra data depend on the type of object being spawnedNo matter what, the server must send at least one integer to the client, although 0 is a valid value. If a number other than zero is provided (for all entities), the following data is appended to the end of the object data:
+
In some cases, the data field has no meaning, but is only used to indicate presence of velocityIn others, it (and velocity) is always ignored.
 +
 
 +
== Item (id 2) ==
 +
 
 +
The int value is ignored, but should be set to <code>1</code> to indicate that velocity is present.
 +
 
 +
== Minecarts (id 10) ==
 +
 
 +
The int value itself specifies the minecart's functionality:
  
 
{| class="wikitable"
 
{| class="wikitable"
|- class="row0"
+
|-
! class="col0" | Field Name
+
! Value
! class="col1" | Field Type
+
! Minecart functionality
! class="col2" | Example
+
|-
! class="col3" | Notes
+
| 0
|- class="row2"
+
| Empty (ride-able) minecart
| class="col0 centeralign" | Speed X
+
|-
| class="col1 centeralign" | short
+
| 1
| class="col2 centeralign" | <code>0</code>
+
| Chest minecart
| class="col3" | The speed of the object
+
|-
|- class="row2"
+
| 2
| class="col0 centeralign" | Speed Y
+
| Furnace (powered) minecart
| class="col1 centeralign" | short
+
|-
| class="col2 centeralign" | <code>0</code>
+
| 3
| class="col3" | The speed of the object
+
| TNT minecart
|- class="row2"
+
|-
| class="col0 centeralign" | Speed Z
+
| 4
| class="col1 centeralign" | short
+
| Spawner minecart
| class="col2 centeralign" | <code>0</code>
+
|-
| class="col3" | The speed of the object
+
| 5
|}
+
| Hopper minecart
 +
|-
 +
| 6
 +
| Command Block minecart
 +
|}
  
== Meaning of int field ==
+
== Item Frame (id 71) ==
  
=== Item Frame (id 71) ===
+
{| class="wikitable"
 +
|-
 +
! Value
 +
! Orientation
 +
|-
 +
| 0
 +
| Down
 +
|-
 +
| 1
 +
| Up
 +
|-
 +
| 2
 +
| North
 +
|-
 +
| 3
 +
| South
 +
|-
 +
| 4
 +
| West
 +
|-
 +
| 5
 +
| East
 +
|}
 +
You have to set both Orientation and Yaw/Pitch accordingly, otherwise it will not work.
 +
 
 +
Velocity in the packet is always ignored.
 +
 
 +
== Falling Block (id 70) ==
  
 
{| class="wikitable"
 
{| class="wikitable"
|- class="row0"
+
|-
! class="col0" | Field Name
+
! Field name
! class="col1" | Field Type
+
! Field type
! class="col2" | Example
+
! Example
! class="col3" | Notes
+
! Notes
|- class="row1"
+
|-
| class="col0 centeralign" | Orientation
+
| Block type
| class="col1 centeralign" | int
+
| Int
| class="col2 centeralign" | <code>3</code>
+
| <code>12</code>
| class="col3" | 0-3: South, West, North, East
+
| <code><nowiki>BlockID | (Metadata << 12)</nowiki></code>
|}
+
|}
 +
 
 +
Velocity in the packet is always ignored.
  
=== Falling Block (id 70) ===
+
== Fishing Float (id 90) ==
  
 
{| class="wikitable"
 
{| class="wikitable"
|- class="row0"
+
! Field name
! class="col0" | Field Name
+
! Field type
! class="col1" | Field Type
+
! Example
! class="col2" | Example
+
! Notes
! class="col3" | Notes
+
|-
|- class="row1"
+
| Owner
| class="col0 centeralign" | Block Type
+
| Int
| class="col1 centeralign" | int
+
|  
| class="col2 centeralign" | <code>12</code>
+
| The entity ID of the owner
| class="col3" | <code>BlockID | (Metadata << 0xC)</code>
+
|}
|}
+
 
 +
Velocity in the packet is ignored, and instead should be inferred from the shooter's position.
  
=== Projectiles ===
+
{{Need Info|What's the exact algorithm for determining this?}}
  
This includes ghast fireballs, arrows, and fishhooks (probably more).
+
== Arrow (id 60) and Spectral Arrow (id 91) ==
  
 
{| class="wikitable"
 
{| class="wikitable"
|- class="row0"
+
|-
! class="col0" | Field Name
+
! Field name
! class="col1" | Field Type
+
! Field type
! class="col2" | Example
+
! Example
! class="col3" | Notes
+
! Notes
|- class="row1"
+
|-
| class="col0 centeralign" | Entity ID
+
| Entity ID
| class="col1 centeralign" | int
+
| Int
| class="col2 centeralign" | <code>64</code>
+
| <code>64</code>
| class="col3" | The entity ID of the thrower
+
| The entity ID of the shooter + 1 (Subtract 1 to get the actual entity ID)
|}
+
|}
 +
 
 +
== Llama spit (id 68) ==
  
=== Splash Potions ===
+
Velocity is always used even though the data field is always 0.
  
{| class="wikitable"
+
== Fireball (id 63), small fireball (id 64), dragon fireball (id 93), and wither skull (id 66) ==
|- class="row0"
+
 
! class="col0" | Field Name
+
The data field stores the ID of the shooting entity, or 0 if there was no shooting entity.  Velocity is used even if data is set to 0.
! class="col1" | Field Type
+
 
! class="col2" | Example
+
== Shulker bullet (id 67) ==
! class="col3" | Notes
+
 
|- class="row1"
+
Velocity is always used even though the data field is always 0.
| class="col0 centeralign" | Entity ID
+
 
| class="col1 centeralign" | int
+
== Potion (id 73) ==
| class="col2 centeralign" | <code>64</code>
+
 
| class="col3" | Potion data value
+
Velocity in the packet is always ignored.
|}
+
 
 +
== EXP bottle (id 75) ==
 +
 
 +
Velocity in the packet is always ignored.
  
For more information on potion data values, see [http://www.minecraftwiki.net/wiki/Data_values#Potions].
+
[[Category:Protocol Details]]
 +
[[Category:Minecraft Modern]]

Revision as of 15:04, 6 August 2019

This article documents the Data field in the Spawn Object packet. The field is of type Int, and the meaning of its contents depend on the type of object being spawned, as defined in the Type field of the same packet, and is documented below.

In some cases, the data field has no meaning, but is only used to indicate presence of velocity. In others, it (and velocity) is always ignored.

Item (id 2)

The int value is ignored, but should be set to 1 to indicate that velocity is present.

Minecarts (id 10)

The int value itself specifies the minecart's functionality:

Value Minecart functionality
0 Empty (ride-able) minecart
1 Chest minecart
2 Furnace (powered) minecart
3 TNT minecart
4 Spawner minecart
5 Hopper minecart
6 Command Block minecart

Item Frame (id 71)

Value Orientation
0 Down
1 Up
2 North
3 South
4 West
5 East

You have to set both Orientation and Yaw/Pitch accordingly, otherwise it will not work.

Velocity in the packet is always ignored.

Falling Block (id 70)

Field name Field type Example Notes
Block type Int 12 BlockID | (Metadata << 12)

Velocity in the packet is always ignored.

Fishing Float (id 90)

Field name Field type Example Notes
Owner Int The entity ID of the owner

Velocity in the packet is ignored, and instead should be inferred from the shooter's position.

Huh.png The following information needs to be added to this page:
What's the exact algorithm for determining this?

Arrow (id 60) and Spectral Arrow (id 91)

Field name Field type Example Notes
Entity ID Int 64 The entity ID of the shooter + 1 (Subtract 1 to get the actual entity ID)

Llama spit (id 68)

Velocity is always used even though the data field is always 0.

Fireball (id 63), small fireball (id 64), dragon fireball (id 93), and wither skull (id 66)

The data field stores the ID of the shooting entity, or 0 if there was no shooting entity. Velocity is used even if data is set to 0.

Shulker bullet (id 67)

Velocity is always used even though the data field is always 0.

Potion (id 73)

Velocity in the packet is always ignored.

EXP bottle (id 75)

Velocity in the packet is always ignored.