BOSS BATTLE DESIGN CONTEST - KNOWLEDGE IS POWER

Okay Pyrodoom, we don't need a play-by-play. You can post the level when you're done.

author=Rhyme
Is there a limit to the complexity of the battle mechanics itself? If not, then would the judging include how easy and intuitive the unique mechanics are? Are we allowed to explain what stuff does? (Not concerning the boss itself, but the battle system)

I can't think of any reason to include a limit, as long as you explain it. A tutorial seems appropriate if you're doing something pretty unusual - you would probably include a tutorial in the real game at the first point where the player encountered that system also. If the system or the fight is too hard to figure out, that would likely be bad for your score.

author=Rhyme
Is it also allowed to have difficulty selection? I am not sure what you may be looking for as your definition of easy/hard may as well differ from mine.

Works for me.

author=Rhyme
Do you mind unfinished graphics in the submission?

No problem. Graphics will not be judged.

author=Rhyme
Last but not least, should the battle mechanics allow customization (equipment and stuff), should it be set automatically, or do we allow the player to set it him/herself before beginning the boss battle?

I was thinking people would typically just set equipment and such automatically and go straight into the battle. Without having a dungeon full of normal battles to get used to the effects of the different equipment options, it seems likely to result in what feels like the player having to read your mind, which is bad game design and will probably negatively affect the judging of your battle. But if it's an important part of the battle and you don't think the way you're doing it is bad game design, go for it.

author=Max McGee

- Obviously, the boss should not be one you've already made for another game. Nor should the player party.

How much of a RULE is this? How hard/soft/firm is this restriction, and how much wiggle room is there? (Obviously I don't mean just straight-out using database from another game, I mean reimagining and so-forth.)

Re-imagining doesn't bother me so much - you're using an existing basic concept, but doing the work and making new gameplay. I don't want to be like "You can't use a berserker with high HP and a blue mage that starts with no skills in your party, you had a berserker with high HP and a blue mage that started with no skills in your other game." Most berserkers have high HP, most blue mages start with no skills, those are basic class roles. Use your own judgement. If it feels like a new fight to you, then it's a new fight.

That said, my purpose with this rule was more than just to keep people from submitting work they'd already done. It was to get people to make battles outside their comfort zone, to get them not to do things the same way as they always do, to encourage personal innovation and experimentation. I don't just want to give out a fair prize, I also want to get people thinking about how to make battles.

Hoddmimir, just upload it to your locker rather than submitting it as a game.

Please make it standalone, Idida, since there will be lots of judges and not all of them will have the RTPs for every single engine. Try to keep the filesize down since there will be lots of entries. I recommend removing all the music, ambient background sounds, battlebacks, and enemies that you're not using...