+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery General (https://discoverygc.com/forums/forumdisplay.php?fid=3)
+--- Forum: Discovery RP 24/7 General Discussions (https://discoverygc.com/forums/forumdisplay.php?fid=23)
+--- Thread: Rule question (/showthread.php?tid=15044)
Pages:
1
2
Rule question - Derkylos - 01-07-2009
Well...as I don't say "engaging x"...does the engagement not begin anyways?...
However, tying down an inferior number of enemies with some of your ships while the rest go and get caps is kinda lame...
Rule question - Linkus - 01-07-2009
The issue in regards to firing engagements would be say, smuggling and the Navy.
I've seen people who F1 out after being stopped by the Navy/Police, not fired upon at all including by CD, being sanctioned.
Rule question - Orin - 01-07-2009
That's using ooRP game mechanics to avoid an encounter. Running away is within the game mechanics, and the no reengagement rule is only for faiplay in any case.
If you aren't fired on yet, you aren't in an engagement.
Rule question - Jihadjoe - 01-07-2009
' Wrote:Ok if you in RP state your intent to ingage a group of fighter's(all in same group) and 1 cruises away to get a cap ship(switch char's) is this breaking the fleeing/re-ingaging rule?
Being present at said event...
Titan (John Talon) was a distance away, and in the "engagement" no shots had been fired. INfact you were about 10/15k away when Titan turned around to go get a ship that could deal with your osiris.
Thus no engagement had taken place, and thus it was impossible to re-engage...
The rules state that a pvp engagement has started when one party's shield drops bellow 50% I believe.
I also seem to remember you never got within weapons range of ANY of us by the time Titan was already headed off. And you certainly never got within weapons range of him.
Might I also add I was more than a little peturbed by the fact you were just about to attack a guardian an RC and an executioner with an Osiris...
Overkill is something I have been working rather hard to combat in liberty, so having an osiris come in with the expressed intention of -nothing- but blowing up the fighters was something of a kick in the teeth.
Rule question - ryoken - 01-07-2009
' Wrote:That's using ooRP game mechanics to avoid an encounter. Running away is within the game mechanics, and the no reengagement rule is only for faiplay in any case.
If you aren't fired on yet, you aren't in an engagement.
True you are not,and as such a player who's F1's out is allowed to as the rule state's. You cannot F1 out once you are engaged. Problem is people get sanctioned for this, because once a pirate/lawful yell's that famous oh so RP word "HALT!" usually without a name. If you F1 out you get sanctioned because it is considered being engaged. So why is it different for warship's if someone declares they are attacking 3 ship's 5K away who are same ID,and same group? That is my question to the admin staff. As 1 or 2 of these ship's are allowed to run and dock, get their dread's/carrier's/BC's and come back,and it is not "re-ingaging". I myself do not see much difference. What applies to 1? should apply to all, no matter ship class, or situation.
Any admin's wish to jump in here? Please.
Rule question - Reverend Del - 01-07-2009
Ryoken you're wrong what you are sanctioned for when you f1 out is for and I quote "F1 during a player INTERACTION" not engagement but interaction.
Rule question - Fellow Hoodlum - 01-07-2009
There appears to be very little point to this as I believe no engagement ever took place. Its hypothetical
at best, and no one F1ed at anytime ... So lets get back to something sensible shall we ?
Hoodlum