Wind charges are unable to activate redstone components within a claim, regardless of trust level
snurre0 opened this issue ยท 0 comments
Observed Behavior
Wind charges can activate redstone components like buttons, levers and note blocks. This is not possible if those componends are located inside of a claim, regardless of the players trust level.
Expected Behavior
If the player that fires these wind charges are trusted at a level where they have access to manually activate these redstone components, they should also be able to activate them using wind charges.
Reproduction steps
- Place a button, level and/or note block down
- Fire wind charges at them at observer them being activated
- Claim the area around the placed components
- Fire wind charges at them again and observer them not being activated, even if you own the claim and/or are trusted to it
Stack trace or error log
No response
Server version
10.07 18:54:26 [Server] INFO This server is running Paper version 1.21-47-master@62ed302 (2024-07-07T17:34:15Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
GriefPrevention version
10.07 18:55:17 [Server] INFO GriefPrevention version 16.18.4
Configuration
# Default values are perfect for most servers. If you want to customize and have a question, look for the answer here first: http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/setup-and-configuration/
GriefPrevention:
SeaLevelOverrides:
Simplex: -1
Simplex_nether: -1
Simplex_the_end: -1
Claims:
Mode:
world: Survival
world_the_end: Survival
world_nether: Survival
PreventGlobalMonsterEggs: true
PreventTheft: true
ProtectCreatures: true
PreventButtonsSwitches: true
LockWoodenDoors: true
LockTrapDoors: true
LockFenceGates: true
EnderPearlsRequireAccessTrust: true
RaidTriggersRequireBuildTrust: true
ProtectHorses: true
ProtectDonkeys: true
ProtectLlamas: true
InitialBlocks: 225
Claim Blocks Accrued Per Hour:
Default: 150
Max Accrued Claim Blocks:
Default: 300000
Accrued Idle Threshold: 0
AccruedIdlePercent: 0
AbandonReturnRatio: 1.0
AutomaticNewPlayerClaimsRadius: 4
AutomaticNewPlayerClaimsRadiusMinimum: 0
ExtendIntoGroundDistance: 20
MinimumWidth: 1
MinimumArea: 10
MaximumDepth: -64
InvestigationTool: STICK
ModificationTool: GOLDEN_SHOVEL
Expiration:
ChestClaimDays: 9999999
UnusedClaimDays: 9999999
AllClaims:
DaysInactive: 9999999
ExceptWhenOwnerHasTotalClaimBlocks: 10000
ExceptWhenOwnerHasBonusClaimBlocks: 5000
AutomaticNatureRestoration:
SurvivalWorlds: false
AllowTrappedInAdminClaims: false
MaximumNumberOfClaimsPerPlayer: 0
CreationRequiresWorldGuardBuildPermission: true
VillagerTradingRequiresPermission: true
CommandsRequiringAccessTrust: /sethome;/esethome;/createhome;/ecreatehome
DeliverManuals: true
ManualDeliveryDelaySeconds: 30
RavagersBreakBlocks: true
FireSpreadsInClaims: false
FireDamagesInClaims: false
LecternReadingRequiresAccessTrust: true
Spam:
Enabled: true
LoginCooldownSeconds: 10
LoginLogoutNotificationsPerMinute: 0
ChatSlashCommands: /me;/global;/local;/minecraft:me;/tpa;/suicide
WhisperSlashCommands: ''
WarningMessage: Please reduce your noise level. Spammers will be muted.
BanOffenders: false
BanMessage: Banned for spam.
AllowedIpAddresses: 1.2.3.4; 5.6.7.8
DeathMessageCooldownSeconds: 0
Logout Message Delay In Seconds: 0
PvP:
RulesEnabledInWorld:
world: true
world_nether: true
world_the_end: true
ProtectFreshSpawns: false
PunishLogout: false
CombatTimeoutSeconds: 0
AllowCombatItemDrop: true
BlockedSlashCommands: /home;/vanish;/spawn;/tpa
ProtectPlayersInLandClaims:
PlayerOwnedClaims: false
AdministrativeClaims: false
AdministrativeSubdivisions: false
AllowLavaDumpingNearOtherPlayers:
PvPWorlds: false
NonPvPWorlds: false
AllowFlintAndSteelNearOtherPlayers:
PvPWorlds: false
NonPvPWorlds: false
ProtectPetsOutsideLandClaims: true
Economy:
ClaimBlocksMaxBonus: 0
ClaimBlocksPurchaseCost: 0.0
ClaimBlocksSellValue: 0.0
ProtectItemsDroppedOnDeath:
PvPWorlds: true
NonPvPWorlds: true
BlockLandClaimExplosions: true
BlockSurfaceCreeperExplosions: false
BlockSurfaceOtherExplosions: false
LimitSkyTrees: false
LimitTreeGrowth: false
PistonMovement: EVERYWHERE
PistonExplosionSound: true
FireSpreads: true
FireDestroys: true
AdminsGetWhispers: false
AdminsGetSignNotifications: true
VisualizationAntiCheatCompatMode: false
SmartBan: true
Mute New Players Using Banned Words: true
MaxPlayersPerIpAddress: 5
SilenceBans: true
Siege:
Worlds: []
BreakableBlocks:
- DIRT
- GRASS <-- can't understand this entry, see BukkitDev documentation
- LONG_GRASS <-- can't understand this entry, see BukkitDev documentation
- COBBLESTONE
- GRAVEL
- SAND
- GLASS
- THIN_GLASS <-- can't understand this entry, see BukkitDev documentation
- WOOD <-- can't understand this entry, see BukkitDev documentation
- WOOL <-- can't understand this entry, see BukkitDev documentation
- SNOW
DoorsOpenDelayInSeconds: 300
CooldownEndInMinutes: 60
EndermenMoveBlocks: true
SilverfishBreakBlocks: true
CreaturesTrampleCrops: true
RabbitsEatCrops: true
HardModeZombiesBreakDoors: true
MobProjectilesChangeBlocks: false
Database:
URL: ''
UserName: ''
Password: ''
UseBanCommand: false
BanCommandPattern: ban %name% %reason%
Advanced:
fixNegativeClaimblockAmounts: true
ClaimExpirationCheckRate: 60
OfflinePlayer_cache_days: 365
Abridged Logs:
Days To Keep: 7
Included Entry Types:
Social Activity: true
Suspicious Activity: false
Administrative Activity: true
Debug: false
Muted Chat Messages: true
ConfigVersion: 1
Plugin list
No response
Running without GriefPrevention
- I attempted running the server without GriefPrevention installed.
- The problem does not occur when GriefPrevention is removed from the server.
Running with only GriefPrevention
- I attempted running only GriefPrevention on the server.
- The issue still occurs when GriefPrevention is the only plugin running.
Running on a fresh, clean server installation
- I attempted testing for the issue on a new server.
- The issue still occurs on a new server.
Using unmodified client
- I attempted testing for the issue with the vanilla client.
- The issue still occurs when using the vanilla client.
We appreciate you taking the time to fill out a bug report!
- I searched for similar issues before submitting this bug report.