1
0
mirror of https://github.com/Mojang/bedrock-protocol-docs.git synced 2025-08-22 21:02:46 +00:00
Files
bedrock-protocol-docs/html/ServerboundLoadingScreenPacket.html
2025-07-08 11:52:36 -07:00

20 lines
1.8 KiB
HTML

<!DOCTYPE html> <html> <head><style>table{font-family: arial, sans-serif;border-collapse: collapse;width: 100% ;}.tab { margin-left: 40px; }td, th{text-align: left;padding: 8px;}tr:nth-child(even) {background-color: #dddddd;}div#expand{display:block;}</style> </head> <body><h1>ServerboundLoadingScreenPacket (id: 312)</h1>
<table><col width="1%"><col width="99%"><tr><th></th><th></th></tr><tr><td> <b>Purpose:</b> </td>
<td>Sent from the client to the server to message to the server about the state of the loading screen.</td>
</tr><tr><td> <b>Notes:</b> </td>
<td>In order for the client to send a packet with StartLoadingScreen, the server needs to anticipate that this packet is coming.
If the server doesn't expect that we are about to start a loading screen, the server will disconnect the client.
EndLoadingScreen is sent by the client when the loading screen closes.
The Loading Screen Id field will be empty if the loading screen is triggered by the initial loading into of a world.
The Loading Screen Id field will have a value if sent by the server. This currently happens as part of ChangeDimensionPacket if the player is alive.</td>
</tr></table><br><h2>Payload</h2>
<img src="svg/ServerboundLoadingScreenPacket.svg" alt="ServerboundLoadingScreenPacket">
<br><br><br><table><col width="10%"><col width="10%"><col width="15%"><col width="80%"><tr><th>Field Name</th><th>Field Type</th><th>Field Constraints</th><th>Field Notes</th></tr><tr><td>Loading Screen Packet Type</td>
<td>enum ServerboundLoadingScreenPacketType</td>
<td></td>
<td></td>
</tr><tr><td>Loading Screen Id</td>
<td>unsigned int</td>
<td></td>
<td>This will be set if the server gives us a value. If the server doesn't expect this value, then the client will get disconnected.</td>
</tr></table></body> </html>