Following the feedback on this meta-post and some more feedback I got through chat, I am writing this post to lay down all the rules for the RGS I will be hosting.
RGS stands for RGS's Golfing Showdown, a golfing competition.
The RGS will be a golfing competition with 5 code-golf challenges posted with 96 hours interval (4 days) at \$08:00 \pm \epsilon\$ UTC of the 24th and 28th of February, 3rd, 7th and 11th of March.
Each challenge will be a regular code-golf challenge for the whole community.
The winner of the competition will be awarded a 200 rep bounty attributed by me. Also, for each challenge, I will be awarding a 50 rep bounty to the best eligible answer that is in a non code-golfing language1.
(1 a golfing language will be defined as a language scoring 1250 or more in this language ELO rating; if you language is not in the list because your language is younger than the list, \$99\%\$ probability of it being a golfing language; if your language is older than the list, then I will rule on it by judging the amount of 1-byte built-ins your language defines.)
Eligibility and scoring
For a golfer to be eligible for the prize, the golfer must answer all the 5 challenges within the first 96 hours of their respective postings.
For the final competition score the golfer must pick, for each challenge, one of its eligible solutions. The final score is the sum of the byte scores of the chosen eligible submissions.
Eligible submissions are the ones submitted in the first 96 hours of a challenge. After 96 hours of a posted challenge, submission scores are frozen in the sense that, if you have a 10 byte solution after 96 hours and later you golf it to 8 bytes, your score will still be 10 bytes.
These choices shall be listed, and linked to, in the respective submission for the fifth challenge.
- In case of a tie, user with overall shortest solution wins;
- In case of a tie, earliest submitter of shortest solution wins;
- In case of a tie, I retire.
The 5 challenges to be posted will all be code-golf with varied themes. The challenges will be sandboxed privately.
That is, whoever wants to help ensure the challenges are up to the community standards shall comment here, and we will revise the challenges together. The people in this process agree that for every challenge they review, their submissions are only eligible if they were posted 24 hours after the challenge.
As a code-golf challenge, you can always code in whatever you like, but a submission for the \$i+1\$th challenge will only count as eligible if it is in a language other than the top 3 eligible languages of the \$i\$th challenge. Those 3 "banned" languages will be listed in the challenge, for your convenience.
E.g. the first challenge has top 3 answers given in Jelly, 05AB1E and Japt. Then in the second challenge, an eligible submission couldn't use any of those languages. Then, someone submits the shortest answer of the second challenge in Jelly, and the 2nd and 3rd best answers are in Charcoal, APL and Pyth and Keg tie for 4th. In the 3rd challenge, the banned languages are Charcoal, APL, Pyth and Keg. Jelly was not banned because Jelly wasn't an eligible language for challenge 2. Pyth and Keg were both "banned" because they were equally good.
Comment below if you want to be a part of the private sandbox. If you have any major concerns or would like to address these rules, you are welcome to reply. I may edit these rules as more refined feedback comes in.