Shensenn Site Admin
 Karma: Add Karma

Joined: 21 Feb 2006 Posts: 4671
Location: In a pineapple under the sea.
|
Posted: Tue Jul 31, 2007 10:56 pm Post subject: Guide to RPvP and the Immersion War |
|
|
RPvP…What is it?
Roleplay Player vs Player, or RPvP as you will see it, is simply a Player vs. Player combat system in which Roleplay has to be the determining factor before any combat takes place.
For example: Joe drops his Rebel ID in the local cantina and Bev at the bar notices and reports him to the local authorities. A stormtrooper, played by Jim, approaches and questions Joe. Joe does not cooperate and is smacked around a little using /emotes. Joe has had enough and opens fire on Jim
Now we have PvP, initiated by RP. In RPvP, there always has to be a valid RP reason to attack another player.
What is the Immersion War?
In order to add realism and accountability to our RP, all of the guilds within our community have agreed to what we call the Immersion War. Simply put, all of the RP guilds within our community are constantly at a state of war using the guildwar system. Because of the RPvP guidelines we follow (as stated above), red does not equal dead, it simply allows the RP to flow to the PvP part without breaking the immersion of the moment. We are all warring in order to increase our RP immersion. Our guilds have been participating in the Immersion War for over a year now and it is working wonderfully.
Miscommunication does happen and accidents happen, but we are all mature enough to work through these times.
Rules of Engagement:
Rules of Engagement are twofold in a sense.
First, you must be RPing and the RP situation is what leads to any open conflict. This isn't one of the PvP Guildwars/shoot on sight scenarios. On the flipside, your "opponent" must also RP to the point of open conflict as well, therefore giving you the "thumbs up" to enter into combat. Sometimes the lines here can get a little blurry depending on how the RP is going, so as a rule of thumb if you aren't sure either a)send a tell and ask them if it's cool or b)be on the safeside and do nothing.
Second scenario is if you are playing a bounty hunter and have an open bounty on said person then you can shoot on sight to collect the bounty. No one typically wants their character killed off so we have to assume a successful bounty is either a capture or the acquisition of information from that person.
Another example of acceptable "Shoot on sight" would be a planned tactical ambush of an Imperial/Rebel patrol or group. Again the events leading up to the ambush or battle should be RPed, ie: How do you know they are Rebels/Imperials? What are the motives & goals for the attack?
It also goes without saying that crafters/entertainers should not be fired upon since they are probably someone's alt and will not usually be RPing themselves into deadly encounters.
Finally, be aware of where you're aiming/clicking. Accidental weapons discharges sometimes happen - especially when this first goes on and everyone is getting used to it, but be cautious and aware of what you are targeting. If you accidentally shoot at someone or blow up a vehicle you should immediately send a tell or some OOC chat apologizing and offering to get a repair kit if needed. Now if it is a bounty mark running to the speeder then by all means blow that sucker up (in that case there is a justified RP reason for doing so). I'd still probably offer a repair kit, but that's just me.
The most important thing of all is communication. Talk things out before/during/after and determine if everything went as expected. Were there any problems? We want everyone to enjoy this and have a good time and if anyone walks away feeling abused or like they hate this then we need to know and talk it out.
If you are sent to the cloner or just incapped (some people still won't db) you should leave the area immediately to "recover" and should not return for at least a couple of hours - otherwise it just doesn't flow very well:
Turning from my drink I notice a familiar face at the other end of the bar enjoying a jawa beer.
"Hey didn't I just blast that guy and send him to the bacta tanks a couple minutes ago?"
I certainly can't dictate every scenario that may come up during this and wouldn't try, so use your best judgement, RP, and good communication. In the interest of fun and fairness don't be afraid lose, either. You'll have your good days and your not so good days, but if it keeps everyone feeling happy and having fun, I'll take a dive now and then.
Attack on Sight
When it is ok to attack on sight?
Rebel and Imperial Armor: Imperial armor is well, Imperial armor, this also goes for the officer uniforms. You are announcing your faction, be prepared to defend that.
Rebel armor has (I believe) a Rebel emblem on each version. Consider that same as dressing up in stormie armor. If you are visible in this armor prepare to be attacked by Imperial troops if they see you.
Bounty Hunting: If you have a mark on you listed in the (soon to be) Bounty forum, be prepared to be attacked at any time.
Clothing other than any listed above should be considered as normal everyday citizens, including Jedi robes. If you're an Imperial and you have been ordered to detain any Jedi, you can't start shooting everyone in a robe.
Lightsabers: If you walk around showing off your glowstick, activated or not, chances are you will be labeled a Jedi, and get unwanted attention. Perhaps in certain situations it would be better to have the lightsaber tucked under that moisture farmer robe.
Of course, walking into any establishment with a weapon drawn might get everyone nervous and reaching for their sidearms. Having a weapon equipped could also be considered a statement that your intentions could be aggressive.
Imperial, Neutral and Rebel wanted lists: We have started a Rebel wanted list, and that person stated how other factions will react to them. As we get deeper in faction play I think an Imperial list would work as well, persons that the rebels would recognize as important figures in the Imperial chain of command and that would also drawn interest if seen by a group of Rebel troopers. Same goes for neutrals, depending on who they tend to align themselves with.
Friends & Foes
When adding guilds to your Guild War list, ALL guilds should be added, whether they are your current ally or not.
Why?
• Free flowing RP has changes that can be unforseen, a betrayal of a person or a guild may break alliances, waiting on people adding and removing each other from the Guild War list wouldn't allow for the RP to continue until this was done.
• Friendly Fire is a risk during war, although it would not be true friendly fire, as you cannot attack your own guildmates by accident, it does make people think through certain area attacks so that an ally isn't acidentally attacked.
• Think before shooting, now that red dot on your radar may not be an enemy, now that radar is not so important anymore, because not all the red dots are possible enemies.
Deathblow in RP
Death Blow in RPvP will be used only when Roleplay is not to be continued after the fight, or if the target is not meant for capture or continued RP after the fight has concluded.
2 People involved in a fight might have different intentions once the fight is over. For example, if I am a Bounty Hunter, hired to capture a mark, I would choose not to DB if I incapped the target. But if the target was to incap me, then they would more than likely DB me in order to escape the encounter.
Large RP Battles: Death Blow can be used to clear the battlefield. Once you have been death blowed you have been removed and may not return to the battle, unless it has been specified differently before hand.
All death blows should be considered end of current RP, with the person who has been DBed considered injured and unable to return to the fight they were in. The person may not return from the cloner to attack the target again, as well the person who DBed cannot head to the cloner to attack that person again. The DB'er or the DB'ee may request return for continued RP in the event the DB was accidental - it happens.
Currently the only penalty caused by a DB is cloning sickness, if decay or another penalty is put in place we may change the above guidelines.
NOTE: Since this is still brought up from time to time I will restate it again. DB does not equal permadeath. YOU are the only person who can permadeath your character. _________________ Forum guarded by Blast Cannons three days a week. Guess which days.
 |
|