Doing /sudo * c:<Chat Message> will cause a number of players to be flagged as spamming and/or banned (if enabled spam: true)
JasmeowTheCat opened this issue ยท 3 comments
Observed Behavior
When using EssentialsX, running /sudo * c: will cause a number of players to be warned about their noise level, which is in the default configuration of GriefPrevention. They will either be told this message and/or banned, dependent on it being enabled in the configuration.
I have also noticed that the player is Minecraft banned, so /minecraft:pardon has to be executed, and not /unban or any plugin name before it such as /litebans:unban, which may cause confusion when it states "This player hasn't been banned." You probably just want to implement it to be /ban.
Expected Behavior
Not flagging those users as potentially spamming for the same message as the message is obviously the same, but shouldn't cause any issue as each user is saying the message themselves.
Reproduction steps
- /sudo * c:
- Watch the magic happen.
Stack trace or error log
No error - Intended behavior - But obviously not intentional.
Server version
This server is running Paper version 1.21.1-131-ver/1.21.1@84281ce (2024-10-31T17:43:44Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are 1 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.1-122-4430e96 (MC: 1.21.1)
GriefPrevention version
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:
world: -1
world_nether: -1
world_the_end: -1
Claims:
Mode:
world: Survival
world_nether: Survival
world_the_end: Disabled
PreventGlobalMonsterEggs: true
PreventTheft: true
ProtectCreatures: true
PreventButtonsSwitches: true
LockWoodenDoors: false
LockTrapDoors: false
LockFenceGates: true
EnderPearlsRequireAccessTrust: true
RaidTriggersRequireBuildTrust: true
ProtectHorses: true
ProtectDonkeys: true
ProtectLlamas: true
InitialBlocks: 100
Claim Blocks Accrued Per Hour:
Default: 150
Max Accrued Claim Blocks:
Default: 80000
Accrued Idle Threshold: 0
AccruedIdlePercent: 0
AbandonReturnRatio: 1.0
AutomaticNewPlayerClaimsRadius: 4
AutomaticNewPlayerClaimsRadiusMinimum: 0
ExtendIntoGroundDistance: 5
MinimumWidth: 5
MinimumArea: 100
MaximumDepth: -2147483648
InvestigationTool: STICK
ModificationTool: GOLDEN_SHOVEL
Expiration:
ChestClaimDays: 7
UnusedClaimDays: 14
AllClaims:
DaysInactive: 60
ExceptWhenOwnerHasTotalClaimBlocks: 10000
ExceptWhenOwnerHasBonusClaimBlocks: 5000
AutomaticNatureRestoration:
SurvivalWorlds: false
AllowTrappedInAdminClaims: false
MaximumNumberOfClaimsPerPlayer: 0
CreationRequiresWorldGuardBuildPermission: true
VillagerTradingRequiresPermission: true
CommandsRequiringAccessTrust: /sethome
DeliverManuals: true
ManualDeliveryDelaySeconds: 30
RavagersBreakBlocks: true
FireSpreadsInClaims: false
FireDamagesInClaims: false
LecternReadingRequiresAccessTrust: true
Spam:
Enabled: true
LoginCooldownSeconds: 60
LoginLogoutNotificationsPerMinute: 5
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:
world: true
world_nether: true
world_the_end: true
ProtectFreshSpawns: true
PunishLogout: false
CombatTimeoutSeconds: 0
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: true
AdminsGetSignNotifications: true
VisualizationAntiCheatCompatMode: false
SmartBan: true
Mute New Players Using Banned Words: true
MaxPlayersPerIpAddress: 3
SilenceBans: true
Siege:
Worlds: []
BreakableBlocks:
- WHITE_WOOL
- DIRT
- OAK_PLANKS
- CYAN_WOOL
- GRAY_WOOL
- ACACIA_PLANKS
- DARK_OAK_PLANKS
- MAGENTA_WOOL
- SPRUCE_PLANKS
- JUNGLE_PLANKS
- DEAD_BUSH
- GLASS_PANE
- ORANGE_WOOL
- PINK_WOOL
- PURPLE_WOOL
- BLUE_WOOL
- FERN
- SAND
- SNOW
- BIRCH_PLANKS
- BLACK_WOOL
- YELLOW_WOOL
- BROWN_WOOL
- SHORT_GRASS
- GRAVEL
- RED_WOOL
- GREEN_WOOL
- GLASS
- LIGHT_GRAY_WOOL
- GRASS_BLOCK
- LIGHT_BLUE_WOOL
- COBBLESTONE
- LIME_WOOL
DoorsOpenDelayInSeconds: 300
CooldownEndInMinutes: 60
EndermenMoveBlocks: false
SilverfishBreakBlocks: false
CreaturesTrampleCrops: false
RabbitsEatCrops: true
HardModeZombiesBreakDoors: false
MobProjectilesChangeBlocks: false
Database:
URL: ''
UserName: ''
Password: ''
UseBanCommand: false
BanCommandPattern: ban %name% %reason%
Advanced:
fixNegativeClaimblockAmounts: true
ClaimExpirationCheckRate: 60
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: false
ConfigVersion: 1
Plugin list
Not applicable. It's EssentialsX caused this.
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.
What does that do, make everyone send a chat message?
May want to just disable antispam entirely then if you're doing stuff like that.
but shouldn't cause any issue as each user is saying the message themselves.
There could be the case where a spammer joins with multiple accounts, then spams the same message in chat amongst the multiple users.
What does that do, make everyone send a chat message?
May want to just disable antispam entirely then if you're doing stuff like that.
Yes, this command in essentials forces everyone to say the same message.
but shouldn't cause any issue as each user is saying the message themselves.
There could be the case where a spammer joins with multiple accounts, then spams the same message in chat amongst the multiple users.
You do make a valid point here though, so not a bug as per say, but an intentional feature.