the error in question is this:

Description: Unexpected error

java.lang.NullPointerException: Cannot invoke "net.minecraft.client.gui.hud.DebugHud.shouldShowDebugHud()" because "debugOverlay" is null
	at knot//dev.tr7zw.exordium.components.vanilla.CrosshairComponent.captureState(CrosshairComponent.java:32)
	at knot//dev.tr7zw.exordium.components.vanilla.CrosshairComponent.captureState(CrosshairComponent.java:15)
	at knot//dev.tr7zw.exordium.components.BufferInstance.postRender(BufferInstance.java:102)
	at knot//MC//net.minecraft.client.gui.hud.InGameHud.wrapOperation$bid000$exordium$renderCrosshairWrapper(InGameHud.java:3521)
	at knot//MC//net.minecraft.client.gui.hud.InGameHud.render(InGameHud.java:238)
	at knot//MC//net.minecraft.client.render.GameRenderer.render(GameRenderer.java:912)
	at knot//MC//net.minecraft.client.MinecraftClient.render(MinecraftClient.java:1327)
	at knot//MC//net.minecraft.client.MinecraftClient.run(MinecraftClient.java:888)
	at knot//net.minecraft.client.main.Main.main(Main.java:265)
	at app//net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:480)
	at app//net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
	at app//net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
	at app//org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:105)
	at app//org.prismlauncher.EntryPoint.listen(EntryPoint.java:129)
	at app//org.prismlauncher.EntryPoint.main(EntryPoint.java:70)

happens as soon as you join any world, server or not doesnt matter
started happening after updating to 1.4.0 earlier today

disabling fast crosshair solves the issue, but i wonder why is it like this when it worked perfectly before the update

Hm this is weird. You have a bunch of experimental/known broken mods in there too(like Fastanim), so that will make testing harder. I guess I can just bodge a nullcheck around it for now, but no clue if that will behave correctly with these mods.

but the thing is, it worked fine before the recent update.
did you change anything regarding the crosshair rendering?

Can you send the full crash report with the other mods and versions visible? Something is breaking the debug overlay, causing this crash. (I could patch the crash out, but then the crosshair wouldnt work correctly when you open f3)

oh i see, i'll send it in a minute

latest.log
here's the whole log, it actually just hangs without crashing and stuff continues to go on but nothing is rendering, im not even pressing f3 or anything, that's just the regular crosshair

The crosshair depends on f3 being open or not (turns into the xyz direction marker in f3), thats why it depends on it. Yet the crosshair should never render with the debugOverlay not being initialized.

The entire mod has been reworked, you are on 1.20.4, that version has been a year old.

OK just tested, this seems to be a 1.20.4 issue that I didnt catch because the fast crosshair is not on by default due to its buggy visuals. Will add a workaround.

yay