If a stonecutter has more than 128 outputs for a given input item, the 129th output (on the 33rd row) and beyond won't be obtainable and will behave strangely when attempting to use them. This bug only occurs when connected to a server. Singleplayer works as expected.

The datapack used in the video below has been attached. It's an extreme use case, but one I've ran into. For this datapack, the bug starts on the output row that has the budding amethyst block as the last option.
Video example

In the code, using the official mappings, MultiPlayerGameMode.handleInventoryButtonClick(int, int) and StonecutterMenu.clickMenuButton(Player, int) accept an int argument for what output was clicked, but when ServerboundContainerButtonClickPacket get the value, it effectively casts it to a byte, preventing recipes beyond the 128th from being selected. This only happens when connected to a server since the int -> byte conversion never occurs otherwise.