Protein Receiver / Discussion

This is the discussion related to the wiki page Protein Receiver.

borkman 24 Oct 2010 05:03

Got a new message on use:

You can see some of the reasons your samples break down when exposed to air so quickly. You should be able to preserve them a bit better now.

It doesn't make a lot of sense, but looking at the analysis there isn't any question: despite not being poisonous, the serpents have active venom glands. If you can extract them somehow, they're probably good for something.

I was able to extract glands after receiving this.

Magnifico 03 Nov 2010 23:40

I seeded 30 opponents before using a receiver for the first time, and received what look like 3 unlock messages and then the one about having mined this vein pretty deep.

I got the three messages in this order: samples breaking down, venom, barely break food down. If the last one increases the drop rate of partially digested fish, it seems anticlimactic to get that after the one that lets you get serpent venom glands. Maybe there are other interesting things to be found in their stomachs? Or is the order of the messages random?

EDIT: I think one of these results (maybe the last one?) is giving me an additional 2 XP in Perception for beating a Terrible Serpent.

Last edited on 04 Nov 2010 13:55 by Magnifico Show more

Striper 01 Dec 2010 16:56

Just a thought on this, but after getting the "Mined Pretty Deep" message has anyone tried contacting the Dr. who was researching the serpent in the first place?

---

Every once in a while Declare Peace. It confuses the H*ll out of your enemies.

Magnifico 01 Dec 2010 18:48

Dr. Myers has nothing special to say if you talk to him after getting that message, not even if you have a serpent venom gland you could show him.

bigalphillips 25 Aug 2012 19:25

I've been checking when the messages show up:

"Break down in air": 7-9 seedings
"Active venom glands": 15 seedings (6-8 more)
"Serpent's stomach": 22 seedings (7 more)
(more to come)

Full log:

+ show block

(1) You slip some code into OmniTech Autodefense, forcing it to analyze a small section of the protein database.
(2) You request OmniTech Autodefense analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(3) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 2 Memory damage.

Unfortunately, nothing pops up that you don't already know.

(4) You slip some code into The Gatekeeper, forcing it to analyze a small section of the protein database.
(5) You request The Gatekeeper analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.
(6) You request The Gatekeeper analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.

Unfortunately, nothing pops up that you don't already know.

(7) You slip some code into The Gatekeeper, forcing it to analyze a small section of the protein database.
(8) You request The Gatekeeper analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.
(9) You request The Gatekeeper analyze the protein more, causing it to freeze up a bit and take 2 Memory damage.

You can see some of the reasons your samples break down when exposed to air so quickly. You should be able to preserve them a bit better now.

(10) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(11) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 2 Memory damage.
(12) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 4 Memory damage.

Unfortunately, nothing pops up that you don't already know.

(13) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(14) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 4 Memory damage.

Unfortunately, nothing pops up that you don't already know.

(15) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.

It doesn't make a lot of sense, but looking at the analysis there isn't any question: despite not being poisonous, the serpents have active venom glands. If you can extract them somehow, they're probably good for something.

(16) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(17) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 4 Memory damage.
(18) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(19) You request Password Lock analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.

Unfortunately, nothing pops up that you don't already know.

(20) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
(21) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.

Unfortunately, nothing pops up that you don't already know.

(22) You slip some code into Password Lock, forcing it to analyze a small section of the protein database.

There are a few proteins in the serpent's stomachs that should preserve anything they've eaten. If these results are right, they barely break the food down at all. Huh.

bigalphillips 10 Aug 2013 23:14

1 You slip some code into the virus, forcing it to analyze a small section of the protein database.
2 You slip some code into the virus, forcing it to analyze a small section of the protein database.
3 You slip some code into the virus, forcing it to analyze a small section of the protein database.
4 You slip some code into the virus, forcing it to analyze a small section of the protein database.
5 You slip some code into the virus, forcing it to analyze a small section of the protein database.
6 You slip some code into the virus, forcing it to analyze a small section of the protein database.
7 You slip some code into the virus, forcing it to analyze a small section of the protein database.
8 You slip some code into the virus, forcing it to analyze a small section of the protein database.
9 You slip some code into the virus, forcing it to analyze a small section of the protein database.
10 You slip some code into the virus, forcing it to analyze a small section of the protein database.
11 You slip some code into the virus, forcing it to analyze a small section of the protein database.
12 You slip some code into the virus, forcing it to analyze a small section of the protein database.
13 You slip some code into the virus, forcing it to analyze a small section of the protein database.
14 You slip some code into the virus, forcing it to analyze a small section of the protein database.
15 You slip some code into the virus, forcing it to analyze a small section of the protein database.
16 You slip some code into the virus, forcing it to analyze a small section of the protein database.
17 You slip some code into the virus, forcing it to analyze a small section of the protein database.
18 You slip some code into the virus, forcing it to analyze a small section of the protein database.

You load up the receiver on your comm and run it to see what might be hanging out there.

You can see some of the reasons your samples break down when exposed to air so quickly. You should be able to preserve them a bit better now.

It doesn't make a lot of sense, but looking at the analysis there isn't any question: despite not being poisonous, the serpents have active venom glands. If you can extract them somehow, they're probably good for something.

There are a few proteins in the serpent's stomachs that should preserve anything they've eaten. If these results are right, they barely break the food down at all. Huh.

There we go, the whole thing is nice and orderly now. For a creature as strange as that one, it's interesting how little is actually going on in its body.

Huh. You're not sure why you didn't notice it before… past the simple protein signatures, there's a pattern burning its way through.

It's hard to say what it means, but damned if it's not interesting.

You've mined this vein pretty deep. If there's anything else to learn about these critters it's through hands-on experience and not protein analysis.

18 viruses seems to be enough for serpent pattern at least.

Magnifico 11 Aug 2013 00:36

It's possible that the seeded sites are global rather than per player. I had seeded 11 sites and 8 defenders over the last two days but didn't have time to play and finish the job. So it's possible that it only took you 18 because you snaked a bunch of my data, you big jerk. :P

I suppose I could check by using a receiver and seeing what I get, but I just took a load of stimulant dust so my Body wouldn't cap at roll (since I was anticipating another hacking session), so getting another serpent sample to make a second receiver will be jitter-inducing. Oh well, such is the burden of SCIENCE. I'll report my findings when I can.

EDIT: I used a receiver and only got three facts, the last being that the serpents hardly break down food. Well, better than the zero facts I was expecting/fearing.

Last edited on 11 Aug 2013 02:24 by Magnifico Show more

Vholes 24 Dec 2013 07:48

+ show block

You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
You slip some code into The Gatekeeper, forcing it to analyze a small section of the protein database.
You slip some code into OmniTech Autodefense, forcing it to analyze a small section of the protein database.
You slip some code into OmniTech Autodefense, forcing it to analyze a small section of the protein database.
You request OmniTech Autodefense analyze the protein more, causing it to freeze up a bit and take 3 Memory damage.
You slip some code into OmniTech Autodefense, forcing it to analyze a small section of the protein database.
You request OmniTech Autodefense analyze the protein more, causing it to freeze up a bit and take 4 Memory damage.
You slip some code into OmniTech Autodefense, forcing it to analyze a small section of the protein database.
(Infected 5 sites using the echo chamber with a protein seeder equipped, but there was no analyze message.)
The system crackles with new activity as your protein seeder goes to work. (level 1 site)
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
The system crackles with new activity as your protein seeder goes to work. (level 3)
The system crackles with new activity as your protein seeder goes to work. (level 1)
The system crackles with new activity as your protein seeder goes to work. (level 1)
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
The system crackles with new activity as your protein seeder goes to work. (level 2)

used receiver: expose to air, venom glands, barely break down food (only one stage left to go)

You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
The system crackles with new activity as your protein seeder goes to work. (level 2)
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
You slip some code into Password Lock, forcing it to analyze a small section of the protein database.
You slip some code into The Gatekeeper, forcing it to analyze a small section of the protein database.
You slip some code into The Gatekeeper, forcing it to analyze a small section of the protein database.
You request The Gatekeeper analyze the protein more, causing it to freeze up a bit and take 4 Memory damage.

used receiver: final message

---

In the beginning, men were mortal.

Last edited on 24 Dec 2013 08:41 by Vholes Show more