A follow-up to 2.11.6, from the same report.

The warning now names the plugins that could be responsible

2.11.6 started saying when something else on the server overwrites view or simulation distance. Useful, but it left the obvious question open: which plugin? On the server this came from, answering that meant going through forty plugins by hand.

There is no way to catch the writer in the act, since Bukkit has no event for it and the call is long gone by the time the next check notices. What can be answered is which plugins are even able to do it: a call to setViewDistance leaves the method name in the calling class, and Bukkit API names survive obfuscation. So the warning is now followed by a second line:

Plugins installed here that CAN write view or simulation distance: ClearLag.
This lists what is capable of it, not what did it - a plugin whose feature is
turned off still appears, and so does one that only changes it per player.
Check their configs for a view-distance option before changing anything, and
do not remove a plugin on the strength of this line.

The wording is deliberate. The scan proves capability, never guilt: a plugin with the feature switched off still matches, and Player#setViewDistance is spelled the same as the world method, so per-player plugins match without ever touching a world. It exists to turn forty plugins into two worth checking, not to pick one out.

If nothing matches, it says so too, and points at server.properties and proxies instead.

The scan reads the jars once per server start, on a background thread, and only after a conflict has actually been detected. Servers that never hit one never pay for it.

Upgrading

No config changes and no new keys. Replace the jar and restart.