Custom Items and ModelEngine Models Under Anticheat Checks

Short answer

Custom items can change attack speed, reach, damage, or knockback, and model-based entities can move the hit target away from the vanilla hitbox. An anticheat that assumes vanilla values may alert on legitimate hits. List every custom item and model entity in use, run a fixed set of hits on staging for each one, and log the alerts before you change any check.

Where custom items change combat numbers

Custom item plugins often set their own damage, attack speed, or reach values. Some use item attributes. Others apply their effects in plugin code when a hit lands. Each method changes what the server accepts, so a check that uses vanilla numbers for a sword can read a custom weapon as impossible.

Which values change depends on how each item is built. Open the item definitions on your own server rather than assuming a weapon behaves like its vanilla counterpart. A weapon named like a sword can carry very different numbers.

How model entities affect hit detection

Model-based entity plugins place a visual model over an entity. Some also spawn invisible or interaction entities that receive the hit. The registered target can then sit at a different position or size than the vanilla mob. Reach and hitbox checks compare the attacker's position with that target, so an offset target can look like a hit from too far away.

The effect depends on where the interaction entity sits and how the plugin updates it. Stand at a few fixed distances on staging and compare the alert distance with the distance you actually hit from. Do not assume the model's visual edge matches the server's collision box.

Find the check that reacts

Use this table to decide which test to run first. Each row names a setup, the check family that may react, and a test you can repeat on staging. The table lists what to test, not a measured result.

Test each item on staging

A repeatable test gives you evidence you can compare after each change. Use the same server version, the same anticheat version, the same client, and a flat test area with one fixed target. Change only one variable per run.

• List every custom item and model entity type in use, with the plugin name and version for each.
• Copy the attack, reach, and knockback values each item sets from that plugin's own configuration.
• Build a staging area with a flat floor, a fixed target, and marked distances.
• For each item, run the matching test from the table and log every alert with its distance and time.
• If alerts appear only with one item, compare that item's values with what the flagged check expects.
• Change one setting, rerun the same test, and keep the result next to the change.

Why item-based exemptions are risky

It can be tempting to exempt a whole item from a check. Items can reach players through drops, trades, shops, or staff commands, so an item exemption works for anyone who obtains the item. Scope any relaxation to the check that alerted and keep the rest of that check active.

Model-based hitboxes raise a similar concern in the other direction. An offset target may let a player land hits from a distance the vanilla target would not allow. Test the target from both sides before you loosen any reach or hitbox setting.

What we have not verified

We have not tested any specific item plugin or ModelEngine release against any anticheat. Hit behavior depends on the plugin version, the server version, and the anticheat version together. The results of your own staging run are the only evidence that applies to your server.