Return to Video

Storytime with Colt - Data-Driven Design - HTML5 Game Development

  • 0:00 - 0:03
    Now, there comes a point in every game developments life where content
  • 0:03 - 0:07
    creators, artists and designers, become very frustrated with the engineers on a
  • 0:07 - 0:12
    project. You see, most novice engineers for game dev, when adding artwork and
  • 0:12 - 0:17
    content into a game, will usually hard code the path references to assets.
  • 0:17 - 0:20
    Which means that if a designer or artist, wants to change that data, they have
  • 0:20 - 0:24
    to go talk to an engineer first. Which, engineers usually have a back-log of
  • 0:24 - 0:28
    30-60 days worth of tasks, kind of slowing down the entire project. More
  • 0:28 - 0:31
    experienced engineers know how to avoid this and actually move themselves
  • 0:31 - 0:36
    towards a concept of data driven design. A concept which allows non-engineers
  • 0:36 - 0:39
    to effectively change the execution of the flow and the assets in the game
  • 0:39 - 0:44
    without ever having to talk to an engineer. Basically this works by providing
  • 0:44 - 0:47
    some sort of simplistic data file outside of the game code, a text file, XML,
  • 0:47 - 0:52
    JSON. Something that the designers and the artists can quickly iterate on
  • 0:52 - 0:56
    without having to talk to anybody in the pit. Case in point, let's say a
  • 0:56 - 0:59
    designer and an artist need to find the optimal animation time for some kick
  • 0:59 - 1:03
    maneuver on a 2D fighting game. Well, it'd be great if they could actually sit
  • 1:03 - 1:06
    at the desk and try different variations of art creation and timing without
  • 1:06 - 1:08
    actually having to go talk to an engineer to change the frames that are
  • 1:08 - 1:14
    referenced. Most games these days actually have a huge backbone of data-driven
  • 1:14 - 1:18
    design. Of course, you end up in a very, very weird position is that if you
  • 1:18 - 1:20
    have too much data driven design you actually become a slave to it, in the
  • 1:20 - 1:25
    sense that most of your code exists out there. So changing small situations
  • 1:25 - 1:29
    becomes very, very difficult, and you actually have to bring an engineer back
  • 1:29 - 1:34
    in. So walk that line very finely. You want to be just data driven enough that
  • 1:34 - 1:36
    it makes sense and everyone can get their job done, but not so much that it
  • 1:36 - 1:40
    actually causes problems to your larger architecture.
Title:
Storytime with Colt - Data-Driven Design - HTML5 Game Development
Description:

more » « less
Video Language:
English
Team:
Udacity
Project:
CS255 - HTML5 Game Development
Duration:
01:41

English subtitles

Revisions Compare revisions