jcochran

There are two fees associated with the auction house. They are the deposit and the cut. The deposit is based upon the vendor price and for the servers here since the AH time is shorter than retail. In any case, if your item sells, the deposit is refunded. If the auction expires, you don't get a refund. The cut is a simple percentage of the final sale price. For the faction auction houses, the cut is a straight 5 percent. For the neutral auction house, the cut is 15%. So in a nutshell. If the auction sells, the auction house retains 5% of the sale price and refunds your deposit. If the auction expires, the auction house retains the deposit.

I'm not a lawyer, but I just did a google search about the legality of torrents in Germany, and the root issue is that a torrent client not only downloads, but also uploads. It's the uploading part that gets you into legal hot water. A direct download is OK, if the content being downloaded is illegal, the entity hosting the content is the one in trouble, not you. So doing another google search, I found this URL http://retro-wow.com/page/connect and there's a nice link there for a direct download of the 1.12.1 WoW client in its 4.95 GB glory.

They should retain their buffs and debuffs. As for the mention of the Hakkar plague, Blizz's solution was to modify the plague so it couldn't exist outside the instance.

I feel your pain about Stitches yesterday. And as Nola said, that's Blizz like and it happens from time to time. My solution? Put Westfall on hold quest wise and go over to Loch Modan, or even Darkshore. All three zones are the same level wise.

Yes, there are addons that track where you've found resource nodes in the past (Gatherer comes to mind). The issue however, is that those addons don't tell you that the historic resource node is currently available for harvesting. Merely that you did get something there sometime in the past. You're still limited to tracking one type of node at a time.

Heck, if you want to look at something concrete that isn't Blizzlike, just look at hunter pets. From release until Patch 1.7 the abilities of hunter pets was limited to Bite, Claw, Cower, Dash, Dive, and Growl. Patch 1.7 added Furious Howl, Prowl, Scorpid Poison, Screech, Great Stamina, Natural Armor, and the Arcane, Fire, Frost, Nature, Shadow resistances. Patch 1.8 added Lightning Breath Patch 1.9 added Charge, Shell Shield, Thunderstomp. As a player of a hunter, I happen to enjoy using a Boar with Charge and am quite thankful that Elysium isn't 100% Blizzlike.

He ate his wheaties?

There's also an issue with what people define as "instant". I know for a fact that the current version of Auctioneer on retail also has an automatic buy feature. But it doesn't work quite the same way as Aux's. What happens is auctioneer displays a window that you click yes, or no to in order to buy the selected item. And that falls totally within the rules requiring human interaction with placing bids. Additionally, it can also cause a response time on the order of 1 second or less depending upon the human.

The +5 mining glove idea is good. A minor refinement that many people overlook is to have the enchantment cast on a pair of white (so the gloves won't soulbind when worn), cloth (so any class can wear them) gloves. You'll then have a pair of gloves to help you past those awkward skill boundaries and when you've past them all, you can mail those gloves to an alt or friend who also has mining. Since you're now past the Iron threshold, here's a suggestion for when you get up to Mithril and need to get some. If you're alliance, go to the blasted lands and enter the Armory. I generally find 2 to 4 mithril nodes every time I visit and there are no mobs hostile to the alliance there. As for horde, all of the mobs there are hostile.

In general it's a bad idea to pick both mining and herbalism. The issue is that you can only track one type of node at a time. Other than that limitation, there's nothing preventing you from handling both professions.

The skill bonus makes this easier to make. So orange turns to yellow sooner, not later. With that said, I have a vague memory that gaining skill points is based upon the unaltered skill while the ability to make something is based upon the altered skill. This means that although the pattern changes from orange to yellow sooner, you'll still have a 100% chance of gaining a skill point on a pattern that changed to yellow within the last 15 skill points. Also means that patterns that newly changed to grey still have a small chance of providing a skill point.

Have to agree with the OP that the mute is overly sensitive. As an example, I use the addon "Auctioneer" to keep track of prices in the Auction House. It has an option to auto respond to messages of the form "?[item link]" and send a whisper to the person saying that trigger message given the latest and historical prices on the ilnked item. I've enabled that option option to allow my fellow guild members to see that data. And I will get muted from time to time simply because I've gotten those price check requests a few times too close to each other.

Actually no. If you read my post, you can exceed the 321 limit and usually not see any problems. The 321 limit reserves 100 bytes per guild member. Those 100 bytes are to store the member's name, rank, public note, and officer's note. If not many public and officer notes are made, then the 321 limit is conservative and can be exceeded. But as the overall guild description size approaches the 32K limit, you will have issues either creating or modifying those notes. And those issues are highly likely to result in the submission of bug reports even if the server is handling things properly.

Some people aren't happy unless they have something to complain about. Ignore them.

Definitely herbalism is better than mining. Reason is quite simple. Flasks and Elixirs. At 60, there's not much demand for ores to craft items, so your main market is people leveling alts. But 60s with cash to spare are gonna want consumables and the the flask and elixir market has a high demand for herbs. As for tailoring, only reason is the pre-raid BiS BoP craftables. And after a bit of raiding, those crafted items will be replaced.

Warlocks are the best because our bread is bandages and the tears of our victims our drink.

I have got to wonder about your focus on seconds per kill. Are you dotting the mob, then spamming shadow bolts until it's dead? And if so ... Why? When I play an affliction warlock, I'll send in the VW, dot up the mob. then send the VW on towards the next mob. No shadow bolts, no wands. Just dot 'em up and let 'em die. Yes, the time it takes for a mob to die is a few seconds longer than what it would take if I were to toss off shadow bolts. But from my point of view, the mana I spend on a shadow bolt is wasted mana because the DoTs ticking away are going to kill the mob anyway, assuming you allow the DoTs enough time to do their job. The only real limit to how fast I can kill is the GCD limiting how fast I can dot things up. As far as I'm concerned, a mob has three states. 1. Alive - I haven't done anything to it ... yet. 2. Dead, but still moving - It has dots and as far as I'm concerned, it's dead, it just doesn't realize it yet. 3. Dead and lootable. - Finally still enough for me to loot it. And from the tone of this thread, it seems that's there's entirely too many warlocks that are afraid of mobs that are in state 2 and are wasting mana using shadow bolts to speed up its transition to state 3 when what they should do is find another mob in state 1 and move that mob over to state 2. So why care if a mob takes 30 seconds to die? The real metric to measure is how long you take between starting combat between mobs. If I spend 8 seconds from start of mob to starting the next mob, but the mobs take 25 seconds after I start combat to die, and you spend 12 seconds from start to end of combat before starting the next mob, who's killing mobs faster?

You don't seem to understand Lju's answer... There was a bug where minions despawned when their master was killed. That bug was fixed so that they no longer despawn. See https://elysium-project.org/bugtracker/issue/3272 Your video is showing them operating as intended.

Actually, there's another very good reason for the 321 cap. Did you ever wonder where the rather strange number of 321 came from? Once you understand that, then you'll understand why it exists. The WoW client in vanilla gets a single message detailing the guild membership. So let's work from there. Maximum length of a message to the client = 32768 Overhead of message = 10 Maximum number of ranks within a guild = 10 Maximum length of guild info message = 500 Maximum length of guild message of the day = 128 Maximum information per guild member = 100 Now the key is that the message to the WoW client can never ever exceed 32768. So let's calculate the maximum number of guild members we can cram into that message. First, let's subtract the overhead and one time guild information. So 32768 - 10 - 10 - 500 - 128 = 32120. Which means we have 32120 bytes available for guild membership. And given the 100 limit, we now have 32120 / 100 = 321. And that is where the guild member cap of 321 is set. In order to increase the guild cap beyond that, the WoW client would have to use more than 1 message to describe the guild. Which means that the WoW client would have to changed. And that is the one thing that we absolutely can not do. The guild member cap isn't some arbitrary number set by someone saying "This is what vanilla used and therefore we're going to slavishly use the same number." It's set by "This is what the software for the vanilla client expects and it has an inherent limitation of 321 that can't be exceeded without modifications to the vanilla client." Is it possible to exceed the limit of 321 within the vanilla client? I personally would say "Yes" because it's unlikely that every guild member will use the maximum of 100 bytes for their entry (overhead + name length + message length). But if there's more than 321 guild members, it's possible for the 32768 byte limit to be exceeded by people simply editing their public notes. And having the server check each attempt to edit the user's public not to make sure the result doesn't cause the guild description to exceed the limit would be a real pain in the rear as well as being a non intuitive work around. For example, assume that "Joe" is someone who joined the guild fairly early and make a fairly descriptive public message "Tank, 300/300 mining/blacksmithing" and then as the guild grows, "Fred" who's a late comer decides to edit his public message to also read "Tank, 300/300 mining/blacksmithing" and instead of his attempt working, he gets an error message indicating that it's not possible to set that message. WTF?!?!? Fred is unable to set a message that's IDENTICAL to Joe's? Any bets on how rapidly a bug report is going to be created by Fred? So sorry folks, the 321 guild member cap is here to stay.

This is a bad idea. The issue is that streaming Vanilla WoW on twitch is against the TOS for Twitch. I'd recommend searching google and examining the results. https://www.google.com/q=is+streaming+vanilla+wow+against+twitch+terms+of+service

If you're using Microsoft Windows, then while you're connected, issue 'netstat -a -n' from a command prompt. That will display all the active IP connections your computer has at that time. Then you can examine the output and figure out the IP address that you're connected to. In my case, I play on the Darrowshire realm and the IP address I get is 164.132.233.125. Doing a whois on that IP address indicates that I'm connecting someplace in France. Now, that may be a proxy that in turn forwards to another location, but that doesn't matter since I have no control over that. What matters is where I enter the Elysium system and that is in France. Another way to deduce the location of where you're connecting is to look at the realmlist.wtf file that you must have to connect. You'll see the name logon.elysium-project.org which if you do a DNS lookup on translates to 164.132.233.125. Notice that's the same IP address as I determined via netstat. Once again, I get an indication that I'm connecting somewhere in France.

I don't know what skill is required to mine thorium. But with that said, it's rather easy to find out. 1st, just go to a thorium node and take a swing at it. You'll get an error message telling you exactly what skill level is required. 2nd, just go to a mining trainer and see what skill is required to smelt thorium. That will be the same skill required to mine a small thorium node. As for mining truesilver, the best places are the same as the best places for mining Mithril.

I would agree that announcements would be quite useful and desired. I strongly disagree with the concept of "stopxp". The problem with stopxp is that it will increase the population of twinks and twinks are one of the major causes of people avoiding battle ground. The twink population will likely respond that they're not doing anything that anyone else can do. The problem with that argument is that some people just want to accomplish some PvP quests and continue leveling. They aren't dedicated towards spending their time exclusively in battle ground. And it is unreasonable for anyone to expect someone to dedicated several weeks of effort just to enter a battle ground and be on even footing with some twink who has BiS in every slot for his level. So YES to announcements. That would be helpful and useful. And NO to stopxp. Think battle grounds are dead now? They will be far deader if the twink population increases.

Well, there's only 1 good reason in my opinion to multi-box and thankfully, the ToS permits it. To have a character that knows enchanting be able to enchant gear of other alts on the same faction. Make two accounts and in theory have 1 account with up to 1 alliance and 9 horde, and the other account with up to 1 horde and 9 alliance. The two singleton characters know enchanting as one of their professions. Any other use in my opinion is being an abusive guest on the free servers that are being provided for our use.

And the odds of all the party members getting back online within a reasonably small window is .... ? Nope, rebooting the server does reset the queue, but causes other problems that are rather annoying. If you're in an instance, you will need to see about getting a new group together and running a brand new instance, because you have a snowballs chance in hell of getting the 5 people back together in a reasonable time frame. When the queue is restarted, unless you're extremely lucky, you're going to be waiting for up to an hour to get back on. That hour is a lot better than the 8+ hours the unfixed queue was running at, but still a rather long time.