You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is a very large amount of worlds on the build server that uses this plugin. For servers using Scaffold, it clutters the chat to the point where you may not be able to scroll up past a certain point and read the list of all of the worlds due to Minecraft's limitations.
Not including different chat window sizes that users choose, This will leave out worlds that go in the alphabetical order they're meant to be in, because they get cut off. Not only this, but it's hard to read each one at a single time and it shouldn't just come out in one little string in chat.
The fix
Add a way to navigate worlds via pages. Rather than output a string of the worlds, generate a page for a certain amount of worlds. This way, navigation is much more efficient. A command like /worlds list 1 would display alphabetically the first page, and so forth.
The issue
Currently, there is a very large amount of worlds on the build server that uses this plugin. For servers using Scaffold, it clutters the chat to the point where you may not be able to scroll up past a certain point and read the list of all of the worlds due to Minecraft's limitations.
Not including different chat window sizes that users choose, This will leave out worlds that go in the alphabetical order they're meant to be in, because they get cut off. Not only this, but it's hard to read each one at a single time and it shouldn't just come out in one little string in chat.
The fix
Add a way to navigate worlds via pages. Rather than output a string of the worlds, generate a page for a certain amount of worlds. This way, navigation is much more efficient. A command like
/worlds list 1
would display alphabetically the first page, and so forth.https://hub.spigotmc.org/javadocs/spigot/org/bukkit/util/ChatPaginator.html
Image
The text was updated successfully, but these errors were encountered: