The Bug:
Right-clicking the fletching table in spectator mode flashes the crafting table’s GUI for a split second. This is probably happening because the fletching table is using GUI group ”0xFF” which isn’t a valid one.
-------------------------------------------------
Steps to Reproduce:
1. Get a "Fletching Table" and place it down.
2. Go into spectator mode by using "F3 + N", "F3 + F4" or by just typing in chat "/gamemode spectator".
3. While in spectator mode go near the fletching table that you’ve just placed and then right-click the previously mentioned block.
--------------------------------------------------
Linked issues
is duplicated by 16
Attachments
Comments 18
This is working as intended, see MC-143441.
To explain why the other one is resolved – it's resolved as "works as intended" meaning that it's known behavior, but intended. Bugs that are resolved as "fixed" are specifically fixed, but there are a few other resolutions (including, of course, "duplicate").
Here is FletchingTableBlock.java
. Note that this is an extension of CraftingTableBlock.java
. A solution would be to just make it an extension of Block.java
instead.
package net.minecraft.world.level.block;import net.minecraft.core.BlockPos;
import net.minecraft.world.InteractionHand;
import net.minecraft.world.InteractionResult;
import net.minecraft.world.entity.player.Player;
import net.minecraft.world.level.Level;
import net.minecraft.world.level.block.state.BlockBehaviour;
import net.minecraft.world.level.block.state.BlockState;
import net.minecraft.world.phys.BlockHitResult;public class FletchingTableBlock extends CraftingTableBlock {
protected FletchingTableBlock(BlockBehaviour.Properties paramProperties) {
super(paramProperties);
}
public InteractionResult use(BlockState paramBlockState, Level paramLevel, BlockPos paramBlockPos, Player paramPlayer, InteractionHand paramInteractionHand, BlockHitResult paramBlockHitResult) {
return InteractionResult.PASS;
}
}
Only the first version an issue occured in, and latest versions are of interest, not outdated versions in between. (First one only so the cause can be narrowed down to code changed in said version.)
Confirmed in 19w11a onwards