Reporter Issue 2: Difference between revisions

← Older edit

Reporter Issue 2 (view source)

Revision as of 19:03, 15 May 2020

1 byte removed , 15 May 2020

m

spare [ removed

Ceciri

7,850

edits

Revision as of 23:09, 24 April 2020 (view source) Rich (talk \| contribs) (math) ← Older edit		Latest revision as of 19:03, 15 May 2020 (view source) Ceciri (talk \| contribs) m (spare [ removed)
Line 9:		Line 9:

	==FROM STARBASE 118==		==FROM STARBASE 118==
	UFOP has decided to be more interactive, that is, to have our ships interact with each other and otherwise behave more in sync. Therefore, we need to add another rule. If a simmer wishes to be assigned to more than one ship, they must create a new, separate character for each ship. That way, ['''Android Dan''' on the '''Centris''' and '''Android Dan''' on the '''Isannah''' don't ever have the perplexing situation of meeting each other on an united mission. If you have one character on more than one ship currently, please write Admiral Wolf to correct the problem. If you have any questions about this new policy, please feel free to write me.		UFOP has decided to be more interactive, that is, to have our ships interact with each other and otherwise behave more in sync. Therefore, we need to add another rule. If a simmer wishes to be assigned to more than one ship, they must create a new, separate character for each ship. That way, '''Android Dan''' on the '''Centris''' and '''Android Dan''' on the '''Isannah''' don't ever have the perplexing situation of meeting each other on an united mission. If you have one character on more than one ship currently, please write Admiral Wolf to correct the problem. If you have any questions about this new policy, please feel free to write me.