▶ Quests ◀ | Set up goals for players! 2.6.4

Allow your players to do quests with a GUI selector

  1. LMBishop
    Native Minecraft Version:
    1.14
    Tested Minecraft Versions:
    • 1.14
    Source Code:
    https://github.com/LMBishop/Quests
    Contributors:
    Reinatix, ToastedCoconut, nicuch
    Sponsored by:
    [​IMG]
    [​IMG]

    [​IMG]
    This plugin was built and programmed against the 1.14 API. This plugin was tested on a Spigot server running 1.15.1.
    If this plugin is native to a version pre-1.13, it will not natively support 1.13+ blocks and items.
    Code (Text):
    VERSION   COMPATIBLE
    1.15.x    Yes (T)
    1.14.x    Yes (A)
    1.13.x    No
    1.12.x    No
    1.11.x    No
    1.10.x    No
    1.9.x     No
    1.8.x     No
    1.7.x     No

    KEY:
    * = the plugin is VERY LIKELY to work, but not confirmed
    # = the plugin has reduced features
    A = native version
    T = tested
    Please note: if your version is not listed and the latest version listed is compatible, the plugin is likely to work, but not confirmed.

    [​IMG]
    Quests is full of features for you to play with, you can create any type of quest you need. Each quest can have multiple tasks, which the player must complete before the quest is complete. The player can be rewarded for completing the quests, giving the player something to work towards. All of this and the below for free, forever!
    • A complex quest system.
    • Many* different task types to choose from (14+ - click here).
    • A quest GUI.
    • Categories.
    • Requirements for quests (set up quest stages etc).
    • Cooldowns for quests.
    • Very customisable.
    • Developer API (custom task types etc).
    *during the beta, some task types may not be functional.

    [​IMG]
    • /quests [or /q] - opens quest GUI
    • /quests help - view help screen for quests commands
    • /quests q/quest <questid> - start quest directly by ID.
    • /quests c/category <categoryid> - Open category directly by ID.
    • /quests a/admin - view help for admins
      • /quests a/admin opengui - view help for opengui
        • /quests a/admin opengui q/quest <player> - forcefully open quests GUI for player (bypassing quests.command permission)
        • /quests a/admin opengui c/category <player> <categoryid> - forcefully open category by ID for player (bypassing quests.command permission)
        • These commands are useful for command NPCs.
      • /quests a/admin moddata - view help for quest progression
        • /quests a/admin moddata fullreset <player> - fully clear a players data file
        • /quests a/admin moddata reset <player> <questid> - clear a players data for a specifc quest
        • /quests a/admin moddata start <player> <questid> - start a quest for a player
        • /quests a/admin moddata complete <player> <questid> - complete a quest for a player
        • These commands modify quest progress for players. Use them cautiously. Changes are irreversible.
      • /quests a/admin types [type] - view activated task types, and information on a specific one.
      • /quests a/admin reload - reload Quests.
      • /quests a/admin update - check for updates.
    [​IMG]
    • quests.command - permission for base /quests commands
    • quests.admin - permission for /quests admin commands and update notifications.
    [​IMG]

    GitHub
    https://github.com/LMBishop/Quests

    Please make sure you are using Java 8. Install this on your server by adding the downloaded file to the /plugins folder. Make sure to RESTART the server (do not reload!) and Quests should load.

    Default configuration:
    See: this page

    Creating a quest:
    See: this page

    Allowed task types:
    See: this page

    Set up instructons for task types:
    See: this page

    Video Guides



    These guides are unofficial and may not be up to date.

    [​IMG]
    Quests has been using bStats to keep data about how the plugin is used. This data is anonymously sent and has no way to be traced back to you. Metrics can be disabled by disabling it in the bStats configuration.

    Quests has been using bStats to keep data since version 2.0.0-beta. Metrics data can be found here: https://bstats.org/plugin/bukkit/Quests

    [​IMG]
    You can contribute to the project by contributing code to the public repository. If you are contributing code, you also agree that you grant us the rights to your code.

    The source code can be found here: https://github.com/LMBishop/Quests

    [​IMG]
    [​IMG] [​IMG] [​IMG] [​IMG] [​IMG] [​IMG]
    [​IMG]
    Bl3ndXDXD, xryus, caio174875 and 17 others like this.

Recent Updates

  1. Data loss fix
  2. Fix data loss
  3. Fishing task type fixed

Recent Reviews

  1. edude0
    edude0
    5/5,
    Version: 2.6.3
    To everyone using this plugin or thinking of downloading it, use version 2.6.2 - the latest version, 2.6.3, fixes auto-quest start data loss, but BREAKS all the rest of the quest data loss, so all the quests get reset every server restart. 2.6.2 is extremely stable and has no bugs besides the auto-start quests, which doesn't even need to be used.
  2. Dito
    Dito
    2/5,
    Version: 2.6.3
    this is very good plugin but when player left game player quest restart why ? please help me i will rate you five star
  3. emrhnnaydnn
    emrhnnaydnn
    4/5,
    Version: 2.6.3
    ___________________________________________

    I'm sorry it only supports 1.14 and above :(

    ___________________________________________
  4. LordYarkan
    LordYarkan
    4/5,
    Version: 2.6.2
    The plugin is very good, but this option is interesting :).
    daily-quests:
    enable soon please :(

    And add an option of
    per-world: "to enable in certain worlds"
    Having this you deserve the 5 stars
  5. MoonSoD
    MoonSoD
    5/5,
    Version: 2.6.2
    Been using it for the past month on a production server, 40 - 50 players on a single spigot server 1.15.1. No problems with it so far, there was a bug, which got fixed after I submitted an issue on GitHub. Really light on the server, absolutely simple to configure but I would like some advanced configuration options. Great for a free resource!
  6. kamalsingh
    kamalsingh
    5/5,
    Version: 2.6.1
    Using this plugin for the past 2 years and its working without any issues. One of the best plugin for adding quests feature to any type of server...
    Author is an awesome person, He added my suggestions i did on discord. Awesome support...
  7. CombatWiZ
    CombatWiZ
    4/5,
    Version: 2.6
    This plugin would be perfect. However, response on the Discord is non-existent. As I have a question concerning natural block placements aligning with mining type quests. Players can use silk touch to just place and break blocks.
  8. MeerBiene
    MeerBiene
    5/5,
    Version: 2.6
    if you have more than 1 braincell left this is the plugin for you. Its just out of the box plug and play, the example quests are detailled and tell you exactly what to change in the config, 10/10 would buy again
  9. Milky7777
    Milky7777
    1/5,
    Version: 2.6
    The plugin doesn't support a lot of quest types and also the new versions doesn't worth anything because it is only 1.14 based, while I tried it and it is unstable atm.
  10. Superalex0102
    Superalex0102
    1/5,
    Version: 2.6
    It is a good plugin, but has a lot of deficiency, and now also support for the rest of the versions are removed. I'm using 1.13 and it doesn't make sense to remove the last version of the latest version. 1.14 spigot still has plenty of bugs, performance issues and I'm not the only one who says this. And also if you check https://bstats.org/plugin/bukkit/Quests only 28% are using 1.14, where as even 1.8 has more usage over the plugin and 1.12.2 is 24%. Think about this. Thanks.
    1. LMBishop
      Author's Response
      1.13 is possible however i have already made the decision to absolutely leave versions pre-1.13 behind due to drastic changes in the api. 1.13 is 15 months old, 1.14 is 6 months old, 1.8 is 61 months old, i can’t have support for versions pre-1.13 without losing the ability of having 1.13/4 blocks due to the changes that happened in the api