Add Shelf#getSlot using Vector

[Doc94]

Close #13398 by adding a method for determinate the slot using a Vector, works like the same than the logic for ChiseledBookshelf

test:

@EventHandler
    public void onPlayerInteractEvent(PlayerInteractEvent event) {
        final Player player = event.getPlayer();
        final Block block = event.getClickedBlock();
        if (block == null) return;
        if (block.getState() instanceof Shelf shelfState) {
            player.sendMessage(Component.text("Shelf: " + shelfState.getSlot(event.getClickedPosition())));
        } else if (block.getState() instanceof ChiseledBookshelf chiseledBookshelfState) {
            player.sendMessage(Component.text("ChiseledBookshelf: " + chiseledBookshelfState.getSlot(event.getClickedPosition())));
        }
    }

javaw_2025-12-28_13-06-20.mp4

[Lulu13022002]

Can you move the implementation to a common class like CraftSelectable or something.
PlayerInteractEvent#getClickedPosition should probably be renamed too but it can be done in another PR to not rely on a deprecated method.

Also next time don't show an image for your test code it's not convenient.

[Lulu13022002]

It's not safe to cast the block data cause a plugin could simply change it to something else.

[Doc94]

Well i base in the other implementation... Maybe a Precondition.checkState can be good here?

[Lulu13022002]

A precondition is better -1 has some other meaning here, i did the change for you. But from a quick look it's impossible for this method to return -1?

[Doc94]

looks like but not sure.. i prefer keep that docs xd

[Doc94]

Can you move the implementation to a common class like CraftSelectable or something.
PlayerInteractEvent#getClickedPosition should probably be renamed too but it can be done in another PR to not rely on a deprecated method.

Also next time don't show an image for your test code it's not convenient.

Okay, for the common class just move all to a new class with static methods not?