I think @handle started with Twitter as a way to reference people directly. If it didn't start there it's certainly where it's most commonly coming from these days.

yes take your SD card and boil until pliable roll in seasoning toss on the grill enjoy

INC

why are you using a GRP? something like a DAT would be way better suited, especially since GRPs only work in 16-bit color

Should add a save file so I don't have to play all the way through every time. Otherwise, nice work!

woomy

You probably shouldn't be so public about it considering what happened last time.

AND has higher precedence than &&. In fact, && and || have the lowest precedence on the operator table, probably on account of their shortcutting. The parents around the AND shouldn't be necessary, unless I'm missing something.

Yeah scaling in SB is quite not good

smilebasic creepypasta

Miiverse: asking the hard-hitting questions.

You forgot to save it didn't you? That sucks. Here's a protip: hit SHIFT/F2 with a slot editor open to pull up a save dialog. Never use DIRECT to save again! F1 becomes LOAD as well. Simply having more than one slot is a godsend as well in editing. Also as a person on the internet I'm required to acknowledge my recognition of that reference. ;-)

I too am curious

Look into DEF. Here's examples: DEF TEST NAME$ PRINT "HELLO, "+NAME$ END TEST "Jimmy" DEF SQUARED(NUM#) RETURN NUM#*NUM# END PRINT SQUARED(2) Something weird to mention: DEFs are completely untyped, they don't even type check their arguments! You can also make DEFs that don't take arguments, so they make gosub and goto completely obsolete.

Bug. Will be fixed in coming 3.3.1 update

Numbers are, by default, treated as real-type. There is an integer division operator DIV which treats its terms and result as integers. ex. 10 DIV 3 is 2. SB also has implicit conversion from int to real and vice-versa so there's no headaches about that. 10.8 DIV 3 is 10 DIV 3 in its eyes.

An addendum to the number types: variable typing is determined when you declare them with VAR. You use a suffix character at the end of the name. VAR A$ would be a string, VAR A% would be int and VAR A# is double. No suffix defaults to double, unless you set OPTION DEFINT in which case it defaults to int (I recommend just always using suffixes)

I'd call that the VAR command instead of the VAR function. There is a VAR() form but it does something entirely different.

@sam you can't do that anymore

Will you be creating new feature/bug threads on the English community? It would be nice to have. Thank you. Anyway, using COMMON on VAR or DIM to allow all slots to access them would be great. Labels would be cool too. That way we won't need to use VAR() or a special string format to access these things out of slot. Eg. COMMON VAR A%, COMMON DIM B#[2], COMMON @C