Finally, the GOTO on line 26 will throw an error too, since it's missing its argument, which is a label to go to. If you need help with anything, or if you're new with SmileBASIC, just ask about it. This community is sure to help!

Some other notes... Unlike some other languages, you don't need to finish each instruction with a semicolon (;). In fact, this will probably cause many errors, so I'd recommend erasing them. Line 25 will also throw an error, since the syntax is wrong. I think you meant to do the assignment before the instruction, with the values in parenthesis being its arguments.

Also, there is no need to pass 2 arguments to the BUTTON function unless you are using multiplayer. The first parameter selects the feature (type of button press) you want to get the status from, and the second one selects the terminal (multiplayer participant). For example, BUTTON(3) will return the status of all buttons released. You can check out all features on the help entry for BUTTON.

Sorry, but #B is an invalid variable identifier. Anything that starts with a numeral (#) is considered a constant, which can't be assigned to. For example, #B is the constant for the B button bit mask. A correct identifier would be simply B.

Nice job making it to 30! I do intend to keep working on this. I'm just a bit busy with other stuff at the moment. Thanks for playing!

Neat! I would've never been able to notice that! Can't really see a use for this, but it's there. ¯\_(ツ)_/¯

Did you try setting it to wumbo?

@Squirt Ok, then.

Europe has different standards for software releases than America or anywhere else. For example, you usually make sure software is available in the 6 major languages of Europe. (Can't really remember which from the top of my head.) It takes time, but it will probably still happen.

Thanks a lot Stewart! I knew I could get rid of those unfilled pixels by rendering the wheel with something other than lines! I have a little irk with how you drew the borders, since you fill them in with circles and paint filling, taking away a bit of transparency, but that's just a nitpicking of mine. However, it's really neat that you helped me with this. Seriously, thank you!

I'm seeing a lot of these type of discussions lately, but it's understandable why. SmileBASIC is supposedly coming to Europe soon. Wether it's later this year or early next year, but it's supposed to release soon. Just be patient for a little bit longer, and you'll probably get it.

Abou the screenshot, I'm sorry for my lack of artistic skills. It felt like I needed to show its capability for drawing, and fruit was the first thing that I thought of. Also, I'm serious about the bug hunting! If you can fix any bugs without sacrificing any features, or if you can add new features altogether, please comment about it!

[Key in screenshot.] A lot of people seem to have liked my HSV wheel post. I went ahead and polished it a bit, and it now includes a neat little paint mode! It still has a few bugs (invisible last stroke, something, something, magenta), and the wheel still renders slowly, but at least it's only a single file, right? Feel free to look at its messy code. If you can fix its bugs, do tell!

Successfully made an HSV color wheel! However, it looks ugly and renders slowly. Hmm, I wonder how people like Suu make stuff like this so well optimized... Perhaps exhaustively drawing with graphics functions was a bad idea...

Actually, that's pretty much what happens to every project whose developer isn't willing to commit to. Personally, I may have a big backlog of projects to complete, but I'm still working on them and hope to see each of their releases.

If I recall correctly, really small negative numbers may print as zero when printing due to rounding, while still showing the negative sign.

Here's a tip: If you're replying to someone, do it on the pertaining comment thread, not just any of their posts. This very comment is an example on how NOT to reply.

I'm not sure anyone can explain MML in a short way. The quickest way to get started is probably the MML guide in the help menu. To access it, simply type MML in the editor and press the help button.

OriginX and OriginY would be the sprite's top-left corner's coordinates within the sprite sheet. For example, in the default sprite sheet, the first one would be on (0,0), the second one on (16,0), the third on (32,0), etc.

It seems to me that you have a pretty bad case of corrupted files. I hadn't actually seen something like that actually happen, but I figured it was possible. If you want to correct this, I'd say you should delete all data for SmileBASIC (including the app itself) and redownload everything. If you want to keep some of your files, make sure to back them up to the cloud (upload, but don't publish).