t is not designed for Raid environment in any way.
sorry you feel that way. many folks approach things differently, and while we try and approach things to be as broad as possible there are still "decisions/choices" that we make - we don't always get the right, even the second time around, but we always do take things into consideration.
this "not designed for raids" thing is pretty obnoxious hearing it thrown around as a slight or a jab because it just isn't true nor is it the whole picture. First and foremost the plugins *are* made/designed with the single boxing person doing group content in mind, that is their primary focus, and this is where the majority of mq users spend their time, so our focus for UX and fun and ease of use and such should be there. Having said that, there are countless of 1-6 irl person teams who run nothing but the cwtn plugins to do all the raids (and have cleared all content with them since CoV), and the large majority of the tweaks, adjustments, changes, additions, functions, and features comes from raid environment specifically. I mention this
> here <. Some things become easy and not untimely to implement - like one of the reasons i've been going back and adding automatic usage of some things like bifold and bps and various useful items for class to class - is folks share their toon and might not have the add clickies on this pc, or that person's pc and we want to help have the smoothest experience possible "out-the-box".
Take MQ2Bst and useLowestProgression that just got added - I *knew* about the reason/issue dince they put in the second progressive ability - dbg just didn't really give the new versions of the abilities much other than the secondary effects (think like hps and ds reduction), but huge mana cost increase. We try and avoid coding around shitty dbg design as much as possible - assuming in good faith they're going to fix their game, because if it is something that drastically bad, then people will submit bug issues and it will get resolved. Unfortunately, people would rather say mq2bst sucks dogshit because it is using a spell that you were *sold* as an expansion feature instead of using one from several years ago. Folks also will get up-in-arms and call flaming sucking dogshit if you don't use the most recent ability - take the amount of PMs/DMs I've gotten about mq2shaman using an older progressive spell because we match their BP for double duration.
My best suggestion is make your case, don't toss dogshit, try to not make assumptions about how/why - because it is probably missing a lot of important context - and cwtn and I can and will do our best to accommodate what we can where we can.
Unfortunately, we very intentionally don't plan on making our plugins an unmaintainable jumble of weird bloated special 1-time things - we want something that is going to be around for as long as mq/rg/eq is around, and hopefully we can continue to add functions and features that are desired/needed.
Please feel free to PM me with any pain points you have and I'm happy to take a look at each of them - more information the better
having said that, the timer2 thing makes good sense, and is now defaulted that we won't use the offensive timer 2 unless you turn it on (and aren't tanking)
tone (and especially mine) can be hard to read online, so if this reads like im upset or anything, i'm totally not, i appreciate you adding to the conversation that this was necessary.