[SPIGOT-915] Large getEntities calls filtering too greedy Created: 23/May/15  Updated: 08/Jul/15  Resolved: 08/Jul/15

Status: Closed
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Nicolas Glassey Assignee: Thinkofname
Resolution: Fixed Votes: 0
Labels: 1.8.3, 1.8.5, api, entity, plugin
Environment:

Linux raidstone.net 3.14.39-1-lts #1-ARCH SMP Sun Apr 19 13:09:40 CEST 2015 x86_64 GNU/Linux



 Description   

One of the latest spigot updates has broken all the "getEntities" calls from API.

I have made a small plugin to count all mobs in a certain radius (link + sourcecode below) that has been working flawlessy since 1.8 came out, and when I updated to latest spigot version a few hours ago, that kind of messages happen in chat every time I use my command :

[14:25:23 WARN]: Filtered out large getEntities call -8,5 9,5

This affects spigot 1.8.5, AND 1.8.3, since version git-Spigot-870264a-0a645a2, at least.

Obviously, it renders my plugins completely unusable.

Plugin's sourcecode :
https://git.raidstone.net/MobCount/
(user: spigot, pass: spigotjira)

Direct .jar download :
https://lla.pokeby.com/MobCount.jar
(no NMS code, compatible with all 1.8 versions so far)

Usage : /countmobs <radius>
Radius is squared.
It usually worked flawlessy with radius up to 150², and started lagging a bit after that, now it's just unusable with radius 9² !



 Comments   
Comment by Black Hole [ 23/May/15 ]

Looking at the code it's filtering calls above about 160 blocks.

The filtering makes perfect sense, since it's loading a lot of chunks and the server might become unresponsive.
But an option for server owners to raise this limit could be helpful.

Comment by Nicolas Glassey [ 23/May/15 ]

Just as an addition to my original issue creation, I've tested the plugin on a clear spigot 1.8.5, with no other plugin than mine on it.

Comment by ian davies [ 23/May/15 ]

This is an issue, it's readily produced by Clear Lag http://dev.bukkit.org/bukkit-plugins/clearlagg/ and is visible in console as a routine process of the plugin. Running a /lagg area command over 70 reproduces the issue in the console immediately. In game any lagg area commands over 70 radius fails immediately, less than 70, the error message is not seen and the command is succesful

Generated at Sat Apr 05 06:16:25 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.