Incompatibility with mod "Silent Gear"

[unilock]

When on a Forge server running under Velocity via Ambassador, the mod "Silent Gear" does not work properly.
(Silent Gear is a mod that introduces "modular" tools and equipment, a la Tinker's Construct.)

Proxy:

• Velocity: 3.1.2-SNAPSHOT-179
• Ambassador: 0.5.1

Client / Backend:

• Minecraft: 1.18.2
• Forge: 40.1.80
• Ambassador-Forge: 1.18.2-0.2.1
• Silent Gear: 2.10.14
• (Caelus API: 1.18.1-3.0.0.2)
• (Curios API: 1.18.2-5.0.7.1)
• (Silent Lib: 6.2.0)

When crafting a Silent Gear tool through any means, an "invalid item" is produced rather than the expected tool.

Expected:

Despite being a red X, the tool seems to function normally otherwise.

Here's some information I've gathered regarding when this bug is encountered:

• Connecting to the backend server directly (w/o Ambassador) works fine.
• Connecting to the backend server directly, logging out, restarting the backend server with Ambassador-Forge installed, then connecting to the backend server via Velocity + Ambassador works fine as well.
• After a game restart, connecting to the backend server via Velocity first does not work.
• Afterwards, restarting the backend server without Ambassador and connecting to it directly (without a game restart in between) does not work.

Note that tools created as "X"s later appear correctly when directly connecting to the backend server first, and tools created as normal appear as "X"s when connecting via Velocity first. So I assume the item data remains the same between relogs with or without restarting the game.

Also note that, rather than making a direct connection to the backend server before connecting via Velocity, you can instead simply load a singleplayer world. This has the same effect, regarding making Silent Gear tools look correct.

If I recall correctly, connecting to the server via Velocity first (to trigger the issue) will not affect the look of the tools in a singleplayer world loaded afterward, in the same gameplay session (i.e. without restarting the game). That is to say, Silent Gear will work fine in singleplayer, even after connecting to the backend via Velocity (which would otherwise break Silent Gear).
Also IIRC, after leaving singleplayer as above and connecting to the backend via Velocity a second time (in one session), the mod will continue to work fine.
(I say the above ambiguously, as I last tested singleplayer in the context of this issue with a modpack (All the Mods 7), which had a tendency to crash when switching from multiplayer to singleplayer.)

Let me know if I need to clarify anything, as I've come to realize that this issue is rather difficult to explain in text. Maybe I should make a diagram of some sort...

[unilock]

Fixed in v1.1.2-alpha :)