• Announcements

    • Forum Rules (Updated 3/22/14)   07/14/10

      Welcome to the Elitist Jerks forums, a WoW discussion forum targeted towards topics regarding high-end raiding and analysis of game mechanics. We ask you to take a few minutes to read the following before making use of these forums.   First, a point of clarification. The name of these forums is not intended ironically; we have high standards for the discussion that occurs herein, and we're quite unapologetic about it. If you feel our rules are stupid or arbitrary, we don't really care. If you don't wish to follow them, you're welcome to return to the official Blizzard forums.   Following is a brief listing of our forum rules; note that it is by no means exhaustive, as in our experience people are quite innovative in finding new ways to be stupid. These are simply a set of guidelines to get you started in the right direction. If you follow them, you will generally do fine here; however, if you concoct some creative new form of stupidity, our moderators feel no need to restrain themselves in letting you know. All posters are to make an effort to communicate clearly. In particular, all posts should be made in a reasonable approximation of proper English. We realize that a significant number of you are not native speakers, and we do not expect perfection: merely effort. Please obey basic rules of capitalization and punctuation, avoid chatroom abbreviations ("lol", "imo", "u", and the like), and pay at least minimal attention to sentence and paragraph structure. This includes not starting a new paragraph for each sentence. All opinions should be stated as succinctly as possible. Do not make multiple consecutive posts; rather, multi-quote and include all your ideas in a single post. Do not quote huge blocks of text to add a short reply; instead, quote only what you need to to make your point. Do not break a single quoted reply into multiple blocks; doing so needlessly lengthens your post without aiding its readability. And don't provide unnecessary backstory: if it isn't relevant to the question you're asking or the point you're making, we don't need to know about it. All discussion should be both polite and civil. Trolling or flaming in any form is forbidden. Just because someone disagrees with you does not mean they are stupid or on drugs and their personal hygiene isn't really relevant to the discussion. Regardless of the merit (or lack thereof) of your argument, it should be made in a way that is neither insulting nor condescending. Whining in any form is forbidden. Blizzard is not incompetent or stupid and they are not intentionally screwing you over and neither is anyone else. If all you're going to do is complain, don't bother posting. Threads should be started if and only if there is some reasonable topic to discuss. If the issue you wish to discuss is covered in an existing thread, use it rather than creating a new one. If you are asking a simple question that you expect to have a simple answer, ask it in one of the "Simple Questions/Simple Answers" threads. But if you feel there is a topic of discussion not well-covered by existing threads, feel free to start a new thread to discuss it. Some sub-forums restrict new members from creating new topics unless they've made at least 10 approved posts, to prevent spamming or bad posts. If you really think it deserves a new thread before you have 10 posts, contact a moderator with your post content. Do not post unless you have something new and worthwhile to say. Do not bump, quote for truth, cross-post, or post only to say thanks. We don't want to hear your funny story about something that happened in your raid last night, your baseless speculation is unproductive, and your idea for a new ability really isn't that interesting. We don't care what gear you are hoping to get or just received. If you have an idea you'd like to share with the community, support it with analysis, testing, or both that indicates you've put some thought into it. (Note: Posting of a new untested spec falls under this rule, unless you have done the grunt work and have information to support your amazing new spec don't even bother posting it here.) Do not beg for hand-holding. These are forums for discussion and analysis, not for answering any question that you might happen to dream up. Search and read before posting--do not post a question unless you are fairly confident that the answer isn't widely known or easily attainable. In particular, we do not want to take a look at your armory or WWS to tell you what you're doing wrong and we're not interested in making your tough gear or spec decisions for you. We expect you to use the search function and also to read the first post as well as the last 5 pages of the thread you are posting in. Chances are your question has already been answered. Additionally, do not post asking for confirmation of a simulation result. If you think there is a problem with the Sim you are welcome to PM the author. All accounts must have a valid WoW profile. If you no longer play and have deleted all characters you used to have, you may select the "No WoW Account" option; otherwise, this information must be filled out for your main character. If you fail to observe this rule you'll be permanently banned from our forums. We do not permit anonymous posting. Do not sign your posts. People can see who you are from the profile printed to the left of each post, so signing your posts is redundant and simply takes up space. Similarly, you do not need to link your armory in your post, as if people wish to see it they can get it from your profile. Do not respond to terrible posts. Do not respond to a blatantly awful post (a post that is in clear violation of the rules) either in an attempt to moderate them or to answer a question they posed. Your post will just be warned/infracted and removed with the post you are replying to. If you feel that a post is in violation of these rules, please report it and the moderators will deal with it as we feel is appropriate. No Advertising. Do not make posts solely for the purpose of advertising your site/blog/twitch/etc. You may post such things if it's relevant and adds to discussion at hand. If you have information to share, share it here with a link back to your blog or whatever. Do not post "I have information, come to my site to get it". That will result in an immediate infraction and post removal. Also, we will remove any link to a site that violates a games TOS/EULA such as gold selling sites.

      If you violate a forum rule, you will receive an infraction. Most infractions are worth one point, although we reserve the right to give you more at any time if we feel you deserve them. If you accumulate too many infraction points, you will receive an automatic (usually temporary) ban which revokes your posting privileges, as follows: 3 Points - 1 Day 5 Points - 3 Days 8 Points - 1 Week 10 Points - 1 Month 15 Points - Permanent

      Familiarize yourself with The Banhammer, an archive of all infractions given by the moderators here; it will give you some examples of what not to do. Also feel free to take a gander over The Dung Heap, which will give you a good idea of what these forums would look like if we weren't such jerks.   Thank you for joining the discussion!
    • Site Maintenance   10/01/15

      Beginning Thursday (Oct 1st), Elitist Jerks will under maintenance to upgrade to the new IPS 4.0 software. This upgrade will bring new features and better performance to the site all around.  We expect site to be down at least a few hours since EJ has a massively large database that needs updating and verification.-Complete After upgrade, some features will be missing or broken initially but will be quickly addressed throughout the coming days. Forums will work day one and it's little things like bookmarks and Pages modules that may need updating. -In Progress Update: Appears background cron processes hung up the site for about an hour on Tuesday, October 6th, while it was unmonitored. Site has been restored but may have to be briefly taken down again to see why they hung the servers to prevent it from happening again. Known Issues So Far: Recent Posts/Topics seems to be stuck on pretty much all non forum pages. This appears to be a bug in IPS with no known solution at the moment.White space is being wasted causing forums to be too slim. There are plans to address this.Guild Homepage is currently disabled because of bug number 1. It'll be restored if a way can be found to address bug 1, but that may involve opening a ticket with IPS and awaiting a fix, if a local fix cannot be found.Spoiler tags didn't import correctly in upgrade. They still work but aren't applied to post until you edit/save post at least once. Just hitting edit then save immediately will fix spoiler tags.url tags also imported strangely.Old wowhead "item" tags are depricated. They may be re-added to fix some issues with older guides, but for most part it's better to just use the modern wowhead.js which auto parses actual wowhead links automatically into tooltips/names. Just post wowhead links in guides and the js will do the rest. You don't need a special BB code for items.There is a weird broken image under everyones name in their posts.Old article links will be broken do to IPS 4 changing url path to remove some pointless "/_/" directory. The articles are still there and can be found in guides menu. You just may not be able to click links from any threads linking to them without editing out the "/_/" part of url. I'll fix most of this little by little when more important stuff is taken care of. External links/google search results may run into same problem. That will just rely on waiting for google to reindex new paths.DBM landing page Announcement/News feeds are borked. No better way to describe it then that. DBM news can still be read in the DBM News subforum without issue.-FixedWith 9 fixed, now DBM page also has the post/topic feed bug (bug number 1).After you login, you are thrown to an error page saying page cannot be found. Another bug with IPS 4 apparently. Harmless though. Just click "forums" and you'll get forum index since redirect after login is busted.


  • Content count

  • Joined

  • Last visited

About Blazeflack

  • Rank
    Von Kaiser
  • Birthday 05/09/86

WoW Profile

  • Character Name Blazii
  • Guild Aegis
  • Guild URL http://aegis-guild.dk

Blazeflack's Activity

  1. Blazeflack added a post in a topic [Fixed] Error when deleting DBM Core profile   

    Yes, the "Default" profile is missing. I think I was able to delete it, but I haven't seen it return even though I cleared all DBM savedvariables files.
  2. Blazeflack added a topic in Archived Reports   

    [Fixed] Error when deleting DBM Core profile
    The following error is triggered when deleting a newly created profile:
    Date: 2015-01-23 15:55:32 ID: 1 Error occured in: Global Count: 1 Message: ..\AddOns\DBM-Core\DBM-Core.lua line 2435: attempt to index field 'Options' (a nil value) Debug: DBM-Core\DBM-Core.lua:2435: SetRaidWarningPositon() DBM-Core\DBM-Core.lua:1395: RepositionFrames() DBM-Core\DBM-Core.lua:1389: DeleteProfile() DBM-GUI\DBM-GUI.lua:2628: callfunc() DBM-GUI\DBM-GUI_DropDown.lua:95: DBM-GUI\DBM-GUI_DropDown.lua:80 Locals: self = <table> { MoveSpecialWarning = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:8013 StopLogging = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5219 CheckVoicePackVersion = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:7942 GetModByName = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5949 CHAT_MSG_MONSTER_EMOTE = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:4450 shortTermEventsRegistered = 1 GetTime = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3030 DeleteProfile = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1374 UPDATE_SHAPESHIFT_FORM = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2877 ShowUpdateReminder = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:4195 PLAYER_REGEN_DISABLED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:4259 CreateModLocalization = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:9318 IsEnabled = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5681 CHALLENGE_MODE_END = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3022 Capitalize = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5774 ADDON_LOADED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:944 BossHealth = <table> { } ShowRaidIDRequestResults = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3954 INSTANCE_GROUP_SIZE_CHANGED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2254 GetBossUnitId = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2391 ToggleRaidBossEmoteFrame = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5630 AddDefaultOptions = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2423 UPDATE_MOUSEOVER_UNIT = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3251 InfoFrame = <table> { } FilterRaidBossEmote = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:848 RequestTimers = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5314 ForceUpdate = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1333 ToggleGarrisonAlertsFrame = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5646 UPDATE_BATTLEFIELD_STATUS = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2955 CHAT_MSG_MONSTER_YELL = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:4446 LFG_PROPOSAL_SHOW = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2840 ReleaseRevision = 12504 RegisterShortTermEvents = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:795 LOADING_SCREEN_DISABLED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3085 GetUnitFullName = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2280 UNIT_DIED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5295 ReceiveCombatInfo = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5332 RegisterCallback = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1115 FindInstanceIDs = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5822 UnregisterCallback = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1124 CHALLENGE_MODE_RESET = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:3013 RepositionFrames = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1393 LFG_ROLE_CHECK_SHOW = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2832 Disable = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5665 ReceiveTimerInfo = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:5338 CHALLENGE_MODE_START = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2992 RangeCheck = <table> { } PLAYER_LEVEL_UP = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2545 LFG_LIST_APPLICANT_LIST_UPDATED = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2859 ModLists = <table> { } ShowLag = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:1746 GetCIDFromGUID = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:2373 AddOns: Swatter, v5.0.0 (<%codename%>) DBMCore, v DBMGUI, v DBMStatusBarTimers, v BlizRuntimeLib_enUS v6.0.3.60000 <none> (ck=7c)
    • 3 replies
  3. Blazeflack added a post in a topic Suggestion: Grow Small & Huge Bars Up/Down Independently   

    I would like to upvote this request and add a related request:
    The ability to choose color for small and big timers independently.
  4. Blazeflack added a topic in Discussion & Feature Requests   

    [Added] Bar Setup: Increase max possible Bar Width
    Could you please increase the max possible width on bars from 325 to 400 or even more?
    The current 325 limit is not quite wide enough to fulfill its purpose in my UI.

    That's using the max possible width of 325 and I would like to be able to make the timers match the width of my chat panel.
    Using the scale functionality messes up the font when using a pixel font, so that is not an option for me.
    Thank you.
    • 0 replies
  5. Blazeflack added a post in a topic [Added] Request: New DBM alert for Fallen Protectors Encounter   

    During our heroic attempts last night we didn't see a single /say from people affected by Sha Shear.

    Was this feature removed in 5.4.3 or is it bugged? The option is still in the GUI, it just doesn't seem to do anything.
  6. Blazeflack added a post in a topic [Balance] WrathCalcs   

    I replaced a few items today and thought I would give it another go. The import worked as it should this time. I am not sure if those 3 items I replaced were the cause of a hidden error or perhaps it was a glitch with my armory page at the time. In any case, it appears to work as it should now.

    Just in case you want to do a follow up check, my druids name is Lumidi on Darksorrow EU.
  7. Blazeflack added a post in a topic [Balance] WrathCalcs   

    For some reason I cannot get the battle.net import to work. My druid has a feral tank spec as the primary spec and balance as secondary spec. The tooltip text on "Force 2nd spec" button states that it should import the first balance spec it comes to. Any chance you could make it search both specs in order to find the balance spec, or work on the force 2nd spec option?

    Just to make sure the import works at all I tested on a druid with balance as primary spec and the import worked fine.

    Windows 7 64 bit
    Microsoft Office 2010 32 bit
  8. Blazeflack added a post in a topic GuildOx - Guild, Character and Loot Rankings   

    Hi Polar. It looks like a lot of our 25 man kills are being listed as 10 man kills. The 3 specific kills in question are "Heroic: Chimaeron", "Heroic: Atramedes" and "Heroic: Maloriak".

    I realize you only pull info from the armory and that it is all automated, but something went wrong during that process. Please find below links to screenshots with names listed of the specific kills, if you want to check up on the achievements. (don't have one for Chimaeron)

    Maloriak: http://aegis-guild.dk/upload/maloriak_25hc.jpg
    Atramedes: Will be uploaded soon

    Edit: After the latest update it seem to have fixed 2 of the issues. The only remaining issue is with our "Heroic: Chimaeron" kill. We killed it on 25 man but still it lists it as 10 man. We haven't killed the boss on heroic on 10 man before that.
  9. Blazeflack added a post in a topic WotLK DPS spreadsheet   

    Looks like [item]Njordnar Bone Bow[/item] has been suffering from a typo up until now. This item is now called "Njorndar Bone Bow" ingame. Might take a while for wowhead to reflect this but thought you should know in case the name change will cause problems when importing from armory.
  10. Blazeflack added a post in a topic WotLK DPS spreadsheet   

    Check that the setting to hide items above x ilvl is set to something above 277. You might need to scroll to the right on the Gear Planner tab to see it.
  11. Blazeflack added a post in a topic WotLK DPS spreadsheet   

    Press the debug button and send a PM with the code to Shandara. Also give any relevant information in the PM such as version of Excel etc.
  12. Blazeflack added a post in a topic WotLK DPS spreadsheet   

    I can confirm the debug error with the progress bar. Last night I was playing around with the spreadsheet and noticed a weird behaviour aswell. I had switched some items around and when running the gear planner it told me that Epaulets of the Devourer was an 11 dps upgrade compared to my current Pauldrons of Lost Hope. When switching it back to Epaulets of the Devourer on the Gear tab I noticed how it went about 11 dps up, then dropped 30 dps making it a downgrade.

    Can anyone think of a good reason for this rather strange behaviour?
  13. Blazeflack added a post in a topic Blood Simple - The Day The Music Died   

    I can confirm that DRW will attack from behind. I used it on a mob while standing in front of it and I saw how DRW sort of spawned in the middle of the hitbox and then moved a few yards back so it was standing behind.
  14. Blazeflack added a post in a topic Blood Simple - The Day The Music Died   

    Looks like there has been a stealth change to how DRW works. I used to use the /cast [target=player] macro but when I tried using it today I got the message "Target is friendly". Upon using the regular spell from the spellbook I also suddenly noticed that DRW shows as a debuff on my enemy target.

    Can anyone confirm this?

    Edit: Someone else noticed it too: World of Warcraft - English (NA) Forums -> Undocumented Dancing Rune Weapon Change?
    Edit2: Sorry, has already been mentioned in the Simple questions / Simple answers thread http://elitistjerks.com/f72/t36775-death_knight_simple_questions_simple_answers/p101/#post1517422
    The macro in the OP needs to be changed/deleted with this change.
  15. Blazeflack added a post in a topic WotLK DPS spreadsheet   


    The spreadsheet currently lists [item]Needle-Encrusted Scorpion[/item] as a better replacement for my [item]Banner of Victory[/item]. I already have [item]Mjolnir Runestone[/item] and I just wanted to make sure that the spreadsheet knows to take this into consideration.

    I know that NES will proc less often than MR and as such they might proc at different times, my question is if it can still be viable to use both NES and MR at the same time or if it will cause you to reach over the cap too often to really be a dps gain? Does the spreadsheet model this correctly, taking into account your passive ArP?