Affected version
CommandPrompterPaper 3.1.1 and the current development branch (5534104).
Description
Freshly generated prompt-config.yml uses DEFAULT for TextPrompt.Response-Listener-Priority, but Bukkit has no EventPriority.DEFAULT value.
Steps to reproduce
- Generate a fresh
prompt-config.yml.
- Leave
Response-Listener-Priority: DEFAULT unchanged.
- Start the plugin with debug logging or inspect the registered fallback Chat listener priority.
Expected behavior
The generated default is a valid Bukkit priority and is registered as documented.
Actual behavior
EventPriority.valueOf("DEFAULT") fails and ChatPromptListener silently falls back to LOWEST.
Technical cause
PromptConfig both emits and lists DEFAULT as valid (PromptConfig.java:330-337), while ChatPromptListener.java:57-63 parses Bukkit's enum and catches the invalid value.
Suggested direction
Use a real default such as NORMAL or LOWEST, remove DEFAULT from the generated valid-values comment, and migrate or warn on existing invalid values.
Affected version
CommandPrompterPaper 3.1.1 and the current
developmentbranch (5534104).Description
Freshly generated
prompt-config.ymlusesDEFAULTforTextPrompt.Response-Listener-Priority, but Bukkit has noEventPriority.DEFAULTvalue.Steps to reproduce
prompt-config.yml.Response-Listener-Priority: DEFAULTunchanged.Expected behavior
The generated default is a valid Bukkit priority and is registered as documented.
Actual behavior
EventPriority.valueOf("DEFAULT")fails andChatPromptListenersilently falls back toLOWEST.Technical cause
PromptConfigboth emits and listsDEFAULTas valid (PromptConfig.java:330-337), whileChatPromptListener.java:57-63parses Bukkit's enum and catches the invalid value.Suggested direction
Use a real default such as
NORMALorLOWEST, removeDEFAULTfrom the generated valid-values comment, and migrate or warn on existing invalid values.