OK, now I have that post out of the way, let me say a few things about Ore and why closing this thread isn’t necessarily the right thing to do yet.
Ore is going to be a wonderful tool for managing releases. Windy and the team are doing a fantastic job with it so far. By using Ore now, I’m helping test and refine it. I have found bugs and I have suggestions. By commenting on the Ore thread, yes, there is an element of testing there too. But it’s also far from perfect - and I don’t say that to upset anyone, everyone knows there is a lot to do with it yet.
If you look at my Ore thread, you will see that there are lots of posts that are release notes, I spend a lot of time writing them to try to show case what you can do, and how you do it, because that’s really important in the usability of a plugin! However, as well as having huge release notes, you get them twice because I can’t attach two versions to one Ore release, I have to release a 1.10.2 and 1.11.2 version (but there is a ticket open by someone else to change this, thankfully). So whenever I release a feature release, I break the flow considerably, and it just means that things don’t get responded to.
Here, I have control over that, a quick message, and back on my way.
Because of this, the replies inbetween do get lost, and it’s easier to see the flow of the conversation here. Thus, I will keep it open for the time being, but encourage bugs and feature requests to go to GitHub and quick help can be sought from our Discord channel where I am so thankful for the community that’s been so helpful when I’ve just not been there, or in a bad mood!