• Announcements

    • Maniq

      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!


New Members
  • Content count

  • Joined

  • Last visited

About Myrroddin

  • Rank
    Glass Joe

WoW Profile

  • Character Name Myrroddin
  • Gender Male
  • Race Human
  • Class Priest
  • Realm Llane
  • Realm Location United States
  • Guild Knights of the Storm
  • Alternate Characters Jelia, Vanhoeffen, Uthartian, Badash
  1. ToC files, DBM, and the Curse Client

    Huzzah, it worked! The Curse Client isn't endlessly trying to install DeadlyBossMods anymore! Even with hard-embed libs, I thought it would work, as I have an AddOn that I hard-embed for debug purposes, yet the stripping works fine. /whew
  2. ToC files, DBM, and the Curse Client

    It should, in theory, work, even with Curse being a clone with a remote repository. The no-lib lines should be ignored by your packager (they are by Wowinterface) and the zip should be made properly. Now that I know your process, added a line like ## Version: @project-version@ Will not work, as your system would think that is the literal version number, while Curse would package it correctly. Since that is the case, may I knindly request that you do put the Version field in manually? It currently doesn't exist at all.
  3. I noticed some time ago that the Curse Client repeatedly tries to install the no-lib-strip version if you have that setting. As soon as you hit the Refresh button, DBM gets reinstalled. Rinse, repeat. So I took a look and found out why. Nothing is wrong with the pkgmeta, but the ToC file for DBM-Core is messed up, albeit only slightly. All other ToC files are correct. ORIGINAL ## OptionalDependencies: LibSharedMedia-3.0, LibChatAnims Libs\LibStub\LibStub.lua Libs\CallbackHandler-1.0\CallbackHandler-1.0.xml Libs\LibChatAnims\LibChatAnims.xml Libs\LibSharedMedia-3.0\lib.xml CORRECTED ## OptionalDependencies: LibStub, CallbackHandler-1.0, LibSharedMedia-3.0, LibChatAnims #@no-lib-strip@ Libs\LibStub\LibStub.lua Libs\CallbackHandler-1.0\CallbackHandler-1.0.xml Libs\LibChatAnims\LibChatAnims.xml Libs\LibSharedMedia-3.0\lib.xml #@end-no-lib-strip@ Would you like to fix this minor, yet annoying issue, or shall I do a commit to your mainline repository on Curseforge? On a side note, I can add repo keyword substitutions for DBM's version, so people will know in the AddOns screeen. Apparently I am not allowed to attach a copy of the file to this post.
  4. I found something that might be better than checking for zone:http://wowpedia.org/API_IsInInstance ... If you aren't in an instance, then don't exit the movie. God forbid Blizzard mixing the two for solo instances. Yikes!
  5. Because of something I am working on unrelated to DBM, but related to maps and mapID, could you elaborate why mapID "is far from accurate" please? As far as I can tell, the mapIDs are immutable, and the only caveat is when the player has the map open, in which case: Save the open map to variable Close the map Get the mapID of the current zone Open map Set map to previous variable Oh yes, it is a pain (thanks, Blizzard), but isn't that how it is done?
  6. I was doing the following three quest in Badlands: http://www.wowdb.com/quests/27713-the-day-that-deathwing-came http://www.wowdb.com/quests/27714-the-day-that-deathwing-came-the-real-story http://www.wowdb.com/quests/27715-the-day-that-deathwing-came-what-really-happened And then I noticed DBM's feature of not showing a cinematic you have already seen prevented the second and third quests from being functional. When you are on those quests, your character gets replaced by a playable cinematic character, and you perform the actions described in the quests' stories. Once completing the first quest in the chain, DBM learns which movie it is, and thus never lets it be seen again. If you fail the first quest, or move onto the second or third quests, DBM automatically exits the cinematic and you cannot do the quests. When I checked the saved variables for DBM, I saw a list of "MoviesSeen", but that doesn't help me because there is no description to indicate which movieID is which. What I suggest to fix this is perform a zone check before exiting a cinematic. Assuming Blizzard adds more such quests, then exit the function that cancels movies if you are in x, y, or z zones. Badlands is zoneID 3. Things might get complex if the player has the map open, but it can be done.