Advertisement
English transcript
MALE SPEAKER: Carolyn VanEseltine, our guest today,
has been in video games since roughly the start
of the current century.
She got hooked on designing them,
and then on observing what kinds of games
other people are making and connecting those,
and also what kinds of games people haven't been making
and are just thinking of now.
So Carolyn VanEseltine.
[APPLAUSE]
CAROLYN VANESELTINE: Hi, everybody.
As [INAUDIBLE] introduced me, I'm Carolyn VanEseltine.
And I'm here today because everybody can dance.
I know there's this punch line that normally goes after that,
everybody can dance, but not everybody should dance.
I don't believe that.
I believe that everybody can dance
and that everybody who wants to dance should dance.
I think they should dance, I think they should sing,
I think they should write poetry.
I think they should do whatever art expression moves them.
I think that art expression is a natural human right that
transcends every boundary we have.
The problem is, this hasn't been true for our youngest art form.
And by our youngest art form, of course,
I'm talking about video games.
Historically, there's been a very high border
to being part of video games, because historically, in order
to make video games, you need to be a programmer,
you need to know somebody who can program
and who's willing to work with you,
or you need to have the money to hire a programmer.
For this reason, the people who've been making video games
are extremely different than the people who have been singing
or writing poetry or dancing.
I have a quick question before I fully
get into this, which is, I'd like
to know how many people here are programmers.
Great.
OK.
Thank you so much.
Just didn't want to make any assumptions.
Now there's a terminology thing I
should hit before I keep going.
There is a difference of opinion about the difference
between coding and programming.
So I just want to admit I'm going
to use those synonymously for the most part.
When I talk about someone who is a no-programmer, what I mean
is someone who is not fluent in any scripting language,
or-- I mean, someone who is not fluent in any programming
language, or I mean someone who identified themselves
to me as not being a programmer, because a lot of this
is about self-identification.
So I want to take a step back and tell you
a little bit about my history with video games, which
starts in 1980, when I was born into a house
with a computer, which was true of fewer than 1%
of American households at that time.
When I was five years old, my dad, because he is awesome,
introduced me to Colossal Cave Adventure.
I thought that this was the best thing I had ever seen.
I could tell the computer things and the computer
would do things.
It was fantastic.
He printed out the source code in Fortran
on our old dot matrix printer.
It was about this big, from the perspective
of someone about this tall.
And I would carry it to day care.
I wanted to understand it.
I wanted to know what was going on.
Fourth grade.
My fourth grade elementary had a school computer lab.
I met Logo there.
Logo go with the turtle.
The turtle is awesome.
You told it what you wanted to do,
and it would just do it on the spot,
and you could make procedures and you could link
all these commands together.
In fifth grade, I had decided I wanted to make video games.
I had this idea it was like a mashup of Infocom's Wishbringer
and Colossal Cave Adventure and Jurassic Park.
It had dinosaurs.
It was going to be great.
And I would map it all out on graph paper,
and I would write all the text descriptions down.
By eighth grade I knew a little Basic.
I knew a little Pascal.
At one point I borrowed a book from the library
that had an explanation of Conway's Game of Life in basic.
So I typed it into the computer, and it
was a really bad implementation of Conway's Game of Life.
So every time the cells hit the edge of the board,
they would break.
My parents saw what I was doing, and one of them
showed me one way to make it better,
and the other showed me the other way to make it better.
Of, you know, the millions of ways you could
have made that program better.
It was a pretty bad implementation.
But the point I'm trying to make here
is that I wanted video games.
I wanted this.
I wanted to be part of this.
I had wanted it my entire life.
And I had every advantage.
There was a computer in my house when I was born.
I have never lived in a house without a computer.
Both my parents were programmers.
There was a computer lab at my school
I had basic programming concepts from about five years old.
So I went to college and I majored in creative writing.
And I never took a single computer science course
because one of my friends had told me
that the Comp Sci professor who taught Comp Sci
101 deliberately washed people out who didn't want to major.
I didn't want to major.
Programming was great, but it was a means to an end.
And there weren't any game programming classes.
I didn't know how to take my little bit of Basic,
my little bit of Pascal-- even if it had been expanded,
I didn't know how to take that and make something
with graphics.
I didn't know how to make something
that you could put on a disc in a box on a shelf,
and then someone could go to the store
and buy it and put it in their console.
Those were the people who made real games.
It wasn't a meaningful aspiration for me
and so I faded out of games.
I'm standing here in front of you today,
and I did say I was a professional game developer.
So you can tell that at some point I got back on the horse.
But I didn't do it by learning to program.
I came in the back door.
There was a company called Simmtronics Games.
And they started somewhere in '94, 95, I think.
And I apologize if I just got that wrong.
But the pertinent part is that what they were making
was a pay for play mud.
And it was available on America Online.
And I wound up doing volunteer customer support for them
in exchange for my pay for play being play instead of pay.
So I got through the door there.
Eventually they hired me on.
When they hired me, it was to run in-game events,
it was to write documentation, and it was
to do more customer support.
At that point, I was in the games industry.
And I had no idea how to make my own game.
I knew how to support someone else's.
But games were for people who knew how to program.
They were for people who could put that disc
in that box on that shelf.
I didn't know how to do any of that, which
meant they weren't for me.
So obviously, at some point, I got over this.
I got over this because of a system called Inform 7.
Inform 7 made it possible for me to release my first game.
One Eye Open is a psychic horror game.
It was a collaboration between me and my friend Caelyn Sandel,
and it came out in 2010.
The reason I was able to create and release a game
is because of a system called Inform 7.
Inform 7 looks like that.
It does not look like a programming language.
To me, with my limited background and experience,
when I saw something like this, when
I saw something that looked like English,
I was a creative writing major.
English was comfortable.
I knew how to work with it.
I had the confidence.
I said yes, I can make something that looks like that.
Inform 7 was created by Graham Nelson.
Graham Nelson was looking specifically at non-programmers
and trying to make a system that was more comfortable for them.
It has an integrated development environment.
It is actually a transpiler.
It does not go from Inform 7 to working game.
It goes from Inform 7 to Inform 6 to working game.
What you're looking at right here
is a relatively common in fiction
snapshot of a game called Cloak of Darkness.
It's a very bad game.
But the point of Cloak of Darkness
is to show how various systems handle the creation
of various game elements.
This is what Cloak of Darkness-- well,
this chunk of Cloak of Darkness-- looks like in Inform
6.
If you know how to program, this is not scary looking.
If you don't, computer code is intimidating.
Computer code is intimidating because the computer
doesn't think like a person.
The point of learning to program is
learning to think like the computer operates.
That's the whole point of computer science.
If you don't know how to think like the computer operates,
then you need some kind bridge.
You need something that makes it easier
for the way you think to correspond with the way
that the computer operates.
And that's what Inform 7 was for me.
When I originally launched my game,
I was working at Harmonix by then.
I'm not going to go into the details of how
I got there, but assume it was kind of like how I got
into games in the first place.
When I launched my game, I was really excited about it.
I told a bunch of people at Harmonix, hey, I made a game.
And one of the engineers asked to see my source code.
I would be happy to show you my source code.
I sent over my source code.
Inform 7 actually tells you your word count instead of your line
count, so I knew that it was upwards of 100,000 words.
I had no idea what that meant in lines of code.
I still don't.
But I sent it over, and he sent it back and said,
you accidentally sent me your design notes.
I wanted to see the source code.
But that was my source code.
I didn't have anything else to show him.
He had looked at it and seen it as something
that a non-programmer could do, something
that a non-programmer could understand.
Inform 7-- don't get me wrong-- can actually
do some extraordinarily complicated things.
But Inform 7 was released in 2006.
In the year 2006, use of Inform 6 it dropped like a rock.
An by the time you get to 2012, Inform 6
alone was hardly being used anymore at all
because the people who were making interactive fiction
were people who were coming from a programming background,
but also from a writing background.
They had the same experience I did.
Also, Inform 7 has an integrated development environment,
which makes everything so much better.
Here's the problem with Inform 7.
Inform 7 is a scripting language.
It has a very specific syntax.
The syntax is actually as specific as the syntax
for Inform 6, which means that even though it looked intuitive
and it was easy to read, oh, man,
you can get the most amazing compiler errors out of it.
And because it's trying very much to help you and figure out
what you meant to do, it's not as simple
as, I think there might be a semicolon missing.
It's kind of amazing, actually.
I love Inform 7.
I don't claim that it's for everybody.
I'm going to digress for a second,
because I do come, as a hobbyist, very much
from an interactive fiction background.
Inform 7 is used to make parser games.
Parser games tend to look like that
when someone who doesn't know how to play parser games
plays a parser game.
They try commands that don't work because they don't
understand the limits, because they haven't been
taught to play parser games.
There's an actual skill involved here.
You need to know that you need to make
these noun-verb or verb-noun combinations.
And you need to understand that it's just not
understanding English.
There are a lot of people who play and love parser games.
There are a lot of people who get frustrated by the fact
that the prompt is giving them this illusion
of infinite choice, but in reality they
have very limited choices available to them.
But there are systems that are easier than this.
This is the other major branch of interactive fiction.
It's called choice-based interactive fiction,
and it actually comes from the tradition of game books
and from choose your own adventures.
Instead of giving you an illusion of infinite choice,
it shows you exactly what you can do in that room.
And the actuality is, all you can do in
that room is walk around.
That makes it so much less frustrating
to people who don't have the skill
to interact with that program, who don't have the experience.
So bringing it back to game engines.
What's needed is a game engine that
is just as accessible as this, something
that takes that experience of, I don't know what to type,
and turns it into, I know what I can type, or not even type.
This is Construct 2.
And Construct 2 is a visual scripting engine
for making graphical games.
It is something that presents everything in menus.
It presents everything with drag and drop.
What you're seeing right here is actually
a script in the making.
If you click the little heart image, which
is the A frame sprite with the left mouse button,
it will rotate 90 degrees.
And it's currently offering me the chance
to add another action to this script.
This is not a complicated script.
But once you start adding them together and chaining them,
just like a small program can become something dramatically
larger, a small script can join with others to become a game.
Just because it works with visual scripting
does not mean that a program is necessarily going to be simple.
All it's doing is making the syntax accessible.
Here you can see that there are a lot of things
you can do from the system object, many of which
are extremely important, many of which
require mastering the engine apart from the scripting side.
There are actually a number of engines in this style.
They are engines that are based around the idea
that it will be easier for people
to code if they don't have to fight with syntax.
This is an image from the game Airscape: The Fall of Gravity.
Airscape was greenlighted through Steam.
It received multiple awards, including
an award on its physics engine specifically.
It was created entirely in Construct 2.
It is a fiendishly difficult puzzle platformer.
And the developer selected this system specifically
because he didn't have experience making
games with programming yet.
He needed something that was accessible to where he was
at the time he was starting.
There are a number of other game engines in this same vein.
Clickteam Fusion, GameMaker: Studio, GameSalad, and Stencil.
The last one is Stencil.
And there are others, but those are some major ones.
I'm not going to go through and detail all of them,
because what I actually want to do is move to show you
a completely different kind of game engine.
This is Twine.
Twine is designed specifically for making
choice-based interactive fiction games.
What you're seeing here is the design interface.
And since Twine games are played as this series of web pages,
essentially, you can see with a map the web page forming.
This is actually the exact same Cloak of Darkness section
that you saw before, although I didn't
implement the rest of it.
Here's the thing about Twine.
I didn't try to teach you Inform 7.
I didn't try to teach you Construct 2.
Those take half an hour, at least,
to teach somebody, if what you want
is for them to go from zero to game.
And that's regardless of whether they have a programming
background or not.
Let's face it, a language is a language.
There's syntax to learn.
There's a system to learn.
I can teach you to Twine in 30 seconds.
I have done this repeatedly.
You can make a basic Twine game with the information
you get in 30 seconds, which is, start at the start.
Type whatever you want into that passage.
Whenever you want to make a link to a new passage,
put in double brackets.
It will open up a new passage for you.
Keep going until you are done.
Hit Build.
Build story.
You now have a playable web page.
You can put it anywhere you want and people can play your game.
It is that simple.
And that is why people are flocking
to Twine right now, because there is no game engine more
accessible.
Twine is free.
It is also open source.
And it supports a lot more than simple hyperlink.
It has full support for variables,
for conditional logic, for extensions with images
and CSS and video and sound.
And it also extends with JavaScript.
But for that basic game, the first experience
of, I made a thing, there it is, it's
amazing for someone who never thought
they could make a game before.
Here's a different engine.
Choice of Games.
Choice of Games is also an interactive fiction engine.
But it's an interactive fiction engine
that is aimed at a very specific audience.
And it's aimed at a very specific audience
because it's used to create a very specific kind of game.
Choice script is used specifically
to make novel-length interactive fiction.
Choice of Games is a commercial company
that is making its money on selling
novel-length interactive fiction.
They are not aiming at programmers.
They're aiming at writers, specifically
writers who never intended to make this kind of system.
It's as simple as it can be because they
need it to be accessible to this specific audience.
There isn't actually an ID for Choice of Games,
for Choice of Games choice script.
The system you use actually has extraordinarily simple syntax,
and you just write it in manuscript form.
When you're done, what you get looks like this.
This is actually optimized for people playing
on their iPads or other touchscreen devices,
but you can play on a computer as well.
And again, it's very intuitive to play.
Select your option, click Next, move on.
These are three examples of engines
that are also aimed at creating very specific kinds of games.
Ren'Py is specifically for visual novels.
RPG Maker is specifically for RPGs.
Adventure Game Studio is specifically
for click and point adventures.
Again, I'm not going to walk you through the full details of all
of these.
All of these engines are aimed, or had
as a primary audience, people who don't know how
to program in mind.
This one was aimed programmers.
Unity is a big deal.
They currently have 45% of the market share for game engines
used in commercial games.
47% of developers are using it.
4.5 million developers are registered.
And they have 600 million gamers,
at a minimum, playing projects created with Unity.
Unity uses C# and JavaScript as its languages.
This is not something that's accessible to people
who don't know how to program, except that a company
saw the void.
The people who make playMaker put a visual scripting system
on top of Unity.
It is in use at actually some rather large studios.
Most famously, Blizzard used the visual scripting system
playMaker when it was making Hearthstone.
Hearthstone is a digital collectible card game,
and the income is estimated at about $20 million a month.
It's a very successful card game.
The reason why they used playMaker
was so that, with their 15-person team that
was working on it, the art team was
capable of building things in the engine
without needing to pull a programmer off what
they were doing at the time.
Specifically, playMaker is a visual state editor,
and it's also a runtime library.
But the net effect is of a visual scripting system that
was built directly into Unity.
In addition to large studios using it
for specialized projects, it is possible to make a full game
with playMaker.
Jenna Hoffstein is the founder of Little Worlds Interactive.
Her launch product was The Counting Kingdom,
which is a tower defense game that is aimed at teaching kids
arithmetic.
She made it completely in Unity with the support of playMaker.
Now I've been talking about non-programmers.
I've been talking about programmers.
When it comes to game development,
do programmers have an advantage over non-programmers?
It depends on what you mean by advantage.
A lot of people ask if non-programmers
can use these tools to compete with programmers,
but that depends so much on what you mean by compete.
When I talk about game developers,
I'm not just talking about people who want
to make games commercially.
I'm going to show you one of my favorite quotes
about game development.
It's from Zoe Quinn.
"How to win at game jams: Go.
Make a thing.
It doesn't have to be good or finished.
OK, cool, you won."
This is an attitude I can get behind 100%.
Games are not intended to be polished commercial games.
This is kind of like a 48-hour hackathon.
You want to get from zero to game, and at the end
you have the joy of having done it.
And possibly you polish and refin
…
has been in video games since roughly the start
of the current century.
She got hooked on designing them,
and then on observing what kinds of games
other people are making and connecting those,
and also what kinds of games people haven't been making
and are just thinking of now.
So Carolyn VanEseltine.
[APPLAUSE]
CAROLYN VANESELTINE: Hi, everybody.
As [INAUDIBLE] introduced me, I'm Carolyn VanEseltine.
And I'm here today because everybody can dance.
I know there's this punch line that normally goes after that,
everybody can dance, but not everybody should dance.
I don't believe that.
I believe that everybody can dance
and that everybody who wants to dance should dance.
I think they should dance, I think they should sing,
I think they should write poetry.
I think they should do whatever art expression moves them.
I think that art expression is a natural human right that
transcends every boundary we have.
The problem is, this hasn't been true for our youngest art form.
And by our youngest art form, of course,
I'm talking about video games.
Historically, there's been a very high border
to being part of video games, because historically, in order
to make video games, you need to be a programmer,
you need to know somebody who can program
and who's willing to work with you,
or you need to have the money to hire a programmer.
For this reason, the people who've been making video games
are extremely different than the people who have been singing
or writing poetry or dancing.
I have a quick question before I fully
get into this, which is, I'd like
to know how many people here are programmers.
Great.
OK.
Thank you so much.
Just didn't want to make any assumptions.
Now there's a terminology thing I
should hit before I keep going.
There is a difference of opinion about the difference
between coding and programming.
So I just want to admit I'm going
to use those synonymously for the most part.
When I talk about someone who is a no-programmer, what I mean
is someone who is not fluent in any scripting language,
or-- I mean, someone who is not fluent in any programming
language, or I mean someone who identified themselves
to me as not being a programmer, because a lot of this
is about self-identification.
So I want to take a step back and tell you
a little bit about my history with video games, which
starts in 1980, when I was born into a house
with a computer, which was true of fewer than 1%
of American households at that time.
When I was five years old, my dad, because he is awesome,
introduced me to Colossal Cave Adventure.
I thought that this was the best thing I had ever seen.
I could tell the computer things and the computer
would do things.
It was fantastic.
He printed out the source code in Fortran
on our old dot matrix printer.
It was about this big, from the perspective
of someone about this tall.
And I would carry it to day care.
I wanted to understand it.
I wanted to know what was going on.
Fourth grade.
My fourth grade elementary had a school computer lab.
I met Logo there.
Logo go with the turtle.
The turtle is awesome.
You told it what you wanted to do,
and it would just do it on the spot,
and you could make procedures and you could link
all these commands together.
In fifth grade, I had decided I wanted to make video games.
I had this idea it was like a mashup of Infocom's Wishbringer
and Colossal Cave Adventure and Jurassic Park.
It had dinosaurs.
It was going to be great.
And I would map it all out on graph paper,
and I would write all the text descriptions down.
By eighth grade I knew a little Basic.
I knew a little Pascal.
At one point I borrowed a book from the library
that had an explanation of Conway's Game of Life in basic.
So I typed it into the computer, and it
was a really bad implementation of Conway's Game of Life.
So every time the cells hit the edge of the board,
they would break.
My parents saw what I was doing, and one of them
showed me one way to make it better,
and the other showed me the other way to make it better.
Of, you know, the millions of ways you could
have made that program better.
It was a pretty bad implementation.
But the point I'm trying to make here
is that I wanted video games.
I wanted this.
I wanted to be part of this.
I had wanted it my entire life.
And I had every advantage.
There was a computer in my house when I was born.
I have never lived in a house without a computer.
Both my parents were programmers.
There was a computer lab at my school
I had basic programming concepts from about five years old.
So I went to college and I majored in creative writing.
And I never took a single computer science course
because one of my friends had told me
that the Comp Sci professor who taught Comp Sci
101 deliberately washed people out who didn't want to major.
I didn't want to major.
Programming was great, but it was a means to an end.
And there weren't any game programming classes.
I didn't know how to take my little bit of Basic,
my little bit of Pascal-- even if it had been expanded,
I didn't know how to take that and make something
with graphics.
I didn't know how to make something
that you could put on a disc in a box on a shelf,
and then someone could go to the store
and buy it and put it in their console.
Those were the people who made real games.
It wasn't a meaningful aspiration for me
and so I faded out of games.
I'm standing here in front of you today,
and I did say I was a professional game developer.
So you can tell that at some point I got back on the horse.
But I didn't do it by learning to program.
I came in the back door.
There was a company called Simmtronics Games.
And they started somewhere in '94, 95, I think.
And I apologize if I just got that wrong.
But the pertinent part is that what they were making
was a pay for play mud.
And it was available on America Online.
And I wound up doing volunteer customer support for them
in exchange for my pay for play being play instead of pay.
So I got through the door there.
Eventually they hired me on.
When they hired me, it was to run in-game events,
it was to write documentation, and it was
to do more customer support.
At that point, I was in the games industry.
And I had no idea how to make my own game.
I knew how to support someone else's.
But games were for people who knew how to program.
They were for people who could put that disc
in that box on that shelf.
I didn't know how to do any of that, which
meant they weren't for me.
So obviously, at some point, I got over this.
I got over this because of a system called Inform 7.
Inform 7 made it possible for me to release my first game.
One Eye Open is a psychic horror game.
It was a collaboration between me and my friend Caelyn Sandel,
and it came out in 2010.
The reason I was able to create and release a game
is because of a system called Inform 7.
Inform 7 looks like that.
It does not look like a programming language.
To me, with my limited background and experience,
when I saw something like this, when
I saw something that looked like English,
I was a creative writing major.
English was comfortable.
I knew how to work with it.
I had the confidence.
I said yes, I can make something that looks like that.
Inform 7 was created by Graham Nelson.
Graham Nelson was looking specifically at non-programmers
and trying to make a system that was more comfortable for them.
It has an integrated development environment.
It is actually a transpiler.
It does not go from Inform 7 to working game.
It goes from Inform 7 to Inform 6 to working game.
What you're looking at right here
is a relatively common in fiction
snapshot of a game called Cloak of Darkness.
It's a very bad game.
But the point of Cloak of Darkness
is to show how various systems handle the creation
of various game elements.
This is what Cloak of Darkness-- well,
this chunk of Cloak of Darkness-- looks like in Inform
6.
If you know how to program, this is not scary looking.
If you don't, computer code is intimidating.
Computer code is intimidating because the computer
doesn't think like a person.
The point of learning to program is
learning to think like the computer operates.
That's the whole point of computer science.
If you don't know how to think like the computer operates,
then you need some kind bridge.
You need something that makes it easier
for the way you think to correspond with the way
that the computer operates.
And that's what Inform 7 was for me.
When I originally launched my game,
I was working at Harmonix by then.
I'm not going to go into the details of how
I got there, but assume it was kind of like how I got
into games in the first place.
When I launched my game, I was really excited about it.
I told a bunch of people at Harmonix, hey, I made a game.
And one of the engineers asked to see my source code.
I would be happy to show you my source code.
I sent over my source code.
Inform 7 actually tells you your word count instead of your line
count, so I knew that it was upwards of 100,000 words.
I had no idea what that meant in lines of code.
I still don't.
But I sent it over, and he sent it back and said,
you accidentally sent me your design notes.
I wanted to see the source code.
But that was my source code.
I didn't have anything else to show him.
He had looked at it and seen it as something
that a non-programmer could do, something
that a non-programmer could understand.
Inform 7-- don't get me wrong-- can actually
do some extraordinarily complicated things.
But Inform 7 was released in 2006.
In the year 2006, use of Inform 6 it dropped like a rock.
An by the time you get to 2012, Inform 6
alone was hardly being used anymore at all
because the people who were making interactive fiction
were people who were coming from a programming background,
but also from a writing background.
They had the same experience I did.
Also, Inform 7 has an integrated development environment,
which makes everything so much better.
Here's the problem with Inform 7.
Inform 7 is a scripting language.
It has a very specific syntax.
The syntax is actually as specific as the syntax
for Inform 6, which means that even though it looked intuitive
and it was easy to read, oh, man,
you can get the most amazing compiler errors out of it.
And because it's trying very much to help you and figure out
what you meant to do, it's not as simple
as, I think there might be a semicolon missing.
It's kind of amazing, actually.
I love Inform 7.
I don't claim that it's for everybody.
I'm going to digress for a second,
because I do come, as a hobbyist, very much
from an interactive fiction background.
Inform 7 is used to make parser games.
Parser games tend to look like that
when someone who doesn't know how to play parser games
plays a parser game.
They try commands that don't work because they don't
understand the limits, because they haven't been
taught to play parser games.
There's an actual skill involved here.
You need to know that you need to make
these noun-verb or verb-noun combinations.
And you need to understand that it's just not
understanding English.
There are a lot of people who play and love parser games.
There are a lot of people who get frustrated by the fact
that the prompt is giving them this illusion
of infinite choice, but in reality they
have very limited choices available to them.
But there are systems that are easier than this.
This is the other major branch of interactive fiction.
It's called choice-based interactive fiction,
and it actually comes from the tradition of game books
and from choose your own adventures.
Instead of giving you an illusion of infinite choice,
it shows you exactly what you can do in that room.
And the actuality is, all you can do in
that room is walk around.
That makes it so much less frustrating
to people who don't have the skill
to interact with that program, who don't have the experience.
So bringing it back to game engines.
What's needed is a game engine that
is just as accessible as this, something
that takes that experience of, I don't know what to type,
and turns it into, I know what I can type, or not even type.
This is Construct 2.
And Construct 2 is a visual scripting engine
for making graphical games.
It is something that presents everything in menus.
It presents everything with drag and drop.
What you're seeing right here is actually
a script in the making.
If you click the little heart image, which
is the A frame sprite with the left mouse button,
it will rotate 90 degrees.
And it's currently offering me the chance
to add another action to this script.
This is not a complicated script.
But once you start adding them together and chaining them,
just like a small program can become something dramatically
larger, a small script can join with others to become a game.
Just because it works with visual scripting
does not mean that a program is necessarily going to be simple.
All it's doing is making the syntax accessible.
Here you can see that there are a lot of things
you can do from the system object, many of which
are extremely important, many of which
require mastering the engine apart from the scripting side.
There are actually a number of engines in this style.
They are engines that are based around the idea
that it will be easier for people
to code if they don't have to fight with syntax.
This is an image from the game Airscape: The Fall of Gravity.
Airscape was greenlighted through Steam.
It received multiple awards, including
an award on its physics engine specifically.
It was created entirely in Construct 2.
It is a fiendishly difficult puzzle platformer.
And the developer selected this system specifically
because he didn't have experience making
games with programming yet.
He needed something that was accessible to where he was
at the time he was starting.
There are a number of other game engines in this same vein.
Clickteam Fusion, GameMaker: Studio, GameSalad, and Stencil.
The last one is Stencil.
And there are others, but those are some major ones.
I'm not going to go through and detail all of them,
because what I actually want to do is move to show you
a completely different kind of game engine.
This is Twine.
Twine is designed specifically for making
choice-based interactive fiction games.
What you're seeing here is the design interface.
And since Twine games are played as this series of web pages,
essentially, you can see with a map the web page forming.
This is actually the exact same Cloak of Darkness section
that you saw before, although I didn't
implement the rest of it.
Here's the thing about Twine.
I didn't try to teach you Inform 7.
I didn't try to teach you Construct 2.
Those take half an hour, at least,
to teach somebody, if what you want
is for them to go from zero to game.
And that's regardless of whether they have a programming
background or not.
Let's face it, a language is a language.
There's syntax to learn.
There's a system to learn.
I can teach you to Twine in 30 seconds.
I have done this repeatedly.
You can make a basic Twine game with the information
you get in 30 seconds, which is, start at the start.
Type whatever you want into that passage.
Whenever you want to make a link to a new passage,
put in double brackets.
It will open up a new passage for you.
Keep going until you are done.
Hit Build.
Build story.
You now have a playable web page.
You can put it anywhere you want and people can play your game.
It is that simple.
And that is why people are flocking
to Twine right now, because there is no game engine more
accessible.
Twine is free.
It is also open source.
And it supports a lot more than simple hyperlink.
It has full support for variables,
for conditional logic, for extensions with images
and CSS and video and sound.
And it also extends with JavaScript.
But for that basic game, the first experience
of, I made a thing, there it is, it's
amazing for someone who never thought
they could make a game before.
Here's a different engine.
Choice of Games.
Choice of Games is also an interactive fiction engine.
But it's an interactive fiction engine
that is aimed at a very specific audience.
And it's aimed at a very specific audience
because it's used to create a very specific kind of game.
Choice script is used specifically
to make novel-length interactive fiction.
Choice of Games is a commercial company
that is making its money on selling
novel-length interactive fiction.
They are not aiming at programmers.
They're aiming at writers, specifically
writers who never intended to make this kind of system.
It's as simple as it can be because they
need it to be accessible to this specific audience.
There isn't actually an ID for Choice of Games,
for Choice of Games choice script.
The system you use actually has extraordinarily simple syntax,
and you just write it in manuscript form.
When you're done, what you get looks like this.
This is actually optimized for people playing
on their iPads or other touchscreen devices,
but you can play on a computer as well.
And again, it's very intuitive to play.
Select your option, click Next, move on.
These are three examples of engines
that are also aimed at creating very specific kinds of games.
Ren'Py is specifically for visual novels.
RPG Maker is specifically for RPGs.
Adventure Game Studio is specifically
for click and point adventures.
Again, I'm not going to walk you through the full details of all
of these.
All of these engines are aimed, or had
as a primary audience, people who don't know how
to program in mind.
This one was aimed programmers.
Unity is a big deal.
They currently have 45% of the market share for game engines
used in commercial games.
47% of developers are using it.
4.5 million developers are registered.
And they have 600 million gamers,
at a minimum, playing projects created with Unity.
Unity uses C# and JavaScript as its languages.
This is not something that's accessible to people
who don't know how to program, except that a company
saw the void.
The people who make playMaker put a visual scripting system
on top of Unity.
It is in use at actually some rather large studios.
Most famously, Blizzard used the visual scripting system
playMaker when it was making Hearthstone.
Hearthstone is a digital collectible card game,
and the income is estimated at about $20 million a month.
It's a very successful card game.
The reason why they used playMaker
was so that, with their 15-person team that
was working on it, the art team was
capable of building things in the engine
without needing to pull a programmer off what
they were doing at the time.
Specifically, playMaker is a visual state editor,
and it's also a runtime library.
But the net effect is of a visual scripting system that
was built directly into Unity.
In addition to large studios using it
for specialized projects, it is possible to make a full game
with playMaker.
Jenna Hoffstein is the founder of Little Worlds Interactive.
Her launch product was The Counting Kingdom,
which is a tower defense game that is aimed at teaching kids
arithmetic.
She made it completely in Unity with the support of playMaker.
Now I've been talking about non-programmers.
I've been talking about programmers.
When it comes to game development,
do programmers have an advantage over non-programmers?
It depends on what you mean by advantage.
A lot of people ask if non-programmers
can use these tools to compete with programmers,
but that depends so much on what you mean by compete.
When I talk about game developers,
I'm not just talking about people who want
to make games commercially.
I'm going to show you one of my favorite quotes
about game development.
It's from Zoe Quinn.
"How to win at game jams: Go.
Make a thing.
It doesn't have to be good or finished.
OK, cool, you won."
This is an attitude I can get behind 100%.
Games are not intended to be polished commercial games.
This is kind of like a 48-hour hackathon.
You want to get from zero to game, and at the end
you have the joy of having done it.
And possibly you polish and refin
…