Paper plugin which executes a command when it detects a player using full bright texture pack
NoFullBright is a small Paper/Spigot plugin that detects likely client-side "fullbright" use in configured worlds and runs a configurable command when a player exceeds the warning threshold.
Every scheduled interval (default: 200 ticks initial delay and 200 ticks between runs) the plugin scans all players in the configured worlds and evaluates each player:
Note: players are only checked when they are in Survival game mode. Players in Creative or Spectator mode are ignored by the checks.
report-command (with the %player% and %world% placeholders) and resets that player's counter.This approach attempts to reduce false positives by requiring repeated detections before taking action.
config.yml)Default config.yml created by the plugin:
# NoFullBright configuration
# worlds: list of world names where the anti-fullbright check runs
# report-command: command executed on violation. You can use %player% and %world% placeholders.
worlds:
- hardcore
report-command: 'report %player% utilizzo della fullbright in %world%'
worlds (list) — exact world names where checks will run. Modify this list to include all worlds where you want the anti-fullbright check active.report-command (string) — the command executed by the server console when a player reaches the warning threshold. The plugin replaces %player% and %world% with the player's name and world name respectively. Make sure the command exists on your server (for example a moderation/reporting plugin). If the command is not available, nothing fatal will happen but no useful action will be taken.%player% — replaced with the player's name.%world% — replaced with the world name.hardcore_1, hardcore_2) update worlds accordingly.light-threshold (default 2)y-limit (default 40)warning-count (default 5)tick-interval (scheduler delay/period)report-command actually exists and is executable by the server console (e.g., a report command provided by another plugin)./plugins: confirm the JAR filename is correct and server logs show it loaded; check server.log for startup errors.Use as you wish. No warranty provided.