Mojira Archive
MC-138886

Exception is not logged when reading options.txt entry fails

The bug

When an entry of the options.txt file could not be read only the warning "Skipping bad option" with option name (and value) is logged. In some cases this is not enough information, instead the thrown exception should be logged as well.

How to reproduce

  1. Create a backup of your options.txt file
  2. Edit the current options.txt:
    • Add an entry without separator (:):
      test
      
    • Add an entry with invalid float value:
      mouseSensitivity:invalid
      
  3. Start Minecraft
  4. Look at the log
    It only logged "Skipping bad option" with the option name, but did not log the exception (indicating why the option is malformed)

Code analysis

20w10a, Mojang names

See net.minecraft.client.Options.load() and look for "Skipping bad option" (there are two occurences).

Cannot Reproduce

Marcono1234

2018-11-04, 08:26 PM

2021-10-01, 08:08 PM

2021-10-01, 08:08 PM

3

7

Confirmed

(Unassigned)

logging, options.txt

Minecraft 18w44a, 20w12a, 20w13b

-