• 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 Slackie

  • Rank
    Bald Bull

Profile Information

  • Gender Not Telling

WoW Profile

  • Character Name Slackee
  • Gender Female
  • Race Blood Elf
  • Class Death Knight
  • Realm Location Europe
  • Guild Thuggernaut
  • Guild URL http://www.thuggernaut.com

Slackie's Activity

  1. Slackie added a post in a topic [Fixed] DBM Pull Timer   

    Ah, okay.  That explains it then.  I don't think the two characters were in the same zone.  False alarm!
  2. Slackie added a post in a topic [Fixed] DBM Pull Timer   

    More information -- I was trying this outside of an instance (in Org) to test.  Should it work outside of an instance?  I just popped into Stormstout to test it and it seems to work, so maybe there's just some bug with trying to use it while in a raid but not actually inside an instance?  This was two people on the same realm.
  3. Slackie added a post in a topic [Fixed] DBM Pull Timer   

    FWIW I am still seeing this problem with 5.4.10 r11061.
    When I do a /dbm pull 10, I see the countdown but others in the raid also running the same version of DBM do not see the countdown.  Also, when other people in the raid do /dbm pull 10, they see the countdown but I do not.
    I tried nuking all of my character-specific DBM WTF files in case there was something in my configuration causing the problem but no change.
  4. Slackie added a post in a topic Armory Scraping   

    There is no JSON URL. You must parse XML or HTML to get active auctions.
  5. Slackie added a post in a topic Armory Scraping   

    It looks like Blizzard is using <canvas> tags with JavaScript to generate the tabards. If you take a look at the data from the guild page as well as [1] that will probably get you started. You would just parse the data from the JavaScript on the guild page and use [1] to figure out how to craft a URL that will point to your particular guild tabard.

    On your guild page Thuggernaut @ Mal'Ganis - Game - World of Warcraft look for the following code:

    <canvas id="guild-tabard" width="240" height="240" style="display: inline;">
    <div class="guild-tabard-default tabard-horde"></div>

    <script type="text/javascript">
    $(document).ready(function() {
    var tabard = new GuildTabard('guild-tabard', {
    'ring': 'horde',
    'bg': [ 0, 41 ],
    'border': [ 5, 14 ],
    'emblem': [ 92, 14 ]

    This results in the JS function retrieving the following URLs:


    You can find the little "hooks" that are on the top here: http://us.battle.net/wow/static/images/guild/tabards/hooks.png

    There are also some color maps for the background color and shadows but I didn't dig much into how that all works. Looking at [1] will help in that respect.

    [1] http://us.battle.net/wow/static/js/character/guild-tabard.js?v7

    The pre-Cataclysm XML/JSON feeds never went away (well, maybe for a couple days right after the new Armory launched). They are still in the same location. Blizzard mentioned in a forum post after the new Armory launched that they were working on a new API for the Armory. Until they are finished with the new API most folks are just using the XML/JSON data from pre-migration or just parsing HTML.
  6. Slackie added a post in a topic Armory Scraping   

    The pageSize key in the URL defines the maximum number of auctions you want returned for a single query. The maximum you can set this value to is 200. Well, you can set it higher, but the maximum number of auctions you will get back from a single query is 200 even if you set the number higher.

    That being said, if you want more than 200 results, you can actually change the start and end values to do your own pagination. If you queried for start=0&end=200 to get the first 200 results for "Cloth" and then used start=200&end=400 for the same query, you should get 200 more auctions that are different from the ones in your first result set.
  7. Slackie added a post in a topic Armory Scraping   

    Anyone have experience interacting with the remote AH (specifically search.json) using a character with UTF-8 symbols in the name?

    I've tried to escape them but I just keep getting the This account does not have any characters who are eligible to use the Auction House error message.

    If I change cn to another character on the same account with no UTF-8 symbols it works fine.
  8. Slackie added a post in a topic Armory Scraping   

    So I have a question that isn't directly related to Armory scraping, but is related to scraping... specifically, I am looking for a programmatic way to get the current patch level of Warcraft. Anyone have ideas? I poked around a bit with Wireshark looking at how the launcher works (pasted below), but I don't see anything that looks like a patch version in the plaintext portion of what it does.

    The important part for me is a programmatic, reliable way to get the data. I can't look inside WTF files. I need to be able to get it off the wire, preferably from Blizzard directly. If there are other options, I'm open to those as well.

    Here is the Wireshark of the launcher starting up if anyone is curious:

    PORT: 80

    GET /wow-pod-retail/NA/config_recommended_na_2.xml HTTP/1.1
    Host: ak.worldofwarcraft.com.edgesuite.net
    User-Agent: Launcher/4.0.0 CFNetwork/454.11.5 Darwin/10.6.0 (i386) (MacBookPro6%2C2)
    Accept: */*
    Accept-Language: en-us
    Accept-Encoding: gzip, deflate
    Connection: keep-alive

    HTTP/1.1 200 OK
    Server: Apache
    ETag: "3173b46d78ca246332f8be5915acbbe3:1291056533"
    Last-Modified: Mon, 29 Nov 2010 18:48:53 GMT
    Accept-Ranges: bytes
    Content-Length: 525
    Content-Type: application/xml
    Date: Sat, 15 Jan 2011 04:21:14 GMT
    Connection: keep-alive

    <versioninfo type="pod">
    <version product="WoW">
    <server id="akamai" url="http://ak.worldofwarcraft.com.edgesuite.net/wow-pod-retail/NA/12911.streaming.2/"/>
    <threshold speed="1000000" red="5" yellow="5" />
    <threshold speed="1000001" red="1" yellow="5" />
    <setting name="patchapplicationstage" value="Recommended"/>
  9. Slackie added a post in a topic Armory Scraping   

    Of the people I collaborate with on the Armory stuff, all of us are still using the "old" mechanisms to interact with the Remote Auction House. Shortly after Blizzard rolled out the new Armory they disabled the "old" URL's, but the new Armory didn't support any easy way to gather data (it returned actual HTML, not XML/JSON).

    Due to popular demand from people who actually parsed Armory data, they re-enabled the old URL's while they work on finalizing an API for accessing the new Armory.

    This was a thread on the subject: WTB XML Feeds! Offering lunch at Javier's! - Forums - World of Warcraft

    When interacting with World of Warcraft, you can specify the character with the 'cn' key, like this:
    GET /auctionhouse/search.json?pageSize=50&rhtml=false&cn=Charname&f=1&r=Mal%27Ganis

    It also works for creating an auction, bidding, etc. All of the actions will accept 'cn' (character name), 'f' (faction) and 'r' (realm).

    In short, don't use the new Armory URL's (yet) unless you just like parsing HTML. If you want XML/JSON just use the old URL's until they publish the new API.
  10. Slackie added a post in a topic Armory Scraping   

    I've put a lot of the changed stuff up online for my personal use at: https://www.ef.net/remote_auctionhouse.

    Just some of the changes with the new Armory and for ease of having everything in one place rather than spread around in multiple places. I'll try to keep it updated with new stuff we discover as time permits.
  11. Slackie added a post in a topic Armory Scraping   

    From a PM:

    There is an additional key required now (other than the auction id (auc) and amount to bid (money)) that is "xtoken". The value of this key is taken from the cookie "xstoken" that is set during login.

    These new "xtoken" and "xstoken" keys are used for several of the operations. There seems to be some confusion with them, for example in the POST request for bidding on an auction, the "xtoken" value is taken from the cookie "xstoken" (note the "s").

    In the cancel operation, the "xtoken" value comes from the "xtoken" cookie, same with the create operation.

    In the deposit operation when creating a new auction, there is also a new key "sk", which is derived from the "xstoken" cookie.
  12. Slackie added a post in a topic Armory Scraping   

    This should get you started:

    browse: GET https://us.battle.net/wow/en/vault/character/auction/horde/
    bid_auction: POST https://us.battle.net/wow/en/vault/character/auction/horde/bid
    cancel_auction: POST https://us.battle.net/wow/en/vault/character/auction/horde/cancel
    create_auction: POST https://us.battle.net/wow/en/vault/character/auction/horde/createAuction
    deposit (ticket request): POST https://us.battle.net/wow/en/vault/character/auction/horde/deposit
    money: POST https://us.battle.net/wow/en/vault/character/auction/horde/money
    my_auctions: GET https://us.battle.net/wow/en/vault/character/auction/horde/auctions
    my_bids: GET https://us.battle.net/wow/en/vault/character/auction/horde/bids

    Keep in mind that the "horde" portion of the URL is dynamic and can be "horde", "alliance", or "neutral".

    So far I've found that the bid, cancel, create, deposit (ticket request) and money requests all return native JSON.

    I still haven't found a way to get the browse, "my auctions", or "my bids" requests to return anything but HTML.

    Also, upon looking at this I got the idea that since all of the POST requests returned JSON that maybe any POST request would, but sending POST instead of GET to the browse URL still results in HTML.
  13. Slackie added a post in a topic Armory Scraping   

    Lost my last post in the ether, but it looks like Blizzard has moved over to the new Armory in prep for Cataclysm.

    They have switched to using REST calls for using the Remote AH. Here are the new base search pages:

    [/code] Browsing has also changed: [code]
    https://us.battle.net/wow/en/vault/character/auction/horde/browse?key=val&key2=val2 (same options at the end as before)

    The old method of setting rhtml=n to get JSON/XML does not seem to produce JSON/XML anymore. This should probably be what people work on figuring out first.

    I have not looked into the other methods for posting/canceling auctions yet, but they should be trivial to discover.
  14. Slackie added a post in a topic Armory Scraping   

    Yes. I had to modify my library to raise an error when I get the "You must log in." message so that scripts know they need to authenticate again.
  15. Slackie added a post in a topic Armory Scraping   

    Thanks for finding status.json, I hadn't seen that before. Does anyone know of a way to find current transactions remaining without actually posting a new auction or bidding on something? That would be useful.

    Here are all the various URLs I know about, just so everyone is on the same page (I didn't add status.json from above yet)

    root: "http://www.wowarmory.com/auctionhouse/"
    status: "http://www.wowarmory.com/login-status.xml"

    # Miscellaneous
    money: "http://www.wowarmory.com/auctionhouse/money.json?%s"
    alerts: "http://www.wowarmory.com/vault/calendar/alerts-user.json?%s"
    inventory: "http://www.wowarmory.com/auctionhouse/inventory.json?%s"

    # Calendar
    calendar: "http://www.wowarmory.com/vault/calendar/month-user.json?%s"
    calendar_world: "http://www.wowarmory.com/vault/calendar/month-world.json?%s"
    calendar_details: "http://www.wowarmory.com/vault/calendar/detail.json?%s"

    # Mailbox
    mailbox: "http://www.wowarmory.com/auctionhouse/mail.json?%s"
    mailbox_move: "http://www.wowarmory.com/auctionhouse/takeMail.json?%s"

    # Auctionhouse related
    auction_post: "http://www.wowarmory.com/auctionhouse/create.json?%s"
    auction_browse: "http://www.wowarmory.com/auctionhouse/search.json?pageSize=50&rhtml=false&%s"
    auction_active: "http://www.wowarmory.com/auctionhouse/auctions/index.xml?rhtml=false&%s"
    auction_cancel: "http://www.wowarmory.com/auctionhouse/cancel.json?%s"
    auction_deposit: "http://www.wowarmory.com/auctionhouse/deposit.json?%s"
    auction_buy_get: "http://www.wowarmory.com/auctionhouse/bid.json?%s"
    auction_buy_post: "http://www.wowarmory.com/auctionhouse/bid.json"