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
If I create objects with the following glyphs for defining levels: S, O, U, N, D and attempt to create a level where they appear in a particular order in a line such as ####... #.O#... #..###. #@P..#. SOUNDS. ######.
I get a bunch of errors since the parser seems to think I'm trying to define a second SOUNDS section, expected behavior is that the objects assigned to those glyphs appear in the level.
The text was updated successfully, but these errors were encountered:
Related bug, you can use the glyph after object name convention in the objects section to define an object's level glyph as =, which works until you try to put it at the start of a line in the level definition.
Which is a bug. The parser should assume a level if possible. For PS, the test for all EqualsRow and sections can be suppressed in the LEVELS section. For some forks it may be harder.
If I create objects with the following glyphs for defining levels: S, O, U, N, D and attempt to create a level where they appear in a particular order in a line such as
####...
#.O#...
#..###.
#@P..#.
SOUNDS.
######.
I get a bunch of errors since the parser seems to think I'm trying to define a second SOUNDS section, expected behavior is that the objects assigned to those glyphs appear in the level.
The text was updated successfully, but these errors were encountered: