🎨 Customization

GUI items

You can customize the items displayed in the GUI for both categories (default: Chest) and quests (default: book). For quests, use /qa/qaAdmin commands for NotQuests editeditOpens subcommands for editing a specific quest. <quest><quest>Identifier of the quest to edit; use /qa list to see available quests.Acceptsquest name guiItemguiItemShows or changes the item displayed in GUIs. <material><material>Material of item displayed in the Quest take GUI.Acceptsmaterial, custom item, hand, any, or comma-separated materials. For categories, use /qa/qaAdmin commands for NotQuests categoriescategoriesManages quest categories. editeditOpens subcommands for editing a quest category. <category><category>Category to editAcceptscategory name guiItemguiItemShows or changes the item displayed in GUIs. <material><material>Material of item displayed in the category GUI.Acceptsmaterial, custom item, hand, any, or comma-separated materials.

Advanced items (e.g. custom model data)

NotQuests supports any items - even the most complex one. This includes special items from other plugins! Internally, notquests uses the Bukkit Item Serialization API, so notquests supports anything that supports that.

Do you have any item which is complex like that (so not just a material)? Then hold the item in your hand and use 'hand' as material name. E.g. if you want your super fancy enchanted custom model data item to be displayed in the GUI for a category, hold it in your hand and use /qa/qaAdmin commands for NotQuests categoriescategoriesManages quest categories. editeditOpens subcommands for editing a quest category. categoryName<category>Category to editAcceptscategory nameExamplecategoryName guiItemguiItemShows or changes the item displayed in GUIs. hand<material>Material of item displayed in the category GUI.Acceptsmaterial, custom item, hand, any, or comma-separated materialsExamplehand. That easy!

Translations

You can edit most strings and translations in notquests (currently not all of them, but the most important ones). This can be done in the "languages" folder of notquests

Customize the entire GUI

Every GUI lives as its own editable .yml file in the plugins/NotQuests/guis/ folder. In there you can rearrange the whole layout, swap materials and move buttons around — the structure: lines are a little visual map of the slots, and the icons: / items: sections define what goes in them.

The text shown in a GUI (titles, button names and lore) comes from your language file in the languages/ folder instead. So: layout lives in guis/, wording lives in languages/. Which GUI files get used is set by gui.main-gui-name and gui.npc-gui-name in general.yml.

Color codes

Colors are supported basically everywhere in notquests - but not the legacy ones you used to know. Stuff like &6 or &c won't bring you far - it has long been abandoned by Mojang & kept alive by Spigot - as NotQuests thrives to be as modern and innovating as possible, it abandoned those too.

Instead, we are now using MiniMessage, which allows you to do even more advanced stuff easier, like RGB colors, gradients, and even click commands & hover messages! You can find the MiniMessage docs here.

Let's start by giving our quest a colorful display name:

/qa/qaAdmin commands for NotQuests editeditOpens subcommands for editing a specific quest. TheVirus<quest>Identifier of the quest to edit; use /qa list to see available quests.Acceptsquest nameExampleTheVirus displayNamedisplayNameQuest display name shown in quest lists, quest previews, GUIs, and chat messages. Supports MiniMessage formatting. setsetSets the selected quest's display name shown in GUIs, previews, and chat. <red>A <bold>Deadly</bold> <#eb34a1>Virus<display-name>New quest display name. Supports spaces and MiniMessage formatting.Acceptstext

Or even:

/qa/qaAdmin commands for NotQuests editeditOpens subcommands for editing a specific quest. TheVirus<quest>Identifier of the quest to edit; use /qa list to see available quests.Acceptsquest nameExampleTheVirus displayNamedisplayNameQuest display name shown in quest lists, quest previews, GUIs, and chat messages. Supports MiniMessage formatting. setsetSets the selected quest's display name shown in GUIs, previews, and chat. <rainbow>A <bold>Deadly</bold></rainbow> <gradient:#eb34a1:#ffffff>Virus</gradient><display-name>New quest display name. Supports spaces and MiniMessage formatting.Acceptstext

Pretty cool, right? You even have auto-completions for all MiniMessage color tags for many commands. At the same time, NotQuests has added some internal colors which you can use to achieve a consistent look. For example <highlight>, <highlight2> or <main>. Those can be customize inside of the config, to change NotQuests entire color scheme.

Example: clickable link in the description of your first objective of a quest:

/qa/qaAdmin commands for NotQuests editeditOpens subcommands for editing a specific quest. yourquestname<quest>Identifier of the quest to edit; use /qa list to see available quests.Acceptsquest nameExampleyourquestname objectivesobjectivesManages objectives on this quest or parent objective. editeditOpens subcommands for editing a specific objective on the selected quest. 1<objectiveId>Objective ID shown by this quest's objectives list.Acceptsobjective idExample1 descriptiondescriptionObjective description shown in objective lists, progress output, and GUIs. Supports MiniMessage formatting. setsetSets the selected objective's description text. <click:OPEN_URL:yoururllink>Click here</click><Objective Description>Task text shown to players for this objective. Supports spaces and MiniMessage formatting.Acceptstext