MC-267868Vanilla resource pack not properly enabled on first launch
Step to reproduce:
1) Create a new .minecraft instance for the game (in our case, just remove the "resourcePacks" and "incompatibleResourcePacks" lines form your options.txt will work)
2) Launch the game, wait for the options init
3) You can see in your options.txt that resourcePacks is an empty list (it should contain "vanilla" because the vanilla pack is loaded)
4) Go to the pack screen and close it immediatly, the game will reload ressources even if you did not change anything because the list of enabled packs on the screen contain the vanilla pack, but the list in the options do not
5) You can verify that "vanilla" has been added to the resourcePacks list in options, and that going back to the pack screen and close it will not trigger more reload
UPDATE:
Found an easy fix. You just have to add "vanilla" to the default list in the GameOptions class constructor.
Linked Issues
NormalCreated Issue:
Vanilla resource pack not properly enabled on first launch
Step to reproduce:
1) Create a new .minecraft instance for the game (in our case, just remove the "resourcePacks" and "incompatibleResourcePacks" lines form your options.txt will work)
2) Launch the game, wait for the options init
3) You can see in your options.txt that resourcePacks is an empty list
4) Go to the pack screen and close it immediatly, the game will reload ressources even if you did not change anything because the list of enabled packs on the screen contain the vanilla pack, but the list in the options do not
5) You can verify that "vanilla" has been added to the resourcePacks list in options, and that going back to the pack screen and close it will not trigger more reload
Step to reproduce:
1) Create a new .minecraft instance for the game (in our case, just remove the "resourcePacks" and "incompatibleResourcePacks" lines form your options.txt will work)
2) Launch the game, wait for the options init
3) You can see in your options.txt that resourcePacks is an empty list
4) Go to the pack screen and close it immediatly, the game will reload ressources even if you did not change anything because the list of enabled packs on the screen contain the vanilla pack, but the list in the options do not
5) You can verify that "vanilla" has been added to the resourcePacks list in options, and that going back to the pack screen and close it will not trigger more reloadUPDATE:
Found an easy fix. You just have to add "vanilla" to the default list in the GameOptions class constructor.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Mojang] Maxime Lebrot](../../../data/avatars/users/18941.svg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Step to reproduce:
1) Create a new .minecraft instance for the game (in our case, just remove the "resourcePacks" and "incompatibleResourcePacks" lines form your options.txt will work)
2) Launch the game, wait for the options init
3) You can see in your options.txt that resourcePacks is an empty list (it should contain "vanilla" because the vanilla pack is loaded)
4) Go to the pack screen and close it immediatly, the game will reload ressources even if you did not change anything because the list of enabled packs on the screen contain the vanilla pack, but the list in the options do not
5) You can verify that "vanilla" has been added to the resourcePacks list in options, and that going back to the pack screen and close it will not trigger more reloadUPDATE:
Found an easy fix. You just have to add "vanilla" to the default list in the GameOptions class constructor.
![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Gegy![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
[Mojang] Gegy
Could you provide additional details on how this affects the game?
It does not affect most players, and even for the players that encounter it, it happen only one time.
It's a bug because the reloading of resources when you quit the resource pack screen should only happen when you added/removed a pack, or changed the order in the list. It's not a priority because occurences are rares, but this is one of these bugs that give a feeling of a non polished game, even more when you now that it needs only one line of code to fix it.
I've fixed it in a mixin if you want to check:
https://github.com/Brancieq-Paul/Pack-Stack-Memory/blob/main/src/main/java/fr/paulbrancieq/packlistfeatures/mixin/GameOptionsMixin.java
(the only relevant method for our case is the first Inject in the <init>)