The following code takes the address of the FloatBuffer that it has received using MemoryUtil:

MemoryUtil assumes that it is working with direct byte buffers, and uses Unsafe to read the value of the address field from the buffer. However, if this is not a direct buffer, such as one allocated with FloatBuffer.allocate(16), then the value returned from MemoryUtil is not defined (since non-direct FloatBuffers don't have an address field).

At best, this will crash the game, and at worst it will place the contents of the matrix somewhere on the heap.

Recommended fix:

    /**
     * @reason Optimize
     * @author JellySquid
     */
    @Environment(EnvType.CLIENT)
    @Overwrite
    public void writeToBuffer(FloatBuffer buf) {
        if (buf.remaining() < 16) {
            throw new BufferUnderflowException();
        }

-        if (UnsafeUtil.isAvailable()) {
+        if (buf.isDirect() && UnsafeUtil.isAvailable()) {
            this.writeToBufferUnsafe(buf);
        } else {
            this.writeToBufferSafe(buf);
        }
    }

For non-direct buffers, the address field will simply be left uninitialized at a zero address, so the worst-case scenario here is a memory access violation. Regardless, good catch. Thanks.

Ah interesting, I just looked and address is a field of Buffer, which I didn't know before. Good to know that there's no possible memory corruption here. Thanks for the fix!