MiniMacro wrote:um, it's a 5B module? you said yourself that 0CC's 5B implementation was different than 0.5 beta's implementation.
As Threxx has pointed out, no pattern data exists for the Sunsoft 5B. Instrument data will not be incompatible because none of the instruments have any "Noise / mode" macros (I believe this is where most conflictions happen). This module can even be opened in FamiTracker 0.4.2, which was the last official build to [partially] support Sunsoft 5B before its disabling in 0.4.3. One could potentially make a Sunsoft 5B module in that build and share any form of file necessary to compile it, as was done in the old forums - users would often post text files to import. Would you be against that?
This module can also be opened in 0.5 beta 5 with no issues.
MiniMacro wrote:also, if you are going to use the attachment feature of the forum to post 0CC (or any other fork) modules, it must be an NSF file.
This thread forbids the attachment of FamiTracker Modules made with forks. The rule also calls for the use of "an NSF [...] and, optionally, a modified FTM which is compatible in some measure with the official version of FamiTracker". Fortunately this rule does not apply to download links, effectively meaning users can construct posts whereby the only way of accessing their work is via the link. This is not what some might call "the best method", and of course a separate forum for 0CC-FamiTracker exists, but nothing in the rules states that a forked module cannot be shared via a download link, and by extension, that a post cannot consist only of that link (and relevant information).
This aside, I quite like the OP's module.