The real issue is that you used a patched client that gave you an advantage over other players and now you can't use it.
'); document.write(''); var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = false; } else // Load Rest of YUI remotely (where possible) { var yuipath = 'https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build'; var yuicombopath = ''; var remoteyui = true; if (!yuicombopath) { document.write(''); } } var SESSIONURL = ""; var SECURITYTOKEN = "guest"; var IMGDIR_MISC = "warmane/misc"; var IMGDIR_BUTTON = "warmane/buttons"; var vb_disable_ajax = parseInt("0", 10); var SIMPLEVERSION = "422"; var BBURL = "https://forum.warmane.com"; var LOGGEDIN = 0 > 0 ? true : false; var THIS_SCRIPT = "showthread"; var RELPATH = "showthread.php?p=3264496"; var PATHS = { forum : "", cms : "", blog : "" }; var AJAXBASEURL = "https://forum.warmane.com/"; var CoTTooltips = { rename: true, icons: false, iconsize: 15, qualitycolor: true, overridecolor: { spells: '#839309', items: '', npcs: '#fff', objects: '#fff', quests: '#ffb100', achievements: '#fff' } }; // -->
The real issue is that you used a patched client that gave you an advantage over other players and now you can't use it.
Not necessarily. The "Amazing" thing can be used for legitimate quality-of-life improvements. Problem is, in a simplified way, the things it gives access to (which are meant to be out of reach for add-ons) can also be used to say, make a name tag appear on someone in stealth, and there's no way to distinguish these uses. There's no allowing "good" uses and barring "bad" ones, it's an all-or-nothing deal, and unfortunately fair play takes precedence.
Why dont u make your own patch then?
I spent weeks if not months polishing my UI (its fully open source including SavedVariables on top of it) to be compatible with the new API just for it to be banned out of nowhere leaving me with a d*ck in my hand... Theres absolutely no way I am going to do that once again just to be able to play in the first place. I rather stop playing on this server entirely...
According to the issue addons give advantages over other players, who don't have healbot, omni cc, weakauras, gladius and quartz. It's gotta be time to ban all dat **** off and play a game the way it was created for! No raid health frames for healers, no numbers on cooldowns, only manual buff and cooldowns tracking, only hardcore!
UPD: oh, how could i forget that - multiboxers! Isn't it's time to fix this plague yet? Aren't they accidently get any "advantages" over other players? Does anyone love this, besides mbx of course? Looks like they are annoying both for enemies and teammates - oneshot when you playing versus them and waste of slot by HK farmer instead of victory purposes for teammates (just watch that 5 dots at the middle of the WG or BG map, and yes - not only the 40ppl bgs). But this is absolutely fine - who cares about that 4 fully automatic applications, right? But awesomewotlk is another deal, feel the difference and don't confuse!
Edited: September 24, 2025
Read my post again. This has nothing to do with who makes it.
If players want to go look for the developer, go ahead. I can't see our Staff doing that. But the "solution" would be removing all functionality that allows add-ons to do things they aren't meant to. I don't know how much would be left of it without that.
This was a decent explanation. Thank you.
Warmane just needs to remain transparent. It is very discouraging, though, that the solution is to be restricted to the warmane client, which is the easy way to solve the situation, with players losing in their overwall experience with the server prohibitting using updated clients that give you a much better experience, aesthetically.
For the... I don't even know what time it is now... people can still use HD patches just fine. They just have to do it manually following some guide, instead of using a modified client with other stuff along. If by "better aesthetic experience" you mean from using game functions add-ons shouldn't be able to use anyway, though, oh well I suppose, we can't just let exploits be because of "aesthetics."
This also has nothing to with with "easy way to solve it," as you should know by reading the post you quoted and complimented. This is a binary situation, it's either yes or no, there's no way to control or separate how something is being used, so either all uses are allowed, including the cheating ones, or none is, and it's unfortunately obvious which one we have to do.
Dude theres a 20 years old exploit thats BUILT IN inside the client by default (which makes it pretty much undetectable server-side, so outside of using a custom client, you are not going to do anything against cheaters) and everyone and their mum abuses it since the beginning of time.
Yet nameplate API, that adds guids to nameplates so that you dont have to handle each nameplate function using UIParent or some other monstrosity that tanks your FPS, is the real evil here, yea sure...
Yes, awesomewotlk was abusable by bad actors, it opened a plethora of new cheating angles. But as long as you use the old client, ppl will cheat regardless and theres nothing you can do about it. Just ban the bad actors and move on... on TBC there wasnt a single issue with it. On WOTLK everyone and their mum cheats, scripts and AHKs anyways so it doesnt matter.
I apologize if any of my wording mislead you and made you feel like this was a debate about whether this would be implemented or not, so let me clarify: it isn't a debate. All I'm doing here is explain what and why, not trying to convince you to agree with our reasons, especially if you're set on thinking otherwise. Even if I was, let me tell you this pseudo-reasoning of "there are other issues, so let this one be" doesn't convince anyone. You don't leave problems you can fix be because there are problems you can't fix, that's not how anything in the world works.
Edited: September 26, 2025
I've been logged out for a couple weeks and logged in today to see this message popping up. Just to clarify, all I have to do is re-download and install the warmane client? I have a ton of add-ons. But I had never had any issues before.
Depends on what's causing it. If you just use the "Amazing" thing, removing the .dll should do it (and break any add-on that use it), as a few players have replied.
I've been using the awesome_wotlk patch for over a year now because it allowed me to make warmane look and feel a lot closer to how WOTLK classic did, mostly due to improved nameplate castbars and being able to attach weakauras to nameplates for aura monitoring rather than using addons such as flyplatebuffs to see what's going on.
I understand that the decision to disallow awesome_wotlk is not up for debate, and that the server's leadership decided this was the only acceptable course of action due to fairplay issues which the patch introduces.
My question is whether the leadership team is open to revisiting their stance down the line if the patch could be modified to restrict any functionalities in breach of your fairplay standards while still allowing for classic-like functionality with the API extensions for weakauras and nameplate castbar improvements people have enjoyed?
I understand that the onus must be on the developer(s) and not Warmane, but are you open to conversation with the developer(s) and is there a possible pathway towards an officially sanctioned 'enhanced Warmane client' that meets your fairplay standards, or do you consider the matter closed?
Thank
Already answered over a week ago. We won't be messing with any clients or releasing "enhanced" versions. Whether the plugin will work with Warmane is entirely up to the developer removing anything that shouldn't be used by a regular player with regular add-ons. But then, again, I'm not sure what you expect to be left. You're already using it because regular add-ons aren't able to do those things, which would be gone.
Edited: October 2, 2025