Mod completely breaks on some servers.

[IceBlossom]

I couldn't really think of a better title, but these screenshots should do justice.
I have confirmed this happens when JUST Terrestria (+Fabric API) is installed.


First image is on MCC Island, second is on Hypixel.

[gniftygnome]

Are you running a vanilla client without Terrestria installed? That does not work and is not intended to work.

[IceBlossom]

No. This is on Fabric (Loader version 0.16.5) and the latest version of Fabric API for 1.21.1

[gniftygnome]

Please provide the client logs.

[gniftygnome]

Actually, when you say it breaks on some servers, do the servers have Terrestria installed? It must be installed on both and it must be the same version.

[IceBlossom]

No. I don't wanna try and sound rude, but why would practically any non-survival server with vanilla compatibility have world gen mods installed?
The logs say practically nothing, but here you go.
latest.log

[gniftygnome]

Mods that add blocks and items to the game have to be on the server. That is a fundamental requirement. Some use clever hacks to avoid having to be installed on the client (but Terrestria is not one of these). Having Terrestria installed on the client and not on the server is not a supported configuration.

[IceBlossom]

I understand that having the mod not on the client side wouldn't allow it to be used. However, wouldn't the client just not be able to use it considering the server doesn't have any of the relevant data? And so nothing would be wrong?
If that's the case, then why does having the mod installed on the client break everything on a server?
These screenshots, like the ones in the start of this thread, are on MCC Island, Hypixel, and Minr's lobbies with JUST Terrestria and Fabric API/Loader.

And by the way, all those blocks. Ones that aren't there in the server, all the waterlogged blocks. They all act like they are actually there on the client, so I am able to stand on those. To other players, it looks like I'm floating.

When looking at the F3 screen, looking at the blocks that appear on the client side do say what they are, even when in reality it should be air, or a completely different block.

These screenshots were taken on my normal modpack with 100+ mods without Terrestria (including world gen mods like Structory, Terralith, Tectonic, and Blooming Biosphere for singleplayer use, which is what I installed Terrestria for) and does not affect what I see on vanilla servers at all (can't include Minr due to it not telling me what mod I have that's problematic).

Why Terrestria would cause this huge of an issue on servers that simply don't have the mod installed is beyond me.

[gniftygnome]

It doesn't break anything, the texture locations just aren't where they are on the server, so the client shows you the wrong textures.

[IceBlossom]

Okay, so I could get it showing me the wrong textures. But why would the mod put in entirely new blocks that are no where to be found on a vanilla client? And change the properties of some blocks to be waterlogged? Incorrect textures should not be able to do that.

[gniftygnome]

They should just be waterlogged on the client. Block states are part of how textures are selected, so selecting the wrong texture can mean selecting a waterlogged one. Same with seeing the modded blocks. Nothing changed on the server, but on the client you can see a modded block because those modded blocks are now part of the client's blocks and texture atlas.