tab completion takes extreamly long about protocolsupportpocketissues HOT 6 OPEN

change spigot.yml option

tab-complete: -1

this solution will be work nice

from protocolsupportpocketissues.

@magicus I think this prio is high and it isn't a visual glitch

from protocolsupportpocketissues.

Blame pe for doing it way too slow.

from protocolsupportpocketissues.

#blamemojang #blamePE

from protocolsupportpocketissues.

I agree with Shev. It's hard to do anything about; apparently PE has some non-linearity in how it handles their data structures. Possible fixes includes:

1. Disabling tab completion altogether
2. Disabling tab completion completely if the number of commands pass a certain limit
3. Arbitrarily dropping commands from tab completion after a limit
4. Trying to merge the expanded PE "command node chains" into the more compact "nodes with alternatives" that PE seem to use internally, in the hope that this improves performance.

None of the solutions seems particularly attractive. The option 4 seems like the only chance to have a really desirable result, but we don't know if it will work, and going there will require quite a bit of complex algorithms -- which in worst case will have an unacceptable performance cost at the server. It wouldn't surprise me if such merging would end up at O(n^2) or above, and then we'd just shift the penalty to the server.

from protocolsupportpocketissues.

There is a work-around suggested above, which is basically 1), but as an option you can select yourself. I can't seriously think of a much better way to handle this.

from protocolsupportpocketissues.