Resource pack resets after entering configuration phase
Description
After receiving a ClientboundStartConfigurationPacket the client appears to reset it's current server resource pack, although there is no other server resource pack sent during the configuration phase. For server networks with a server resource pack, this might become a problem, as they can't send a re-configuration packet without reloading resources twice (maybe only once if the resource pack is sent during the configuration phase, haven't tested it).
I'm not sure if this change was intended with the switch to the configuration network phase (like the deletion of chat messages MC-265250), but I don't think the resource pack should reset on every configuration change (without leaving the server).
Linked Issues
is duplicated by4
MC-265673Server resource pack unload after re-entering configuration phaseDuplicateMC-278095Resource pack load and unload using a server transfer tool DuplicateMC-278265Server resource pack is removed after double transferDuplicateMC-278822Server resource packs are cleared when transferring while in the configuration phase.Duplicate
Created Issue:
Resource pack resets after entering configuration phase
Description
After receiving a ClientboundStartConfigurationPacket the client appears to reset it's current server resource pack, although there is no other server resource pack sent during the configuration phase. For server networks with a server resource pack, this might become a problem, as they can't send a re-configuration packet without reloading resources twice (maybe only once if the resource pack is sent during the configuration phase, haven't tested it). Additionally it looks like it's no longer possible to update tags, features or registry data without reloading resources twice (for a server with a server resource pack).
I'm not sure if this change was intended with the switch to the configuration network phase (like the deletion of chat messages https://bugs.mojang.com/browse/MC-265250), but I don't think the resource pack should reset on every configuration change (without leaving the server).
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Description
After receiving a ClientboundStartConfigurationPacket the client appears to reset it's current server resource pack, although there is no other server resource pack sent during the configuration phase. For server networks with a server resource pack, this might become a problem, as they can't send a re-configuration packet without reloading resources twice (maybe only once if the resource pack is sent during the configuration phase, haven't tested it). Additionally it looks like it's no longer possible to update tags, features or registry data without reloading resources twice (for a server with a server resource pack).
I'm not sure if this change was intended with the switch to the configuration network phase (like the deletion of chat messages
https://bugs.mojang.com/browse/MC-265250), but I don't think the resource pack should reset on every configuration change (without leaving the server).Description
After receiving a ClientboundStartConfigurationPacket the client appears to reset it's current server resource pack, although there is no other server resource pack sent during the configuration phase. For server networks with a server resource pack, this might become a problem, as they can't send a re-configuration packet without reloading resources twice (maybe only once if the resource pack is sent during the configuration phase, haven't tested it). Additionally it looks like it's no longer possible to update tags, features or registry data without reloading resources twice (for a server with a server resource pack).
I'm not sure if this change was intended with the switch to the configuration network phase (like the deletion of chat messages
MC-265250), but I don't think the resource pack should reset on every configuration change (without leaving the server).
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
Description
After receiving a ClientboundStartConfigurationPacket the client appears to reset it's current server resource pack, although there is no other server resource pack sent during the configuration phase. For server networks with a server resource pack, this might become a problem, as they can't send a re-configuration packet
without reloading resources twice (maybe only once if the resource pack is sent during the configuration phase, haven't tested it).Additionally it looks like it's no longer possible to update tags, features or registry data without reloading resources twice (for a server with a server resource pack).I'm not sure if this change was intended with the switch to the configuration network phase (like the deletion of chat messages
MC-265250), but I don't think the resource pack should reset on every configuration change (without leaving the server).
![[Mojang] Maxime Lebrot](../../../data/avatars/users/18941.svg){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
is cloned by
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
is duplicated by
relates to
is cloned by
Seeing as
MC-265673was closed now as a duplicate of this I feel like this should be reopened now. I don't think this is a feature request. The client unnecessarily reloading the complete resources wasting processing power and energy in the process seems like a bug to me (besides the actually lost functionality of course which some might think of as a feature request but in reality breaking this makes server resource packs basically unusable in any of the wide-spread settings that they are used).Please re-evaluate if it's not possible to improve this process somehow so that packs do not always need to be reloaded if they didn't actually change.
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
is duplicated by
After creating this issue, I came across this one which seems to be the same problem: MC-265463
Thank you for your report!
We're tracking this issue in MC-265463, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-265463) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-265463, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-265463) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm, this will be very annoying for users on servers with network-wide resource packs
This is a feature request
The link you pinned is not working.
Any news about this ?
This is a very problematic situation for users playing on server networks.
Each time a user switch of backend server location in a network, the resource pack reset ...
The feedback got deleted/not approved by Mojang. If this is handled as a new feature I don't know where to request it, if it won't be accepted on the feedback page. You are not alone with this issue, it affects every server using a server wide resource pack. As other resource pack bugs with the new configuration phase got fixed in the latest snapshot, I'll just hope this gets silently fixed in a future version as well.
This worked fine in the past and is really annoying when just switching servers in a network now...
Would be awesome if this could get resolved.