Difference between revisions of "Object Data"
(Updated outdated info) |
(Cleanup) |
||
Line 27: | Line 27: | ||
|} | |} | ||
− | The Notchian client clamps invalid values into the valid range through the modulus operator. | + | 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. | Velocity in the packet is always ignored. | ||
Line 51: | Line 51: | ||
|} | |} | ||
− | The Notchian client clamps invalid values into the valid range through the modulus operator. | + | 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 | + | {{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. | ||
Line 105: | Line 105: | ||
== [[Entity_metadata#Warden|Warden]] == | == [[Entity_metadata#Warden|Warden]] == | ||
− | If a value of 1 is specified, the Warden will | + | {| class="wikitable" |
+ | |- | ||
+ | ! Field name | ||
+ | ! Field type | ||
+ | ! Notes | ||
+ | |- | ||
+ | | Pose | ||
+ | | 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]] |
Revision as of 19:55, 20 October 2023
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.
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 |
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.
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. |