Tanked

Not sure if you have any clue where you are, but we are on a vanilla server, vanilla comes right before TBC (the burning crusade) So yes BEFORE TBC is when Battle Shout gave plenty of threat. That is what I am saying. You obviously are either confused, don't understand what I am saying due to a language barrier or something. But get off of my posts please. I am sick of you trying to derail or misinform my posts which are accurate. I have already reported you to the staff. Regardless the bug is that it is NOT PRODUCING THREAT at all. The way it should work here is producing threat 55 times the number of party members buffed plus also pets that are buffed THEN divided on the mobs that are in combat. All you are doing is confiming what I am saying, but saying it as if I am wrong about something. So please buzz off

I am trying to report a bug and when submitting it is giving a 500 internal server error. For the meantime I will post the bug I was initially trying to report in this thread.

This issue still getting buried multiple pages deep. I also have something posted in the contact administrator forum, which has a couple views but still not one response....

@OP Battle Shout is NOT producing ANY threat here whatsoever, DO NOT listen to these idiots and pally tank advocates like Killerduki I am unable to post in the bug tracker due to a 500 internal server error but you can add to what I have put in the support forum. And yes I have tested it in game, it produces exactly 0 threat no matter how many or how little the amount of mobs or number of players/pets buffed. https://forum.elysium-project.org/index.php?showtopic=25797

Bumping again as I am an active bug reporter and cannot post anything due to this 500 internal server error. I will attempt to make an in game ticket today, but my guess is it will be redirected here.

This is why you shouldnt visit those gold selling/powerleveling websites or give your account information to anyone.

Bumping so hopefully staff can see through all of the mess in this forum

Please stop following me around on the forums posting misleading information. In the link you provided as "proof" he doesn't even give accurate or detailed information in regards to this specific issue. I do not want to cause trouble on the forums as I am here to help my fellow community members, hence why I have tested things in game, and done the research, as well as being a very long term wow player and experienced the way this should work first hand on retail servers years ago. Please refrain from posting false or misleading information as this post is intended for the developers here on Elysium to see since the bug tracker is down and to address a serious issue with the warrior class. Unfortunately alot of information has been lost over time, but the fact remains that the way battle shout should have worked and did work between the release and up to just prior to patch 2.0.1 was that it generated alot of threat. The numbers should be accurate of ti generating 55 threat per player or pet buffed and then split amongst the mobs you are fighting. You can read where they nerfed it in patch 2.0.1 (the release of burning crusade) even though it is very general how they describe it in the official patch notes (source: https://web.archive.org/web/20110411211511/http://us.battle.net/wow/en/game/patch-notes/2-0-1 ) They state: Fixed an issue where Warrior "Battle Shout" was causing too much threat. This is where they actually put a flat cap of 50 on the threat that battle shout generated. Prior to this, it worked as I have originally posted in this thread.

Yes it's called getting your domain whitelisted with the major email providers...

UPDATE: I have been able to test this in game today. Battle Shout unfortunately is bugged and not producing any threat generation at all. In addition, trying to add a bug to the tracker is giving a 500 internal server error, so I have temporarily posted it in the help and support section of the forums. Please feel free to comment there as to bring attention to this major bug for warriors https://forum.elysium-project.org/index.php?showtopic=25797

Yes, unfortunately alot of warriors do not know to stance dance. Tanking is extremely easy if you have a decent group and know how to use the appropriate skills. As far as killerduki, nobody is denying the threat is divided amongst the mobs, but learn basic math bud. 55 PER PARTY MEMBER BUFFED, then split that amongst the mobs. SO, if you are tightly packed enough/get all five members (not even counting pets) buffed that is 275. Now take that 275 and you can for example say we have even 6 mobs on you. That's 45.83 threat per mob. even if rounded down to 45, that is still more than the 43 per mob from Demo Shout. The other benefit is Battle Shout doesn't have a range like Demo Shout does. So with 6 or less mobs, Battle Shout clearly outweighs spamming Demo Shout, and the less the better, so on 3 mobs with 5 party members buffed it would put 91.6 threat on each mob. Anyways I am rambling, @Killerduki, you should really not post about things where you cannot even do basic math. @OP the only thing now is to see if Battle Shout works properly here. I was able to finally log on my warrior, but not long enough for any testing. I will report back later today whether it is bugged or not.

I am having an issue with two characters on the PVP realm. Their old names had special characters in them, so they are flagged for rename, yet when I try to rename them, it stays at "renaming character" for about 3-5 minutes, then just says "Character Rename Failed" I have tried this over and over for about half an hour now with no success.

Final UPDATE: Was able to successfully rename my characters after the server population went down a bit in the middle of the night. It seems it was just timing out.

UPDATE: This is still happening and have spoken with over half a dozen other people with the same issue. It may be possible that it is a timeout issue right now, I do hope that is the case.

I played a Prot Warrior back on classic wow, on the retail servers. Prior to patch 2.0.1 Battle Shout WAS a beast for AOE threat generation. You can ask any warrior that played back then. Regardless of what any website says. From my own experience on retail (during classic/vanilla times) Battle Shout was very useful until it was nerfed in 2.0.1, On Nost (before Elysium) it did not work correctly and barely generated any threat if any, also on the old bug tracker here there is a report of it not working correctly. And regardless of numbers or how it was divided, it should generate more threat than spamming Demo Shout. Your statement saying Battle Shout is a useless AOE threat generator tells me you DEFINITELY did not play a prot warrior on the live servers back then.

Confirmed workaround. Just used my smartphone, disconnected from my wifi (same network my pc was getting the error from) so it was going through the cell network (different IP address). Then proceeded to Nost to generate a new token, logged into Elysium and applied the token and worked right away. Thanks again for the discovery Kalpak!

Hold Ctrl and scroll your mousewheel down, it will reduce the size of the stuff on the screen and reveal the button

Hold Ctrl and scroll your mousewheel down lol

The download links are down, but the torrent link on the website is still functional as of now. Just used it about an hour ago.

Yes, on retail or if scripted correctly, Battle Shout is a very effective tool for generating AOE threat, but from my personal experience, on Nost they changed it as if it was like a future patch when it was nerfed. I had tested it many times there and was not working properly as it should in 1.12. and even reported it in their bug tracker with no progress. Hopefully it will function correctly here, as it is a huge help. I will check the bug tracker here to see if there is an issue, otherwise I will be on tomorrow when the realms are ready to go. Still fighting this 500 internal server error trying to get my characters transferred at the moment. EDIT: The old bug tracker has a report of it not generating threat at all, which I am hoping this is from an old core. I will test it as soon as possible. Just for reference: (http://vanilla-wow.wikia.com/wiki/Battle_Shout) Threat generationBefore Patch 2.0.1, Battle Shout generated 55 threat for every party member who received the buff. This made it better than Demoralizing Shout for gathering groups of mobs for AoE. It was also used frequently in Phase 1 of the Nefarian fight in BWL. However, as of patch 2.0.1, Battle Shout has been 'fixed'. It now generates about 50 threat total[citation needed], no matter how many party members got the buff. The old days of Battle Shout tanking are quite over. The threat generated is not restricted by range (unlike Demoralizing Shout), and is divided among all the mobs that have the warrior on their hate list.

You can check back on the forums for any updates or lack of reports of it happening, or you can also go to the main page and check the social media links. Quickest way would probably just be to leave a browser window up with your token entered and try it periodically.

500 Internal Server Error here as well. Seems there is something happening server side. I have tried everything on my side to see if it would go through (different browser, clearing cache, etc.) to no avail. A junior GM replied in a different thread and said to keep an eye on social media for any update, but none of the social media accounts are showing info about this either. I am pretty sure the staff has someone that can diagnose the issue, but here is a quick general reference for some things they can check since the 500 internal error is a general error code and not very specific. https://www.lifewire.com/500-internal-server-error-explained-2622938 If they are stuck, I can possibly hop on a discord chat to offer whatever help I can. I will periodically check back for private messages. Either way good luck to the staff in seeing this resolved quickly. And thanks so much for all the time and effort you guys put into this project!