Similar to [/message queuemessage sticky] and [/message winnermessage sticky], voting menus such as Ready Up, Map, and Hero should also have the option to have the message stick to the bottom of the channel. Very helpful as voting menus get pushed up whenever there's multiple people speaking in the queue channel.
Current queues force all map bans to happen at the beginning of a best-of-N series. This causes issues as players must ban maps before they even know which game mode they are playing. Banning a map for a mode that never gets picked defeats the purpose of the ban phase. I suggest adding an option to split the voting process into separate rounds for each game. For every game in a series, the flow should go from mode selection, to map bans for that specific mode, and lastly the map vote. For example, a best-of-3 series would repeat this cycle 3 times. In game #1, players pick the mode, they are given N map bans per team, and vote on the remaining maps. Game #2 and #3 would follow the same flow. A fallback should trigger if the chosen number of bans ever exceeds the available map pool.
Create a new system of queue priorities or fix the partys - The partys now have full priority, doesnt matter if players have 100 priority value, partys will take their place, would be alot helpful if it has a way to let partys players join queue instead of just dont let them join when some positions are full, and let players who wave priority values take the place of partys players (or at least create an option to enable/disable it), i already know about the party prevent overfill, but the problem its the worst way to dont let partys replace the other ppl, let party join queue but dont replace players, and add a way to players with priority really have priority :pray:
Players often flood the newly created channel/thread, effectively burying voting menus and forcing other players to scroll up to find them. A command like [/tempchannels slowmode (duration)] can help keep the channel spam-free while still allowing players to share important information like private lobby codes.
I run a 6v6 server and currently my players have to manually vote captains for the team selection process. It would be great if the bot could automatically assign captains based on their role in the queue rather than through Discord roles. The reason I want to avoid Discord roles is because multiple people have the same roles so the command that is similar to what I’m asking doesn’t work properly, using queue position would make this consistent and significantly speed up the queue process. (Ex. The game I run is volleyball and there is always 2 setters and I just want whoever is in that role in the queue to be the captain when the queue starts
When the /player ban command is used, it would be great if the bot automatically assigned a configurable Discord role to the banned player (e.g., a “Queue Ban” role). Once their ban duration has expired, it would also be helpful if the bot sent them a direct message notifying them that their ban has been lifted.
If a party exceeds the maximum average MMR, then they are unable to party together. This may help limit top players in the server teaming and "smurfing" against others in the queue.ex. Set a party MMR average limit of 1000 MMR- Player 1 has 1600 MMR & Player 2 has 1200 MMR, since the average Party MMR is 1400 then they can't party together
It would be nice like what you have in your server with the count of most queues most daily games etc. to have it somewhat transformed to have it within your own queue like have daily players, queues played just stuff that would be good info to have
After a queue pops and teams are created, allow for 1 mutually agreed upon trade to further balance teams. This works especially well in situations where you opt for automatic teams balanced by MMR but also takes into consideration new players that might be overinflated or for servers of mixed skills where players might be under ranked with their MMR relative to their true skill.
Put the user's name who initiated the vote, onto the embed after someone runs /cancel
I would like to see a timed queue lock, so that it automatically unlocks the queue and allows players to join queue after a certain amount of time
I would love to see an addition of the ability to export your configs to a text file, make changes to the text file, then import the changes back. The intent behind this is that if I need to make multiple queues with different configurations, making the changes on the text file, then importing it would be much easier to do and see. The current method involves using the templates and then I have to run each command that I want toi change the setting for, then check info each time to see if everything applied. With the config file, I can change it before the queue goes live all in one go. The saved templates are fine, but i prefer to use the template this way. I dont expect a whole lot of people to use this method, but I also dont think I would be the only one who would like this.
I would like to see a feature for updating your saved templates. For the updating templates, I just want to be able to update my templates. The easiest example I have is if I have a template with specific map choices, any person I share my template with will only have those map choices. If the map choices change due to preference or the game itself no longer offers certain maps, anyone I share the template with will need to make those changes to remove the maps that are no longer available. I dont know where the templates are stored, but I would imagine they are stored on a file share that can fill up. I think an update feature could possibly relieve that potential future issue as well.
Just like for leaderboard, add a "Export to CSV" Ui element to the discord bot or website for the specified match history, with date ranges as well.
When a player joins the queue and the bot auto pings, you can only have it ping at a certain entry (for example the first person that queues). Add the ability to auto ping at various entries (for example, when a player first joins a queue and another instance when only 1 player is required to start the lobby. In a 3v3 matchmaking, this would be at the 5th player queueing).
When you have an uneven distribution of roles in a queue, the bot should default to using MMR as a secondary method for balancing. For example, if you have 4 bronze players and 2 plat players, each team gets 1 plat player and 2 bronze players. However, if you have 3 of each, you can only do 1 bronze player and 2 plat players and 2 bronze players and 1 plat player. In this case, the bot should look at the MMR of the players and balance it accordingly. So the two bronze players would receive the plat player with the highest MMR.
Welcome You can take a look at what we're working on here. We want to hear your feedback! Drop a vote, leave a comment, or post a suggestion below. Thanks, Team NeatQueue Hub