►
Description
In this session, we will first understand basic gaming architecture and then quickly deploy running real-time, session-based multiplayer dedicated game servers on Kubernetes clusters. We will be using the public cloud to spin up a Kubernetes cluster and understand how easy it is to quickly deploy, scale and run a dedicated gaming server.
KC Ayyagari (Krishna Chytanya Ayyagari) currently works for Google as a Senior Customer Engineer and he specializes in Cloud Infrastructure Modernization. Based out of New York, in his role, he focuses on Google Cloud technologies and works for enterprise sales teams. Prior to Google, KC worked for Microsoft, IBM, Thomas Reuters, Infosys and he has over 13 years of industry experience. A startup mentor, program manager and a trained architect, he has been active in the space of cloud computing for over 10 years and had experience in building large scale startup programs and designing technical solutions for some of the largest companies as well as Governments. He had experience working with and mentoring startups from all over the world. He is an active startup mentor for many accelerators including the United Nations (UN) and Google Launchpad.
A
A
You
can
just
call
me
so
krishna
is
a
senior
customer
engineer
at
google
and
I
think
we
are
currently
based
out
of
new
york
and
the
us
right.
Yes,
thank
you
very
much
for
joining
us
and
krishna
will
be
talking
to
us
about
how
to
build
your
first
multiplayer
dedicated
game
server
on
cuba.
This
is
an
exciting
thing.
We
have
a
lot
of
gamers
in
the
community
here,
so
they'll
definitely
want
to
know
how
to
do
this
so
over
to
you,
krishna.
B
B
Yeah,
okay,
great
by
the
way
I'll
be
presenting
the
screen
do
if
there
is
any
pings,
please
feel
free
to
stop
me,
but
here's
our
agenda
so
we'll
just
do
some
small
intro
I'll
be
talking
about
the
game
infrastructure
as
a
whole.
How
the
game,
backhand
and
frontline
looks
like
I'll.
Take
you
through
building
a
game
step
by
step.
B
By
the
way
I
have
a
a
core
script
which
I
already
executed
given
the
time,
but
also
I
have
the
course
script
which
I'll
explain
you:
how
to
build
or
deploy
a
game
server
on
kubernetes
I'll.
Also
talk
to
talk
you
through
a
another
way
of
doing
that
using
agonist,
which
is
an
open
source
project
and
I'll
tell
you
the
difference
between
doing
the
hard
way
versus
our
secondary
and
I'll.
Summarize
that
and
we'll
leave
there
so
within
half
an
hour
I'll
try
to
cover
as
much
as
possible.
I
have
some
simulation.
B
I
have
some.
I
have.
I
mean
two
demos
for
you
to
look
into
and
understand
how
the
game
infrastructure
looks
like
so
intros.
My
name
is
krishna
chaitanya.
You
can
call
me
casey.
That
should
be
good
enough.
I
am
a
senior
customer
engineer
working
with
google
it
I've
been
with
google
for
last
four
and
a
half
years
did
a
lot
of
roles.
You
know
random
startup
program
in
india
moved
to
u.s
now
working
with
enterprise
customers
and
their
sales
belongs
to
enterprise
sales
division.
B
B
The
way
it
looks
like
is,
you
have
multiple
clients.
It
can
be
mobile,
pc
handhold,
whatever
the
client
you
use,
you
have
a
front
end
and
you
have
a
back
end
on
the
front
and
have
two
components:
game
platform,
services
and
dedicated
game
servers.
Dedicated
game
servers
is
the
place
where
your
your
game
is
actually
deployed
now
analytics
and
game
database
is
again,
you
know
at
backend
now,
if
you
go
deep
dive
into
what
is
game
platform
services,
this
is
where
a
lot
of
things
happen
like
leaderboard
matchmaking.
B
B
This
can
be
like
online
lobby
chat,
inventory
management.
All
the
you
know,
axillary
services,
which
ones
which
you
see
on
top
of
the
games,
are
kind
of
like
we
can
bundle
them
into
something
called
game
platform
services.
We
have
dedicated
game
servers.
This
is
exactly
where
the
game
is
actually
hosted.
This
can
be
thousand
thousands
of
servers
based
on
the
game,
you're
playing
it
can
be
deployed
in
multiple
regions.
It
can
be
deployed
in
multiple
hardware,
no
matter
where
the
game
is
residing
on
now
coming
to
the
game
database.
B
B
Residing
I
mean
you,
you
can
create
a
shared
state
where
you
can
store
the
game,
assets
in
a
game
database
and
all,
and-
and
finally,
you
have
analytics
back
so
where
the
queries
you
understand
how
what's
happening
within
the
game,
the
events
within
the
game,
all
that
information,
which
are
real
time
happening,
can
be
captured
in
analytic
stack.
So
these
are
like
four
major
blocks.
I
just
simplified
a
lot
of
gaming
infrastructure
for
your
understanding,
but
try
looking
at
these
i4
foundational
building
blocks
to
build
any
kind
of
back-end
for
a
game
server.
B
Now
this
entire
back-end
can
be
deployed
anywhere
like
you
can
deploy
it
in
on
private
cloud.
You
can
deploy
it
on
public
cloud.
You
can
actually
do
even
make
a
fully
managed
solution.
Doesn't
matter
it's
like
you're
running
on
kubernetes.
You
can
run
it
anywhere
for
for
this
session,
a
lot
of
demos.
You
will
see.
I
created
kubernetes
engine
on
google
cloud.
Just
it
just
makes
my
you
know
deployment
easy,
but
you
can
choose
to
deploy
that
anywhere
in
any
cloud
or
any
public
data
center.
A
B
Go
through
what
happens
when
two
players
wanted
to
play
now.
This
is
kind
of
a
traditional
workflow
where,
when
two
players,
if
you
look
at
I'm
just
turning
on
the
laser
pointer,
so
here
are
the
two
players
who
wanted
to
play
a
game.
So
there
will
be
something
called
matchmaker
who
will
decide
who
two
players
would
be
playing
with
each
other
or
kind
of
match
them,
send
a
request
to
a
service
called
a
server
manager
which
essentially
takes
a
game
server
from
the
machine
cluster
and
then
dedicate.
B
I
mean,
send
the
request
back
to
matchmaker,
which
will
allocate
two
players
on
the
dedicated
game
server
now
rephrasing
it.
You
send
a
request
to
matchmaker
matchmaker
talks
to
server
manager,
server
manager,
talks
to
machine
cluster
dedicates
a
game
server
I
mean
takes,
takes
out
a
game
server
which
is
near
to
the
players,
send
the
request
back
players
directly
connect
to
the
machine
cluster.
I
mean
dedicated
game
server
design,
you
know
which,
which
the
server
manager
decided
and
then
they
start
playing.
Why
don't
you
use
load,
balancer
and
etc?
B
Obviously,
the
game,
the
latency,
is
very,
very
important.
The
typical
architecture
of
having
a
load
balancer
between
clusters-
all
this
doesn't
work,
so
you
need
to
think
differently
in
terms
of
how
two
players
talk,
I
mean
connect
to
a
game.
It's
more
like
a
server
manager
assign
some
sort
of
code,
which
I
would
say,
the
server
manager
talking
to
a
cluster,
taking
the
game
server,
sending
it
back
to
two
people.
That's
how
the
workflow
looks
like
now.
The
highlighted
part
on
the
right
is
what
we
need
to
concentrate
on.
B
What
do
we
do
to
create
a
server
manager
which
will
take
a
game
server
or
how
this
deployment
of
cluster
of
game
servers
via
server
manager
looks
like
now,
I'm
going
to
show
you
a
simple
demon
of
of
of
a
first
bit
of
open
arena
again,
which
which
I
deployed
on
kubernetes
engine
now
the
whole
there
are
so
many
constraints.
Don't
look
at
this
game
as
like
a
fully
production
game,
but
more
on
more
or
less
a
a
smaller
version
of
a
dedicated
game
server
I
deployed
just
before
joining
this
call.
B
So
what
I'll
show
you
know
it
runs
one
match
it
I
mean
you
can
look
at
the
constraints,
it's
it's
not.
What
I
wanted
to
showcase
is
this
is
not
a
production
grade
gaming,
but
obviously
this
is
exactly
what
I
just
showed
you
on
this
screen.
I'm
gonna
deploy
that
I
already
deployed
that
and
I'll
show
you
so
before
we
go
there.
What
is
the
step-by-step
process
of
building
this
architecture?
B
First
of
all,
you
can
take
open
arena
game
server
you
can
set
up,
I
mean
you
can
containerize
it
before
you
deploy
under
kubernetes
cluster
and
setting
up
a
kubernetes
cluster.
I
did
it
on
google
cloud
you
can.
I
had
something
called
scale
manager
scale.
Manager
is
a
service
which
will
look
into
the
cluster
scales
the
cluster.
If
there
is
a
huge
load
that
is
an
optional
service.
I
did
it
because
you
just
need
to
have
that
scaling
on
workloads
like
you.
B
You
need
to
have
more
virtual
machines
available
to
you
if
the
game
is
actually
scaling
so
scale
manager
is
a
service
which
runs
on
top
of
kubernetes,
which
will
scale
the
cluster
if
at
all
needed,
and
we
verify
the
setup
we
connect
to
the
game
server,
we
start
playing
the
game
now,
most
of
them
is
one-time
work.
Setting
up
kubernetes
cluster
is
obviously
done
on
cloud.
We
verify
connecting
to
game
servers,
that's
what
we
do
it
like.
Let
me
show
you
the
script.
B
Excellent,
so
if
you
look
at
the
script
for
which
the
first
time
you
know
you
install
the
tools
there
there
are,
I
mean.
Obviously
the
tools
are
cubelet
and
docker.
You
start
actually
downloading
the
game
server
from
from
from
from
the
storage
which
we
have
once
you
have
that
the
second
step
is
containerizing
this
I
don't
want
to
go
deep
dive
into
individual
commands,
but
giving
you
a
high
level
idea
that
this
part
is
about
containerizing
and
uploading
it
to
content
registry.
Once
you
have
that
this
is
an
important
step,
as
I
mentioned.
B
If
you
remember
the
first
slide
of
what
I
showed
you,
there
is
a
game,
server,
game
state
and
a
game
database.
So
the
game
assets
has
to
be
deployed
on
a
storage
which
is
shared
with
kubernetes.
So
I
created
a
virtual
machine
attached
a
file
attached
a
storage
file
into
it
onto
it,
and
then
you
know
cleansed
formatted.
The
disk
set
up
my
assets
into
it
deleted
the
virtual
machine.
B
Had
the
disk
ready,
set
up
firewall
network
created
a
computing
created
a
kubernetes
cluster
on
google
cloud
and
then
attach
to
the
disk
as
a
volume
on
volume
claim
by
the
way,
whoever
is
new
to
kubernetes.
Think
of
it
is
a
declarative
programming
way
of
you
know
it's
a
content
orchestration
engine
for
for
containers.
B
The
scale
manager
is
something
where,
as
I
mentioned,
I
would
use
this
program
to
scale
my
kubernetes
cluster
whenever
it
is
needed
the
nodes
when
it
is
needed
and
finally,
I
deploy
open
arena
using
the
open
arena,
which
I
already
containerized
deployed
r2
as
my
content
registry
I'll
go
ahead
and
deploy.
Let
me
show
you
my
screen
of
what
I,
where
I
deployed
this.
So
if
you
can
see
my
screen,
this
is
the
cluster
which
I
created,
and
here
is.
Let
me
show
you
kubernetes
cluster
one.
B
B
B
B
So
ports
can
see,
there
are
scale
manager
which
is
running
and
there
is
open
arena
dns,
which
is
actually
the
the
the
node
which
inside
the
pod,
which
is
running
so
this
already
executed-
and
it's
done
now,
let's
delete
that
cube.
Cpl
delete
pod,
open
arena
dns.
Let's
redeploy
that
open
arena
dns
part
again
now,
let's
deploy
the
pod
again.
B
If
you
wanted
to
see
how
the
part
looks
like
it's
very
simple,
this
is
how
the
part
looks
like
there
is
it's
talking
to
a
volume
claim
where
the
assets
are
located
and
then
starting
actually
and
play.
Is
you
know,
opening
up
a
container
with
certain
arguments
which
says:
hey
run
this
container
run
this
game
server
on
a
specific
pod
and
make
it
ready.
So
it's
a
very
simple
service.
B
B
B
B
B
B
A
A
B
I'll
expand
that
so
maybe
I'll
zoom
it
again
for
you
yeah.
Thank
you
sure
thanks.
So
you
missed
nothing
by
the
way,
if
you
don't
even
see
the
text
because
I'll
share
this
script
later.
But
to
for
your
information,
what
I
did
is,
I
just
deployed
the
game.
Server
like
I
did,
I
just
deployed.
I
just
did
the
same
steps
I
containerized
a
game
server,
which
is
an
open
arena
game
server.
I
set
up
a
kubernetes
cluster.
I
set
up
a
scale
manager.
B
I
verified
the
setup
I
connected
to
a
game
server
and
started
showing
you
the
connection
directly.
So
it's
a
very
simple
task,
step
by
step.
This
is
how
you
can
actually
build
a
game
server.
If
you
wanted
to
do
of
your
own
and
and,
as
I
said,
the
kubernetes
cluster
can
be
deployed
anywhere.
I
chose
google
cloud
you
can
set
up
on
your
laptop.
It
can
be
done
now.
B
The
challenge
with
this
kind
of
approach
is,
if
you
look
at
the
whole
architecture,
you're
building
everything
of
your
own
you're,
actually
building
your
game
machine
cluster,
the
server
matchmaker,
the
best
part,
is
you're.
Getting
all
the
benefits
of
kubernetes,
your
parts
are
deployed,
it's
scalable.
You
can
run
anywhere,
it's
a
hybrid
cloud
now.
What?
If
I
tell
you,
there
is
a
better
way
of
doing
this,
though
this
is
absolutely
a
perfect
way
of
doing,
but
there
is
another
way
of
doing
that,
so
that's
called
agonist
way.
Agonist.
B
So
if
you
look
at
this
is
an
open
source
project
dedicated
to
run
dedicated
game
servers
on
kubernetes
it
was,
it
was
done
by
ubisoft
and
google
cloud
you
can.
You
can
find
all
the
kinds
of
examples
also
all
sort
of
documentation
on
it,
it's
as
good
as
a
kubernetes
project.
Now
what
against
does
is
against
is
a
battery's
included,
open
source,
dedicated
game
server,
hosting
and
scaling
project
which
runs
on
top
of
kubernetes.
B
B
How
does
the
game
server
looks
in
a
guinness
world?
So
the
way
games
over
looks
in
against
world
is
obviously
you
take
a
game.
Server
application
create
attempt,
declaratively,
create
a
game
server
and
then
actually
start
send
it
to
kubernetes
api.
The
benefits
of
that
is
again.
It
can
be
deployed
in
hybrid
environments.
Physical
missions
can
reduce
the
cost.
Cloudbus
can
handle
the
capacity
now,
comparing
that
with
the
traditional
architecture,
traditional
architecture
send
them
request.
A
matchmaker
send
a
request
to
server
manager,
server
manager
dedicates
again
server
clients
connect
to
the
server.
B
You
start
playing.
That's
what
we
saw
in
our
demo
now
compare
that
with
agonists.
The
kavanaugh's
looks
like
this.
Everything
now
is
part
of
kubernetes.
So
if
you
look
at
back
and
forth,
there
is
nothing
like
the
machine.
Cluster
is
only
in
kubernetes.
Everything
is
actually
outside.
I
mean
our
components
within
kubernetes.
Now,
if
you
look
at
kubernetes
against
architecture
now,
I'm
going
to
have
you
know,
I
still
have
custom
matchmaker
I'll
talk
about
custom
matchmaker
in
a
while.
B
There
is
another
open
source
project
called
open
match
which
can
do
a
better
job
of
you
know
talking
to
agnes
and
does
matchmaking
for
you,
but
imagine
you
have
a
custom
matchmaker
again
now
client
wanted
to
play
a
game
like
I
wanted
to
play
a
game.
I
send
eric.
My
mission
sends
a
request
to
custom
matchmaker
abu
bakr
wanted
to
play
a
game.
He
sends
his
request
goes
to
custom
matchmaker.
Now
the
request
the
matchmaking
is
done.
There
and
it
the
request,
will
be
sent
to
kubernetes
api
kubernetes.
B
Api
will
talks
to
against
controller
where
address
controller
will
talk
to
a
fleet.
I'll
talk
about
fleet
in
a
short
while,
but
against
controller
will
talk
to
your
fleet,
takes
a
dedicated
game.
Server
allocates
a
dedicated
game
summer
for
us.
Send
the
request
back
to
custom
matchmaker.
Will
custom
matchmakers
send
that
information
to
the
clients
and
the
clients
connected
to
game
connect
to
game
server,
same
process,
traditional
architecture
in
an
agonist
way?
Everything
is
kubernetes.
Now
how
you
deploy
you
know.
Kubernetes
I
mean
a
game
in
agonist
is
very
simple.
B
By
the
way
before
we
go,
how
we
can
deploy
against
has
sdk
integrations
in
different
languages,
have
different
functionalities.
The
reason
why
you
need
this
kind
of
sdk
functionality
is,
if
you
are,
if
your
game
server
wanted
to
talk
to
again
us
wanted
to
integrate
to
against,
to
do
a
lot
of
activities.
Sdks
really
helped.
So
you
can
actually
build
your
own,
integrate
your
own
custom
game
server
with
economist
start
playing
that
so
it
kind
of
gives
you
it
takes
away
the
problem
of
you
managing
the
entire
cluster
agnes.
B
Does
that
for
you,
your
game
server
actually
can
talk
to
agnes
can
do
a
lot
of
functionality
using
sdks.
Now
it
works
across
cloud
providers.
It
does
auto
scaling.
It's
auto
scaling
is
very
easy.
It
has
local
tool
deployments
and
you'll
have
you'll,
have
a
map,
dashboard
and
metrics
for
for
agnes.
Now
this
is
how
it's
typical
game.
Server
deployment
declaration
looks
like
so
sonic.
B
Let's
take
a
first
person,
shooter
fbs
game
called
zanatec,
and
if
you
wanted
to
dedicate
or
deploy
a
game
server,
you
can
now
deploy
a
game
server
using
same
as
what
kubernetes
does
you
can
have
a
game,
server
kind
and
you
can
specify
the
ports
where
the
name
obviously-
and
you
can
specify
the
ports
where
the
game
server
will
actually
open
and
run
and
the
template
of
image.
Of
the
zonatic
example,
I
mean
zonatic
game
server,
which
you
wanted
to
containerize
and
deploy.
B
So
previously,
if
you
look
at
the
script,
which
I
did
you
do
a
lot
of
stuff
for
actually
deploying
containerizing,
deploying
that
managing
that
and
all
that
stuff
now
nothing
you
just
say:
I
want
a
game
server
like
how
you
wanted
a
pod.
You
can
say
I
want
a
kind
of
game
server,
and
this
is
my
container.
This
is
my
port
and
and
against
will
be
able
to
deploy
that
for
you
so
game
server
deployment
is
easy.
Now
you
want
a
fleet
of
game
servers,
you
need
multiple
game
servers,
not
just
one.
B
Now
you
have
another
template
called
like
another
declarative
way
of
creating
fleet.
So
fleet
is
more
like
multiple
game
servers
same
as
how
you
look
at
deployment
in
kubernetes
fleet
has
multiple
replicas
have
a
template
where
you
can
specify
the
ports
and
the
template
for
image
which
will
run
the
fleet
for
you.
So
things
boil
down
to
very
simple
now
the
controller
will
be
running,
that
running
fleet
running
game
server.
For
you
and
the
last
one
is
game
server
allocation.
Now
you
have
a
fleet
of
game
servers.
B
Kubernetes
api
wanted
to
delete,
allocate
a
game
server
for
you
and
send
the
request
back
to
matchmaker,
based
on
whether
the
game
server
is
available
for
connection
or
not.
You
don't
want
to
delete
a
game
server
which
is
which
in
which
players
are
running,
so
these
kind
of
requests
are
done
using
game
server
allocation,
so
game
server
location
is
another
request
which
you
can
actually
send
where
you
will
be
matching
with
the
name.
The
fleet
within
the
fleet
help
me
with
a
cluster
image
called
zonatic.
B
Instead
of
you
managing
it
off
your
own,
so
it
just
makes
the
back
end
development,
so
so
so
easy
now.
Combining
this
with
something
called
open
match
will
give
you
much
more
advanced
features
so
open
match.
You
can
write
custom
logic
within
your
console,
custom
logic
to
create
or
find
compatible
players
items
with
open
match
running
together
can
actually
build.
B
You
can
build
a
better
game
server
within
very
short
period
of
time.
Now,
to
summarize,
obviously
the
request
comes
to
open
match.
You
can
write
custom
match
logic
with
an
open
match.
Talks
to
kubernetes
kubernetes
talks
to
against
controller
antagonist
controller,
finds
a
dedicated
game
server
within
the
fleet
takes
the
game
servers
and
the
requests
back
to
controllers
where
the
people
or
the
clients
get
connected.
Now,
let
me
show
you
again
a
script
again,
so
let
me
show
you,
I
guess
before
we
go
to
agnes
script.
B
Here
is
what
how
you
can
deploy
that
in
again,
so
I
have
shown
you
a
big
script
for
gaming
on
the
hardware.
So
again,
a
script
is
very
simple:
create
a
cluster
and
you
know
call
the
cluster
give
a
cluster
a
name,
and
this
is
let
me
quickly
run
that
for
you.
I
know
we
are
running
out
of
time,
but
let
me
show
you
a
demo
quickly,
so
what
we,
what
we
are
doing
is
I
just
created
a
kubernetes
cluster,
restore
and
deployed
installed
agnes
onto
it
and
then
deployed
again.
B
That's
it
so
three-step
process.
Very,
very
simple.
Rest
of
everything
is
handled
by
the
scaling,
the
deployment
of
a
game
server.
Everything
is
the
packaging
of
solution
and
then
deploying
that
everything
is
handled
by
agnes.
So
you
don't
need
to
do
a
lot
of
hard
lifting
on
your
part,
so
I
already
created
a
cluster.
If
you
look
at
the
sorry,
I
already
created
a
cluster
called
against
demo
cluster.
I'm
just
reusing
the
same
for
this
demo.
B
Okay,
now
let
me
go
to
view
engine,
so
this
is
a
simple
game.
What
it
is
doing
is
I
I'm
gonna
send
a
whatever
I
type.
It
will
send
me
back
the
request,
so
it's
a
simple
server
game
server
running
on
kubernetes
cluster
use
on
against
what
which
I
created.
So
let
me
open
a
virtual
machine
and
then
send
a
request
to
this
terminal.
A
B
B
B
A
A
B
A
B
B
B
B
B
Little
so,
if
you
observe
now,
I
can
say
cube,
get
cube,
ctl
gets
game
servers.
Game
server
is
another
declarative.
When,
if
I
install
logins,
you
will
get
game
servers
as
another
type.
Actually,
so
I'm
saying
hello
world,
you
know
creators
community,
so
you
can
see
that
I'm
actually
playing
with
I
mean
I'm
able
to
ping
the
game
server
on
a
udp
report
and
then
get
the
request.
So
if
I
wanted
to
shut
down
the
game
server,
I
can
do
that.
B
I
can
say
exit
and
if
you
see
get
game
servers
you'll
be
seeing
it
is
getting
shut
down.
So
essentially,
what
we
did
is
I've
deployed
a
game
server.
I
installed
against.
I
deployed
a
game
server.
On
top
of
it,
I
connected
to
the
game
server
and
then
started
actually
playing
with
that
from
another
virtual
machine.
So
to
summarize,
the
the
kubernetes
agonist
way
of
doing
this
again,
clients,
requests
and
agnes
will
do
the
fleet
management
dedicate
the
game
server
back
to
it.
So
this
is
what
the
two
ways
of
like.
B
If
we
go
back
to
our
agenda,
what
we
discussed
so
far
is
to
summarize
I
explained
you
the
game
server.
Then
I
explained
you
how
you
can
build
the
game
from
scratch
by
creating
multiple
services,
like
you
know,
by
containerizing
game
server
and
then
deploying
on
kubernetes
cluster,
then
I
showed
you.
The
difference
between
that
and
against.
B
Agnes
is
an
open
source
project
and
how
it
is
differentiates
how
it
extends
kubernetes
api
to
give
you
much
more
functionality
and
how
that
how
there
is
an
sdk,
functional,
sdk
integration,
where
your
game
servers
can
work
with
economist
and
then
explain
you
multiple
terminologies
and
agonists
a
lot.
There
are
a
lot
of
examples
for
against
you
can
build.
You
can
start
playing
a
lot
of
games
by
deploying
that
there
is.
You
can
play
zonatix
game
on
against
very
short
time.
B
All
the
examples
are
there
in
github
and
and
you
can,
you
can
find
more
information
at
agonist.dev
and
if
you
wanted
to-
and
I
can
actually
share
the
script
for
deploying
games
over
without
diagonals
also-
and
you
can
compare
and
contrast
these
two
and
understand
how
the
game
server
works.
So
this
is
I'll,
stop
here
on
right
out
of
time,
but
over
to
you.
If
you
have
any
questions
or
else
this
is
this,
is
it.
A
Yeah,
that's
awesome.
I
think
what
we'll
be
looking
forward
to
is
sharing
the
scripts
and
the
your
slides,
so
we
can
share
to
the
community
we'll
send
it
to
everyone
that
has
vp
and
also
when
we
are
uploading
your
video
online.
We
also
share
the
the
scripts
and
the
facts
that
you
shared.
Thank
you
very
much
for
your
time
and
it's
been
awesome
having
you
thanks
thanks.
Everyone
thanks
for
your.