Rules

Competition Goal

• Participants implement the game announced in advance using Scratch and the corresponding hardware kit.
• The goal is judged by how closely the participant’s result matches the game presented in advance.

Judging Standards

• Scoring is based on how closely the participant reproduces the mission play video of the problem announced in advance.
• As in the video, the person lying on the screen must change whenever CPR succeeds. (All 4 people must be shown.)
• To adjust the difficulty of running the game, the pressure sensor detection range can be changed.

  Example) When the pressure sensor detection range is measured on a 0–100 scale

  - Original coding pressure sensor threshold: 70

  - Adjustable pressure sensor threshold: 50

Scoring Items

Scoring items and points may be partially adjusted depending on competition operations.

Parts Used

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

1. Personal laptop (a laptop charged to last at least 2 hours, or a laptop charging adapter)
2. Probo Scratch environment
3. The completed hardware for the announced Mallang Mallang Coding Journey Level.3-chapter.3, or the parts to assemble it
4. Hardware parts required to implement and run the chapter

Usage Restrictions

Only the officially provided sprites and resources below may be used during production. The following are restricted.

1. Using external resources such as external images, sounds, or sprites
2. Using pre-made script code
3. Downloading or importing external projects (sb2 files)
4. Viewing books, textbooks, or internet materials during the match
5. Referring to other participants’ work

Problem Disclosure

• The problem is announced to participants before the competition.
• Participants must implement the game of the announced chapter from scratch on-site within the time limit.

Production Process

After the match starts, participants work in the following order.

• Check the video of the problem announced in advance
• If needed, assemble the hardware (assemble exactly as the assembly diagram, including sensor types, number, positions, and cable wiring)
• Load the officially provided Scratch project
• Implement scripts
• Check sensor and hardware inputs
• Test-run the game

Coding & Judging

• No further edits are allowed after the given coding time ends. (After the coding time ends, all participants are prohibited from touching their laptops.)
• After the given coding time ends, judges move through the seats in order and inspect and score the results for the problems they are each in charge of.

Preparation

• Prepare Probo Scratch and the Mallang Mallang Coding Journey Level kit that matches the announced problem.
• Bring your own laptop; the referee will inspect your equipment on-site before the match starts.
• Not bringing a personal laptop results in point deductions in operation and scoring.
• Assemble the hardware in advance. Assembly on-site is possible, but it must be done within the time limit for coding.
• Download and prepare the officially provided sb2 project file above in advance.

During the Match

• Coding must be completed within 1 hour in total. (If the hardware was not assembled in advance, on-site assembly time is also included.)
• After 1 hour, all coding work ends. Wait with your chair pushed back until you are judged.
• Touching the laptop or attempting to code after time is up is considered cheating and results in disqualification.

Exclusions

• Sound expression is excluded from the judging items.
• The game description (intro) before the game starts, as well as mission success/failure, is excluded from judging.

Time Limit

• A total of 60 minutes of coding time is given. (Including hardware assembly and modification time)
• The hardware configuration and form must be identical to the LV3 Chapter 3 assembly diagram.
• All hardware-related and coding work must be completed within 60 minutes in total.

Procedure

1. Equipment inspection (before the competition starts)
   • Laptop: Load the project file (sb2) officially provided on the website, then get the referee’s confirmation. Close the laptop after confirmation. (Using it before the competition starts is considered cheating.)
   • Kit: Prepare the hardware fully assembled in advance. If completed hardware is not prepared, make sure you have all parts needed to assemble the hardware on-site.
2. Match start
   • Time limit 60 minutes
3. Hardware assembly
   • Assemble exactly as the assembly diagram; modifications are not allowed.
   • Completed hardware may be prepared before the competition.
4. Mission/game coding
   • Check the video provided on-site and implement the coding identical to the game.
5. Waiting for judging
   • No separate review requests are accepted during the match; judging proceeds in order after the given 1-hour coding time ends.
   • When the time limit ends, all participants must stop coding regardless of completion, move their chairs back, and stay away from the desk.
6. Inspection & scoring
   • The participant being judged must move their chair close to the desk and show the implemented game to the referee.
   • At the referee’s request, participants may be asked to rerun the game repeatedly or operate it.
   • Several referees take turns scoring in order.
   • Each participant must be judged by several referees.
7. Results & awards

After Time Is Up

• After 1 hour, move your chair back and stop coding.
• Touching the laptop or attempting to code afterwards results in disqualification.