Murlocs are taking over A Healadin’s Tear! Dirty cheater pallies beware.
I’ve stayed mostly quiet on the whole RealID business since Zel knows more about general privacy issues than I do. But if you’ll indulge me gentle reader on this topic, I do have some points I’d like to make.
We all know there are plenty of great reasons not to be excited about RealID. Most are about how it exposes possibly rare or unique names, how it could expose professionals who don’t want to be outed as gamers, or even endangers young gamers who may not realize the full extent of their online actions yet. But what I want to talk about is how it is a betrayal of an emotional investment. To better illustrate this I will need to go to a long, long time ago, in a mmorpg far far away.
Before I ever created my first WoW toon, spawned next to the Northshire Abbey and saw a NPC with a bright exclamation above his head inviting me to go whack something with my mace, I was a fairly involved Star Wars Galaxies player. As you might remember from the post about guild democracy I met my guild on the forums. Now when I initially was asked to play SWG by a friend I didn’t understand how any game could be so good as to justify a recurring payment to play. I was a mmo noob. We all were at some point. But pretty soon I came to accept that I pay $15/month and I get to play in their house. It was a pretty fair deal. But here is the twist, all the time you play is an investment into your game.
In order to address the addon security flaw that would allow addons to datamine my real name via Real ID, though I have no Real ID friends, I switched on parental controls and disabled Real ID. I had been trying to avoid parental controls, since their current implementation is also an account security risk. Lesser of two evils?
OK, what the hell? I just threw up in my mouth a little.
Apparently, the post-cataclysm forums will be “Real-ID only.” That’s right, if you wanna post, you’d better be prepared to fork over your real name. Fortunately, it won’t be retroactive to the current forums. Raise your hand if you went through and deleted ALL your old posts anyway? Yep, I did.
In a way, I feel like the situation with the quality of the posts on the forums is one of Blizzard’s own making by allowing posts by character name. In most forum environments, you choose one handle. That forum handle is your only identifier, and you don’t get an alternate identity. No posting on a “level 1 alt”. No pretending to be someone else posting in the same thread to agree with your own character.
An obvious solution to trolls is to simply give each person a unique handle, as other forums do. People are likely to speak respectfully if there is some form of accountability. Someone who has the same “name” day in, day out, is not “anonymous”, and will gain a reputation for good or bad posts.
My prediction: Blizzard will lose a lot of quality feedback from those unwilling to expose their real names.
- Those who have a lot to lose from exposing their real names are professionals who want to protect their careers. Lawyers, CEO’s, and Doctors will not want their names to come up on a google search in the WoW forums, because it may make clients/patients view them in a negative light.
- Many women are very unwilling to expose their real names due to potential stalking risks that men do not have.
- People with common names will still have the benefits of anonymity and will not be on an equal footing with those who have uncommon names. A “John Smith” has little to lose by exposing his real name.
Blizzard in effect is creating a specific subgroup for feedback that is not representative of the player base. While admittedly forum posters are already a subgroup of the players at large, this change further whittles down and homogenizes that subgroup.
Tale of Woe
Discover that theme borked in IE.
Disable all plugins. Nope, not the problem.
Try new themes.
Get errors with new themes.
Oh wait, the old theme works with IE, just disable the featured posts box.
Happy, but feeling dumb that I didn’t think of this before…
But now suddenly there are errors with this theme… and errors without this theme!
Try to restore from Backup.
Restore from backup-to-the-backup.
Lose 3 days of posts.
Copy missing posts from feed reader.
Oh wait, no it doesn’t work with IE. At least not all versions of IE.
Try to make an export backup before testing new themes.
Unable to make a backup due to errors.
WordPress Codex gives dumb answers about 3.0 requiring code futzing before you can export posts.
Revert to unedited default theme.
Default theme has errors.
No theme works.
DUBYA TEE EFF?
Sparkleparty – dead
Blood Queen whatsherface – dead too
Wrynn Buff makes me strong
My numbers are super high
I get sad elsewhere
In attempting to change my theme (because it was not working in IE), some things went wrong. Thinking myself ever-so-clever, I reverted to the last backed-up version of the site (that’s what backups are for, right?). This glitched and deleted all but 8 of my comments. That backup program is no longer my friend.
Fortunately – for me – I have a secondary backup program running. Unfortunately, that is the “backup of last resort” and only backs up once a week. So I reverted to 6/23 and everything since then was lost. Well except the posts I salvaged from the feed reader and reposted, but the comments are gone.
I’m very glad I backed up my stuff, and have backup redundancies. Hooray for being paranoid.
See kitten movie! Â See kitten chase the mousie! Â SEE KITTEN CHASE THE MOUSIE!
Ok fine, fine, Iâ€™ll find you the kitten movie.
I don ‘t pretend to have tested all these solutions, but I am gathering as best I can fixes for grid plugin incompatibility so we can all upgrade Grid without issues!
(being updated as testing progresses)
First: Grid Updates
WowAce seems to have the latest version of Grid before Curse, but it ‘s an alpha.
Tested Working Release Versions
Ones that I have had occasion to test, not exhaustive list.
- GridSideIndicators (now updated and working)
- GridStatusHealTrace (wewt, was not working before)
- GridStatusSelf (newly updated! 6/30)
Alphas & Betas of Plugins:
If you are having a problem with plugins, try downloading their most recent versions, though alphas or betas, from wowace. If you ‘re not having a problem, then, uh don ‘t. The release versions may still work (have not tested EVERYTHING).
- Gridstatuslifebloom (curse.com ‘s is a year old). Source: Comment on Grid Entry on Curse.com (that it totally works with new grid)
- GridStatusMending (curse.com ‘s is also a year old) Release version broken. Alpha is Murloc Parliament Tested and approved!
- GridStatusRes Release version broken. Alpha is Murloc Parliament Tested and approved!
- GridStatusSelf Release version broken. Alpha is Murloc Parliament Tested and approved!New Release version 6/30!
Recently updated, it works now. Murloc Parliament Tested and approved!
Open up GridSideIndicators.lua and put the following text as the first line:
local GridFrame = Grid:GetModule(â€œGridFrameâ€) Workaround is no longer needed since the module has been updated.
Source: Kurn ‘s Corner
Open up GridStatusPWShield.lua and:
1) Remove Line 3 (RL = …), you don’t need it and it may cause errors.
2) Add beneath or above Line 7: local GridRoster = Grid:GetModule(“GridRoster”)
3) Change the line with GridStatusPWShield = GridStatus:NewModule(…) to the following:
GridStatusPWShield = Grid:GetModule(“GridStatus”):NewModule(“GridStatusPWShield”)
Murloc Parliament Tested and approved!
Source:on GridStatusPWShield Entry on Curse.com
I will continue to update this as information comes in. Please help by posting any additions or links in the comments and I will edit the information into the post.