Create a subcommand for /queue called /queue status. This command can be called by a player when they are in a queue to get information regarding the queue.
What to include:
- What queue the player is actually in
- How many total players are in the queue and how many players are needed
- A click action to leave (can be done in minimessages)
Message mockup
Minimessage Markup
Success state
<#585b70>[<gradient:#cba6f7:#585b70>Brawl</gradient><#585b70>]<reset> <#e8edff>There (is|are) currently <#8bd5ff>3<#e8edff> players in the queue for Payload<newline><#a6e3a1>[Click] to leave the queue
Error state
<#585b70>[<gradient:#cba6f7:#585b70>Brawl</gradient><#585b70>]<reset> <#ed8796>You are not in a queue so no status can be retrieved
Subtasks
- Create a path in lang service
t() function to handle pluralization of words. Make a clean api for both the markup in the en.yml file and how to actually denote what value will drive the plural in the t() function builder.
- Future state when parties are implemented: we could show the names of the other players in the player's party somewhere in the status report. ex: "You, Fred and Bob are in the queue for NAME, there are 5 total players and 10 are needed to start"
Create a subcommand for
/queuecalled/queue status. This command can be called by a player when they are in a queue to get information regarding the queue.What to include:
Message mockup
Minimessage Markup
Success state
Error state
Subtasks
t()function to handle pluralization of words. Make a clean api for both the markup in theen.ymlfile and how to actually denote what value will drive the plural in thet()function builder.