VoxelUpdateResponse
LEGACY — never emitted. The game server retired the dedicated voxel-update response opcode (132); an applied update now arrives as your own VoxelUpdateNotification (the sender is included in the chunk fan-out) and failures arrive as GenericErrorResponse. This type remains in the UdpNotification union for backward compatibility only — do not select it in new code; it will be removed in a future major version.
type VoxelUpdateResponse {
appId: BigInt!
chunkX: BigInt!
chunkY: BigInt!
chunkZ: BigInt!
distance: Int!
decayRate: Int!
uuid: String!
sequenceNumber: Int!
epochMillis: BigInt!
}
Fields
VoxelUpdateResponse.appId ● BigInt! non-null scalar
The ID of the app where the voxel update was processed.
VoxelUpdateResponse.chunkX ● BigInt! non-null scalar
The X coordinate of the chunk containing the voxel.
VoxelUpdateResponse.chunkY ● BigInt! non-null scalar
The Y coordinate of the chunk containing the voxel.
VoxelUpdateResponse.chunkZ ● BigInt! non-null scalar
The Z coordinate of the chunk containing the voxel.
VoxelUpdateResponse.distance ● Int! non-null scalar
Chunk replication distance (0-8) from the original message.
VoxelUpdateResponse.decayRate ● Int! non-null scalar
Decay algorithm (0-5) from the original message.
VoxelUpdateResponse.uuid ● String! non-null scalar
The unique identifier for this voxel update.
VoxelUpdateResponse.sequenceNumber ● Int! non-null scalar
The sequenceNumber echoed back from the originating sendVoxelUpdate request (a uint8, 0-255, wrapping at modulo 256). Use it to correlate this response with that send. Correlation only — not an idempotency key.
VoxelUpdateResponse.epochMillis ● BigInt! non-null scalar
Server-generated epoch milliseconds timestamp.
Implemented By
UdpNotification union