Not every roleplay situation or interaction will be entirely player driven.
World events, faction leaders, holidays, and quests are all potential roleplay sparks. But given the “whole world” aspect of such events and characters, there are some things that you’ll want to avoid when you’re picking up that kind of roleplay though, usually where it starts to impact things that are out of your character’s control.
(There’s been a lot said about claiming relationships with NPC’s in your backstory, so I’m going to leave that part alone.)
Say you want to write a story set in Icecrown, about the Argent Crusade. It’s possible that Tirion Fordring might make an appearance in your fic somewhere – after all, he is the leader of the Argent Crusade. If you hang around there long enough, you just might see him! And, since he’s a charismatic leader, it’s not out of the question that your character might drop him a salute and have him smile and salute back, or say something encouraging. Tirion’s a nice guy, you know. Even if he is a badass too.
Where you run into trouble is if your story forces weakness on Tirion Fordring without his or Blizzard’s “consent.” If your character is a disillusioned old soldier and hates Tirion, and they charge into the Argent camp like a madman screaming challenges for a duel – which he accepts and then your character beats him soundly and injures him? That pushes the envelope too far, for a number of reasons. Tirion’s essentially a faction leader. He’s got guards. Someone running in screaming like a madman would be forcibly removed as a threat to his safety not allowed to run loose, let alone allowed to challenge him in a duel. And then to assume that your character is such a badass that they would beat him up and win?
There are a number of problems with this, not just in that you’re kind of pulling a “I beat up a lore character so I’m awesome”.
Those NPCs are there for everyone; Blizzard writes them, and all of our characters interact them. If your story backs one of those NPCs in a corner and forces some form of action/response/whatever on them or their organization, that story is now influencing the RP that everyone else has, and creating a situation that will cause conflict for every new RPer you encounter. If you have to explain to every single character that you run into that “No, Sylvanas really isn’t the leader of the Forsaken anymore. That guy Jimbob over there killed her last year,” you’re probably doing it wrong.
What’s the solution then, if you need a fall guy?
Write your own.
An NPC that you create or make up has no such complications. People write up, characterize, and then kill off/torture/do horrible things to their own personal NPC’s all the time. The difference is that YOU create these characters, and ultimately control them. They have no bearing on other players.
Once you start creating NPCs, it becomes kind of addicting! You’ll want to keep a list of who you’ve created (and who’s been killed off). That’ll help you manage where NPCs are at any given time, and help you remember which is truly a badass NPC and which is just a foil or a fall guy for someone else.
Blizzard creates and controls their own NPCs, and as such, you can’t just up and kill them. Or take their place. Or beat them into a bloody pulp and make them unable to do their jobs. How does this actively affect your RP?
Let’s take an example from my own RP:
Bryan and Elizabeth Cross, the proprietors of The Silver Shield in Old Town.
The Silver Shield – as a shop – exists. Bryan Cross is a Blizzard controlled and written NPC as a sheildmaker and blacksmith. Aely rents an apartment underneath their shop. If something were to happen in that shop, Bryan Cross couldn’t be harmed in a way that would make him unable to do his job… because he’s still there in Stormwind. I couldn’t kill him, or cut off his arm. (And I especially couldn’t get mad when someone else brought up that Bryan Cross was standing in his shop selling shields, because OMG I KILLED HIM NO HE’S NOT.) When I write things about Bryan Cross, he’s doing blacksmithy or shieldmakery things – or he’s being a responsible shopkeeper that’s looking out for his and his family’s interests.
His wife, on the other hand, is entirely fictional. Elizabeth Cross exists only in my RP and in the RP of people that choose to use her in their stories. If something terrible came of Elizabeth Cross, it wouldn’t affect other players at all. Should a story demand it, she is, essentially, disposable – not that I’d ever want to get rid of her. I rather like Bess Cross.
But anyway, I think that illustrates the point pretty well.
It all basically boils down to this: Blizzard NPC’s doing relatively ambiguous things consistent with their roles as NPC’s are fine in roleplay.
Matthias Shaw is a sneaky bastard without a lot of scruples – having him do sneaky scruple-less bastard things in a fic is pretty consistent (though it’d probably make more sense to make up a henchman of his). Varian Wrynn has a temper when it comes to Orcs. Thrall ultimately seeks peace for Azeroth. When you take NPC’s out of those roles and force them into your story (particularly as a way to increase your character’s Absolute Badass Value), you start to get into the realm of lorebreaking.
So use Blizzard’s NPCs wisely. They’re there as “untouchable” leaders for a reason; they’re the consistent thread that holds this world together. Taking them out, putting them down, and reducing their influence isn’t a particularly good way to get your point across, because it forces your story to be accepted (or rejected) by other players.
Write your own NPCs instead! And always be aware of the laws of Absolute Badass Value (if you’ve not read that post, you really should). Your fellow RPers will thank you!
- Godmodding and Griefing (116)
- On Privacy, Real ID’s and Roleplay (49)
- XX and XY in RP (47)
- Population Disparity (34)
- Tanking Perceptions (33)