Difference between revisions of "Object Data"

From wiki.vg
Jump to navigation Jump to search
(Updated this severely outdated page to the latest version)
(Use Template:Type for type links.)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
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.
+
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 [[Entity_metadata|type of entity]] 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.
+
== [[Entity_metadata#Item_Frame|Item Frame]] ==
−
 
 
−
== Item Frame ==
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 28: Line 26:
 
  | East
 
  | East
 
  |}
 
  |}
−
You have to set both Orientation and Yaw/Pitch accordingly, otherwise it will not work.
+
 
 +
The Notchian client clamps invalid values into the valid range through the modulus operator. If the resulting value is negative, the absolute value is used.
 +
 
 +
Velocity in the packet is always ignored.
 +
 
 +
== [[Entity_metadata#Painting|Painting]] ==
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Value
 +
! Orientation
 +
|-
 +
| 2
 +
| North
 +
|-
 +
| 3
 +
| South
 +
|-
 +
| 4
 +
| West
 +
|-
 +
| 5
 +
| East
 +
|}
 +
 
 +
The Notchian client clamps invalid values into the valid range through the modulus operator. If the resulting value is negative, the absolute value is used.
 +
 
 +
{{Warning|Although the values of 0 and 1 are invalid, the Notchian client uses the same clamping algorithm as [[#Item_Frame|Item Frame]], which can result in any value from 0 to 5. If the resulting value is invalid, the entity will fail to spawn.}}
  
 
Velocity in the packet is always ignored.
 
Velocity in the packet is always ignored.
  
−
== Falling Block ==
+
== [[Entity_metadata#Falling_Block|Falling Block]] ==
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 41: Line 66:
 
  |-
 
  |-
 
  | Block state ID
 
  | Block state ID
−
  | Int
+
  | {{Type|Int}}
 
  | ID of the block state that the falling block will represent.
 
  | ID of the block state that the falling block will represent.
 
  |}
 
  |}
Line 47: Line 72:
 
Velocity in the packet is always ignored.
 
Velocity in the packet is always ignored.
  
−
== Fishing Float ==
+
== [[Entity_metadata#Fishing_Hook|Fishing Hook]] ==
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 55: Line 80:
 
  |-
 
  |-
 
  | Owner
 
  | Owner
−
  | Int
+
  | {{Type|Int}}
 
  | The entity ID of the owner
 
  | The entity ID of the owner
 
  |}
 
  |}
 +
 +
{{Warning|If the entity with the Owner ID doesn't exist in the client, the entity will fail to spawn.}}
  
 
Velocity in the packet is ignored, and instead should be inferred from the shooter's position.
 
Velocity in the packet is ignored, and instead should be inferred from the shooter's position.
Line 63: Line 90:
 
{{Need Info|What's the exact algorithm for determining this?}}
 
{{Need Info|What's the exact algorithm for determining this?}}
  
−
== Projectile ==
+
== [[Entity_metadata#Projectile|Projectile]] ==
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 72: Line 99:
 
  |-
 
  |-
 
  | Owner ID
 
  | Owner ID
−
  | Int
+
  | {{Type|Int}}
 
  | The entity ID of the owner
 
  | The entity ID of the owner
 
  |}
 
  |}
 +
 +
== [[Entity_metadata#Warden|Warden]] ==
 +
 +
{| class="wikitable"
 +
|-
 +
! Field name
 +
! Field type
 +
! Notes
 +
|-
 +
| Pose
 +
| {{Type|Int}}
 +
| If a value of 1 is specified, the Warden will spawn in the [[Entity_metadata#Entity_Metadata_Format|emerging pose]].
 +
Any other value is silently ignored.
 +
|}
 +
  
 
[[Category:Protocol Details]]
 
[[Category:Protocol Details]]
 
[[Category:Minecraft Modern]]
 
[[Category:Minecraft Modern]]

Latest revision as of 22:32, 24 February 2024

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 entity being spawned, as defined in the Type field of the same packet, and is documented below.

Item Frame

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

The Notchian client clamps invalid values into the valid range through the modulus operator. If the resulting value is negative, the absolute value is used.

Velocity in the packet is always ignored.

Painting

Value Orientation
2 North
3 South
4 West
5 East

The Notchian client clamps invalid values into the valid range through the modulus operator. If the resulting value is negative, the absolute value is used.

Warning.png Although the values of 0 and 1 are invalid, the Notchian client uses the same clamping algorithm as Item Frame, which can result in any value from 0 to 5. If the resulting value is invalid, the entity will fail to spawn.

Velocity in the packet is always ignored.

Falling Block

Field name Field type Notes
Block state ID Int ID of the block state that the falling block will represent.

Velocity in the packet is always ignored.

Fishing Hook

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

Warning.png If the entity with the Owner ID doesn't exist in the client, the entity will fail to spawn.

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?

Projectile

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

Warden

Field name Field type Notes
Pose Int If a value of 1 is specified, the Warden will spawn in the emerging pose.

Any other value is silently ignored.

Retrieved from "https://wiki.vg/index.php?title=Object_Data&oldid=18896"