Pattern Break (DXX) values reset after saving and closing

[TipTopTomCat]

For some reason, I can't get this pattern break command (DXX) to be anything other than D00 in some tracks. For example, I can't get it to stay as D02 when I save, close it, and reopen it, it always reverts back to D00. It's not consistent when/where it happens: with some files it's fine, other times it only works when I do something weird like two DXX commands on the same line, then one of them stays and the other changes back to D00 next time. Not sure what causes this in the end

Attached is an example .mod with the issue in question. Pattern 1 has a DXX command that I can't get to save as anything other than D00.

[Saga Musix]

This was caused by an overzealous detection of NoiseTracker modules and is already fixed for the next OpenMPT update: https://bugs.openmpt.org/view.php?id=1765

The correct value is saved in the file, but it is ignored when loading it.

[TipTopTomCat]

Good to know! I think from that and after some experimenting, I just have to make sure that I don't re-open and re-save a song with a DXX value until that fix. Looking forward to the next version then!

[Saga Musix]

The best way you can avoid this problem is by making sure it's impossible for OpenMPT (or other software with similar heuristics) to assume that the module was made with NoiseTracker by using effect commands not supported by NoiseTracker; in that case ProTracker effect interpretation will always come into play. The easiest way is to simply have a tempo command in the first pattern: Even if you use the default 125 BPM tempo, just put an F7D effect in the first pattern next to the F06 and the module will no longer be assumed to be a NoiseTracker module (as NoiseTracker didn't support the tempo command).