@MDXF That's one of the huge changes I made in my variant. It makes it confusing, lol.

@TehPers I wish I could've made the change when I created the language, but at the same time, it would invalidate all existing code and become inconsistent with Rubik's notation.

Wait, no. Making the change at any time would become inconsistent with Rubiks notation no matter when I did it, and copy-pasting so many double-strucks would be awful.

Making the change now would invalidate all existing code. I'd have to make a new language, like Cubically [Variant] as you've done.

I think I'm going to incorporate lots of changes you made, such as floating point notepad and more math functions. I'm also going to add a command to read and execute Rubik's notation. A second notepad is another thing I'm thinking about; it would increase Cubically's capabilities astronomically without removing too much fun (cough pain cough) from the language.

The hard part is not directly adding variables and such.

A second notepad would introduce the need for a third, so in the end, relying on expandable memory (the cube?) is most effective

I need to do more challenges with the variant to see what it needs. It definitely can use some more support for arrays lol

Hmm

@TehPers How so?

@MDXF How what?

Oh phone didn't show linked post

You'd come across problems where you need to store 4 variables, or a whole string

One idea is to use the notepad and bitwise functions, but that can only take you so far