Editing Talk:Vex
From Destinypedia, the Destiny wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 20: | Line 20: | ||
::::::: Alright, so why don't you type in the words Axis Mind (the way it is capitalized here) in the search. Then click on the red link. It will take you to an editing thing. Then just do like you would normally when editing. Also don't forget to add a boss template with the appropriate info. When you finish, hit save and that is all you need to do. :) [[File:Vex Logo.png|20px|stick|link=]][[User:Arcmind|<span style="color: #b30000;" title="Arcmind is an administrator.">'''Arcmind'''</span>]] <sup>'''[[User talk:Arcmind|<span style="color:#EAC117>Execute long hold for reactivation.</span>]] [[File:Hand of God.png|6px|stick]] [[Special:Contributions/Arcmind|<span style="color:#EAC117">AI-COM/ACMD SIGNOFF</span>]]'''</sup> 18:35, 30 August 2017 (EDT) | ::::::: Alright, so why don't you type in the words Axis Mind (the way it is capitalized here) in the search. Then click on the red link. It will take you to an editing thing. Then just do like you would normally when editing. Also don't forget to add a boss template with the appropriate info. When you finish, hit save and that is all you need to do. :) [[File:Vex Logo.png|20px|stick|link=]][[User:Arcmind|<span style="color: #b30000;" title="Arcmind is an administrator.">'''Arcmind'''</span>]] <sup>'''[[User talk:Arcmind|<span style="color:#EAC117>Execute long hold for reactivation.</span>]] [[File:Hand of God.png|6px|stick]] [[Special:Contributions/Arcmind|<span style="color:#EAC117">AI-COM/ACMD SIGNOFF</span>]]'''</sup> 18:35, 30 August 2017 (EDT) | ||
:::::::: [[ | :::::::: [[Axis Mind|I already did it]]. You're welcome. :) {{User:Primus Draug'oth/Sig}} 18:45, 30 August 2017 (EST) | ||
::::::::: That's fine I'm gonna edit it now or in the future anyway thank you. -- [[User:Titan66|Titan66]] ([[User talk:Titan66|talk]]) 18:46, 30 August 2017 (EDT) | ::::::::: That's fine I'm gonna edit it now or in the future anyway thank you. -- [[User:Titan66|Titan66]] ([[User talk:Titan66|talk]]) 18:46, 30 August 2017 (EDT) | ||
== | == Transformation or infection | ||
It is believed that Vex are not born or made, so much as converted. When Asher Mir was infected with Radiolarian fluid, his arm turned into a Vex construct. Kabr, the Legionless would have suffered a similar fate had he not used his Light to become The Aegis. | |||
"This mean vex mindfluid contain siva like nanobot that can convert objects into vex structure and it can also convert organic life into vex | |||
--[[User:Nittin Das|Nittin Das]] ([[User talk:Nittin Das|talk]]) 15:38, 19 April 2018 (EDT) | |||
Not nanobots. That's not what the Vex cells are. They're described as infectious as far back as Destiny 1, Ghost Fragment: Vex 4. Think of them as a cancer operating on a macroscale. --{{User:Dante the Ghost/Sig}} [[User:Dante the Ghost|Dante the Ghost]] ([[User talk:Dante the Ghost|talk]]) 15:49, 19 April 2018 (EDT) | |||
== Transformation or Infection == | |||
It is believed that Vex are not born or made, so much as converted. When Asher Mir was infected with Radiolarian fluid, his arm turned into a Vex construct. Kabr, the Legionless would have suffered a similar fate had he not used his Light to become The Aegis. | |||
(This mean vex mindfluid contain siva like nanobot that can convert objects into vex structure and it can also convert organic life into vex) [[User:Nittin Das|Nittin Das]] ([[User talk:Nittin Das|talk]]) 16:08, 19 April 2018 (EDT) | |||
== | == SIVA, the Vex, and Other Theories == | ||
I | I'm aware there are several previous discussions on this topic, but I've been thinking about this more and more and wanted to throw some ideas around for general discussion. A lot of this is speculative, but I do try and root my ideas in established lore. | ||
I | [[User:Nittin Das|Nittin Das]] ([[User talk:Nittin Das|talk]]) 16:21, 19 April 2018 (EDT) | ||
== SIVA, the Vex, and Other Theories - Chapter 1 == | |||
SIVA | |||
Origin | |||
We know that SIVA was created by Clovis Bray during the Golden Age and that its initial purpose was to be used as a universal resource for colonization, the idea being that it can be used to create anything necessary during colonization efforts of different worlds. | |||
It's worth noting that at the same time SIVA was being investigated and developed, a separate project was being worked on by Dr. Bray's teams to use nanotechnology to enhance the strength and intelligence of test subjects, but was scrapped due to unforeseen consequences. Focus was then turned solely to developing SIVA instead. This was discovered by Owl Sector during the Transmission incident. I believe this is at least partly important to connecting the dots, but it is where I'm going to speculate. I'll save the rest for later. | |||
Nature | |||
Essentially, SIVA is nanotech that breaks down matter and reconstitutes it as whatever it is programmed to become. The key here is the open-ended nature of of what SIVA is capable of - with the right (or wrong) programming, it can be used to create with endless possibility. | |||
Excerpts from the Grimoire are interesting in understanding not only what it was going to be used for, but how it works: | |||
We've found a way to push our matter encryption technology even further. ~SIVA.MEM.WB002 | |||
Based on this, we can assume that this was originally developed from Engram tech, which is what "matter encryption" refers to. This is important because it immediately implies complex data structures capable of storing huge amounts of data in small spaces. | |||
Habitats, equipment, repairs of all kinds—all of these things can be made from one material. ~SIVA.MEM.WB003 | |||
Pretty straightforward description of what SIVA can be used for that mainly highlights, again, the main idea that SIVA as a whole can used to manipulate matter into just about anything. | |||
SIVA doesn't expire, degrade, or forget. It can remain dormant even on long voyages. ~SIVA.MEM.WB004 | |||
It's an inorganic material, not subject to entropy (likely due to it being derived from Engram tech), and more importantly, has a data storage capacity of some kind. This is important because it tells us that SIVA doesn't need to be directly manipulated, but can be encoded with commands and then "released". This also implies that it has a data transmission structure as well - similar to how machine code for hardware uses binary 1s and 0s, SIVA has some way of reading/writing data that isn't specified. | |||
Well, SIVA requires no external power source, so…forever. ~SIVA.MEM.WB007 | |||
This is also very important. The wording here makes it complicated to be 100% certain of the structure of SIVA and whether individual particles have their own eternal, internal power source, or because of its inorganic nature it simply doesn't require power to work. Most likely, it doesn't require power to perform it functions (data transmission and data storage) but does require power of some kind to be restructured into whatever it is programmed to become. This is speculation at best, however, since the Grimoire and other sources don't really expand on this idea. | |||
Just give it a directive, and it won't stop until it gets a new directive. ~SIVA.MEM.WB008 | |||
This is another sticky one - this can imply either giving inert material its programming which is then executed somehow by an external force, or that once the programming is given, it is self-executing. | |||
Given what we know about SIVA, it seems to be the latter. That adds some additional aspects to the nature of SIVA, namely processing capabilities and possibly some level of either operating structure or "software", so to speak. | |||
In order for the transmitted and/or stored data to be turned into an action by SIVA, data processing has to occur, much like how a CPU translates machine code to some kind of output. Furthermore, for that output to become a coherent outside structure (for example turning SIVA into a replacement part for a colony ship), the input data has to have instructions on how to achieve that end-result and the data processing structure needs to have instructions on how to process that kind of set of instructions. | |||
What I'm getting at is that SIVA is more complicated than it seems, containing at least: | |||
Data storage | |||
Data transmission channels | |||
Data processing | |||
Output capabilities | |||
It's clearly not "intelligent", so we can rule out AI and look at it more simply as an all-in-one universal 3D printer with all-encompassing systems. It can accept commands and use itself as the structure for "printing" whatever it was programmed to become. This is further confirmed by the statement: | |||
General, poorly worded or malicious code is the fault of the programmer, not SIVA itself. | |||
This pretty much confirms that SIVA is not AI, just to get that out of the way. | |||