Kill Aura

What this is for

kill-aura is the built-in combat automation plugin that makes a bot look at nearby targets and attack them when they enter the configured ranges.

This is useful for:

• combat testing
• PvP behavior experiments
• checking entity targeting under load

It is not a general-purpose movement or navigation system. It only takes over the parts of control needed for targeting, looking, swinging, and attacking.

What the main settings mean

The important relationship is:

• look-range should usually be the largest
• swing-range should usually be smaller than look-range
• hit-range should usually be the smallest and most conservative

Enable and tune kill-aura

How the range settings interact

Look range

This controls when the bot begins orienting toward a target.

If it is too small, the bot may react late. If it is too large, the bot may look unnatural or overreact to distant entities.

Swing range

This controls arm swing behavior. It can be larger than hit range so the bot visually starts reacting before an actual attack is possible.

If you set it to 0, swing-only behavior is disabled.

Hit range

This is the real attack threshold. Keep it conservative unless you are explicitly testing edge cases.

If your hit-range is too aggressive, you are more likely to create behavior that is unrealistic or inconsistent with the target environment.

Cooldown and version behavior

kill-aura respects normal attack strength behavior by default.

The plugin adds custom attack delay logic in two situations:

• on protocol versions up to 1.8
• when ignore-cooldown is enabled

That means attack-delay-ticks matters most when you want older-style or intentionally cooldown-ignoring behavior.

If you leave ignore-cooldown off on modern versions, normal attack readiness remains the safer default.

Wall checks and visibility

With check-walls enabled, the bot avoids attacking targets it should not really be able to reach or see cleanly.

That is the safer choice for realistic testing.

Turn it off only if:

• you are testing a very specific environment
• you understand the tradeoff
• you do not care about natural-looking line-of-sight behavior

Safe tuning workflow

Use this order:

1. enable the plugin
2. fill whitelisted-users
3. leave check-walls enabled
4. test default ranges
5. adjust one range at a time
6. only then decide whether cooldown changes are necessary

That keeps your changes attributable. If you alter every range and timing value at once, it becomes much harder to understand what actually improved or broke the behavior.

Common failure patterns

The bot looks at targets but does not hit

look-range is large enough, but hit-range is too small or the cooldown timing is preventing an attack.

The bot swings too early

Your swing-range is larger than needed for the environment you are testing.

The bot attacks through unrealistic angles

Check whether check-walls is disabled or your ranges are too aggressive.

Friendly or protected players get targeted

Your whitelisted-users list is incomplete or misspelled.

Related pages

• Import Accounts
• Import Proxies
• Plugins