Threxx wrote:Glad we're jumping to the insults now; totally helps your point
I don't understand why it is so much to ask that people say that they are using a beta build, especially a beta build which is not backwards compatible with any previous builds. I mean, just make an announcement about it if it is too much trouble to enforce.
I agree with this, to a certain extent. It's practical to make announcements IF
you're using an official beta or official release version. But, for reasons that should be obvious to everyone, it's not practical to even post modules made in unofficial builds that support multiple chips, let alone announcing that it's made in whatever unofficial version.
Let's put it this way, Threxx; you post a module that has every soundchip hacked into it (yes; hacked, because that's not how the original NES ever worked at all) & someone who's totally new to FamiTracker wants to run it. If the guy reads what unofficial version is needed to run it, then it'd be up to him to find a copy & run it (good luck to this guy, though, as most unofficial builds are scattered on the old forum, rather than having their own websites). And then, there are those guys who don't bother reading your post & goes straight for the module; he'll then discover that the module doesn't work with the official version of FamiTracker & complains to JSR about it, without knowing that it's a hacked module.
Technically, these forks of FamiTracker that allow for multiple chips are realy allowing the use of hacked modules that go against the NES' specs (which is something JSR's trying to stick with). I'm sure you can create NSF files with multiple chips in MML (correct me if I'm wrong,) but the fact that there's no physical way to integrate all these chips together into a single cartridge (i.e.: without the use of hardware- or software-level emulation,) should tell you a lot about how the visions of some people differ from both the reality of the original system, as well as JSR's desire to stick to that reality.
And this ignores those users who are too ignorant to read posts, as well as those users who aren't savvy enough to know where to download these unofficial builds that support multiple chips.
And that's why I agree with the staff not permitting these hacked modules; as artistic as they may be, they're hacked modules that require an unofficial version that permits hacked modules (& to new people, these copies aren't exactly as easy to find unless they're well informed & know how to read). I'd rather not see this place get flooded with complaints to JSR about not being able to open a module that they don't know is a hack (as do all staff members).