![]() |
|
Rule 6.7 - Printable Version +- 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 6.7 (/showthread.php?tid=62249) |
Rule 6.7 - Anonymous User - 06-27-2011 http://discoverygc.com/forums/index.php?sh...=102621&hl= Quote:6.7 Attacking freighters, transports, liners or demanding cargo from the same is not allowed for cruisers and battleships. EDIT: + add to all IDs which can have caps: "Cannot escort traders in a Capital ship" to j): pirate transport pirates for example USI in front of liberty dread (no matter indie or official)... pirate transport gets blasted to k): transports shoots one of a group of players -> whole group is free to pew him even if they are caps (we already are allowed in "self defence" but why not add it + allow our allys/friends as well) why? this is freelancer discovery ROLEplay not ruleplay. would be totally inRP to be able so. Just a idea to solve the ooRP abuse pirating transports do here and there. Rule 6.7 - Fletcher - 06-27-2011 Sure makes sense. Rule 6.7 - Hielor - 06-27-2011 K) would allow cruisers and above to pirate by being present while a smaller vessel is doing the actual demand. Then, when the trader shoots back at the smaller vessel, the cruiser/whatever blows up the trader. J) is meh. I think it should be that lawful caps should be able to make an RP demand of unlawful traders, and if they don't comply, they can shoot. How about just: Quote:Cruisers and battleships may not demand cargo or credits or be involved in a demand for cargo or credits. However, they may make RP demands (e.g., "leave the system" or "leave that trader alone") and open fire if the transport fails to comply. This allows lawful caps to protect traders, but still prevents caps from being used for piracy. Rule 6.7 - Anonymous User - 06-28-2011 ' Wrote:This allows lawful caps to protect traders, but still prevents caps from being used for piracy. we also have to prevent caps used as escorts Rule 6.7 - Python 72 - 06-28-2011 My vote goes for Hielor's point. Although yet again abuse could occur, when Transport is given unreasonable demand by Cruiser, so transport says no. Then Cruiser is 'justified' in attacking, and can take cargo. Rule 6.7 - Anonymous User - 06-28-2011 ' Wrote:K) would allow cruisers and above to pirate by being present while a smaller vessel is doing the actual demand. Then, when the trader shoots back at the smaller vessel, the cruiser/whatever blows up the trader. i change that to: ""k) Transports/Freighters who engaged you or a allied/friendly vessels in sight can be shot.."" RP demand/piracy = engage soo..... /edit: fixd bad grammar Rule 6.7 - Python 72 - 06-28-2011 Would it be possible to define lawful vs unlawful cap ships, and make the definition there? Then the lawful caps will be bound by their RP anyway, so wouldn't be able to pirate. Rule 6.7 - Anonymous User - 06-28-2011 lawfull forces cannot pirate anyways http://discoverygc.com/wiki/index.php/ID who is lawfull or unlawfull can be seen here for example Rule 6.7 - Arashi - 06-28-2011 Should have put an "Other/Alternate" option for those that think the rule's need to be changed/updated but didn't agree with how you proposed the points. I agree a pirate, that pirates within local comms range of a capitol ship is asking to get blasted by said capitol ship. How to re-write the rule to deter abusing it as much as possible is the real question. I've made such suggestions before, as I'm sure many have... It's really up to the Dev/Admin Team, to propose the change, otherwise this is just another poll that will turn into a flame thread as the traders vs the pirates start arguing in their own favor. Rule 6.7 - Python 72 - 06-28-2011 So then making a rule based on this, IE anyone with appropriate Lawful ID in a Cap can engage if justified by RP, it could work. Course, you would still need the exceptions like Outcasts in Alpha, but i cant see a problem there. |