Setting versioner.variables.update_available.false to the White Color (§f) with a Lang file will break any CustomMainMenu configuration where a custom Background is used #4
Hello, it's me again. Found an issue where, as the title says, having the versioner.variables.update_available.false set to be any text with the §f minecraft color code (white) will break any CustomMainMenu configuration where a custom background is used, whether it is a single image or a slideshow.
Here is what happens:
The interesting thing is that when hovering over the text, the background will appear
This example CustomMainMenu config uses a single image. When using a slideshow, hovering over the text will only show you the transitions.
Note that this whole minecraft instance only has Versioner, CustomMainMenu and all their required mods. Modlist.
The only change made to the CustomMainMenu auto generated config file is removing the default minecraft panorama and setting a static image.
The only change made to the Versioner auto generated config file is adding a link to a .json to verify the version.
Using any other color or no color at all (afaik) doesn't cause this issue.
Hello, it's me again. Found an issue where, as the title says, having the
versioner.variables.update_available.false
set to be any text with the§f
minecraft color code (white) will break any CustomMainMenu configuration where a custom background is used, whether it is a single image or a slideshow.Here is what happens:
The interesting thing is that when hovering over the text, the background will appear
This example CustomMainMenu config uses a single image. When using a slideshow, hovering over the text will only show you the transitions.
Note that this whole minecraft instance only has Versioner, CustomMainMenu and all their required mods. Modlist. The only change made to the CustomMainMenu auto generated config file is removing the default minecraft panorama and setting a static image. The only change made to the Versioner auto generated config file is adding a link to a .json to verify the version.
Using any other color or no color at all (afaik) doesn't cause this issue.