anyone who submits Doggtales v2.0 will be DQ'd from the entire series of contest.
I definitely would vote a 'troll' entry lower than others that were seriously trying to convey original ideas, but, my opinion, DQ'ing anyone would be a bit of a killjoy, yea. With Doggtales being an exception, every FamiCompo troll entry in past years was always giggled at, but subsequently downvoted to the bottom of the stack.
If anything, could we DQ the high-votes of such entries? I think a voter who puts these kind of things higher than serious entries is more of a problem than the authors who submit them.
I've got a proposition for another category. Anyone remember those minimalist challenges that people were doing a while back where you're only allowed to use the classical format (2A03 with no DPCM) and one instrument? How about a category like that for originals (I imagine it would be hard to implement for covers)?. Especially if these are going to be judged using .ftms instead of .nsfs.
"Classical" is the category we'll be kicking off with (for both covers and originals)... Not sure how what you're proposing is different? Except for the 1-instrument thing, but that's needlessly crippling I think.
Seriously though, I haven't decided if there should be a maximum amount of entries per person yet. I guess we'll go with one or two per entrant at first and then adapt the rules to the degree of participation or something.
one per entrant. quality > quantity, and that's especially important if it's going to be a showtune for FamiTracker, you wanna make sure people devote all their energy into one submission.
I vote in favour of Dave, since modules demoing what the tracker is capable of would be a pretty big deal.
Would two modules make it in as demo modules per expansion chip (one original, one cover)? Or would a few of the best be included to display both technical skill and tracker capability, and some easier examples for people new to the program?
I'm not entirely sure yet. It might be just one per competition, three per competition or even three or four per chip (though that would require an extra voting process which people mightn't appreciate much). It really depends on how much demo material jsr is willing to bundle with the program, and how big the participation is. I suppose if we get 15 entries then it's fair to pick the best 3 modules, whereas if only 4 people submit then we'd have to go with only the best one. I guess 4-6 modules per sound chip on average would be a reasonable amount.
Is "the current famitracker version" referring to the .8 beta or the .7 stable?
If I were to wager a guess, I'd say whatever the stable is at that time. Meaning, for now, use 0.3.7, but whenever 0.3.8 becomes stable, start using that instead.
