Crash report / options.txt contains deleted resource packs
The bug
When you delete a resource pack you used lately, Minecraft does not update the options.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
→ You will see that the resource pack is still listed as active resource pack.
Created Issue:
Crash report / options.txt contains deleted resource packs
I am not sure if this is a bug with the launcher of Minecraft itself.
When you delete a resource pack you used lately, Minecraft does not update the option.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
You will see that the resource pack is still listed as active resource pack.
- Unresolved
- Open
- Minecraft Launcher - Public
- Unconfirmed
- crash-report delete options resource-pack
- 1.6.43
I am not sure if this is a bug with the launcher of Minecraft itself.
When you delete a resource pack you used lately, Minecraft does not update the option.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
You will see that the resource pack is still listed as active resource pack.I am not sure if this is a bug with the launcher of Minecraft itself.
When you delete a resource pack you used lately, Minecraft does not update the option.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
You will see that the resource pack is still listed as active resource pack.
I am not sure if this is a bug with the launcher of Minecraft itself.
When you delete a resource pack you used lately, Minecraft does not update the options.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
You will see that the resource pack is still listed as active resource pack.
I am not sure if this is a bug with the launcher of Minecraft itself.
When you delete a resource pack you used lately, Minecraft does not update the options.txt file causing crash reports to contain wrong information.How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
You will see that the resource pack is still listed as active resource pack.
The bug
When you delete a resource pack you used lately, Minecraft does not update the options.txt file causing crash reports to contain wrong information.
How to reproduce
- Download the attached resource pack
- Load it in Minecraft
- Close Minecraft
- Delete the resource pack
- Open Minecraft again and close it (to make sure it did not remove the resource pack from the options.txt file)
- Open the options.txt file
→ You will see that the resource pack is still listed as active resource pack.
Is this still a concern in the current Minecraft Launcher version 2.0.805 / 2.0.806? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened it as soon as the requested information has been delivered.
Looks like this is a Minecraft issue. Please move this report to MC.
Confirmed for 1.13.1.