Difference between revisions of "Object Data"
m (This should've been updated to spawn entity a while ago.) |
|||
| Line 1: | Line 1: | ||
| − | This article documents the '''Data''' field in the [[Protocol#Spawn | + | This article documents the '''Data''' field in the [[Protocol#Spawn Entity|Spawn Entity]] 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 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. | 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. | ||
Revision as of 10:50, 13 November 2021
This article documents the Data field in the Spawn Entity 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.
Contents
- 1 Item (id 2)
- 2 Minecarts (id 10)
- 3 Item Frame (id 71)
- 4 Falling Block (id 70)
- 5 Fishing Float (id 90)
- 6 Arrow (id 60) and Spectral Arrow (id 91)
- 7 Llama spit (id 68)
- 8 Fireball (id 63), small fireball (id 64), dragon fireball (id 93), and wither skull (id 66)
- 9 Shulker bullet (id 67)
- 10 Potion (id 73)
- 11 EXP bottle (id 75)
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.
 |
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.
