[Feature Request] Command aliases #707
Comments
|
More command aliases are coming in the rewrite, please stop creating issues I already know. |
How can I understand what is coming in the rewrite when it is not documented anywhere?
So, don't suggest features? That sounds counterintuitive? All the issues I have opened are new feature requests anyway |
The rewrite is nowhere finished to be stable in production, so documentation doesn't exist, it'll exist once it's in production right now.
I'm not saying stop suggesting features, I'm saying stop creating issues that me or other developers know / are well known that need to be fixed.
All the issues you have created (#708 & #704 are exceptions) are well known issues I already know and hold off or planned in the next version. |
Look, I don't want to fight about this, continuing development on a bot that archives the same thing is redundant and a waste of my time, but I am unsure of how you wish for me to know what is planned. The other two issues are #707 and #705. Just to ensure I have not missed anything, I reread all the issues. I could not find one that mentioned the questions raised in #705 and #707, so it is unclear to me what features you guys have thought up internally and what are new suggestions :), I hope I am not missing something obvious. If so, do point me in the correct direction |
To make it easier to come from other bots. This is a list of aliases I have thought of
prune:purgeban --soft:softbanwarn:pointwarnings:points,checkpointscheckwarningsThe text was updated successfully, but these errors were encountered: