Before we dive in, I think it'd be important to just say a few words about the word-vomit you're
about to
read.-
All of this babbling is just my own personal theorizing and headcannoning of both Minecraft itself,
but
also
some specific Youtuber references and concepts (you'll know when you get to them). If you have other
headcannons
or ideas, that's great and I'd love to hear them and discuss them! As stated on the MCYT project
main
page,
please do feel free to send me an electronic mail with your pointers!
Again, don't take this too seriously lol. All of this is just for the purpose of fun and brain
dumping
XD.
Enjoy!
The first crucial step that we need to get down in writing before starting, is defining what exactly
I
mean when
I say that Minecraft in itself is a sentient being.
“Minecraft” isn't just the name of the world the “players” inhabit, but also functions, in a way,
like
God
herself. The players cannot exist without Minecraft, however, Minecraft can. Minecraft is, on a base
level,
creation. It is Minecraft that not only allows the players to exist, but also the reason for their
creation in
the first place. It is not like Earth, it is more aware than that. Still, Minecraft is code, but
Minecraft is
also organic.
In this context, we can confidently assume that so-called “admin” players are more akin to angels
than
traditional bouncers or event-organizers, but instead hold a special ability that other players do
not:
The
power to control a set world, and by extension, the players within.
It is the entity of Minecraft herself that grants these special abilities when commissioned, as the
“admins” do
not inherently possess those abilities. Any player can become an admin sure, but it is a process of
world
creation or transferral of admin abilities that they have to go through before gaining such a title.
By this logic, (and mostly also, headcannoning the shit out of this) that entities known simply to
fandom as
“Watchers”, can co-exist and also differentiate themselves from admins, as they weren't players
first -
admin
later, but rather “birthed” by the goddess of Minecraft with those capabilities already woven into
their
code.
Which brings me to my next topic-
Like the entity of Minecraft, the players consist of code- more specifically, a form of Player-ID,
characteristics and their primary server (I'll get to that later down the page don't worry).
The Player-ID is exactly what it sounds like: a string of numbers and letters that makes up the main
container
for all of what/who that specific player is, as well as being an identifying number for easier
server
and admin
manipulation.
To better understand this theory, let me bring up an example:
CLOWNPICHERE
ClownPierce is a player, and let's say for demonstration purposes, that his Player-ID looks
something
like this:
INFODUMPHERE
The ID system functions much like a family tree, with the “parent-code”, (BirthSpawn: Overworld,
Nether
or End)
informing other choices down the line, (Horns, Colors, Other physical characteristics, etc.)
In Clowns example, he is Netherborn, so that parent-code informs what his color-palette will look
like,
(in his
case, red, black and white) and if he has hybrid characteristics - and if he does - what species and
percentage
of hybrid he is.
In the case of headcannoning some players as the parents of other players, it's important to note
down
how exactly players “spawn” into the world:
A “parent” player is not required for the creation of a new one (Minecraft will occasionally spawn
players at
will into Hub-Servers), but if 2 players were to want children, the process would be more akin to
code-splicing
than actual, human pregnancy. Parent-A would hypothetically duplicate half of their coded attributes
and
code
splice them together with the other duplicated half of Parent-B to create new code, I.e, a child.
(It is
important to note, that this process does not require 2 parent players, and can instead be done with
only 1 if
need be.)
“Now Deena-” I hear you snicker from behind your screen, “this is all well and good, but what about
respawning?
How come players can become permanently injured, or even just get a haircut if their appearance is
code-locked
and they're able to respawn? What about permadeath? Tell me the answers!”
I like that you're so passionate and I will try my absolute very best!
I imagine so-called “code-protection” is something that all players regardless of skill-level, just
inherently
know how to do. Think of it like breathing. It's something that we humans do on a daily basis. We do
it
so much
in-fact, that 99% of the time we're not even doing it on purpose. We're doing it automatically.
Code-protection
works much the same way, where the players do it without even thinking about it. However, in moments
of
extreme
stress or surprise, that spell can break.
Again think of the breathing metaphor: If someone makes you aware that you're doing it, you start
overcompensating and doing it manually (sorry btw), and it may take you a while to forget.
Code-protection is
much the same. The second a player becomes aware of how much danger they're in, or if caught by
immense,
genuine
surprise, their code-protection breaks.
This is also a general explanation as to why so many players with headcannoned scars or other
permanent
changes
like lost limbs or horns, lose them either during battles or by their own mistakes and/or accidents.
This is also why just dicking about with your friends and play-killing each other will not leave any
permanent
damages. Simply, the player is not afraid to die.
Now as for permadeath, I don't have a proper explanation - doN'T THROW TOMATOES YET!!
The simplest possible explanation would of course be complete code deletion. Admins have some
semblance
of
control over player code, but not to the extent of deletion, only bans. It must be Minecraft
herself, or
the
closest thing to her, (Watchers, etc, whathaveyou.)
How about servers? How can a player be on multiple servers at once? And what happens if you die on a server with
permadeath and are out
until next season like LifeSteal?
Much like Player-ID, the player also has a Server-Index located within their code-file that dictates
what their
“main” server is. The average player can only be serverbound to 2-3 at once without glitching out.
These
glitches only occur when the player has been off-world for too long (think Spiderverse). If their
primary server
happens to be hardcore or with a similar concept, upon death, the player would simply be stuck in
the
void,
unable to access their own code to go off-world or escape to a single player world. Their full trust
would
either lie in the admin to access their code and let them out of the void, or wait it out until next
season,
(not pleasant.)
An admin can choose to serverbound a player if they so wish, making the player unable to go
off-world at
all.
This is why “admin abuse” is such a controversial topic amongst players.
Now with speedrunners the server hopping becomes a bit tricky- The player must be bound to at least
1
primary
server, but with speedrunners creating and deleting worlds as fast as they do, it would only make
sense
to have
a set hub for them to return to after running- and that would act as their primary server.
Of course there are exceptions to all of these rules, and with headcannoning everything is possible,
but
to put
all this word salad more plainly:
The “player” is made of code, as is everything else, mainly Minecraft itself. The player's code can
be
broken,
duplicated or deleted. It can be given power over other players and it can choose to abuse that
power.
Minecraft
is an entity, a God, with the final say in every issue or act of creation.
These guidelines can of course be heavily modified or might straight up not apply to specific
players,
(I'm
thinking players like Grian, BranzyCraft or Philza Minecraft.)
Everything is possible, after all: Minecraft is creation. Minecraft is God.
