# Solutions

The other three possible Kens to be extracted were: 

1. **Normal Ken:** Though his time in the pod might have been traumatic and he might be a bit confused as to what happened to him, the team would have managed to extract Ken without ShaDAO tampering with memories.
2. **ShaDAO Sympathizer Ken:** The team would have fallen right into ShaDAO’s trap. Somewhere along the memory path, they messed with Ken’s core memories and though they might have thought they were sparing Ken from bad memories, they instead manipulated him to be sympathetic to ShaDAO. 
3. **Memory Loss Ken:** If the team had gone this path, the Ken that would have emerged from Cold Storage would have had his memory erased. Not only would he have no idea who Zinc or Spice were, but he would also have to rediscover who he himself was all over again.

Quest #6 in a metaverse (CryptoVoxels) recreation of Cold Storage, with the community trying to save Ken!

Here’s the number of players that visited each memory. Was your decision the popular choice? 

<figure><img src="https://2106229997-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcqAa14wpsQyhbBAYwRd%2Fuploads%2FPBq6JBBPsMcyt9T2xLan%2Fimage.png?alt=media&#x26;token=b3e26c18-96bd-493d-84b9-f5b264889fac" alt=""><figcaption></figcaption></figure>

Ken 1 (Memory Loss Ken): 65 (6.1%)

Ken 2 (Killer Rage Ken): 434 (41.0%)

Ken 3 (Plain Typical Ken): 167 (15.7%)

Ken 4 (ShaDAO Sympathizer Ken): 393 (37.2%)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cyberbrokers.com/user-guide/missions/alpha/qa-m06/solutions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.