1
00:00:00,240 --> 00:00:07,040
Last time on developing, I picked my game engine 
- Unity - and I started to learn how to use it.

2
00:00:07,040 --> 00:00:13,840
But now it's time to reveal the idea for my 
game and, well, get started with making it.

3
00:00:14,400 --> 00:00:21,600
But where does one begin when developing 
a game? And I think this is a vitally

4
00:00:21,600 --> 00:00:27,600
important question because, as you are about 
to see, if you take the wrong direction

5
00:00:27,600 --> 00:00:35,637
when you start developing a game it can be 
disastrous for the project. Let me explain.

6
00:00:44,800 --> 00:00:49,840
Okay so let me start with the idea 
for the game. I am going to make,

7
00:00:49,840 --> 00:00:56,640
and brace yourself because this is crazy, a 2D, 
side-scrolling, platform game. Yes, I know, every

8
00:00:56,640 --> 00:01:02,320
indie developer starts by making a side-scrolling 
platformer. But I think I have some good reasons.

9
00:01:02,320 --> 00:01:07,360
I love the genre. Platformers are 
relatively easy to make in the

10
00:01:07,360 --> 00:01:12,640
grand scheme of things - it’s not a MMO at 
least. And I've made loads of videos about

11
00:01:12,640 --> 00:01:17,760
platformer level design and character 
design which should prove helpful.

12
00:01:17,760 --> 00:01:24,240
Now this is also going to be a, brace yourself 
again, platformer with a unique twist. The

13
00:01:24,240 --> 00:01:31,680
idea is that the character in my platformer is 
magnetic which means they will repel away from

14
00:01:31,680 --> 00:01:38,560
some platforms and attract to others. And you 
can change your polarity with a button press.

15
00:01:38,560 --> 00:01:43,200
The idea actually came from this game: The 
Legend of Zelda: Oracle of Seasons. In this

16
00:01:43,200 --> 00:01:49,040
game you have a magnetic glove power-up which 
allows Link to repel from some surfaces and

17
00:01:49,040 --> 00:01:54,400
attract towards others. You can also use it to 
pick up large metal balls for puzzle solving

18
00:01:54,400 --> 00:02:00,720
and use it to fight enemies. It's a really cool 
mechanic but it does feel somewhat limited by

19
00:02:00,720 --> 00:02:06,960
the genre, the top down camera perspective, and 
of course the limited technology of the Game Boy.

20
00:02:06,960 --> 00:02:14,240
So I thought… what if I were to borrow that 
game idea and put it in a different genre:

21
00:02:14,240 --> 00:02:20,000
a fast-paced, 2D platformer. Something 
akin to Celeste or Super Meat Boy. A game

22
00:02:20,000 --> 00:02:25,360
where you have to master the magnetism 
for speed and fluidity and precision.

23
00:02:26,080 --> 00:02:31,440
So that is the idea. And the question now 
is: where do I begin with it? Do I just

24
00:02:31,440 --> 00:02:37,840
jump into Unity and start coding? Do I jump into 
Photoshop and start making some artwork for it?

25
00:02:37,840 --> 00:02:42,880
Do I start thinking about the storyline 
or the characters? Where do I begin?

26
00:02:43,600 --> 00:02:49,360
I'm going to level with you: this is not the first 
game I've ever tried to make. Ever since I was a

27
00:02:49,360 --> 00:02:54,720
little kid I've come up with ideas for games, and 
at various points in my life I have tried to make

28
00:02:54,720 --> 00:03:02,720
those games in different tools and whatnot. But 
I almost never finish those games and I think

29
00:03:02,720 --> 00:03:10,640
the reason is the same, every single time: I 
start in the wrong manner. Let me show you.

30
00:03:10,640 --> 00:03:18,640
So I got this folder from my parents house 
and it is full of notes and sketches and

31
00:03:18,640 --> 00:03:24,000
ideas for a game I was going to make a few 
years before I started Game Maker’s Toolkit.

32
00:03:24,000 --> 00:03:28,640
That is actually just a mouse mat for 
Starcraft Ghost. That game never came out,

33
00:03:28,640 --> 00:03:32,800
did it? That might be worth 
something actually, put that in the eBay pile.

34
00:03:32,800 --> 00:03:38,560
So this game was going to be called Carter's 
Curse. It was about famed archaeologist Howard

35
00:03:38,560 --> 00:03:43,680
Carter, the dude who discovered Tutankhamen's 
tomb. And, in my game at least, he would also

36
00:03:43,680 --> 00:03:49,440
awaken an ancient Egyptian curse meaning he'd 
have to fight zombies and mummies and ancient

37
00:03:49,440 --> 00:03:57,600
Egyptian gods. I remember spending hours and hours 
drawing all of this stuff. I mean… what a nerd!

38
00:03:58,480 --> 00:04:04,480
Anyway. So how would you go about fighting these 
enemies? The answer: playing Picross puzzles.

39
00:04:04,480 --> 00:04:10,000
Picross is this logic-based, grid-based, puzzle 
game… a bit like Sudoku. Nintendo's made loads

40
00:04:10,000 --> 00:04:15,200
of Picross games. I was really inspired by games 
like Bookworm Adventures where you have a puzzle

41
00:04:15,200 --> 00:04:20,240
at the bottom of the screen, and completing the 
puzzle does damage to enemies in a little fight

42
00:04:20,240 --> 00:04:25,200
scene at the top of the screen. And so my idea was 
kind of the same: you'd have a Picross grid at the

43
00:04:25,200 --> 00:04:30,000
bottom of the screen and Howard Carter would 
be fighting monsters at the top of the screen.

44
00:04:30,000 --> 00:04:36,080
So I jumped into development. I was making the 
game in an app for iPad called Codea which lets

45
00:04:36,080 --> 00:04:42,080
you make iOS games on your iPad. I'd actually 
previously used it for a very standard Picross

46
00:04:42,080 --> 00:04:48,480
app for iOS so I knew I could probably code 
it, but I wanted the graphics to be amazing so

47
00:04:48,480 --> 00:04:52,800
I jumped into Photoshop and just started 
making loads of sprites and animation frames.

48
00:04:52,800 --> 00:04:59,280
I actually have a Dropbox folder that is full of 
sprites and animations. I made loads of different

49
00:04:59,280 --> 00:05:05,760
characters, I made finishing moves for Howard 
Carter, I made an introductory cutscene, I made

50
00:05:05,760 --> 00:05:10,480
menus with big juicy buttons 
to press. I really got into it.

51
00:05:10,480 --> 00:05:16,080
But then I realised something. 
Something quite important. Something

52
00:05:16,880 --> 00:05:26,080
quite detrimental to the project. The game wasn't 
any good! It was really bad, it wasn't fun at all.

53
00:05:26,080 --> 00:05:29,440
And the more I coded it and 
the more I developed it the

54
00:05:29,440 --> 00:05:35,920
more I realised what the problem was: Picross 
just doesn't have enough depth for this

55
00:05:35,920 --> 00:05:41,120
type of game. You can't really have tactics 
or strategy, you can't change what you're

56
00:05:41,120 --> 00:05:47,040
doing depending on which enemy you're fighting, 
and ultimately it was immaterial that you were

57
00:05:47,040 --> 00:05:51,920
fighting enemies. You could ignore that entire 
top part of the game and the game would still

58
00:05:51,920 --> 00:05:55,760
work because all you're doing is just playing 
Picross puzzles. So it meant that I didn't have

59
00:05:55,760 --> 00:06:00,480
the ability to make the game more difficult 
or more interesting depending on which enemy

60
00:06:00,480 --> 00:06:05,040
you were fighting and it meant the player was 
just doing the same thing over and over again.

61
00:06:05,040 --> 00:06:11,520
I had made a game that was shallow and repetitive 
and dull. And maybe I could have fixed it but I

62
00:06:11,520 --> 00:06:18,240
was so far gone at that point and so demoralised 
that I just kind of scrapped the whole thing.

63
00:06:18,960 --> 00:06:26,640
So what was my mistake? Well, with many, many years 
of hindsight… it's been almost a decade now… it's

64
00:06:26,640 --> 00:06:31,840
pretty obvious to me what happened. And it's 
this: when you're making a game there's a bunch

65
00:06:31,840 --> 00:06:38,000
of different things you have to create. The main 
ones being the music, the art, the game design,

66
00:06:38,000 --> 00:06:44,400
the story, and the code. And now it's easy 
to think of them as being equal… but they're

67
00:06:44,400 --> 00:06:50,560
not. In a lot of cases, the game design is 
not equal but instead it is the foundation

68
00:06:50,560 --> 00:06:58,000
upon which all the other parts sit. And so if you 
get that bit wrong the whole thing falls apart.

69
00:06:58,000 --> 00:07:02,000
I mean you can fix the bugs and you can 
redraw the graphics, but if the gameplay

70
00:07:02,000 --> 00:07:07,760
is fundamentally flawed well the whole 
project can sometimes be unsalvageable.

71
00:07:07,760 --> 00:07:11,840
And this is pretty much what happened 
to me. I spent so much time on the art

72
00:07:11,840 --> 00:07:15,680
and animation that by the time I 
finally got around to the gameplay,

73
00:07:15,680 --> 00:07:20,640
I realised that the whole thing was flawed. 
I had basically built a house on really

74
00:07:20,640 --> 00:07:26,560
shaky foundations and then I was surprised and 
upset when my toilet fell through the floor.

75
00:07:26,560 --> 00:07:31,520
Embarrassingly this is not the only time this 
has happened to me. I wanted to make a film noir

76
00:07:31,520 --> 00:07:35,840
point-and-click adventure game with a unique 
procedural generation clue system - but

77
00:07:35,840 --> 00:07:39,520
I spent so much time on the story 
and researching the time period that

78
00:07:39,520 --> 00:07:42,240
I never got around to actually 
designing that system.

79
00:07:42,240 --> 00:07:46,640
And I wanted to make a fast-paced 
modern twist on the mobile game

80
00:07:46,640 --> 00:07:51,920
Snake but I got bogged down in bug fixing 
and trying to get the movement code perfect

81
00:07:51,920 --> 00:07:56,640
that I never found out if that game was 
any fun before I got bored and burnt out.

82
00:07:57,200 --> 00:08:02,480
So every time I've tried to design my 
own game I've put other elements like

83
00:08:02,480 --> 00:08:06,960
story and graphics ahead of the gameplay. Why?

84
00:08:07,680 --> 00:08:15,040
Well I think it comes down to making two very 
wrong assumptions. Assumption one is that the game

85
00:08:15,040 --> 00:08:20,400
always felt kind of cool in my head, so I just 
kind of assumed that the game would be fun

86
00:08:20,960 --> 00:08:28,320
when I made it. Obviously that was wrong. And 
assumption two is that I'm not able to find out

87
00:08:28,320 --> 00:08:33,760
if the game is fun until I've built the 
game. I have to just kind of keep making

88
00:08:33,760 --> 00:08:40,400
the game and at some point I'll realise 
if it's any good… right? No, wrong again.

89
00:08:40,400 --> 00:08:47,520
And this is all very cringe-worthy to say because 
now the answers are so obvious. But they weren't

90
00:08:47,520 --> 00:08:52,560
obvious then - it's only since doing Game Maker’s 
Toolkit, since researching game development, since

91
00:08:52,560 --> 00:09:00,080
interviewing dozens and dozens of game designers 
that I now know how most successful games start.

92
00:09:00,080 --> 00:09:05,680
You see game designers have loads of ideas all 
the time and I'm sure they all seem amazingly

93
00:09:05,680 --> 00:09:12,400
fun in their heads. But the best game designers 
know that their brains are horrible smelly liars.

94
00:09:12,400 --> 00:09:19,040
The only way to know if a game idea is 
good is to build it, to test it. But

95
00:09:19,040 --> 00:09:25,760
instead of having to build the entire game, 
designers just have to build a… prototype.

96
00:09:25,760 --> 00:09:32,480
A prototype is just this small scrappy test bed 
for an idea, just designed to see if the idea

97
00:09:32,480 --> 00:09:37,680
is fun or not. These prototypes are 
usually incredibly ugly with just

98
00:09:37,680 --> 00:09:45,280
unfinished art or basic shapes or sprites stolen 
from other games. They're often buggy and broken

99
00:09:45,280 --> 00:09:51,280
and they have nothing in them but the bare minimum 
features needed to test that mechanic. They are a

100
00:09:51,280 --> 00:09:55,760
just functional enough version of the 
game idea, built as quickly as possible,

101
00:09:55,760 --> 00:10:03,520
with the only purpose being to see if that game 
idea works. Is it fun or interesting? Is it

102
00:10:03,520 --> 00:10:09,760
worth pursuing? Is it a strong foundation 
upon which to build the rest of the game?

103
00:10:09,760 --> 00:10:15,280
And so that's what I'm gonna do. This time I'm 
gonna get it right. I’m gonna focus exclusively

104
00:10:15,280 --> 00:10:19,280
on making the prototype and I am 
going to be extremely disciplined

105
00:10:19,280 --> 00:10:23,120
and not do anything other 
than just test this game idea.

106
00:10:23,120 --> 00:10:28,240
So in terms of art, I'm just going to pull stuff 
off Google Images. There's going to be no music,

107
00:10:28,240 --> 00:10:33,840
there's no story, I'm not going to think about the 
name of the game or the name of the characters.

108
00:10:33,840 --> 00:10:38,240
I'm not gonna start designing an app icon 
for a game that hasn't even been built yet,

109
00:10:38,240 --> 00:10:43,520
Mark, you idiot. The code will definitely 
be buggy and broken because I'm still just

110
00:10:43,520 --> 00:10:46,880
learning Unity, but it should be good enough

111
00:10:46,880 --> 00:10:52,960
to see if this idea works. Just a sandbox to 
test out game mechanics and see what's fun.

112
00:10:52,960 --> 00:10:56,400
So let's get started, and open up Unity.

113
00:10:56,400 --> 00:11:00,720
The first thing I needed to do was to have a 
character who can just move left and right and

114
00:11:00,720 --> 00:11:05,520
jump, so I just have it apply forces to 
the rigidbody when I hit the right keys.

115
00:11:05,520 --> 00:11:10,880
This already had some problems, which wasn't a 
great start, but I got there in the end. Then

116
00:11:10,880 --> 00:11:17,200
I put a magnet in the scene and needed to make it 
so the character would attract towards the magnet.

117
00:11:17,200 --> 00:11:23,200
Now to get this working I had to become an 
expert programmer, I had to use my galaxy brain

118
00:11:23,200 --> 00:11:29,200
coding skills, so I limbered up my fingers and 
typed in the following line of code… how do I

119
00:11:29,200 --> 00:11:34,240
move a rigidbody towards another object. 
Okay, yes, I Googled it, found some code,

120
00:11:34,240 --> 00:11:38,880
and slapped it in my project. But I did make 
sure I understood how it works - it basically

121
00:11:38,880 --> 00:11:44,080
finds the direction between the character and 
the magnet and applies forces to the rigidbody

122
00:11:44,080 --> 00:11:49,680
in that direction. I also tweaked the code so that 
it would speed up as you get closer to the magnet.

123
00:11:50,320 --> 00:11:54,960
Then I made it so you could turn off the magnet 
with a button press which had the intended

124
00:11:54,960 --> 00:11:59,120
effect of keeping the character's velocity 
going, sending them flying through the air.

125
00:11:59,120 --> 00:12:04,640
So if I slap a platform up here I can attract 
the character towards the magnet then let go

126
00:12:04,640 --> 00:12:10,880
and jump up here. Which does feel pretty 
good… but it's a little hard to control

127
00:12:10,880 --> 00:12:15,360
things. This code maybe isn't perfect, 
things get out of hand pretty easily.

128
00:12:15,360 --> 00:12:20,000
But as I was researching this stuff, I 
stumbled upon something really useful in

129
00:12:20,000 --> 00:12:26,720
Unity. It's a built-in component called the point 
effector, and it's basically… a magnetic field.

130
00:12:26,720 --> 00:12:31,760
I don't know how I missed this, the icon for it 
is literally just a magnet. Here's how it works:

131
00:12:31,760 --> 00:12:37,440
you give a GameObject a collider and a point 
effector, and then set an attract strength.

132
00:12:37,440 --> 00:12:42,720
And now when a rigidbody is in the collider, 
it's attracted towards the center of the field.

133
00:12:42,720 --> 00:12:48,720
You can also use Unity's layer mask system to 
make it so it only attracts certain objects.

134
00:12:48,720 --> 00:12:52,560
So this would certainly make the game 
a lot easier to make, so I decided to

135
00:12:52,560 --> 00:12:56,400
remake the prototype. And, yes, 
the game feels more grounded.

136
00:12:56,400 --> 00:12:59,840
It's easier for me to tweak things 
and I can do cool stuff like

137
00:12:59,840 --> 00:13:04,880
if I put the attract point on the poles of the 
magnet, this happens - which looks pretty sweet.

138
00:13:04,880 --> 00:13:09,760
But when I made this second prototype, for 
some reason… not quite sure why, I decided

139
00:13:09,760 --> 00:13:16,400
to not use Mario this time, but replace him with 
a picture of a magnet for the main character. And

140
00:13:16,400 --> 00:13:23,120
this kind of gave me an idea: what 
if the character is not magnetic,

141
00:13:23,120 --> 00:13:29,760
but there is a magnet in the game world. And the 
character can walk over and pick up the magnet.

142
00:13:29,760 --> 00:13:34,960
To achieve this I used Unity's built-in 
joint system, it's another component.

143
00:13:34,960 --> 00:13:39,520
This allows you to connect two rigidbodies 
together using different types of joints like

144
00:13:39,520 --> 00:13:44,960
hinges and springs. So now the character is 
essentially holding the magnet and if the magnet

145
00:13:44,960 --> 00:13:49,920
is attracted to a piece of metal, the character 
goes with it. Until you let go of the magnet,

146
00:13:49,920 --> 00:13:53,040
and now you can walk around again. 
And that gameplay I wanted before,

147
00:13:53,040 --> 00:13:57,680
with using the trajectory of the magnet to 
send your character up to a higher platform,

148
00:13:57,680 --> 00:14:01,680
that can still be achieved by just 
letting go of the magnet in mid-air.

149
00:14:01,680 --> 00:14:04,560
Plus it allows for all sorts of 
other things, like you can have

150
00:14:04,560 --> 00:14:07,600
two magnets, or more. And you could maybe, like,

151
00:14:07,600 --> 00:14:13,120
place the magnet up here, then get an enemy to 
chase, you turn off the magnetism, and splat!

152
00:14:13,680 --> 00:14:20,240
Oh this is kind of cool, actually. Maybe this 
could work. Suddenly the game felt way more

153
00:14:20,240 --> 00:14:25,680
interesting than my original idea, which I have to 
admit I was starting to get a little bit worried

154
00:14:25,680 --> 00:14:30,720
about. When your character is magnetic and being 
attracted and repelled it's very easy to feel

155
00:14:30,720 --> 00:14:36,160
a bit out of control, but having the magnet be 
a separate object means you get times where you

156
00:14:36,160 --> 00:14:41,200
are completely in control as the character, and a 
bit more out of control when holding the magnet.

157
00:14:41,200 --> 00:14:46,080
Plus, I was a bit worried just how many ideas I 
could come up with for a game where the character

158
00:14:46,080 --> 00:14:52,320
is magnetic. But as soon as I had it as two 
separate entities, the ideas just started flowing.

159
00:14:52,320 --> 00:14:57,760
Plus I really like games where you move back and 
forth between two distinct types of gameplay,

160
00:14:57,760 --> 00:15:03,200
like, think how Mario Odyssey changes when 
you do and don't have the hat. So in my game,

161
00:15:03,200 --> 00:15:09,760
the character is nimble and can jump really high 
without the magnet, and slow and leaden when

162
00:15:09,760 --> 00:15:14,960
holding the magnet - but, of course, that magnet 
allows for all sorts of amazing possibilities.

163
00:15:14,960 --> 00:15:20,720
Now I shouldn't be surprised that an even better 
idea emerged during the prototyping process. As we

164
00:15:20,720 --> 00:15:26,880
saw in the GMTK episode The Games That Designed 
Themselves, it's pretty common for new ideas to

165
00:15:26,880 --> 00:15:31,760
emerge during prototyping. Take a look at the 
game Crypt of the Necrodancer: when that game

166
00:15:31,760 --> 00:15:37,440
was originally designed, it was just supposed to 
be a roguelike with a tight time limit in between

167
00:15:37,440 --> 00:15:42,560
your turns. But as the designers made it, they 
realised that it would be even more interesting

168
00:15:42,560 --> 00:15:46,400
if, instead of it being on a timer, 
it was set to the beat of a song.

169
00:15:46,960 --> 00:15:51,600
So prototypes aren't just a way to 
test and prove the validity of an idea:

170
00:15:51,600 --> 00:15:55,920
they are a way to generate 
new and even better ideas.

171
00:15:55,920 --> 00:16:00,160
Now during this whole stage I made 
another interesting discovery in Unity:

172
00:16:00,160 --> 00:16:04,800
this one is called sprite shapes. And 
it's generally used to make really cool

173
00:16:04,800 --> 00:16:08,080
organic level design, like you 
might see in the Ori games,

174
00:16:08,080 --> 00:16:13,600
but for my purposes I just put on a blank colour 
and this allowed me to make level design really,

175
00:16:13,600 --> 00:16:18,400
really fast. I could just snap together a 
prototype area by dragging handles around

176
00:16:18,400 --> 00:16:22,960
like doing something in Photoshop. So I built 
the prototype again and this time I wanted the

177
00:16:22,960 --> 00:16:28,240
character to be a little bit better to control, 
something closer to a real video game character.

178
00:16:28,240 --> 00:16:33,920
Now I don't want to get bogged down in 
coding movement and jumps, so I downloaded a

179
00:16:33,920 --> 00:16:39,040
character control script off the internet. 
It works really good, I can focus on tweaking

180
00:16:39,040 --> 00:16:45,520
it or remaking it or whatever in the future: 
right now I don't want to put time into that.

181
00:16:45,520 --> 00:16:50,160
Also in this prototype I started looking 
at some more mechanics like being able to

182
00:16:50,160 --> 00:16:54,800
throw the magnet and then being able to 
recall it back to you like Thor and his

183
00:16:54,800 --> 00:16:59,760
hammer. And because the magnet rigidbody bumps 
into the character's rigidbody, it gives you

184
00:16:59,760 --> 00:17:04,800
this little bit of feedback when you catch the 
magnet. It's like free game feel, it's amazing.

185
00:17:04,800 --> 00:17:09,520
And then I came up with various scenarios 
that you could use the magnet in, like

186
00:17:09,520 --> 00:17:14,160
throwing it at a wall to create a platform. 
Maybe connecting it to a piston and then

187
00:17:14,160 --> 00:17:18,480
disconnecting it at the right time to send 
it flying. Maybe switching its polarity to

188
00:17:18,480 --> 00:17:24,400
jump between two conveyor belts. Or how about you 
weigh down this platform, stand on the top of it,

189
00:17:24,400 --> 00:17:30,160
and then change the magnet's polarity to shoot you 
up in the air? Whoa this is actually pretty cool,

190
00:17:30,160 --> 00:17:35,120
right? This is looking like a 
video game. This is pretty fun!

191
00:17:35,120 --> 00:17:41,120
And this really was the point where I felt like 
this game idea certainly has some potential. It's

192
00:17:41,120 --> 00:17:46,160
original: I've seen a bunch of magnet-based 
games but nothing quite like this.

193
00:17:46,160 --> 00:17:52,080
It allows for both platforming and puzzle 
based gameplay. It feels like ideas for this

194
00:17:52,080 --> 00:17:56,960
game just flow really easily so I can build 
loads of different levels. And, best of all,

195
00:17:56,960 --> 00:18:02,320
it's just really fun to play. I can just jump 
into this scene in Unity and pick up a controller

196
00:18:02,320 --> 00:18:06,720
and it's quite enjoyable. That 
is surely a very good sign.

197
00:18:06,720 --> 00:18:13,120
And so this is the power of prototypes: 
you can use them to test if a game idea

198
00:18:13,120 --> 00:18:16,320
is actually any good. And, if you're really lucky,

199
00:18:16,320 --> 00:18:20,720
you might find that new ideas emerge 
during that prototyping phase.

200
00:18:20,720 --> 00:18:26,880
Now I think you do have to have a certain level 
of discipline here, you really do have to say ‘I’m

201
00:18:26,880 --> 00:18:32,000
not going to focus on anything extraneous right 
now, just the gameplay’. And, I mean, it is hard.

202
00:18:32,000 --> 00:18:37,520
Like, in this video I didn't show you the entire 
week I spent looking at particle effects and

203
00:18:37,520 --> 00:18:43,280
shaders and UI elements and things like that - I'd 
gone right back to that old behaviour of getting

204
00:18:43,280 --> 00:18:49,520
distracted and carried away by stuff that just 
doesn't matter right now. But luckily I caught

205
00:18:49,520 --> 00:18:54,400
it in time and scrapped that prototype, before 
getting back to the stuff that is important.

206
00:18:54,400 --> 00:18:59,600
And ultimately I think it worked out: I ended up 
building something that I think is pretty fun,

207
00:18:59,600 --> 00:19:06,000
that does have potential, and that I am excited 
to work on. My previous games which I tried to

208
00:19:06,000 --> 00:19:11,600
make when I was much younger were built with a 
sort of blind hope that the game would be fun,

209
00:19:11,600 --> 00:19:16,640
which isn't the most confidence-inducing 
way to make a game. But now it feels like

210
00:19:16,640 --> 00:19:22,000
I'm building on a really strong foundation 
and so all those other aspects - the story,

211
00:19:22,000 --> 00:19:29,200
the music, the artwork - that can be built with 
faith that the underlying foundation is solid.

212
00:19:29,200 --> 00:19:34,400
And so I feel like this is 
the way to start making games:

213
00:19:34,400 --> 00:19:39,840
building a prototype. The only question 
is: what the hell do I do next?

214
00:19:40,720 --> 00:19:45,120
I guess we'll find out next time, in the 
next episode of Developing. Thank you

215
00:19:45,120 --> 00:19:51,840
so much for watching and I hope you'll join me 
on the next episode of this journey. Goodbye.

216
00:20:14,320 --> 00:20:18,320
The idea actually came from this game, 
The Legend of Zelda: Oracle of Seasons.

217
00:20:19,600 --> 00:20:22,240
Damn it. From this game. Oops.

218
00:20:25,120 --> 00:20:31,760
From this game. It came from this game. This 
game. This game. This game: The Legend of Zelda:

219
00:20:31,760 --> 00:20:38,080
Oracle of Seasons. The idea actually came from 
this game: The Legend of Zelda: Oracle of Seasons.

220
00:20:39,920 --> 00:20:41,120
That was pretty good.