Newer
Older
\usepackage{ulem}
\usepackage[utf8]{inputenc}
\usetheme{metropolis}
\usepackage{tikz}
\usetikzlibrary{calc,trees,positioning,arrows,chains,shapes.geometric,%
decorations.pathreplacing,decorations.pathmorphing,shapes,%
matrix,shapes.symbols}
\usepackage{graphicx}
\graphicspath{{images/}}
\title[CE810 GD2]{CE810 - Game Design 2}
\subtitle{Recap}
\date{Monday (AM), 14 May 2018}
\author{Joseph Walton-Rivers \& Piers Williams}
\institute{Univeristy of Essex}
\newcommand{\keyterm}[1] {\textbf{\alert{#1}}}
%\usepackage{beamer}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\section{Game Design}
\begin{frame}{Rules}
\item Games have rules
\item Rules are important \begin{itemize}
\item Too many rules $\Rightarrow$ Not fun
\item Too few rules $\Rightarrow$ Not fun
\end{itemize}
\end{enumerate}
\end{frame}
%TODO give this section a better name
\section{Richard's Hierarchy}
\begin{frame}{Richard's Hierarchy}
\item These slides are 'borrowed' from Prof. Bartle's slides.
\item Although we've used a different font...
\item We're recapping this because it's important to what we're doing
\item also, you've done exams since then...
\end{itemize}
\end{frame}
\begin{frame}{Richard's Hierarchy}
\item Tokens (aka entities)
\item Rules
\item Features
\item Gameplay
\end{itemize}
\end{frame}
\begin{frame}{Tokens}
\begin{columns}
\begin{column}{0.7\textwidth}
\begin{itemize}[<+->]
\item Things that can \textbf{act} or \textbf{be acted upon}
\item Game Rules \textbf{directly} concern tokens
\item In \textbf{computer} games, tokens are usually the \textbf{programming} objects/entities
\begin{itemize}
\item They \textbf{may} have associated assets
\item They \textbf{may} have associated properties
\end{itemize}
\end{itemize}
\end{column}
\begin{column}{0.3\textwidth}
\includegraphics[scale=0.2]{chessQueen}
\end{column}
\end{columns}
\item Rules refer to \textbf{tokens} and each \textbf{other}
\item Features emerge from rule interactions
\item Example:
\begin{itemize}
\item Rule 1 - Artillery kills infantry with no cover.
\item Rule 2 - Artillery makes craters.
\item Rule 3 - Craters provide cover for infantry.
\note{Company of Heroes by Relic entertainment implemented this example}
\item The \textbf{emergent feature} is ``Defences need to be managed''
\item Rules \textbf{together} with features form the \textbf{mechanics} by which gameplay emerges
\end{itemize}
\end{frame}
\begin{frame}{Features}
\item Features are what makes this game different to other games.
\item In terms of mechanics, this usually means ways to organise tokens
\item it can mean ways to organise tokens
\item Features emerge from interactions between game rules
\item Gameplay emerges from iterations between features.
\end{itemize}
\end{frame}
\begin{frame}{Gameplay}
\item In the same way that features emerge from rule interactions, gameplay emerges from feature interactions
\item Sid Meier: ``A series of interesting choices''
\item Gameplay is what players do in the game to have fun
\item There are subjective degrees of gameplay
\end{itemize}
\end{frame}
\subsection{An Example}
% TODO
\section{Something else}
\begin{frame}{Loops}
\item Positive feedback loops
\item Negative feedback loops
\end{itemize}
\end{frame}
\begin{frame}{Positive Feedback Loops}
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
\begin{columns}
\begin{column}{0.4\textwidth}
\begin{itemize}[<+->]
\item In a positive feedback loop, the better you do something the easier it becomes.
\item Your lead will increase if being ahead gives you an advantage
\item Unstable and not good between players
\end{itemize}
\end{column}
\begin{column}{0.6\textwidth}
\only<1>{
\begin{tikzpicture}
\node[draw](res) at (0, 0) {Resources};
\node[draw, align=center](city) at (4.5, 0) {Settlements\\ \& Cities};
\path[->]
(res) edge [bend right] node [below] {Pay for} (city)
(city) edge [bend right] node [above] {Generate} (res)
;
\end{tikzpicture}
}
\only<2>{
\begin{tikzpicture}
\node[draw, align=center](kill) at (0, 0) {Tower \\ Kills Enemy};
\node[draw, align=center](gains) at (2, 2) {Gains \\ Experience};
\node [draw, align=center](lvlup) at (4, 0) {Tower \\ Levels Up};
\path[->]
(kill) edge [bend left] node [left] {} (gains)
(gains) edge [bend left] node [left] {} (lvlup)
(lvlup) edge [bend left] node [below] {Kills more} (kill)
;
\end{tikzpicture}
}
\only<3>{
\begin{tikzpicture}
\node[draw, align=center](scores) at (0, 0) {You Score \\ A Hit};
\node[draw, align=center](drunk) at (2, 2) {Other Player \\ More Drunk};
\node[draw, align=center](less) at (4, 0) {Other Player \\ Less Accurate};
\path[->]
(scores) edge [bend left] node [left] {} (drunk)
(drunk) edge [bend left] node [right] {} (less)
;
\end{tikzpicture}
}
\end{column}
\end{columns}
\end{frame}
\begin{frame}{Negative Feedback Loops}
\begin{columns}
\begin{column}{0.4\textwidth}
\begin{itemize}[<+->]
\item In a negative feedback loop, the better you do something the harder it becomes.
\item Your lead will decrease if being ahead gives you a disadvantage
\item Very good at all levels of gameplay
\end{itemize}
\end{column}
\begin{column}{0.6\textwidth}
\only<1>{
\begin{tikzpicture}
\node[draw, align=center](winning) at (0, 0) {More \\Villages};
\node[draw, align=center](robbed) at (2, 2) {Gets \\Robbed};
\node[draw, align=center](less) at (4, 0) {Less Chance \\ Of Winning};
\path[->]
(winning) edge [bend left] node [above left, align=center] {More \\ Likely} (robbed)
(robbed) edge [bend left] node [above right, align=center] {Leads \\ To} (less)
;
\end{tikzpicture}
}
\only<2>{
\begin{tikzpicture}
\node[draw, align=center](expand) at (0, 0) {Capture Cities \\ Too Fast} ;
\node[draw, align=center](upkeep) at (2, 2) {Too much \\ to defend};
\node[draw, align=center](lose) at (4, 0) {Lose Citites \\ Couldn't Defend};
\node[draw, align=center](worse) at (2,-2) {Worse Off \\ Than before};
\path[->]
(expand) edge [bend left] node [left] {} (upkeep)
(upkeep) edge [bend left] node [right] {} (lose)
(lose) edge [bend left] node [right] {Possibly} (worse)
(worse) edge [bend left] node [left] {Idiot} (expand)
;
\end{tikzpicture}
}
\begin{tikzpicture}
\node[draw, align=center](ahead) at (0, 0) {Overtake};
\node[draw, align=center](gets) at (2, 2) {Gets Shot \\ At};
\node[draw, align=center](overtaken) at (4, 0) {Gets Overtaken};
\path[->]
(ahead) edge [bend left] node [left] {} (gets)
(gets) edge [bend left] node [right] {} (overtaken)
;
\end{tikzpicture}
}
\end{column}
\end{columns}
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
\end{frame}
\section{Game Parameters}
\begin{frame}{Evolution}
\begin{figure}
\includegraphics[width=.8\linewidth]{images/shmup}
\caption{Mechanics are like a game's DNA, and they often evolve from earlier games}
\end{figure}
\end{frame}
\begin{frame}{'Inspiration'}
There are great opportunities for mining minor variations on existing games
\vspace{0.5cm}
\begin{columns}[T,onlytextwidth]
\column{0.5\textwidth}
\centering
\includegraphics[width=0.9\linewidth]{images/game_old}
\column{0.5\textwidth}
\centering
\includegraphics[width=0.9\linewidth]{images/game_new}
\end{columns}
\end{frame}
\end{document}