Yes, I did consider reporting this issue, but I believe it's a bug that users cannot intentionally reproduce, and as I recall, such a bug requires /whereami (information about the current CubeCraft node) and there's no way to check it later, so even if I report it, it would be difficult to fix...