libGDX Jam survival guide

35
Game Jam Survival Guide

Transcript of libGDX Jam survival guide

Page 1: libGDX Jam survival guide

GameJamSurvivalGuide

Page 2: libGDX Jam survival guide

Prepara&on?WhatPrepara&on?

Chooseyourtools!– Programminglanguage,IDE– Audioeditors&generators– Graphicseditors– Mapeditors

Usewhatyoualreadyknow!

Page 3: libGDX Jam survival guide

AudioTools&Resources

hDp://www.bfxr.net/

Page 4: libGDX Jam survival guide

AudioTools&Resources

hDp://www.audiotool.com

Page 5: libGDX Jam survival guide

AudioTools&Resources

hDp://audacity.sourceforge.net/

Page 6: libGDX Jam survival guide

AudioTools&Resources

FreeSoundeffects&Music*– hDps://www.freesound.org/– hDps://soundcloud.com/(CCGroup)– hDp://openmusicarchive.org/– hDp://dig.ccmixter.org/– hDp://www.indiegamemusic.com/

*AlwayscheckJamrules

Page 7: libGDX Jam survival guide

GraphicsTools&Resources

hDp://www.gimp.org/

Page 8: libGDX Jam survival guide

GraphicsTools&Resources

hDp://www.getpaint.net/index.html

Page 9: libGDX Jam survival guide

GraphicsTools&Resources

hDp://pinta-project.com/releases

Page 10: libGDX Jam survival guide

GraphicsTools&Resources

hDp://esotericsoRware.com/

Page 11: libGDX Jam survival guide

GraphicsTools&Resources

hDp://www.blender3d.org/

Page 12: libGDX Jam survival guide

GraphicsTools&Resources

FreeGameArt*– hDp://opengameart.org– hDp://kenney.nl– hDp://www.lostgarden.com– hDp://www.gameart2d.com

*AlwayscheckJamrules

Page 13: libGDX Jam survival guide

MapEditors

hDp://www.mapeditor.org/

Page 14: libGDX Jam survival guide

MapEditors

hDp://overlap2d.com/

Page 15: libGDX Jam survival guide

The5PhasesofJamming

1.  TeamBuilding2.  Brainstroming3.  Setup4.  ImplementaZon5.  FinishingTouches

Page 16: libGDX Jam survival guide

TeamBuilding

Youwillneed– Developers– Audio&graphicsarZsts*– Game/leveldesigners– Coordinator

ThelaDertwocanbedonebyanyone!

*Rareunicorns

Page 17: libGDX Jam survival guide

TeamBuilding

Developers– Dotheprogrammybits– Needtosplituptasksamongthem•  Graphics,Controls,Physics,UI,...

–  Thelessoverlapcode-wisetheeasier!

– NeedtotellarZstswhatformatstheyneed

– Needtodefinehowgame/leveldesignercreatescontent

Page 18: libGDX Jam survival guide

TeamBuilding

Graphics&AudioArZsts– Dotheartsybits– Needtosplituptasksamongthem•  UI,background,characters,effects,...

– Needtoagreeonanartstyle

– Mayneedtocreateplaceholderartearlyon

Page 19: libGDX Jam survival guide

TeamBuilding

Game/LevelDesigner– Doesthecontentbits– Needstodefinethegamemechanics

– Needstodefinethegameprogression

– Needstocreate„levels“– NeedstoplaytestandgivefeedbacktodevsandarZsts

Page 20: libGDX Jam survival guide

TeamBuilding

Coordinator– Makessureeveryoneknowswhattodo

– Keepstrackofthingstobedone

– Keepstrackofdependenciesbetweenteammembers

– KeepstrackofZme– Keepstrackofhumanneeds(food,sleep)

Page 21: libGDX Jam survival guide

TeamBuilding

–  Ifyouhavenodevelopers,lookintoConstruct2–  IfyouhavenoarZsts,usepreexisZngartorprogrammerart

–  Ifyouhavenogamedesigner,everybodybecomesagamedesigner

–  Ifyouhavenocoordinator,pickoneperson–  Ifyouarealone,yougettodoallthethings:D

Page 22: libGDX Jam survival guide

Brainstorming

Goals– Getahigh-levelunderstandingofyourgame

•  Genre•  Gamemechanic•  Secng&Story•  Artstyle

– TakeZmelimitsintoaccount•  FPS,MMORGP,RTSarelikelynotyourbestbets

– Thinkoutsidethebox!(hurrdurr...)

Page 23: libGDX Jam survival guide

Brainstorming

To-do1.  Gatherideasfromeveryone2.  Pickmostpromisingoneviavote3.  Definegenre&gamemechanics

-Usepen&paper!4.  Definesecng&story5.  Defineartstyle

-LetarZstsdrawquickmockups

Don‘tbeafraidtothrowthingsawayDon‘tbeafraidtoiterate,takeyourZme

Page 24: libGDX Jam survival guide

Setup

Goals– Getadetailedunderstandingofyourgame

• Whatwillthedevelopershavetodo?• WhatwillthearZstshavetodo?• Whatwillthegamedesignershavetodo?

– Defineinterfacesbetweenallteammembers•  Howdodevelopersworkwitheachother?•  HowdoarZstsgettheirartintothegame?•  Howdogamedesignerscreategamecontent?

– Definetasksandtheirorderforeveryteammember!•  Coordinatorresponsibleforkeepingtrackoftasks

Page 25: libGDX Jam survival guide

Setup

To-do1.  Developersagreeonplajorm&

toolstouse2.  ArZstsagreeonartstyle3.  DevelopersandarZstsagreeon

howtogetartintothegame4.  Developersandgamedesigner

agreeonhowtocreatecontent5.  EachsubteamdefinestheiriniZal

tasks6.  CoordinatorkeepstrackofthingsAsuperlightweightKanban-likeboardcanhelp

Page 26: libGDX Jam survival guide

Implementa&on

Goals– Getthedamnedgamedone!– Ensuretohaveaplayableprototypeearly

•  PrioriZzetasksaccordingly•  Gamemechanicsfirsttoseeiftheyarefun!

– Realizeyou‘lllikelynotgeteverythingdone!• WhichiswhyyoushouldhavesomethingplayableatalmostallZmes•  Cutcorners,killfeatures,focusonthecoreofyourgame

Page 27: libGDX Jam survival guide

Implementa&on

To-do1.  Everysub-teamworksontheir

task2.  Coordinatorkeepstrackof

progress3.  Sub-teamstalkwheneverthey

needto(re-)defineandprioriZze(new)tasks

4.  Goto1Yourhighestpriorityshouldbetohavesomethingplayableearlyon!

Page 28: libGDX Jam survival guide

Implementa&on

TipsforDevelopers–  Usesourcecontrol(git,SVN),doNOTuseshareddrives,ZIPfiles,e-mail!

–  Don‘tcodeforre-use–  Don‘topZmize–  Trytocreateamodular-designsopeopledon‘tdependoneachothertomuch•  Onepersonresponsibleforgraphics,oneforUI,oneforAI,oneforcontrolls,etc.

– Makesuregamedesignercancreatecontentasearlyaspossible

– MakesurearZstsexporttoeasytouseformats– MakesurearZstsworkforsomestandardresoluZon!– MakesurearZsts&gamedesignerunderstandlimitaZons

Page 29: libGDX Jam survival guide

Implementa&on

TipsforArZsts– Makeiteasytoexportyourarttotheproperformat– Makesureeveryoneusesthesamecoordinatesystem/resoluZon!

– UsedescripZvenamesforfiles•  Good:badguy-walk-leR.png,Bad:w_1_2.png

– Haveonesharedfolder(Dropbox,GoogleDrive)containingassetsreadyforthegamedesigner/developerstointegrate•  Don‘tputmulZpleversionsofthesamethingthere!•  Havewhateverlocalfolderstructureforworkinprogressassets

Page 30: libGDX Jam survival guide

Implementa&on

TipsforGameDesigners– Talktothedevelopersaboutwhat‘spossibleandwhat‘snot

– Focusonsimplemechanicsbuttrytoputinatwist

– Favorsimplelevel-designover„brainy“complexlevels–theytaketolongtodesign!

–  Ifyouhavedown-Zmehelp/bethecoordinator!

Page 31: libGDX Jam survival guide

Implementa&on

TipsforCoordinators– Ensurethateveryonecanstaybusy

•  GathertheteamtodiscussnewtasksorreprioriZzecurrenttasks

– Checkonprogressregularly•  Ifsomethingtakestolong,astheteamtoreprioriZze/killfeatures

– Makesureeverybodyisremindedtheyarehuman•  Makeeveryonetakebreaks•  Makepeoplegotosleep•  Makepeopleeatanddrink

–  Ifyouhavedown-Zme,takeonataskyoucando!

Page 32: libGDX Jam survival guide

FinishingTouches

Goals– Submitaplayablegamebeforethedeadline:D

Page 33: libGDX Jam survival guide

Finishingtouches

To-do1.  Featurefreeze2-3hours

beforethedeadline2.  Createabuildfor

submission3.  Getteamtogetherand

decidewhattopolishintheremaininghours

4.  Ifpolishingworksout,createanewbuildforsubmission

Page 34: libGDX Jam survival guide

FinalThoughts

– Sleep!– Eat&Drink!– Takebreaks!– Makenewfriends!

Page 35: libGDX Jam survival guide