CloverBootloader: [SOLVED][REGRESSION] Legacy custom entries rename via "Title/FullTitle" broken since r5115

Until r5108 (last version with old theming engine), Clover boot GUI would correctly display MBR volume labels set in the GUI custom legacy section:

In this case, since Windows 10 boot volume is not the Windows install but the System-reserved volume, I first hid the actual Windows 10 volume in Clover’s Hide Volume section, then relabeled the legacy System-reserved volume to Windows 10 via the string extracted from the boot log:

  		<array>
  			<dict>
  				<key>Ignore</key>
  				<false/>
  				<key>Hotkey</key>
  				<string>W</string>
  				<key>Hidden</key>
  				<false/>
  				<key>Volume</key>
  				<string>HD(1,MBR,0x8F50DEE8,0x800,0xFA000)</string>
  				<key>Disabled</key>
  				<false/>
  				<key>Type</key>
  				<string>Windows</string>
  				<key>FullTitle</key>
  				<string>Windows 10</string>
  			</dict>
  		</array>

But r5109 broke Windows legacy boot completely - the Windows bootloader was not recognized as Windows but as Mac:

and after selecting the Windows entry, Clover would crash.

With the r5115 update the ability to boot into legacy Windows was restored, but only by introducing a new bug which has remained until the the most current r5127, which is that legacy custom labels broke:

You see the gap between Boot and from? That’s where Clover should find the variable set as Title or FullTitle in config.plist, then display ONLY that title. But the variable content gets lost somewhere since r5115, resulting in what you see.

None of the following makes a difference:

• Title or FullTitle
• Volume’s label System-reserviert instead of the boot string
• Volume’s UUID instead of the boot string
• Theme change - happens even with built-in and any other theme

On first glance this does not seem like a deep-down-the-rabbit-hole bug, hopefully 😃 ?

Let me know if you need any logs or so from me, and I’ll gladly supply.