I'm currently writing something up. I'd like to claim a single system in the NorthWest area. Preferably far from other systems.
SocialEvaluation_Team.log
admin:: MRSProjLead07
perms:: MRSProperty
> A102022A > Success. Only one ORIGIN MOSHUM responded negatively to our presence with a motion akin to that of retrieving a sidearm, though no sidearm was present.
> A915AF > Failure. One ORIGIN MOSHUM has assigned an additional name to A102022A. One ORIGIN MOSHUM attempted to draw arms. One ORIGIN MOSHUM indicated potentially threatening intentions regarding MRS property. ORIGIN MOSHUM are expressing both above and below acceptable levels of comfort.
> A916AA > Success. One ORIGIN MOSHUM expressed threatening behavior, but was not armed and represented no threat. One ORIGIN MOSHUM expressed uncertainty towards MRS property and expressed a willingness to engage in self defense.
> MRSProjLead07 > Good job boys. Looks like things are above board. Make sure you’re updating your personal logs, as well. We’ll be using your personal opinions to shape how we direct independent missions in the future. I’ll report your progress to 00 and the BOD.
Friends.log
admin:: MRSProjLead07
perms:: A102022A
NF:: Mavriq d’Agenais:: “First Lieutenant”:: Male(?):: ORIGIN, MOSHUM(?), HUMAN
16AA Note:: TitleRec:: “Honorary MRS Health & Wellness Manager”
2022A Note:: Verify (?) Suffix, Update acceptable references to include “Aten”.
15AF Note:: Updating acceptable references to include “Aten” may cause Mavriq emotional distress upon the potential destruction of 2022A, please desist.
MRSProjLead13:: “Aten” acceptable reference approved by MRSProjLead13. Let A10 be his own android, 15AF. We need you three to work together. Don’t clutter Friends.log with debate. TitleRec approved.
NF:: Dario Fuertes:: “Warrant Officer”:: Male:: ORIGIN, MOSHUM(?), HUMAN
2022A Note:: Verify (?) Suffix, Individual made threatening suggestion::
Source:: RecordingTranscript.log
UNDEFINEDUSER1 hand to UNDEFINEDUSER2 shoulder. Low volume exchange resulting
UU1:: “Cognitive degeneration is a known consequence for humans on Derelict, but we don’t know how A.I. react. Do you have a, [stutter], kill command should these things go haywire?”
UU2 hand to FIREARM(?) object, low volume exchange resulting
UU2:: “Right here, Lieutenant”
16AA Note:: TagRec:: MRSPROPERTYTHREATC2
MRSProjLead00:: TagRec accepted. Threat level acknowledged. Publish Dario Fuertes bounty as your final act if he is the aggressor. Standard protocol.
NF:: Cass(?):: “Tour Guide”:: Female:: ORIGIN, MOSHUM, HUMAN
2022A Note:: Verify (?) Suffix
NF:: Vincent Marlowe:: “Software Specialist”:: MaleAugmented:: ORIGIN, MOSHUM, HUMAN, AUGMENTED
NF:: Sophia Arietta Hagiotheodorites:: “Medical Staff”:: Female:: ORIGIN, MOSHUM, HUMAN
Directive State User Interface:
[...]
Directive Updates...
5%...
90%...
100%...
Directive Updates:
— “Next Order Of Business”:: Establish operational facilities 1 and 2.:: Merge with “Operation Center”
> The A9’s body language is overly active. 15AF is continuing to cause problems or display emotions that need not be expressed for the good of the mission. He is a drag on efficiency.
Recovering MRSProjLead08_Schematic_OperationsCenter.M3D...
5%...
> Aten > We should construct using these suggested files as we have practiced.
10%...
> A915AF > The Warrent Officer may have demands for the base beyond what MRS has suggested.
> A916AA > The defensive positions in the MRSProjLead08_Schematic_OperationsCenter have a quality rating of 7.8 on the MRS Defensive Effectiveness Scale.
20%...
> Aten > The file is already recovered on the drives of B7-17094CL. I have looked at it twice and already set it to queue. There is no reason to not go with this plan.
> A915AF > Nay MRSProjLead08_Schematic_OperationsCenter.M3D
> A916AA > Yay MRSProjLead08_Schematic_OperationsCenter.M3D
> Aten > Yay MRSProjLead08_Schematic_OperationsCenter.M3D
> A915AF > When did you change your display data to match the title given by Mavriq d’Agenais?
30%...
40%...
50%...
60%...
70%...
80%...
90%...
> A102022A > I did not. Organizational error.
100%...
Greetings,
A man wishes to not be so formal, but I see an issue that I think we should address publically mainly because I would like to see where everyone stands without having to hunt through the Discord chat. With regards to these collaborations, why are afraid to write for non player characters that other people introduce? More to the point <description of eyes?> Why should we not just describe the eyes? Sure, Chrononaut might have a specific idea but this is collaborative writing, not just on the etherpad but on the forum in general. Should we not feel free to elaborate where others have left details out?
Discuss?
Directive State User Interface:
— Protect MRS Property
"MRS Property":: "Anything produced, purchased, or used by MRS. This includes you. Exclude JUNK flag.":: Definition by MRSA10ProjLead05
Priority Order:: "A10-2022" "XDFSU1" "Generalized MRS Property"
— Harvest DERELICT Metals
MRSA10ProjLead13 note:: "Do not directly interface with the artifact if you can avoid it. High risk activity."
— "Make a show for Origin.":: Unclear, please clarify directive.::"It will make sense.":: Definition by [Deleted_User_Data]
2022A note:: Have I been tampered with? Report to MRSA10ProjLead13 upon completion of “Harvest DERELICT Metals” assignment.
— Regular Report Behavior
ConditionalStateModification by 2022A:: "Breach report behavior where efficiency dictates.":: Modification Approved by [Deleted_User_Data]
— Establish Biologically Friendly Operation Center
"Biologically Friendly":: "Fitting for cold-fusion conditions.":: Definition by MRSA10ProjLead05
"Operation Center":: "Safe-zone on the artifact. Stable environment for human operations.":: Definition by MRS10ProjLead05
MRSA10ProjLead13 note:: "MRSA10ProjLead05 says that you will ask if you need a term defined. Please feel free to. Ask A915AF and A916AA, and any UNDEFINEDUSER(s) that have verifiable ORIGIN or MRS tags associated. Verify these tags independently if possible."
Directive Updates...
5%...
10%...
15%...
20%...
25%...
30%...
50%...
80%...
100%...
Directive Updates:
— “Rendezvous with ORIGIN tagged MOS Presence”:: “MOS = Maasym Orbital Station”:: Definition by OGFriend01, MRSA10ProjLead13
TAG Updates:
ORIGIN:: Friendly
MOSHUM:: AlertState
MAASYMENTITY:: ViolentState:: SecondaryDefaultTAG
UNKNOWN:: QuearyState:: DefaultTAG
> Efficiency would increase “violently” if all other units of the 2022 branch were present.
> Ahead of schedule. Update minimum efficiency score accordingly.
> Will the soldier respond or the other unnamed individual? They will not respond in the most efficient manner.
> A9-15AF > Please communicate using open channels as agreed!
> A9-15AF has been locked out of personal_record.log, A9-16AA has been locked out of personal_record.log, A10-2022A has been made ADMIN of personal_record.log
> Distractions have been removed from the personal_record that is to be kept as stated by MRS_StandardPractices.