
48 Hour contests have a mystery theme which take place over the course of one weekend, from Friday 12pm EST to Sunday 12pm EST. Times may vary for each contest.
The rules are simple. On Friday at 12pm EST, or the official start time for each contest, the mystery theme will be announced. These contests will involve a mystery theme to ensure participants can't cheat by sending in levels that have been prepared in advance!
Submission:
You may work alone or with a single partner.
All people who worked on a level must be credited via a Read Me file.
Participants can only have their name on up to two levels.
You agree to have your level contained within the mini-episode that is formed from the entries.
General Rules:
Do NOT discuss your level anywhere. Not just to avoid spoilers but also because you'll be wasting precious seconds!
1. Your level must be created in SMBX2 Beta 4 Patch 3. Prior versions may be supported depending on the context but any 38a levels will be disqualified.
2. If it is obvious that your level has taken longer than 48 hours to create then you may lose points for the Mystery Theme score, but your level will not be disqualified.
3. In the event of a tied overall score, the winning entry will be determined by individual category breakdowns, in the order of: Design / Creativity, Functionality, Mystery Theme, Aesthetics.
4. The Judge, in the event that a level is deemed unbeatable, has the rights to judge accordingly, including looking at the level through the editor or using cheats. This may impact the level's score.
5. Levels already submitted publicly will be disqualified. Levels that have been stolen from others will also be disqualified.
6. Joke levels will not be disqualified. However, do not expect to be awarded a high amount of points for the level.
7. You may submit up to two levels.
8. Your level must contain one exit which is anything other than a Warp Exit, Switch Palace or Game End event.
9. Your level can have up to two secret exits.
10. You must submit before the deadline, failure to do so will result in disqualification.
11. Switch Palace Blocks, and other things that persist across levels, must not be used.
12. SaveData / GameData usage must be initialised in the following way to avoid conflicts:
Code: Select all
SaveData[Level.filename()] = SaveData[Level.filename()] or {}
GameData[Level.filename()] = GameData[Level.filename()] or {}
local saveData = SaveData[Level.filename()]
local gameData = GameData[Level.filename()]- The most important factor is the design and creativity of a level.
- Test, test, test! Your level will score better if it isn't broken.
- Lua code, if used, must function properly. Glitches and crashes may have an effect on your score.
- Try to limit the file size: Use .OGGs, keep the music as short as possible making use of loops, etc.
- While you may submit up to two levels, the 48 hour constraint means that you are likely to perform better if you focus solely on one level!
Judging:
The first contest will be hosted and judged solely by myself. Future contests may vary.
Scoring, out of 100::
Design / Creativity - 40 points - this involves stuff like how creative the level is, how well the level flows, how good the overall level plays.
Functionality - 30 points - this involves stuff like the stability of a level, how well it performs.
Aesthetics - 20 points - this involves stuff like how the level looks.
Mystery Theme - 10 points - how well your level sticks to the mystery theme given.
Participants:
People who have submitted two levels have their name bolded.
----------------------
Taking place between 12pm EST Friday 6th November and 12pm EST Sunday 8th November!

















