Granadilla Update

Enclosed is a hotfix for the previous release of Quests, which made finishing some objectives difficult. In other news, condition messages will now be sent to the action bar instead of chat, the frequency of which can still be modified with the condition-inverval config setting.

Fig Update

Quests-Bungee is no longer required for MySQL player data on Bungeecord servers; you may delete the jar.

Since this project's inception, the Quest Journal (/quests journal) has been a physical item that lived in your player's inventory. Going forward, the command will open a book without taking up any space, through the power of Bookapi. If you still prefer an item, however, simply toggle the new give-journal-item config setting.

Elderberry Update

Updating is highly recommended due to an issue with loading player data in the previous release. Quests-Bungee has also been updated for those using MySQL on their BungeeCord servers. Administrators can now elect to spawn multiple entities at once using the Action Editor (/quests actions).

Durian Update

BungeeCord servers can now use MySQL for player data through Quests-Bungee. After installing Quests on your Spigot/Paper server(s), simply download the Quests-Bungee jar and place it in your BungeeCord server's plugin folder. The jar has no other functionality at this time. In other news, we have restored titles on 1.8 servers and fixed an issue where clicking certain quest names in the editor could result in the user being kicked.

Cantaloupe Update

Last time, we hinted at some new changes coming to Quests. One such change is included in this version: tab completion for commands (where applicable). We've also packaged the usual bug fixes along with some language corrections. Visit us on Crowdin if you'd like to contribute a few translations to your favorite locale.

Blueberry Update

For this update, we included support for newer versions of Denizen, as well as party support for SimpleClans when using Unite. Groundwork has been laid for some exciting changes ahead, in addition to the usual handful of bug fixes. Don't forget to report any issues on Github.

Apricot Update

As we observe the Lunar New Year, please take a moment to read about these important changes.

Users: This update contains some changes which might break how other resources interact with Quests. If you experience an incompatibility with another plugin or module, please report this to the other resource's author as well as on our Github issue tracker.

The ask-confirmation config setting has been replaced with confirm-accept (same behavior) and confirm-abandon (ask confirmation on quit). A new condition-inverval setting has been added for timing of Condition notifications (must be within 3 and 180 seconds).

Developers: In our last update, we informed you of a new artifact ID when using build tools like Maven. In addition to quests-api, you might also need to depend on quests-core for this version of Quests. Our goal is for this second dependency to be temporary as we attempt to maintain some backwards compatibility until the next major release.

Yuletide Update

This yuletide season, we present you with full Minecraft 1.18 support. Developers should take care to use the new module artifact ID if depending on this release with a build tool like Maven.

Xenial Update

Since we sailed away from Minecraft 1.7 support in our previous update, this opens many possibilities for Quests. We hope to add a number of xenial changes for your visitors - the first addition by @datatags is that most prompt text is now clickable, including "Yes / No" to accept a quest. Please note that Spigot objects are required, meaning that you can't use plain ol' Bukkit anymore!

Withdraw Update

After six and a half years, this is the last update before we withdraw support for Minecraft 1.7.9 - 1.7.10 versions. To the 0.2% of servers this affects (according to bStats), we thank you for choosing Quests. Your throwback Cauldron server may continue to use Quests 4.1.1 as long as your heart desires.

This release corrects an issue when first generating the MySQL structure for player data, then attempting to set multiple targets for certain objectives. Specifically, the quests_player_questdata table should have the mobs_killed, mobs_tamed, sheep_sheared, and custom_counts columns be of data type VARCHAR(100) instead of INT.