• Home
  • Index
  • Search
  • Download
  • Server Rules
  • House Roleplay Laws
  • Player Utilities
  • Player Help
  • Forum Utilities
  • Returning Player?
  • Toggle Sidebar
Interactive Nav-Map
Tutorials
New Wiki
ID reference
Restart reference
Players Online
Player Activity
Faction Activity
Player Base Status
Discord Help Channel
DarkStat
Server public configs
POB Administration
Missing Powerplant
Stuck in Connecticut
Account Banned
Lost Ship/Account
POB Restoration
Disconnected
Member List
Forum Stats
Show Team
View New Posts
View Today's Posts
Calendar
Help
Archive Mode




Hi there Guest,  
Existing user?   Sign in    Create account
Login
Username:
Password: Lost Password?
 
  Discovery Gaming Community Discovery General Discovery RP 24/7 General Discussions
« Previous 1 … 242 243 244 245 246 … 779 Next »
OoRP chat

Server Time (24h)

Players Online

Active Events - Scoreboard

Latest activity

Pages (3): « Previous 1 2 3
OoRP chat
Offline SA_Scavenger
04-01-2012, 02:17 PM, (This post was last modified: 04-01-2012, 02:18 PM by SA_Scavenger.)
#21
Member
Posts: 1,252
Threads: 36
Joined: Oct 2010

' Wrote:Should be pretty much all reports. Getting enough commentary on all reports can be quite time consuming.

In any event, using // at any time in system chat is sactionable. Period. You guys know that there is a way, in RP, to actually ask permission to rejoin, don't you?

Seriously - just use your imaginations.

"Open channel. This is the <ship that just disconnected>."
"We just experienced a total power failure that caused us to vanish from your sensors, due to our reduced electronic signature."
"Request permission to rejoin the furball" - or "Our apologies if it appeared we were attempting to be sneaky and confuse your sensor techs."

Wow - what a thought. Actually role-playing the d/c...

And of course, if it's a smaller combat, simply PM the person involved AND make sure you make a post in the 'Oops, I disconnected' thread as a CYA in case they don't accept your apology.

I would say all of the above is fine. On the new player front it always helps to inform them of their mistake before reporting. Then again, not everyone understand the: "Excuse me pilot, but your communications array is malfunctioning as I'm getting strange incoherent 'white noise' coming from your direction. Would you mind getting your communications officer to fix it as soon as possible? Thank you."

Most of the time they ignore you or simply don't understand your use of RP and therefore the only way to get them to stop using OORP is to either break the rule yourself or PM them with a // informing them of their lack of INRP.

Still, a single line of OORP really shouldn't result in a report. It's when they don't respond to warnings or help and continue their OORP conversation that one should think about filing a report.

[Image: tycusdekker.png]
  Reply  
Pages (3): « Previous 1 2 3


  • View a Printable Version
  • Subscribe to this thread


Users browsing this thread:
1 Guest(s)



Powered By MyBB, © 2002-2025 MyBB Group. Theme © 2014 iAndrew & DiscoveryGC
  • Contact Us
  •  Lite mode
Linear Mode
Threaded Mode