• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

Something wrong on Customizing AnimCubeJS?

Tito_H

Veteran
Joined
May 23, 2024
Messages
257
Location
Japan
@bcube, I do not know if you are the right person to ask, but I have one question on Customizing AnimCubeJS.

When I put move=y, move=y', move=z, move=z' (also y2, z2, etc.), and execute, y acts as z moves, and z acts as y moves (I use iPhone viejo).

Does that happen in your PC?
Is this a bug?

Image.jpeg
 
Thank you for reporting this, Tito_H.

Short answer: use the yz parameter, the yz=1 setting to be specific.

Long answer: AnimCubeJS is the succesor of AnimCube which was a program written in Java. When converting the program from Java to JavaScript, we decided to keep the functionality from AnimCube (and extend it in AnimCubeJS). The reason for this decision was to keep it simple and fluent for the webmasters to switch from AnimCube to AnimCubeJS. In your specific case, the webmasters switching from AnimCube to AnimCubeJS would still have the same functionality known from AnimCube, but they have the opportunity to change the meaning of the y and z cube rotations as standardized nowadays. Why keeping the same functionality is important for me/us? I personally was using AnimCube on my website and wrote y as z and z as y in my parameter declaration in the simulators. It would be a headache for me to rewrite my declarations when switching from AnimCube to AnimCubeJS (if the meaning of the y and z cube rotations would be "fixed" in AnimCubeJS by default, thus breaking the simulators from the Java version) because I was using roughly 100 simulators. When keeping the same functionality, switching to AnimCubeJS was simple and fluent on my website.

P.S. an excerpt from the move parameter section: "Y or y - rotates around the y-axis (in the same direction as F/B' or U/D' moves are executed, depending on values of these parameters: yz [...]"
 
Last edited:
Thank you for your quick reply with the background of the reason why the difference exists.
The good thing is that it is not a bug and there is a solution.
 
Back
Top