- Cemetech Contest #24: Collaborative Safari
- 06 Oct 2020 03:56:10 pm
- Last edited by iPhoenix on 12 Oct 2020 07:15:07 pm; edited 3 times in total
Communication is one of the most important parts of any expedition, including software ones. In this contest, you will work with exactly one (1) other person as a team to produce a game centering around this contest's theme: exploring the wilderness.
Teams
You will be allowed to choose your collaborator for this challenge. You can only be on one team. It is advantageous to pick your teammate early, as you cannot start working on this contest without a second person (solo entries are not permitted). Both team members are strongly encouraged to be active in the development process of their submission.
If you're interested in participating but don't know who to team up with, post about your availability in this discussion thread for this contest.
General
Your team's game can be in any language, for any platform. Your submission must incorporate the theme of "exploring wilderness" to qualify- how this is implemented is completely up to you; be creative! You are allowed to use sprites, code, and other assets provided they are public at the start of the contest and the submission is still original. There must not be any inappropriate content or any content that discriminates against others. This contest is open to all Cemetech users, except for judges.
Development
Your team should create a thread to document your progress, with the title format "CC24: Collaborator #1's username and Collaborator #2's username". You are allowed to receive help for this contest, provided that it is done publicly on the forums, SAX, or public channels in IRC or the Discord server. If you receive help from someone, make sure to give them credit in your thread.
Submitting your entry
Submit your entries through email (contest at this website's domain). Submit it in the same format as you would upload the file to the Cemetech archives. In the readme file, please include a contest-specific section that includes the language it is written in and the platform it was written for. Include any optional screenshot(s) in the submission itself. As code quality will be assessed by the judges for scoring, your submission must include the source code for your program. You may choose not to include the source code when you upload your program to the Cemetech archives, but it is required for the email submission. You are also allowed to submit your entry to the Cemetech archives, however, it will not be accepted until the contest submission period is over. All entries must be in by the dates outlined below, under Timeline. You may only submit one entry (if you want to submit an update to your entry, PM either _iPhoenix_ or KermMartian, and re-email your submission). Only one person in your team needs to submit the entry.
Judging and scoring
Judging for this contest will be done by a panel of four judges: _iPhoenix_, Jeffitus, commandblockguy, and Nik. You will be scored on the following broad categories:
All judging criteria are scored out of ten and then summed for a total score. We will consider language and platform restraints.
- Originality: How novel and interesting the core ideas for your game are, including implementation details and platform.
- Style: How well the game is implemented visually.
- Theme: How well the game fits the theme of exploring the wilderness.
- Code Quality: How well the game is implemented. This is a combination of readability, speed, documentation, and optimization.
- Enjoyability: How much we liked playing the game, in general.
Timeline
This contest will begin on October 6th, 2020, and end on Monday, November 30th at 11:59 pm EST. Assuming no delays or extensions, the judges' results will be posted on or before December 7th.
Edit 10/6/2020: Rule change just after release that better indicates what contestants should actually make, as suggested by kg583 in the Discord server.
Edit 10/6/2020: Added a prompt for people to post in this thread if they want to participate
Edit 10/12/2020: Fixed a spacing typo.