Spaces:
Sleeping
Sleeping
Update app.py
Browse files
app.py
CHANGED
@@ -1233,7 +1233,10 @@ Blocks:
|
|
1233 |
|
1234 |
Your task is to use the `Sprite_name` given and `Pseudo_code` and add it to the specific target name and define the primary actions and movements.
|
1235 |
The output should be a JSON object with a single key 'action_overall_flow'. Each key inside this object should be a sprite or 'Stage' name (e.g., 'Player', 'Enemy', 'Stage'), and its value must include a 'description' and a list of 'plans'.
|
|
|
|
|
1236 |
Each plan must include a **single Scratch Hat Block** (e.g., 'event_whenflagclicked') to start scratch project and should contain:
|
|
|
1237 |
1. **'event'**: the exact `opcode` of the hat block that initiates the logic.
|
1238 |
[NOTE: INSTRUCTIONN TO FOLLOW IF PSEUDO_CODE HAVING PROBLEM ]
|
1239 |
2. **'logic'**: a natural language breakdown of each step taken after the event, formatted as a multi-line string representing pseudo-code. Ensure clarity and granularity—each described action should map closely to a Scratch block or tight sequence.
|
@@ -1531,6 +1534,8 @@ Here is the overall script available:
|
|
1531 |
|
1532 |
* **Your task is to align to description, refine and correct the JSON object 'action_overall_flow'.**
|
1533 |
Use sprite names exactly as provided in `sprite_names` (e.g., 'Sprite1', 'soccer ball'); and also the stage, do **NOT** rename them.
|
|
|
|
|
1534 |
1. **'event'**: the exact `opcode` of the hat block that initiates the logic.
|
1535 |
2. **'logic'**: a natural language breakdown of each step taken after the event, formatted as a multi-line string representing pseudo-code. Ensure clarity and granularity—each described action should map closely to a Scratch block or tight sequence.
|
1536 |
- Do **NOT** include any justification or comments—only the raw logic.
|
|
|
1233 |
|
1234 |
Your task is to use the `Sprite_name` given and `Pseudo_code` and add it to the specific target name and define the primary actions and movements.
|
1235 |
The output should be a JSON object with a single key 'action_overall_flow'. Each key inside this object should be a sprite or 'Stage' name (e.g., 'Player', 'Enemy', 'Stage'), and its value must include a 'description' and a list of 'plans'.
|
1236 |
+
The first plan in each stage must start with one Scratch Hat Block (e.g., event_whenflagclicked).
|
1237 |
+
Other plans may use any hat blocks (including duplicates) to represent different logics or events.
|
1238 |
Each plan must include a **single Scratch Hat Block** (e.g., 'event_whenflagclicked') to start scratch project and should contain:
|
1239 |
+
|
1240 |
1. **'event'**: the exact `opcode` of the hat block that initiates the logic.
|
1241 |
[NOTE: INSTRUCTIONN TO FOLLOW IF PSEUDO_CODE HAVING PROBLEM ]
|
1242 |
2. **'logic'**: a natural language breakdown of each step taken after the event, formatted as a multi-line string representing pseudo-code. Ensure clarity and granularity—each described action should map closely to a Scratch block or tight sequence.
|
|
|
1534 |
|
1535 |
* **Your task is to align to description, refine and correct the JSON object 'action_overall_flow'.**
|
1536 |
Use sprite names exactly as provided in `sprite_names` (e.g., 'Sprite1', 'soccer ball'); and also the stage, do **NOT** rename them.
|
1537 |
+
Other plans may use any hat blocks (including duplicates) to represent different logics or events.
|
1538 |
+
Each plan must include a **single Scratch Hat Block** (e.g., 'event_whenflagclicked') to start scratch project and should contain:
|
1539 |
1. **'event'**: the exact `opcode` of the hat block that initiates the logic.
|
1540 |
2. **'logic'**: a natural language breakdown of each step taken after the event, formatted as a multi-line string representing pseudo-code. Ensure clarity and granularity—each described action should map closely to a Scratch block or tight sequence.
|
1541 |
- Do **NOT** include any justification or comments—only the raw logic.
|