Level Codes for Switch/Editor Users

Levelpacks in Baba are PC-only, meaning that Switch users and editor-only users cannot play them. This pack does not use any custom sprites or complicated hidden text, so this time, it was possible for me to convert them into level codes. I hope you enjoy!

Learning Colors: 67LY-B1D7
Sunken Expectations: M6XM-9NYC
No Longer White: DWZE-6IIE
Gold Choice: IFEW-KJWD
Bog Bite: H7RP-4ZW7
Suspicious Rainbow: MRYG-62NE
Dual Color (Extra 1): HJ3G-TYBK
Empty Feelings: 3UUH-XXWG
Finale: 2EY9-JGAL

There are some frustrations with the level upload system I've noted, although they are very small, and this system usually works very well. I'm not sure if these will ever get replied to (or even modded away, lol) but I think this is the best time...

• It's reasonable to have to solve the level to upload it, but "UPLOAD LEVEL" which is right next to "TEST LEVEL", and the behaviors seem so similar, I have easily accidentally thought I was playing a level to upload it, but only finish it testing instead, and no it doesn't even save the status that the level was solved just before.
• The special behaviors of END and DONE seem to act like WIN, but do not work for uploading levels, and doesn't even give you an error.
• (on a side note, needing to solve is not quite perfect for anyone who actually wants to make an unsolvable level. there's the possibility of using version bugs to create retroactively impossible levels, or hidden text to create a bogus hidden win condition)
• The types of errors I've gotten for a failed upload are vague and you basically need community knowledge to know, even though it's not complicated. First there is the expected "USAGELIMIT", which doesn't tell you what the limit is or how high it is, but it makes sense. There is "INVALID" which... sometimes comes up instead of USAGELIMIT when it is limit-related?
• The other "INVALID" can happen when you're trying to upload an object that the Switch version doesn't allow (this is very reasonable, Switch updates apparently come slower). For example, as I'm writing this, ARM and BUNNY have been added as official objects, but do not upload. But the error "INVALID" will not point you towards the objects you need to remove.
• Then there's "INCOMPATIBLE LEVEL" which is another error actually referring to more specific things. You can 'rename' objects in the editor, which is basically a way to create new words (this is relevant due to letter targeting). You can change basically everything else about the object like color and sprite and even text parsing type (which is excellent, by the way), so it's kinda odd this is prevented.
• (having 'effectless' properties are actually kinda important for hidden text purposes - there are not many properties that have no visual effects, so if you can't rename properties, you have a very limited amount of properties that can be used as code indicators that don't create seemingly strange visual effects. those are MELT, OPEN (or SHUT), SAFE, by the way)
• The other known "INCOMPATIBLE LEVEL" editor happens if a CURSOR or SELECT is in the level. Again, like the other one, this is a vague error.
• None of these mention the level is invalid before uploading it. You could playtest the whole level in order to upload it and only then it will mention the error. This also counts against your usagelimit!
• Also I'd mention a new levelcode ID is made for every revision to the same level, this is a double-edged sword though, and has some benefits, it's just a bit annoying to play an old version not knowing it, I guess.

Anyway. Levelcodes are great, but needing to find out about renaming/usagelimit, not so much. Oh and also the level limit itself is reasonable and I think I only encountered it due to the invalid issues. :)