Pagination Utils 2.1.7 - Quality of life features

Added the possibility to whitelist guild IDs for cache-less use, this will probably help developers with thousands of guilds.
For QoL matters, it's now possible to set whether the Message should be deleted or not after the button handling ends (either via "X" button or after timeout) and activate the library during PaginatorBuilder chaining!

Solved issues:

• Issue #22

Changelist:

• It's now possible to whitelist guild IDs for Emote lookup (has no effect when CacheFlag.EMOTE is enabled).
• Added option to delete messages on button handler removal.
• Added direct activation to PaginatorBuilder chaining.
• Removed unnecessary JDK 1.8 leftover declarations.

Pagination Utils 2.1.6 - Yet another private channel fix

Fixed silent failures when checking if event is locked or not in a private channel, as well as some probable minor issues.

Solved issues:

• Issue #21

Changelist

• Added a proper channel check to isLocked method, now it no longer fails when retrieving channel ID.
• Added null assignators to timeouts, there was a weird issue where timeouts would complete even when cancelled.

Pagination Utils 2.1.5 - Ratelimits fix

Solved an issue regarding constantly reaching Discord's ratelimits when retrieving Emotes.

Changelist:

• Added a small cache to store Emote-Guild relationships to prevent the need to constantly loop over each Guild looking for an Emote (stores only Strings, not full Objects).

Pagination Utils 2.1.4 - Who needs cache anyway?

Removed remaining cache dependencies, now everything should work in both cached and cache-less clients.

Solved issues:

• Issue #19

Changelist:

• Created an utility method to solve the issue regarding cache-less clients.

Pagination Utils 2.1.3 - Some hotfixes

Fixed some issues reported from the last release, as well as potential future failures.

Implemented features:

• Feature #18

Solved issues:

• Issue #17

Changelist:

• All BiConsumer have been changed to ThrowingBiConsumer, which will now print RuntimeExceptions to JDA's current logger (may affect those who define buttons in a variable since signature will change from Map<String, BiConsumer<Member, Message>> to Map<String, ThrowingBiConsumer<Member, Message>>).
• Un-silenced reaction removal-related try-catches, now they'll be thrown normally.
• Removed complete() calls and replaced with submit().get().

Pagination Utils 2.1.2 - Custom Emotes fix

Small patch to fix issues regarding custom emotes usage in non-buttonization methods.
For this, Emote configuration has been standardized to ID-only to preventing confusion when building Paginator object or using buttonize method.

Solved issues:

• Issue #13
• Issue #14

Changelist:

• PaginatorBuilder.setEmote() will now take either an unicode or Emote ID (will throw an exception otherwise).

Pagination Utils 2.1.1 - Let there be customizations

Adopted a new way to activate the library, which now allows more customization by the developer (aka you).
That also means the previous method is now deprecated and, while it's still working and present in this version, it'll be removed on the next major version, so I recommend using the new method.

Implemented features:

• Feature #11

Solved issues:

• Issue #9

Changelist:

• Added new Pages.activate() method that takes a Paginator as argument. The Paginator object can be constructed with PaginatorBuilder factory, which allows tweaking of some setting (will have more options futurely).
• Now it's possible to toggle "remove on click" behaviour of the buttons (turning it off will remove MESSAGE_MANAGE permission dependency).
• All default buttons are now customizable through PaginatorBuilder.
• Added a ton of new javadocs for better documentation.

Pagination Utils 2.0.0 - Sharding support

Added support for ShardManager usage as event handler, and enhanced JavaDocs for better explanation.

WARNING: This version may introduce breaking changes from version 1.x.x to 2.0.0, make sure to double check all usages.

Pagination Utils 1.3.0 - The Emperor's New Clothes

Added missing pagination method and fixed some logic errors (which optimized a bit the code). This, however, also removed some exception supressing, so you might notice that the library no longer blocks common JDA throwables such as ErrorResponseException or PermissionException, which were previously filtered and, in most of the cases, completely ignored.

Implemented features:

• Feature #4

Solved issues:

• Issue #5

Changelist:

• Added a skip-less paginate method with canInteract argument;
• Changed all .queue() calls with .submit();
• Updated JDA dependency to latest version (no breaking changes);
• Changed general EventManager structure;

Pagination Utils 1.2.5b - onCancel action

Buttonize method now has a variant with an onCancel action, this allows better management of validations and broader confirmation messages interactions.