Rules

Question Scope

• One chapter is selected from Level 1 to Level 3 of [Mallang Mallang Coding Journey].

Judging Standards

• Participants implement the game of the announced chapter.
• Scoring is based on how closely the result matches the announced problem.

Scoring Items (to be revised / added)

Parts Used

Participants must prepare the following items. (Failure to bring them incurs point deductions and may lead to disqualification depending on the situation.)

• Prepare Probo Scratch and the matching Mallang Mallang Coding Journey Level kit for the announced problem, along with the hardware parts required to implement the chapter (foam board included).

Usage Restrictions

• Only the sprites of the provided problem may be used; external resources are restricted.
• Using pre-made script code or downloading/importing external projects (sb2 files) is prohibited.

Problem Disclosure

• The problem is announced ? weeks before the event.
• Participants implement the mission or game based on the announced chapter.

Production & Scoring

• Participants implement the game of the announced chapter.
• Participants aim to reproduce the game as accurately as possible.
• Scoring is based on how closely the result matches the announced problem.

Coding & Judging

• Participants who finish first may request a review from the referee.
• No further edits are allowed after a review request.
• Referees inspect and score results in order.

Preparation

• Prepare Probo Scratch and the matching Coding Journey Level kit for the announced problem.
• Bring your own laptop; equipment is inspected by the referee before the match.
• Not bringing a laptop may lead to disadvantages in operation and scoring.
• Hardware must be built from scratch. If pre-assembled, it must be fully disassembled before the match.
• If not fully disassembled before the match starts, scoring may be disadvantaged.

During the Match

• After the start, assemble the hardware of the announced chapter.
• Assembly and coding must be completed within 1 hour.
• No further edits are allowed after a review request.
• After 1 hour, move your chair back and stop coding.
• Coding after time is up may incur penalties.
• The foam board is also part of the assembly. Using a damaged foam board is not a penalty, but a missing foam board due to loss is a penalty. The foam board may be purchased or printed; if printed, attach it to 2 mm-thick paper. Please download the printing image from “Download the foam board printing image” on this rules page.

Exclusions

• Difficulty-increase expressions as the stage rises are excluded from the implementation scope.
• Sound expression is excluded from the judging items.
• The game description (intro) before the game starts is excluded from judging.

Time Limit

• A total of 1 hour is given from the start of hardware assembly.
• Hardware must match the announced problem.
• Both assembly and coding must be finished within 1 hour.

Procedure

1. Equipment inspection
   • Laptop: Load the officially pre-provided sprites and resources, then get the referee’s confirmation. Keep the laptop closed after confirmation (using it is considered cheating).
   • Kit: Keep all parts fully disassembled and on standby (points deducted if assembled parts are found; disassemble everything before the referee’s check) / Points deducted if basic supplies such as pin tools are insufficient.
2. Match start
   • Time limit 60 minutes
3. Hardware assembly
   • Assemble exactly as the assembly diagram; modifications are not allowed.
4. Mission/game coding
   • Check the printout provided on-site and implement the coding identical to the game.
5. Review request
   • If coding is completed before the time limit ends, request a review from the referee (no edits after review).
   • When the time limit ends, all participants close their laptops and stop coding regardless of completion.
6. Inspection & scoring
7. Results & awards

After Time Is Up

• After 1 hour, move your chair back, close the laptop lid, and stop coding.
• *Set your laptop in advance so closing the lid does not trigger sleep or shutdown.
• Coding afterwards may incur penalties.