You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Creating a sprite with a name that starts with the name of another sprite creates phantom tiles
To Reproduce
Create a sprig project and create 2 items in the legend, w for winSpace, and wa for Wall
If I want to place the wa, instead of just placing the wall, it places a winSpace and a red square, the req square makes a new row or column of tiles which cannot be interacted with or placed on, generating phantom tiles
Expected behavior
Either WA should be placed just fine or an error should be given saying "Sprite names must be one character"
Actual behavior
Creates phantom tiles with no indication of something being wrong.
2024-07-04.08-20-22.mp4
The text was updated successfully, but these errors were encountered:
I think that's just due to the nature of the map. Maps have a multi-line string of characters representing the bitmaps to be rendered. When the sprite name is longer than a character, "wa" gets added, but it gets parsed as "w" "a". I think having an error added is a good idea though
It should probably just not let you assign a bitmap to a multi-character name in the first place, as that error only appears when the run button is pressed
Describe the bug
Creating a sprite with a name that starts with the name of another sprite creates phantom tiles
To Reproduce
Create a sprig project and create 2 items in the legend, w for winSpace, and wa for Wall
If I want to place the wa, instead of just placing the wall, it places a winSpace and a red square, the req square makes a new row or column of tiles which cannot be interacted with or placed on, generating phantom tiles
Expected behavior
Either WA should be placed just fine or an error should be given saying "Sprite names must be one character"
Actual behavior
Creates phantom tiles with no indication of something being wrong.
2024-07-04.08-20-22.mp4
The text was updated successfully, but these errors were encountered: