Shield Stun

**ShieldStuns A drop-in Paper plugin that takes care of shield configuration so you don't have to.

The Problem Paper has a useful but buried setting called skip-vanilla-damage-tick-when-shield-blocked that improves how shields interact with damage ticks. To enable it, you'd normally have to dig through paper-global.yml, find the right section, and edit it by hand. ShieldStuns does this for you — automatically, on startup, every time.

How It Works Drop ShieldStuns.jar into your plugins/ folder and start your server. That's it.

The plugin runs at startup, reads your paper-global.yml, and sets:

collisions: skip-vanilla-damage-tick-when-shield-blocked: true

If the setting is already enabled, it skips the write entirely. No unnecessary file operations, no performance overhead.

Setup Drop ShieldStuns.jar into plugins/ Start your server Restart once more — Paper needs a restart to apply config changes You're done What You'll See [ShieldStuns] ShieldStuns plugin is enabling... [ShieldStuns] Modified paper-global.yml successfully! [ShieldStuns] Successfully enabled skip-vanilla-damage-tick-when-shield-blocked! [ShieldStuns] Server restart required for changes to take effect! [ShieldStuns] ShieldStuns plugin enabled successfully!

On subsequent startups, if the setting is already correct:

[ShieldStuns] skip-vanilla-damage-tick-when-shield-blocked is already enabled. No changes needed.

Good to Know Paper only — won't work on Spigot or Bukkit No commands, no permissions, no config files — fully automatic Safe to remove — once the setting is applied, it stays in your config even if you delete the plugin Startup load — runs at the STARTUP phase, before other plugins initialize Java 17+ required Troubleshooting Issue Fix paper-global.yml not found Make sure you're running Paper, not Spigot. Start the server at least once to generate configs. Setting not applying Restart the server after the plugin's first run. Permission errors Check that the server process can write to the config/ directory.**