BeautyQuests -----
Quest system with a simple graphical interface. Compatible with SQL databases.How to install:
Placeholders:
%beautyquests_total_amount% to show the total amount of quests
%beautyquests_player_inprogress_amount% to show the amount of quests the player is into
%beautyquests_player_finished_amount% to show the amount of quests the player has finished
%beautyquests_player_finished_total_amount% to show the amount of quests the player has finished, and sums up quests which has been completed multiple times
%beautyquests_started_ordered% to show the advancement of each quest, one after another. You can configure the time to change in the config file.
%beautyquests_advancement_X_raw% to show the advancement of the quest with ID X, but only with the form on one number:
%beautyquests_started_id_list% which returns a list of quests currently in progress for player. The list is an enumeration of IDs, separated with ;
Permissions:
Commands:
/quests or /quests <create|edit|remove|finishAll|resetPlayer|resetPlayerQuest|start|pools|resetPool|seePlayer|setStage|cancel|startDialog|scoreboard|reload|version|list>
Note: please do not use the reload command. It is for debugging purpose only.
How to migrate datas from YAML storage to DB storage
- Download BeautyQuests and put the jar file in your server /plugins folder.
- You can download "stable" version of BeautyQuests by clicking on the blue button, at the top of the page.
- You can also download dev builds with latest experimental features here! Get more informations and constant changelogs on the Discord server.
- Turn on your Minecraft server. Check the console/logs to make sure there are no errors during plugin load.
- Enjoy using /quests create!
- Further configuration (such as language changing or database configuration) can be done by editing the file /plugins/BeautyQuests/config.yml. Make sure to restart your server after saving the file.
Placeholders:
%beautyquests_total_amount% to show the total amount of quests
%beautyquests_player_inprogress_amount% to show the amount of quests the player is into
%beautyquests_player_finished_amount% to show the amount of quests the player has finished
%beautyquests_player_finished_total_amount% to show the amount of quests the player has finished, and sums up quests which has been completed multiple times
%beautyquests_started_ordered% to show the advancement of each quest, one after another. You can configure the time to change in the config file.
%beautyquests_started_ordered_X% to show the advancement of each quest but split into multiple lines
customizable in config.yml
%beautyquests_advancement_X% to show the advancement of the quest with ID
X
customizable in config.yml
%beautyquests_advancement_X_raw% to show the advancement of the quest with ID X, but only with the form on one number:
-1 if the player has not started the quest
-2 if the player is in an ending stage (i.e. in branching)
≥0 the stage ID, if the player is currently doing the quest
%beautyquests_player_quest_finished_X% to show amount of times the quest with ID
X has been finished
-2 if the player is in an ending stage (i.e. in branching)
≥0 the stage ID, if the player is currently doing the quest
%beautyquests_started_id_list% which returns a list of quests currently in progress for player. The list is an enumeration of IDs, separated with ;
Permissions:
beautyquests.*: Gives complete access to BeautyQuests.
beautyquests.start: Gives player permission to start quests.
beautyquests.start.X: Gives player permission to start at most X quests (overrides the maxLaunchedQuests config option ).
beautyquests.command: Gives only access to /quests, but not to the sub-commands.
beautyquests.command.*: Gives access to all sub-commands.
beautyquests.command.[sub-command]: Gives access to a specific sub-command (sub-command: create, edit, ...).
beautyquests.command.listplayer: Gives access to the quest menu ( /quests).
beautyquests.start: Gives player permission to start quests.
beautyquests.start.X: Gives player permission to start at most X quests (overrides the maxLaunchedQuests config option ).
beautyquests.command: Gives only access to /quests, but not to the sub-commands.
beautyquests.command.*: Gives access to all sub-commands.
beautyquests.command.[sub-command]: Gives access to a specific sub-command (sub-command: create, edit, ...).
beautyquests.command.listplayer: Gives access to the quest menu ( /quests).
Commands:
/quests or /quests <create|edit|remove|finishAll|resetPlayer|resetPlayerQuest|start|pools|resetPool|seePlayer|setStage|cancel|startDialog|scoreboard|reload|version|list>
Note: please do not use the reload command. It is for debugging purpose only.
How to migrate datas from YAML storage to DB storage
- In config.yml, set-up the "database" section (see below if it doesn't exist in your file) BUT keep the "enabled" parameter to "false".
- Restart the server and once everything is loaded, use the command /quests migrateDatas (it may take a while, hence it is recommended to disallow players to join during this time).
- If everything is good, you will receive a success message. Turn off your server, set the line "database.enabled" to "true" in config.yml.
- Start your server with BeautyQuests now working on SQL data system!
Resource Information
Author:
----------
Total Downloads:
120,588
First Release:
Apr 11, 2017
Last Update:
Oct 2, 2024
Category:
---------------
All-Time Rating:
Find more info at github.com...
211 ratings
Version
-----
Released:
--------------------
Downloads:
------
Version Rating:
----------------------
-- ratings