Shepard Quest Mk VI, Technological Revolution

We have infinite power, why aren't we using lasers?

Or are they really that much greater of a heat producer?
The Cabira (planned release date 2175-Q4) is a stealthed (via Total Internal Reflection shielding, reactionless Repulsor drives and multi-core eezo FTL system) GRASER frigate that has external docking ports for fighter wings (either 4, 8, or 16 fighters, depending on how large fighters are; that still seems fairly vague). They're basically dreadnought-killers.

That's also the first quarter we can realistically expect to have a Starships-specialized Space Factory III up and running as well, so we'll be able to really crank them out too.

Planned future upgrades include missiles, and for that matter MACs, that shoot black holes; we'll have those in 2176-Q2. After that? Eh; we can go with @Ramble's wave motion guns and max out on the Repulsor canon tree.
 
Last edited:
Special Event Part 2 and Update I Forgot
Special Event Part 2 and Update I Forgot
2173-Q4


That Thing I Forgot:

[X] Start writing those papers on Liara's artifact and what you gleamed from it, empathizing the differences between its technology and yours. Embelish Liara's role - make it look as much as possible as her discovery with your minimum help; this way it would look less like you inventing evidence.


"It's amazing!" Liara exclaims to you, her exuberance overflowing. Her cheerfulness is infectious even over the comm.

"We fabricated a copy of the tool you developed and the device turned on immediately when we used it!" for a moment there is a minor dip in her mood, "most of what was there was corrupted. But! We got one file to work and... It was like a SimulStim, recording. A Prothean's memories recorded and stored for millenia! I'm not entirely sure how the device could even project the memories to me, SimulStim normally requires calibration even for an Asari. Its something to look into later...

"Anyway, I used a simstim rig to make a recording of the memories that could be shared. I'll send you the file! The actual memory is very interesting. Even if one only got the first few seconds it tells us so much! We get to see what an actual Prothean looks like. No one knew what a Prothean looked like before this, we even get to see some other races from that time!

"That's not the best part though! The memory is directions of some sort, sort of a chain of memories of places. I think you're meant to follow the places remembered, like a treasure map or something. The last memory shows a cave. And in that cave..." Liara pauses for dramatic effect, "Is a box!"

"A box?" you encourage her to continue.

"Yes a box!" she says with a smile, "From what little I can tell . It a very sturdy box meant to resist the passage of time. Sort of time capsule like. Whatever it is may still be there, intact."

"That could be interesting, any chance of actually finding it?"

"Well one of the memories shows the stars, and working from there I determined that the location wasn't on Altahe. But instead is on Intai'sei."

"Hmm... Intai'sei, hot, arid, human colonized near-garden world?" You ask looking up the planet.

"Yes that's the one. This dig should be concluded in about a month. I would love to go looking there next." Liara says longingly, "Who knows what could be there?"

"Something to think about in the future. More immediately is there anything else?"

"Well yes, I have written up a few papers using what we've found. I'd like you to look over what I have on the device and the tool you developed. I've also...," Liara looks actually unhappy for their first time during the call, "made a trimmed down version of the memory for the papers that makes it so that no one can find out about the box. A prize like that would be snapped up quickly. People will find out once the artifacts are studied more, but it'll delay any looters."

"Sensible if unfortunate." you say, "I'll get on that paper then."

Possible Company/Personal Action, Treasure Hunt on Intai'sei
Dig final results next quarter!


L-l-l-l-l-look at you, hacker!
[X] ...put my suit on then...
-[X] ...counter the hacker

[X] Bring PI security to full alert in all PI facilities. All power armor teams are to suit up. Defenses are to be warmed up. Non-combat personnel are to be evacuated to shelters immediately.

[X] Initiate full server isolation (as in no power, all connections are to be physically cut if need be, do not leave a single route of attack against the database) for research servers. Security is essential in keeping online, but no need to give potential attack route to PI research database. Send security teams to sweep the facility for potential infiltrators.
-[X] If power can't be cut for some of the servers for some reason (such as sensitive data only present in energy dependent memory, or long-term calculations in progress), at least cut connections.

[X] Alert Mindoir militia and System Alliance forces that a hacking attack is occurring against PI and that a physical attack is highly likely.

[X] Security teams are to move to critical locations. (Security sector, armories, research databases, etc)

[X] Researches who need to save all files before going to safety have dibs for the shield belts in laboratory storages. Gaver Dor is allowed to charge his guns.


With a thought you send a message to security, bringing them to full alert. Security sends out quite alarms and notifications across the Paragon Industries compound. A second message orders the shut down of the research server. Hopefully no important data is being manipulated.

Dumb luck roll: 1D100=>11 Nope nothing important.

That should keep things safe. A final command sends teams to check the data lines showing abnormal activity. You open a mental window to watch their progress.

Security should know what to do from there. Now it's time to pay attention to your own personal safety. You quickly move over to your personal version of the Legionary. The suit is well equipped with all the latest technology you've developed. Now if only it was quicker to get on. Eh... Mk II functionality.

Current Mounted Armament:
4x Hasta Autocannons on arm mounts
2x Pilum Mk II Missile Launchers w/ 3 rounds each on side shoulder mounts
2x SMG Turrets in AMS configuration on top shoulder mounts

Change? (Will take more time)
[ ] Yes
-[ ] With what? (8 Mounts two per arm two per shoulder, any PI gear)
[ ] You're good


That aside you begin trying to counter the hacker. As you begin running programs and sorting data from the servers you keep an eye on the security teams sent to investigate the data lines. Neither team has spotted anything yet, the corridors are free of signs of forced entry nor is there anyone who shouldn't be there present. From your AR window you also notice a distinct lack of anything amiss as the teams move though the corridors. The lack of anything is worrying.

However, you are quickly forced to refocus. Who ever this hacker (or hackers) is, they are apparently very skilled indeed. As unlikely as it seems they are operating a similar skill level as your own. As quickly as you begin to run a program, the hacker notices the change in the network and starts to counter with its own. Chances are if you hadn't stepped in the hacker would have had access right now.

18D6E5=>7|ones:3 Based on the hacker's current rate you've reinforced the security server's firewall enough to last long enough for you to do one other thing.

Do you...
[ ] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)
[ ] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)

Event notes:
Security teams are concentrating at critical points, campus walls are less defended.
Drones are active and patrolling.
Turrets are online.
Non-combatants are being evacuated.
Investigating security teams have found nothing
Recon drones and sensors detect some activity elsewhere in the industrial district, no indications of hostility.
Research Server is offline.
Security Server is secure... for now.
Mindoir militia, police, and System Alliance forces have been notified, but they will not act unless hostilities or physical illegal actions occur.


-----
GM's Note: Well that took forever. I wanted this done nearly two weeks ago :(. Oh well it here now. All the usual. I'd like to in theory, depending on the rate of response resolve voting in a day or two. That way the stuff can get resolved in a timely manner. Assuming I update quickly...
 
Last edited:
[x] You're good
[X] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)


No that is our data. Bad Hacker. We can't risk losing our data.
 
Last edited:
[x] You're good
That's plenty of Dakka
[x] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)
I'd secure the situation first, then trace them later
 
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)
WHO DARES ATTACK US IN OUR OWN HOME?!
 
[X] You're good

[X] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)
I'd secure the situation first, then trace them later
 
[X] You're good

[X] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)
 
[X] You're good

[X] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)

The smart thing to do is stop them from doing what their doing. This is the easiest way.

Note to self, Buy/Build exceptionally old computer (Something with vacuum tubes) that nobody could use or hack into for intern-sec.
 
@Hoyr, what data and computer(s) are vulnerable here? From what I understand, the original situation was that we had two simultaneous attacks going on: the research mainframe and the security server. So am I right in assuming that, now that the research server is offline, we do not have to worry about any (more) of our research being stolen, and at this point all we have to worry about is a security server being sabotaged?

If that's the case, then there's no reason not to try back-hacking the hacker; at the worst he will bring down the security server, which is the other option here.
 
@Hoyr, what data and computer(s) are vulnerable here? From what I understand, the original situation was that we had two simultaneous attacks going on: the research mainframe and the security server. So am I right in assuming that, now that the research server is offline, we do not have to worry about any (more) of our research being stolen, and at this point all we have to worry about is a security server being sabotaged?

Your research server has gone dark as your ordered it to. So it's safe from electronic hacking.

Whats mainly at risk is the security server. So the thing that controls lovely things like comms and E-war systems, can effect turrets and drones, open doors, etc. You know security stuff.

So what you said.

Edit: Data line in this case is basically being used as a generic term for a type of high though put network cable. Instead of calling it a Ethernet cable or fiber-optic cable or whatever they use in space future.
 
Last edited:
[X] You're good
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)


Simply defeating this attack accomplishes very little for us; they almost certainly will simply try again, and again, and again, until they succeed.

If we want to actually stop rather than simply delay data intrusion, we need to find out who is doing this, so we can nail them.

Decent odds it's actually the Geth, which could have some very interesting results if we uncover that fact.
 
[X] You're good
MILK FOR THE KHORNE FLAKES!
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)
 
[X] You're good
[X] ...terminate the data line. (lose the services of some of the security computers, hacker is no longer able to use that access point)
prepare the remaining security computers to repel hackers.
 
If that's the case, then there's no reason not to try back-hacking the hacker; at the worst he will bring down the security server, which is the other option here.

Wait a minute. I think I've detected a possible miscommunication (yay internet)!

The other option only knocks offline a few computers on the security network (that's why I said "some"). The main server and most of the system would still be working, just everything operating off of the compromised cable/line would be offline.

It not a big loss really. A few employees may have to switch terminals or something and there maybe a few minor hiccups as the system compensates for some lost hardware.
 
Last edited:
[X] You're good
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)
 
[X] You're good
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)
 
[X] You're good
[X] ...hack the attacker back. (May gain intel on hacker, success will delay hacking)

Note to self, Buy/Build exceptionally old computer (Something with vacuum tubes) that nobody could use or hack into for intern-sec.
Anything can be hacked. The only way to prevent something from being hacked is to remove all methods of input.
 
Back
Top