LockRotation app

[DoodlesQ]

An app that recreates the behavior of the "lock rotation" tweak from the Quark mod.

This app adds a command, /lockrotation, which saves the player's current orientation for block placement (or an approximation), and applies it to all future blocks placed.
The lock can be disabled by running the command /lockrotation clear or setting the same rotation twice in a row.
Your current saved rotation can be displayed by running the command /lockrotation show.

I am not positive how this app will interact with any modded blocks, although I imagine not well. That's something that can be improved perhaps.
For vanilla blocks, though, I've accounted for as many edge cases as I could think of. Hopefully, I've not missed anything glaringly obvious.

[rv3r]

Shaped stairs aren't getting updated when they get their rotation changed by this script. Locking rotation and trying to make shaped stairs should just produce nicely aligned stairs. Instead I get the attached image. Have you encountered this or tried to make stairs update properly?

[rv3r]

Other than that it certainly functions as expected. Your _castSide function produces some fun results when _sign is passed 0 (especially since gnembon/fabric-carpet#1776 is a thing) but it still works so nbd.

I was a bit confused on how to get the "half" part of the lock to activate and I had to read through the code to find it, so an explanation of how to use the script could be added to the readme entry.

My last major note is that there are a lot of lines that could be optimized with scarpet-specific features (lines 109-117 could become truepos = map(raycast - blockpos - 0.5,ceil(abs(_) - 0.49999) * _sign(_));, ifs can act as their own elif, you can use function returns directly rather than assigning to a variable first, etc.), but it's already so fast that I'm not worried about these minor performance gains.

[DoodlesQ]

I've added a short description to the readme, as well as a holographic indicator when running the command, which should make it a little more obvious how to use it.
I hadn't encountered the bug with shaped stairs, and while I can't seem to recreate your exact screenshot, I have found similar inconsistencies with the way stairs place when rotated.
The problem is easily resolved by simply delivering a block update to the glitchy stair block, but, of course, it doesn't seem to work if I update it programmatically. I might be missing something about the update() function?
I'll continue looking for a working solution that doesn't involve recreating the entire vanilla stair-shaping logic from scratch.

[DoodlesQ]

Alright, I have something working. It's not ideal, but it does work and doesn't seem to have any adverse effects apart from an errant sfx.
I'm sure there must be a better way to do this.