Two bugs in simfile 2.0.0–2.1.0's SSC implementation break multi-value properties, causing them to be truncated or mangled past the first value:
When opening an SSC file, the DISPLAYBPM and ATTACKS properties of both simfiles and charts stop parsing at the first :. For DISPLAYBPM, this means a BPM range of min:max will be incorrectly parsed as a static BPM of min. ATTACKS are completely broken as they use colon as a separator.
The aforementioned properties are incorrectly serialized with colons escaped from SSCChart. This has the same effects described above, but this only affects values with colons that were written to the chart object manually (e.g. chart.displaybpm = "120:240") since the first bug shadows this bug during deserialization.
Two bugs in simfile 2.0.0–2.1.0's SSC implementation break multi-value properties, causing them to be truncated or mangled past the first value:
DISPLAYBPMandATTACKSproperties of both simfiles and charts stop parsing at the first:. ForDISPLAYBPM, this means a BPM range ofmin:maxwill be incorrectly parsed as a static BPM ofmin.ATTACKSare completely broken as they use colon as a separator.SSCChart. This has the same effects described above, but this only affects values with colons that were written to the chart object manually (e.g.chart.displaybpm = "120:240") since the first bug shadows this bug during deserialization.