Seriously, what's the point? OpenMPT does not need to invent yet another incompatible tracker format that noon else will support, and there is little reason to use more than 99 channels in MOD other than "look, I can use 120 channels in this format!"

Oops, there was an error on the Load_mod.cpp file. I reuploaded the modded source code file.

Oops again, another error on the Load_mod.cpp file. I reuploaded the modded source code file once again.

But this is a new magic format exclusively to OpenMPT! There are no xxxC mod files and no other MOD trackers that can make xxxC so that's why I am supporting that. You can make your own MOD file with 100-999 MOD channels with this implemented.

And who is going to play those files? If you don't care about no other application supporting your format, you can just as well use OpenMPT's MPTM format, which already supports more than 99 channels. I'd say the MOD format is already so limited that if you were going to really require so many channels, you would already hit completely different issues (such as only 31 sample slots to use with those 999 channels, limited octave range, limited amount of effects, etc.). I simply don't see why OpenMPT should push yet another incompatible format in this case and getting bad rep for hijacking yet another module format with its own extensions. Hence: Without any clear and convincing use case that would make great things possible that were not possible before, there is no chance that I will add support for this extension.

But it also adds some formats like TDZ1 made from TakeTracker that is missing from OpenMPT.

I contributed to the project HxCModPlayer to support up to 999 MOD channels. See here: http://hxc2001.free.fr/hxcmod

Pretty please stop inventing new variants of old, by design non-extensible, and in particular discontinued (i.e. not actively developed any more) file formats.
You are quite frankly just causing trouble for everyone. I honestly would rather see 999 channel MOD support to be removed from HxCModPlayer again, because it did not even exist before, and thus has no purpose being in any player whatsoever at all.

Even further extending MOD file magic channel number parsing also increases the likelyhood of files getting wrongly detected as MOD files, which is already rather high because of the very short and diverse file magic pattern at an unusual location in MOD files.

regarding TakeTracker (and other tracker for which you added <4 and/or >8 channel support): Do you have any real world files that you can provide for testing? Did you verify that these trackers actually support writing files with these particular channels counts? IFF so, could you provide a clean patch without any non-related changes which adds the missing file magics?

According to http://forum.cdgs-crew.com/viewtopic.php?t=12 for TuComposer on Amiga notes here to prove xxxC is used for up to 256 MOD channels:

The MOD loaders supports ProTracker-Style modules up to 256 channels ! It handles standard IDs like M.K., FLT4, FLT8, EMW3, M!K!, TDZx, xCHN, xxCH and the new xxxC, where xxx is a number from 100 to 256, allowing thus 100 - 256 channels PT-style modules as well as old SoundTracker modules without an ID (even those with 31 samples). It also supports songs (external instruments) and tempo only & fast vol slide MODs, the FT2 Set panning command (8xx) and NoiseTracker's repeat start and its doubled vibratos. But be forewarned that a pattern of an 256 channel PT-style module takes 65536 (464256) bytes. But PowerPacker, XPK, PKZIP, LHA, LZX and the alike will be very happy when crunching such huge patterns :-))) The following tucomposer.library routines have been implemented so far.

So should I set the max MOD channels for xxxC to either 128 to 256 instead?