NotQuests

This release rebuilds the entire command system on Paper's native command API and removes the third-party Cloud framework completely which doesn't seem to be actively maintained anymore. This should allow notquests to be updated to newer minecraft versions quicker.

✨ New features

• New FeedMobs objective. Counts how many times a player feeds a particular mob - wheat to a cow, seeds to a chicken, and so on
• Helpful command menus are back. Typing an incomplete admin command - /qa actions, /qa edit <quest> objectives, /qa conditions, … - now lists the available sub-commands instead of Minecraft's blunt "Unknown or incomplete command" error.

⌨️ A rebuilt command system

• No more Cloud. The command framework has been migrated entirely off the third-party Cloud library onto Paper's native Brigadier command API, behind a small in-house wrapper. They're the same commands you already know, just one fewer dependency that can break on an update.
• A more useful hint bar. The "what to type next" helper above your hotbar now shows the actual argument it wants - [TagName], [Block], [amount] - instead of a generic, sometimes-wrong label, and no longer renders a double /.
• Cleaner tab-completion. Suggestion lists are no longer cluttered by single-letter sub-command aliases or by an unselectable <Enter String> entry when real values (blocks, tags, …) are available.
• Flag values complete correctly. After typing flags that need a value - for example --delay or --player — tab-completion now suggests the value for that flag instead of suggesting --delay / --player again.

🐛 Bug Fixes

• GiveItem rewards and item objectives parse correctly. … rewards add GiveItem grass_block 1 no longer fails with "Cannot parse item argument" - the item argument no longer swallows the amount that follows it. Comma-separated material lists work again too, unquoted: … GiveItem grass_block,dirt 1.
• Your tags are suggested again. Adding a tag-based action or condition (TagInteger, TagString, …) now tab-completes your existing tags instead of only offering <Enter String>.
• Boolean values are suggested where you expect them. Commands like /qa conditions check Flying equals <value> now suggest true and false for the final value.
• Conversation NPC lists are readable. /qa conversations list now shows attached NPCs as labels like citizens:5 (Guard Captain) instead of dumping a raw Java-style object string.
• Number variables that take more than one value work. RandomNumberBetweenRange <min> <max>, block coordinates, and similar no longer have the first number eat the rest of the line.
• Checking a Block variable no longer errors. /qa variables check Block <world> <x> <y> <z> returned a NullPointerException because the y and z coordinates were mis-registered; it now returns the block at that position.
• Commands with two value-flags behave. When a flag's value is omitted (e.g. --min --max 3), the parser no longer mistakes the next flag for the missing value and silently drops it.
• Category display names can contain spaces again — /qa categories edit <category> displayName set Some Long Name - matching how quest display names already worked.

🛡️ Reliability

• Bad version-specific config values no longer crash loading. If a config contains a particle or item name that does not exist on this server version, NotQuests now logs a concise warning and falls back to a safe default instead of failing with a raw enum/config error. This covers general particle settings, GUI item materials, quest/category item stacks, and saved item-selection data.
• The bundled demo conversation no longer uses delays. The sample conversation now avoids delay settings

🛠️ Under the hood

• A real end-to-end command test now runs in CI. Every push boots an actual Paper server with the freshly built plugin and runs every registered objective, action, condition, trigger and tag type through the console, failing the build on error. This caught several of the fixes in this release.

✅ Compatibility

Built for Paper 26.1.2 and Java 25.