At a certain Y on 1.18 claims does not exist!
PirataGu opened this issue ยท 6 comments
Observed Behavior
Anyone can break even inside the claims after a Y
Expected Behavior
Should be claimed even way down the map.
Reproduction steps
https://media.giphy.com/media/f7h8gZkASSUeMK3DDM/giphy.gif
Stack trace or error log
No response
Server version
This server is running Paper version git-Paper-216 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: 30cb7d0)
You are running the latest version
Previous version: git-Paper-137 (MC: 1.18.1)GriefPrevention version
GriefPrevention version 16.18Configuration
# 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:
survival2022: -1
survival2022_nether: -1
survival2022_the_end: -1
Lobby2022: -1
LootWorld: -1
Claims:
Mode:
survival2022_nether: Disabled
survival2022_the_end: Disabled
Lobby2022: Disabled
LootWorld: Disabled
survival2022: 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: 430
Claim Blocks Accrued Per Hour:
Default: 155
Max Accrued Claim Blocks:
Default: 750
Accrued Idle Threshold: 0
AccruedIdlePercent: 0
AbandonReturnRatio: 1.0
AutomaticNewPlayerClaimsRadius: 4
AutomaticNewPlayerClaimsRadiusMinimum: 0
ExtendIntoGroundDistance: 5
MinimumWidth: 5
MinimumArea: 25
MaximumDepth: 0
InvestigationTool: STICK
ModificationTool: GOLDEN_SHOVEL
Expiration:
ChestClaimDays: 9
UnusedClaimDays: 20
AllClaims:
DaysInactive: 100
ExceptWhenOwnerHasTotalClaimBlocks: 10000
ExceptWhenOwnerHasBonusClaimBlocks: 5000
AutomaticNatureRestoration:
SurvivalWorlds: false
AllowTrappedInAdminClaims: false
MaximumNumberOfClaimsPerPlayer: 0
CreationRequiresWorldGuardBuildPermission: true
VillagerTradingRequiresPermission: true
CommandsRequiringAccessTrust: /sethome
DeliverManuals: false
ManualDeliveryDelaySeconds: 30
RavagersBreakBlocks: true
FireSpreadsInClaims: false
FireDamagesInClaims: false
LecternReadingRequiresAccessTrust: true
Spam:
Enabled: false
LoginCooldownSeconds: 60
LoginLogoutNotificationsPerMinute: 10
ChatSlashCommands: /me;/global;/local
WhisperSlashCommands: /tell;/pm;/r;/whisper;/msg
WarningMessage: Please reduce your noise level. Spammers will be banned.
BanOffenders: false
BanMessage: Banned for spam.
AllowedIpAddresses: 1.2.3.4; 5.6.7.8
DeathMessageCooldownSeconds: 120
Logout Message Delay In Seconds: 0
PvP:
RulesEnabledInWorld:
survival2022: true
survival2022_nether: true
survival2022_the_end: true
Lobby2022: true
LootWorld: true
ProtectFreshSpawns: true
PunishLogout: true
CombatTimeoutSeconds: 15
AllowCombatItemDrop: false
BlockedSlashCommands: /home;/vanish;/spawn;/tpa
ProtectPlayersInLandClaims:
PlayerOwnedClaims: true
AdministrativeClaims: true
AdministrativeSubdivisions: true
AllowLavaDumpingNearOtherPlayers:
PvPWorlds: true
NonPvPWorlds: false
AllowFlintAndSteelNearOtherPlayers:
PvPWorlds: true
NonPvPWorlds: false
ProtectPetsOutsideLandClaims: false
Economy:
ClaimBlocksMaxBonus: 0
ClaimBlocksPurchaseCost: 0.0
ClaimBlocksSellValue: 0.0
ProtectItemsDroppedOnDeath:
PvPWorlds: false
NonPvPWorlds: true
BlockLandClaimExplosions: true
BlockSurfaceCreeperExplosions: true
BlockSurfaceOtherExplosions: true
LimitSkyTrees: true
LimitTreeGrowth: false
PistonMovement: CLAIMS_ONLY
PistonExplosionSound: true
FireSpreads: false
FireDestroys: false
AdminsGetWhispers: false
AdminsGetSignNotifications: true
VisualizationAntiCheatCompatMode: false
SmartBan: false
Mute New Players Using Banned Words: false
MaxPlayersPerIpAddress: 3
SilenceBans: true
Siege:
Worlds: []
BreakableBlocks:
- GRASS_BLOCK
- DIRT
- COBBLESTONE
- OAK_PLANKS
- SPRUCE_PLANKS
- BIRCH_PLANKS
- JUNGLE_PLANKS
- ACACIA_PLANKS
- DARK_OAK_PLANKS
- SAND
- GRAVEL
- GLASS
- GRASS
- FERN
- DEAD_BUSH
- WHITE_WOOL
- ORANGE_WOOL
- MAGENTA_WOOL
- LIGHT_BLUE_WOOL
- YELLOW_WOOL
- LIME_WOOL
- PINK_WOOL
- GRAY_WOOL
- LIGHT_GRAY_WOOL
- CYAN_WOOL
- PURPLE_WOOL
- BLUE_WOOL
- BROWN_WOOL
- GREEN_WOOL
- RED_WOOL
- BLACK_WOOL
- SNOW
- GLASS_PANE
DoorsOpenDelayInSeconds: 300
CooldownEndInMinutes: 60
EndermenMoveBlocks: false
SilverfishBreakBlocks: false
CreaturesTrampleCrops: false
RabbitsEatCrops: true
HardModeZombiesBreakDoors: false
Database:
URL: ''
UserName: ''
Password: ''
UseBanCommand: false
BanCommandPattern: ban %name% %reason%
Advanced:
fixNegativeClaimblockAmounts: true
ClaimExpirationCheckRate: 80
OfflinePlayer_cache_days: 90
Abridged Logs:
Days To Keep: 7
Included Entry Types:
Social Activity: true
Suspicious Activity: true
Administrative Activity: false
Debug: false
Muted Chat Messages: falsePlugin 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.
Just noticed that if I modify the claimdata to a negative Y coordinate IT WORKS but the plugin doesn't know how to put the - (minus) behind the number LOOOOL
You need to change MaximumDepth in your config to a suitably small (negative) number.
A newly-written config will default it to Integer.MIN_VALUE, but setting to e.g. -64 should be enough.
EDIT: ah, just saw your mention that you did modify MaximumDepth and still had no luck - hmm. Did you stop the server first and start back up after, or use /gpreload, so you know that the changed value was definitely used?
You claim you've edited MaximumDepth, but have you actually done anything to cause claim extension to occur? Claims do not extend to maximum depth by default, they extend when a player places blocks that aren't trash beneath the claim. Set MaximumDepth to -64 or lower, then build something below 0. A piston, metal blocks, etc. should be enough.
Had this issue on a server I play on too. It was fixed by overriding the sea level, although to what value I do not know. Basically, tricking the config to think sea level is lower than it actually is. Changing the maximumDepth to -64 did not work for us either.
Had this issue on a server I play on too. It was fixed by overriding the sea level, although to what value I do not know. Basically, tricking the config to think sea level is lower than it actually is. Changing the maximumDepth to -64 did not work for us either.
I can assure you that while you may have seen a correlation, that is not the actual cause of claim extension. You can examine the usages of the sea level check to verify this: https://github.com/TechFortress/GriefPrevention/blob/fe94717042415cbddfdf6cdaf52b01415a399794/src/main/java/me/ryanhamshire/GriefPrevention/GriefPrevention.java#L3606
11 references. 1 for TNT placement warning, 3 for surface fluid/creative claim investment score, 1 for explosion handling, 2 for nature restoration, 2 for lava placement, and 2 for aggressive nature restoration via shovel.
Again, you need to actually do something to cause the claim to consider blocks beneath it - GP does not periodically re-evaluate claim depth for you because if you are not making changes to the claim it assumes nothing should change.
Going to close this because OP hasn't responded since being instructed on how to actually cause claim extension once configured.