The issue with adding a command is that it would make Cubically more useful xD while being a completely functional language, like I said earlier, we still gotta keep it difficult... I've always thought about implementing a command to reset the cube. I might do it now that Cubically has grown, I'll think on it for a bit

Resetting the cube would only be slightly useful and wouldn't really benefit you unless your code is really messy

You should be able to reset the cube yourself.

@TehPers "yourself" meaning without a command?

Modulo has been moved out of experimental. _4 sets the notepad to notepad mod cube[4].

@MDXF Yay!

@MDXF You should know how to solve the cube if you mixed it up to begin with. Just undo the moves.

In my opinion, a builtin to check if the cube is solved is exactly the sort of thing that belongs in a rubik's cube-based programming language. I would probably implement it as "face" 8 with the specific value of it being "Sum of the absolute differences between each face sum and the face's starting value"

(Though I may be making incorrect assumptions about the internal workings of the language if I say it seems straightforward to implement it that way)

If you calculate the difference in value for each face between the current value and the original value, then add them together, it will equal 0 lol.

@TehPers Yeah

@KamilDrakari A built-in to check if the cube is solved is a good idea. I've already written a function in the interpreter to check it.

An 8th indexed face though is not how I'd like to do that. I wasn't too happy about having input be its own separate face, having a face solely dedicated to "is the cube solved" would be even worse IMO.

@KamilDrakari tio.run/##Sy5NykxOzMmp/P8/6NDOQzuN/v//b2QEAA

@TehPers That's why I said "absolute difference". Absolute difference between two numbers is always 0 or greater.