1
00:00:00,100 --> 00:00:02,100
The Minecraft title screen.

2
00:00:02,300 --> 00:00:06,400
For seven years, this was the panorama image 
that appeared.

3
00:00:06,500 --> 00:00:15,100
This was later changed in newer versions 
of the game, but for most of Minecraft's 
lifespan, this was the image you would see 
every time you'd play Minecraft.

4
00:00:15,200 --> 00:00:18,600
But have you ever wondered what that image 
really is?

5
00:00:18,700 --> 00:00:21,800
Is it a real Minecraft world that you can 
generate?

6
00:00:21,900 --> 00:00:26,700
Well, let's not get too ahead of ourselves; 
today we have a lot to cover

7
00:00:26,800 --> 00:00:29,700
CC by PyroBlank

8
00:00:30,400 --> 00:00:33,100
Let's start with the history of the Minecraft 
title screen.

9
00:00:33,200 --> 00:00:35,900
In the early days, it wasn't anything too 
special.

10
00:00:36,000 --> 00:00:41,300
The background was just plain ol' dirt, but 
when Minecraft beta 1.8 was released,

11
00:00:41,400 --> 00:00:46,200
The title screen was completely overhauled 
with a brand new moving panorama background,

12
00:00:46,300 --> 00:00:48,000
AND it stuck.

13
00:00:48,100 --> 00:00:56,000
In fact I'd say it stuck around for so long 
that almost every seasoned Minecraft player 
is certainly familiar with this particular 
title screen.

14
00:00:56,100 --> 00:01:00,900
And that's when a programmer by the name 
of Tomlacko go the idea

15
00:01:01,000 --> 00:01:08,600
After watching my video about the pack.png 
project, he got inspired to find the actual 
seed of the title screen image.

16
00:01:08,700 --> 00:01:16,800
At first glance, it almost seemed impossible! 
This image is so blurry that there couldn't 
be any way to get any useful information 
out of it.

17
00:01:16,900 --> 00:01:24,500
However, by looking into the game's files, 
you'll find this: 6 images that make up the 
title screen panorama.

18
00:01:24,600 --> 00:01:30,800
Here we can see a lot more detail, as the 
game itself creates a blur overlay when shown 
on the title screen.

19
00:01:30,900 --> 00:01:35,700
With those image files, Tom started to do 
some research to see if the idea was viable.

20
00:01:35,800 --> 00:01:40,800
Now at first glance at the images, the terrain 
doesn't look like what you'd see in modern 
versions of Minecraft.

21
00:01:40,900 --> 00:01:48,100
If the seed was to be reverse engineered, 
it's crucial that it's known exactly which 
version of the game this image was taken 
in.

22
00:01:48,200 --> 00:01:57,200
At first, this was a bit worrying, because 
between versions beta 1.7 and beta 1.8, Notch 
was working on massive changes to the world 
generation system.

23
00:01:57,300 --> 00:02:04,500
If this picture was taken some time in between 
those versions, the chances of finding this 
image would be next to impossible,

24
00:02:04,600 --> 00:02:08,800
as the development versions of this world 
generator are pretty much non-existent.

25
00:02:08,900 --> 00:02:11,700
But luckily, this wasn't the case at all.

26
00:02:11,800 --> 00:02:17,600
It was as simple as taking a look at the 
image's meta-data,which showed exactly when 
the image was saved;

27
00:02:17,700 --> 00:02:20,300
June 27th, 2011.

28
00:02:20,400 --> 00:02:29,400
Now this date is really important to know 
as this is months before the 1.8 pre-release 
was distributed, and beta 1.7 was even released.

29
00:02:29,500 --> 00:02:36,300
This pretty much confirms that the world 
generation system either had to be beta 1.6 
or beta 1.7,

30
00:02:36,400 --> 00:02:38,800
as it was pretty much identical in both versions.

31
00:02:38,900 --> 00:02:45,500
Now that Tom knew that the project was viable, 
it was time to recruit the others and to 
start looking for clues.

32
00:02:45,600 --> 00:02:49,300
A recreation of the image was also started 
to be constructed.

33
00:02:49,400 --> 00:02:56,500
One technique that was used to confirm block 
placements was a simple program that overlayed 
the recreation with the original image.

34
00:02:56,600 --> 00:03:01,400
This was extremely helpful with the process 
of brute forcing terrain near the end of 
the project.

35
00:03:01,500 --> 00:03:06,300
as that was taking place, a big push was 
starting to be made to try to find the exact 
coordinates of where the image was taken.

36
00:03:06,400 --> 00:03:09,600
Two things were used.

37
00:03:11,200 --> 00:03:15,600
First, similarly to the pack.png project, 
the clouds were used to find the z- direction,

38
00:03:15,700 --> 00:03:22,200
but what separates this the most from the 
pack.png project is the fact that the image 
contains tall grass.

39
00:03:22,300 --> 00:03:27,100
That's right, the tall grass in this image 
was crucial for findng the exact coordinates 
to where this image was taken.

40
00:03:31,700 --> 00:03:32,000
Lemme show you why.