Author Topic: Event Log - Message Delay  (Read 1374 times)

0 Members and 1 Guest are viewing this topic.

Offline DuraniumCowboy (OP)

  • Warrant Officer, Class 1
  • *****
  • D
  • Posts: 88
  • Thanked: 7 times
Event Log - Message Delay
« on: July 14, 2014, 09:04:06 PM »
It would be cool if there was a changeable, global variable that specified how fast messages/reports move from system to system for each empire.  Then on the event log, there would be two single character columns, one for the capital and one for the nearest sector command.  If enough time had passed for the event to be reported in either place, then there is an "x" in the column.  That way, as players/creators we can role play the time lag between reports getting to command posts and delay our responses (if we choose) to better model the lag of messages.  The report arrival indicator would have no actual effects, unless we consider maybe an option for the system to "hide" reports until they make it to a captital or sector command, although that might require some more event logs and time keeping.
 

Offline swarm_sadist

  • Lt. Commander
  • ********
  • s
  • Posts: 263
  • Thanked: 21 times
Re: Event Log - Message Delay
« Reply #1 on: July 15, 2014, 06:18:58 PM »
+1

Have the option to have communications sent throughout the empire, which can be jammed, intercepted or distorted.

Have communications at extreme range be hard to detect without advanced equipment.

Have ship's sent out far enough disappear from player control until their estimated mission time expires and they return, or have the ship be late and require investigation.

Have communications require a path to the capital through jump gates, jump tenders or communication relays.

It would be cool if this applied to NPRs as well. Attacking outlying ships without alerting the whole empire would be nice.