[Bug]: Hopper Protection Doesn't work
ilfarpro opened this issue ยท 3 comments
Version of BlockProt
1.0.4
Description of the bug
Hopper protection just doesn't work. Here is the video with demonstration: https://youtu.be/pD7zDvoITUk
Steps to reproduce
Watch video: https://youtu.be/pD7zDvoITUk
Additional context
Please, fix it ASAP.
Version of game 1.18.1
Version of server: Purpur 1.18.1 (one of latest builds)
My configuration
# BlockProt Config
# Load a language file from the plugins/BlockProt/ directory.
# You can create your own language files and edit existing ones.
# Translations can be missing from this file and will instead be loaded
# from "translations_en.yml".
language_file: translations_en.yml
# The fallback string when a translation cannot be found in translations_en
# and the specified language_file above. This often happens when the plugin
# is updated and there are new translations or translations were renamed. Best
# to then delete the lang/ folder and restart the server.
fallback_string: "Unknown translation"
# If this is true, we will copy and replace the translation files on
# each startup. This is so that when you should update this plugin, any
# new or updated translations are automatically copied and applied. If
# you want to modify and included translation file, you will have to make
# this false.
replace_translations: true
# If set to "true", anytime an admin joins the server, they will
# receive an in-game message if this plugin is outdated.
# If set to "false", no message will be sent but /blockprot update
# will still work.
notify_op_of_updates: true
# If set to "true", redstone will be automatically disallowed on every
# placed block, if the player has lock on place enabled.
redstone_disallowed_by_default: false
# A list of world names the plugin should not be usable in.
# The case of each name is ignored.
# Useful for a mining-only world where a block should not be
# owned by anyone. For example:
# - world_mining
# - world_end
excluded_worlds: [ ]
# Setting this to 'false' will make every new player have
# their lock and place setting set to of. This will be by
# default set to 'true'.
# Note: This does NOT affect players who have previously
# changed this setting.
lock_on_place_by_default: true
# Tile entities that should be locked. Tile entities are blocks
# that can contain items. You can find a detailed list of all
# possible values at https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Material.html.
lockable_tile_entities:
- CHEST
- TRAPPED_CHEST
- FURNACE
- SMOKER
- BLAST_FURNACE
- HOPPER
- BARREL
- BREWING_STAND
- DISPENSER
- DROPPER
- LECTERN
# All varieties of shulker boxes that should be lockable.
lockable_shulker_boxes:
- BLACK_SHULKER_BOX
- BLUE_SHULKER_BOX
- BROWN_SHULKER_BOX
- CYAN_SHULKER_BOX
- GRAY_SHULKER_BOX
- GREEN_SHULKER_BOX
- LIGHT_BLUE_SHULKER_BOX
- LIGHT_GRAY_SHULKER_BOX
- LIME_SHULKER_BOX
- MAGENTA_SHULKER_BOX
- ORANGE_SHULKER_BOX
- PINK_SHULKER_BOX
- PURPLE_SHULKER_BOX
- RED_SHULKER_BOX
- SHULKER_BOX
- WHITE_SHULKER_BOX
- YELLOW_SHULKER_BOX
# Blocks that should be lockable.
# This only works with Spigot 1.16.4 or higher.
lockable_blocks:
- ANVIL
- CHIPPED_ANVIL
- DAMAGED_ANVIL
- ACACIA_FENCE_GATE
- BIRCH_FENCE_GATE
- CRIMSON_FENCE_GATE
- DARK_OAK_FENCE_GATE
- JUNGLE_FENCE_GATE
- OAK_FENCE_GATE
- SPRUCE_FENCE_GATE
- WARPED_FENCE_GATE
# Doors are two blocks and are therefore handled differently.
# This only works with Spigot 1.16.4 or higher.
lockable_doors:
- ACACIA_DOOR
- BIRCH_DOOR
- CRIMSON_DOOR
- DARK_OAK_DOOR
- JUNGLE_DOOR
- OAK_DOOR
- SPRUCE_DOOR
- WARPED_DOOR
Fixed it. Issue was related to my outdated paper.yml hopper settings:
paper.yml hopper section should be like this to fix bug
hopper:
cooldown-when-full: true
disable-move-event: false
ignore-occluding-blocks: false
my old paper.yml hopper section was:
hopper:
cooldown-when-full: true
disable-move-event: true
ignore-occluding-blocks: true
Hmm, thanks. This seems interesting, perhaps I should note this on Spigot/CurseForge. Thanks for letting me know!