Player reported this when teleporting to somewhere else.

All the Mods 10 - 4.4 crashed. The logs have been uploaded to gnomebot.dev:

latest.log | debug.log head / tail (~19MB & ~110k lines) | crash-2025-07-13_13.55.22-client.txt | CurseForge: launcher_log.txt head / tail (~25k lines) | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt

Found �[2;34m1�[0m log analysis results:
�[2;34mCodexMessage�[0m in: crash-2025-07-13_13.55.22-client.txt

Mod list changes beyond the modpack:

�[2;34mMod list wasn't modified.�[0m

Looks like here

This is being discussed in the discord, however unless this can be reproduced with just Ars + vanilla, I believe this is another mod adding invalid blocks to the BlockEntityTypeAddBlocksEvent event.

Block entities do not typically tick or render without their own blockstate, so this occurrence of ticking without its state is normally invalid behavior.

In LevelChunk#tick

    if (this.blockEntity.getType().isValid(blockstate)) {
        this.ticker.tick(LevelChunk.this.level, this.blockEntity.getBlockPos(), blockstate, this.blockEntity);

Was able to reproduce this locally fairly easily actually, looks like the Direction property is missing when teleporting away, but the blockstate is valid.

Fixed in latest, the state from the level on the client does not match the state on the tile which does pass the valid types check.