# data[].attributes.body
Fix Pushed

This MakeCode error has occasionally been appearing in projects containing tilemaps. We are working to learn more about what is causing the issue and have not been prevented from forward progress after recent updates.

Workaround:
Restart the step using the restart button in the top-right of the screen. Ninjas will not lose previous progress.

# data[].attributes.body
Fix pushed

YB Quest is not allowing tilemaps to load. Our tech team is connecting with MakeCode to get to the bottom of this issue.

Workaround:

Resetting the progress for demo accounts and restarting the step inconsistently works.

Restarting in incognito tab inconsistently works.

Dragging out a new set tilemap block and copying the tilemap inconsistently works.

# data[].attributes.headline
Accessing the complete MakeCode code block menu for projects

# data[].attributes.subject
Accessing the complete MakeCode code block menu for projects

# data[].attributes.body
Problem: Ninjas wish to access the entire code block menu instead of the specific categories focused on the level.

Solution: Ninjas can download from IMPACT and import into MakeCode and they continue creating and customizing.

# data[].attributes.body
Problem: Ninja username is not generated in the first attempt, and the ninja cannot log in.

Solution: Delete the ninja's username in MyStudio (leaving it blank), check in the ninja, then look in MyStudio for the newly generated username. Log into IMPACT with the new username.

# data[].attributes.body
7/20/23 Search Feature is live!

The search field is currently missing above the block categories, that will be added in phase 2.

# data[].attributes.body
7/20/23 Filter Blocks are Live!

Currently, all blocks are shown for every activity. We're working on hiding unneeded blocks, especially for White Belt activities.

# data[].attributes.body
7/20/23 Fix pushed!

We are working with MakeCode to solve the issue where the download to hardware button is not working.

# data[].attributes.headline
Set Chrome to clear cache when Chrome quits 

# data[].attributes.subject
Set Chrome to clear cache when Chrome quits 

# data[].attributes.headline
Fixed: Sprite Kind names in MakeCode Issue

# data[].attributes.subject
Fixed: Sprite Kind names in MakeCode Issue

# data[].attributes.body
7/20/23 Sprite Kind Fix pushed to allow for sprite kind editing n blocks.

Editing Sprite Kind names in MakeCode

Issue: The Education Team has been made aware that Sprite Kind names cannot be edited in MakeCode, and this is causing challenges with ninjas, specifically in White Belt Level 4 where Sprite Kinds are introduced.

Current solution: We have been in communication with the MakeCode Arcade team, and they are working to address this issue on their end. In the meantime, we have added the ability to edit code in the JavaScript editor in the White Belt Level 4 Quest and Build 2 activities so that a Sprite Kind name can be edited without resetting the project. Please watch the short screen recording to see how to edit Sprite Kind names in the JavaScript editor, noting that the Sprite Kind name must start with a capital letter, and all instances of the incorrect Sprite Kind name must be fixed in the JS editor before switching back to the Blocks editor.

Please work with your senseis to remind ninjas that Sprite Kind names must begin with a capital letter and match the name and spelling given in the curriculum. Just like functions in code must be spelled correctly for them to run, Sprite Kinds also must follow a specific syntax in MakeCode. If an error is made in naming a new Sprite Kind in an activity other than the 2 named above, a project will need to be reset and the ninja will need to start from the beginning of that project.

Future permanent solution: We will notify everyone as soon as the MakeCode team pushes an update that makes Sprite Kind names editable.

# data[].attributes.body
As we continue to fix bugs and push updates your first line of defense is always to clear your cache or simply work in Incognito Mode. Many incoming tickets have been solved by simply clearing the browser's cache.

# data[].attributes.body
*** This error shows when running the program using an asset name that doesn't exist***

When using the assets tab in Green Belt, a simple misspelling such as an image asset named spriteForward and the ninja writing assets.image`spriteForwad` in javascript will throw this error in the console.  Double check the spelling of assets when this error occurs.

# data[].attributes.headline
🪲Projects are passing with MakeCode Errors

# data[].attributes.subject
🪲Projects are passing with MakeCode Errors

# data[].attributes.body
We removed the "No MakeCode Errors validation" for now as it was not working properly. Please send the project back to the ninja to debug when they submit projects with errors. Once the feature is debugged with MakeCode the tech team will eventually add that last level of validation back in.

# data[].attributes.body
Sometimes 2 Start blocks will appear with one of them frozen in place and can't be deleted.

Current workaround: restarting the activity.

# data[].attributes.body
Some activities are loading in JavaScript.

Workarounds:

1. Close any other tabs that have MakeCode open and refresh.

2. Click Assets, then Blocks.

3. Clicking restart and then on the Blocks button quickly.

# data[].attributes.headline
Do not open MakeCode Arcade editor on another tab while running IMPACT

# data[].attributes.subject
Do not open MakeCode Arcade editor on another tab while running IMPACT

# data[].attributes.body
Doing so causes the editor to sometimes attempt to merge the program and cause conflicts. This behavior is exhibited in the current version of MakeCode, and is not a limitation imposed by IMPACT.

# data[].attributes.body
Custom Assets have been fixed, they should no longer cause projects to freeze. However, naming assets will still cause a bug. Please remind ninjas to not name their assets.

# data[].attributes.headline
Sprite Kinds need to begin with a capital letter

# data[].attributes.subject
Sprite Kinds need to begin with a capital letter

# data[].attributes.body
Creating a sprite kind with a lower case letter will cause an error. The activity step and hint wording have been updated to emphasize this.

# data[].attributes.body
Sometimes in Solve/Explore activities the correct starter code does not load when moving on to the next step.
Workaround:
Restart the step using the restart button in the top-right of the screen. Ninjas will not lose previous progress.

# data[].attributes.body
In some instances, when ninjas draw their own sprites, they may not appear when the sensei reviews the project.

Workaround:
- To save the ninjas artwork, create a new sprite via a second [set sprite] block - In the first, broken sprite's editor press ctrl + a then, ctrl + c to copy the sprite - In the second, new sprite's editor press ctrl + v to paste the artwork - once the second sprite has been safely pasted, delete the first block Note: You must copy/paste the sprite, if you select it from My Assets it selects the same, named/broken sprite, rendering the new block broken as well

# data[].attributes.headline
Do not use parentheses inside string parameters (showLongText, splash, etc)

# data[].attributes.subject
Do not use parentheses inside string parameters (showLongText, splash, etc)

# data[].attributes.body
Doing so causes errors in validation.

# data[].attributes.body
Currently, a personnel (e.g. sensei, CD, owner) can only be assigned to one center for IMPACT.  IMPACT only allows a account to see one center's ninja projects. They would have to log in to a different Sensei Account to view the other center's ninja projects.

Each unique login (email address) is assigned to one specific center in IMPACT at this time. If an email account is added in MS for multiple centers, then the first center that the email gets added to, that's the center the account will be able to view.

Workaround: If you add a "+1" before the "@" on a gmail account, it goes to the same email but is recognized as a different account. ex: craig+1@gmail.com

# data[].attributes.body
Delete their usernames on MyStudio, then re-add them and recheck them in.

# data[].attributes.headline
After checking a ninja in, Ninjas are not able to log into IMPACT!

# data[].attributes.subject
After checking a ninja in, Ninjas are not able to log into IMPACT!

# data[].attributes.body
There is sometimes a very slight delay (no more than 10 seconds) between checking in and IMPACT access activating. Refresh, clear the cache, and try logging in again.

# data[].attributes.body
A number of tickets have been for "bugs" or enhancement requests but are intentional implementations. Please review sensei training and supports. For example:

ticket: code validation not working
solution: look at correct answer in sensei support to see what's missing from the ninja's project

ticket: screen is squished
solution: work in full screen mode (F11) as intended and outlined in sensei training

# data[].attributes.body
There is a browser restriction that doesn't allow the content on the page to produce any audio without interaction-- and since the simulator is within another iframe this restriction would get applied to it too. Users need to at least hit the refresh button or any other interaction once in the simulator for the audio to play.

# data[].attributes.body
7/20/23 Parent emails allow ninjas to review Builds and Projects from previous levels.

In Phase 2 kids will be able to review old projects they worked on previously.
Workaround: You can view submitted projects in the sensei portal.