Okay, so agree or disagree but these are the things I think should change:
1. Players are TOO powerful. This should be a world that you play in and have no control over not the other way around. Why does this matter? Well in BC, when it was still hard to level (as you could die) damage wasn't that bad. Once they changed that with wotlk and players got more powerful we saw burst go WAY up. This continued with Cataclysm and then with MoP. Not only does it make the game feel like less of a world, but it also directly impacts arena cause they can't balance it.
2. Classes all have the same abilities:
Every class feels the same because you're just spamming buttons like a PvE rotation. Also, Self-Healing should NOT be there for every class at the level it is.
3. There are TOO many abilities. This is the reason you keep spamming buttons that used to be much simpler and took more effort to time. For example, in BC with rogues pooling energy for kidney shot/burst. Or a paladin had a HoJ which they could use: for more damage, to stun to heal themselves, to prevent them from reaching your ally, and much more. Each class had unique abilities and MANA actually mattered, which made it much more interesting. On top of that, the abilities don't feel as fun. If you were to get off many spells then it would really hurt, but that meant you had lined up good CC or the other team sucked.
4. Everything is an instant ability or close to quick cast. It kind of ruins the point of a "caster." More importantly no one ever asked fore more instant abilities or CC, in fact the opposite yet we keep getting MORE AND MORE!!!
5. This leads to there being way too much CC because every class is the same. Burning Crusade was based on comps, but mainly mistakes would lead your teams too lose. Once WOTLK came around we saw so many zerg comps where mistakes wouldn't impact you as badly and it was even more based on comp (beastcleave, tsg, wizard cleave.)
6. Base 40% reduction. This makes it so people starting out in BGs can do no dmg and also get raped. In terms of arena, it really hasn't balanced anything and the FOTM still stands stronger then ever. The goal maybe to make it so high end arena is fair, but all it's really done is unbalance pvp in battlegrounds; and still high end is unbalanced. So I'm not saying remove it, but it's not doing it's job at all. On a site note, doing dailies or world pvp, swapping between gear is almost night to day which defeats the purpose of having the "forced into world" interaction.
7. This goes with PvE and PvP, Blizzard made the game they way they wanted to and it was time consuming and challenging. Every expansion everything gets easier and then when they try to make it "artificially" hard, it fails. They can still make it challenging without being time consuming but they need to not give everyone everything.
Remember when you had to get gold for your mounts? Epics weren't everything? You could actually die in the world?
The world used to be mysterious and dangerous; while some of that can't be returned, too much of it got taken away and that's what made it boring.
Anyways that's just my two cents. Thanks for reading!
PuTTY is a neat little program that allows you to do a lot of different things. The specific functions we will be using it for is the ability to tunnel SSH traffic through localhost (127.0.0.1:8080) to our VPS. In laymen’s terms, it will be transferring all of the data over Skype through a secure tunnel so that only the VPS you’re connected to is being exposed to anyone else. PuTTYgen.exe
This is a simple program that we will use that will transform the key we get from Amazon into something that PuTTY can use to automatically connect to our VPS. Windows 7 Firewall
We’re using Windows 7′s Firewall (ANY Firewall can be substituted here) to disable Skype from connecting to the internet. EC2 Amazon Access
Even though it requires a credit card to sign up for and activate, the only tier we’re interested in is 100% free. Amazon may authorize $1 to your CC just to verify that it’s real, but you won’t actually be billed any money. The free-tier that we will be using will be good for 1 year prior to activation. The Process
The problem people have with Skype is that it tends to ignore whatever proxy you throw into the connection information for it. It doesn’t actually ignore the proxy, but it will simply add it to a list of nodes it will consider connecting to if you’re having trouble maintaining a p2p connection with whoever it is you’re chatting with. For security purposes, this makes it useless. Instead of adding our VPS to the Skype proxy list, we’ll add 127.0.0.1:8080. “What’s the point, though? You said it won’t even use that most of the time!” That’s where our Windows Firewall comes in! We’ll use Windows 7′s Firewall to block Skype from making ALL outbound connections to the internet. This means that when Skype tries to connect to the internet when you log in, it will see that there is no connection available. This forces it to look to any proxies the user has supplied for a connection. Ordinarily, these would also not work (since all outbound connections are blocked by our Firewall), however, localhost is not an outbound connection and therefore falls outside of W7′s restricted connections. This means we’ve effectively tricked W7′s firewall into becoming a routing tool! Skype will then begin tunneling traffic through localhost, assuming PuTTY is open and you are connected to your EC2 server that you set-up on Amazon.
If you came here straight from the first page just looking to a guide to mindlessly follow, this will get the job done. However, I highly encourage you to read the explanations given in the pages prior to this so that you have a thorough understanding of what you’re going to be doing with the programs you’ll be working with.
Next, we’ll need to create an AWS (Amazon Web Services) account. You can click the “sign up now” button here - http://aws.amazon.com/ec2/. If you don’t already have an Amazon account, you’ll need to create one of those as well. The micro-instance we’ll be utilizing via Amazon’s EC2 service is free for one year.
After that, we’ll need to sign up for Amazon’s EC2 service and get a micro-instance running.
You can return to the same link earlier (http://aws.amazon.com/ec2/) and click the “My Account/Console” drop down menu in the top right, then click “AWS Management Console”.
Next click “EC2″ under the “Compute and Networking” list
You should see an option that will allow you to “Launch” an instance. Click that.
Select the “Classic Wizard” option and click next.
Scroll down to whatever the latest Ubunutu server is with a star next to it, and press the “select” button next to it. You can leave the 64 bit version selected.
As long as everything looks like this on the next page, you can continue.
Press “continue” on the next page.
Then press “continue” one more time.
The next page asks you to assign a key/value name to the micro-instance you are running. This is entirely arbitrary and will not be used at any point here, so you can name these whatever you want, or simply leave it blank.
For the next page, you’re requested to create a name for your key pair. This will be used later on to log into the micro-instance. After you assign another arbitrary name, you can download this key pair.
On the next security page you need to select the “quick-start” bubble, then click “continue”.
Finally you can “launch” your instance!
Creating a keyfile and setting up PuTTY
Remember where you saved that keyfile that you downloaded earlier? Now we’re going to turn that keyfile into something usable with PuTTY.
Click “load” and search for the key you saved from Amazon. You will have to select “all files” in the bottom right as the file you’re looking for is a .pem file, and not a .ppk file.
Click “save private key” and save it somewhere you’ll remember for later on.
Now it’s time to configure the program that we downloaded earlier, PuTTY.
When you first open up PuTTY, there will be two empty boxes for information. “Host Name (or IP address)” and “Port”. In the “Host Name” box, you need to enter your EC2 information from Amazon. Go to https://console.aws.amazon.com/ec2 and click “1 Running Instance” to bring up a list containing the instance you launched earlier. Select it. At the bottom of the screen you will see your Amazon EC2 IP (it will look something like this). Enter this into the PuTTY Host Name box. For “Port” you can enter “22″.
Make sure the connection type is set to SSH.
On the left side of the PuTTY window, scroll down and expand “Connection”, then select “Data”.
Here you want to enter your “Auto-login username” as “ubuntu”.
Now expand “SSH”, then select the “Auth” option.
In the empty box here you need to search for and enter the location of the keyfile you saved earlier using puttygen.
Now select “Tunnels”. On this screen you want to enter 8080 in the “Source port” box, and make sure you’ve selected the “Dynamic” bubble beneath. Now press “Add” and “D8080″ should appear in the box above.
Now scroll all the way back up to “Session” on the left side, enter whatever you want in the “Saved Sessions” box, then press the “Save” button on the right to save these settings. Now when you open PuTTY, all you’ll have to do is press “Load” and “Open” to recall these settings and open your SSH tunnel.
Use Windows 7 Firewall to block Skype
Search for “Advanced” on Windows 7 and “Windows Firewall with Advanced Security” should come up.
Select “Outbound Rules” from the left column
In the top left, select the “Action” menu and click on “New Rule…”
A box will appear on your screen. Select “Program” and click the next button.
Browse your computer for Skype to block, then press “Next”.
Press “Next” one more time, all three boxes should be marked on this screen.
You can create whatever name you want here; I called my rule “SkypeBlock”.
Now Windows 7 will not allow Skype to make any outbound connections! To test and make sure that this worked, try to open up Skype right now. If you were successful, Skype should fail to connect to the internet. Force Skype to route through localhost
On the Skype login windows, click “Tools”, then press the “Connection options” button.
Under this connection tab, you need to make sure “SOCKS5″ is selected in the drop down menu. Now you need to enter “127.0.0.1″ for the “Host” box and “8080″ for the “Port” box.
And that’s it, you’re done!
Now any time you want to log onto Skype behind your Amazon proxy, all you have to do is open PuTTY, load your settings, then connect to your EC2 instance (via the “Open” button) and you should be good to go!
Conquest earned tally reset, as well as all Honor and Conquest points removed.
All Arena achievements earned since the beginning of Mists of Pandaria removed.
3 day suspension
Dont know If anyone posted that yet, if someone did, just delete this post.
Nice to see that they reset MMR and achievements also, but what will they do with the "legit" 3k teams?
Queueing into wintraders on purpose like 20+ times to get 3k Rating is to me the same as wintrading, just reset them to 1500 or 2200 if they were above 2200 imo.
The only reason this change would seem crazy to anyone with a brain is if they think about it as if it's implemented today.
Yes, TODAY this change would cripple Shamans because Mage damage is insane, because Warriors can Gag Order and do 300k in a few seconds. When DAMAGE gets toned, this is an absolutely no brainer of a change.
You cannot justify being at 10% HP, getting interrupted and being able to drop a Link/Tide. It's really not that complicated. It's not unique or well designed, it was probably a mistake and one that has left Shamans insane for too long.
Bring damage in line so people don't die in a Blanket, and now Shamans are brought closer in line with other healers.
Mahmoudlolz, on 14 November 2012 - 04:29 PM, said:
Gear deleted ? I don't give a shit. Honorbuddy for 1 day and i'm full geared again or just log with a chinese VPN on your account after the ban, delete gold, bank items, everything and delete character, phone blizzard, tell them you got hacked and you will get back your gear, i did this trick 3x times during wotlk and BC.
72h bans ? don't care too.
Fuck yes, thank you blizzard for being so stupid, i was already excepting this, that's why i left all of my teams yesterday and i have now, 12 different character (on different account) with 3200 mmr. Free rank one/gladiator for me and my friends.
This is just a big gift for us (exploiters), not a sanction at all for me
Hello, I've been playing resto shaman since the start of season 8. I've always been a PvPer but was never interested in getting anything more than tier 2 gear which did s8/s9 and then quit s10/s11. Now I'm back and this is by far my favorite expansion to date (I'm a tBC baby)! Looking forward to what new changes within the game bring...see you all in arena!