mozilla
Your Search Results

    Game development documentation status

    This page aims to track all ongoing game development documentation work. You can find raw notes on the game dev docs plan on the Mozilla Wiki, which includes a rough TOC/article structure to indicate how the below docs will be structured.

    Summary

    Pages No tags Needs* tags Missing tags Editorial reviews Technical reviews Outdated pages Dev-doc-needed bugs
    16 4 (25%) 1 (7%) 0 (0%) 0 (0%) 2 (13%) 1 (7%) 1 (7%)

    See also localization status of this section.

    No tags

    Found 4 pages:

    Needs* tags

    Found 1 pages:

    Technical reviews

    Found 2 pages:

    Outdated pages

    Found 1 pages:

    Dev-doc-needed bugs

    Found 1 bugs:

    Bug Summary Release
    1050916 [META] Complete the game developer zone ("Game Center") undefined

    Browse as bug list.

    Localizations

    Please help us to localize this documentation into different languages.

    Language Pages Translated Translations up to date
    fr 16 8 (50%) 3 (18%)
    ru 16 0 (0%) 0 (0%)

    Content outline

    Key:

    • Green: complete
    • Yellow: in progress
    • White: not started
    • Priority ratings:
      • * : priority 1
      • ** : priority 2
      • *** : priority 3

    Intro material

    Article title Rough content summary Potential authors Notes
    * Introduction to web gaming * Little bit of history of web gaming
    * Why is the Web a good gaming platform, and how is this possible?
    * What tools do we have available
    * What does the tool chain look like (from <canvas>/JS to asm.js and Emscripten)
    * How can traditional games developers adapt
    * Examples of existing open web games, to demonstrate that it can be done, and to provide inspiration.
    Austin Hallock from clay.io is updating this one. The existing article is ok, but really could do with being improved upon.
    *** Technology reference

    Teaching and reference material on technology fundamentals in case people need to update their knowledge, for example on Canvas, WebRTC and WebGL. This should be links to other parts of MDN, not new articles. This will be very useful to devs in the long term, although bear in mind that all such reference pages don't exist yet on MDN, and we need to create them in a fairly timely fashion.

    Eventually we will want to be able to link to a list of technology pages on subjects like File API, Full Screen API, Gamepad API, CSS, HTML audio, IndexedDB, JavaScript, Pointer Lock API, SVG, Typed Arrays, Web Audio API, Canvas, WebGL, WebRTC, Web Sockets, Web Workers, XMLHttpRequest.

    This article doesn't really require a separate author as such; it will just be links to other parts of MDN.  

    Tools articles

    Article title Rough content summary Potential authors Notes
    * asm.js   James Long jlong/longster has agree to have a stab at writing this
    * Emscripten   Chris Mills starting to write this Lots of info to cover this being added over at the Emscripten zone.
    * Shumway      
    * Frameworks and tools     This is likely to be multiple articles, covering different tools/middleware that are used to facilitate game creation. Research is needed to ascertain which ones we should cover first.

    Gaming techniques articles

    Isolated coverage of fundamental gaming techniques, assumes knowledge of the underlying technologies. For that, see the technology reference. Each one of these could be multiple articles, and we should explain fundamentals of complex areas such as graphics layer, as well as showing how frameworks and libraries can make the work easier in appropriate places.

    Article title Rough content summary Potential authors Notes
    **The anatomy of a video game   Scott Michaud writing this one The main loop, etc.
    **Collision detection   Louis Stowasser wrote an article covering 2D collision detection.  
    **Physics      
    **Efficient animation   Chris Lord has written something to cover this First been published on his blog
    **2D      
    **3D environments and acceleration      
    **Data storage     Offline installation, updates, appcache, application manifest, etc.
    ***Video and audio     <video> and <audio>, gUM, WebRTC, etc. Cover basic display, manipulation, looping...
    ***Multi-person games     WebRTC, sockets, etc.
    ***Graphics for web games     how to export, formats to use, optimization…
    **Performance optimization     Main thread vs Worker; ASM.js; WebGL; WebCL
    **Games distribution     Information about distributing web games, both online/in open marketplaces and in closed ones such as Google Play and the iOS app store
    ***Touch/pointer control     Touch, pointer events, etc.
    ***iOS/Chrome web shortcuts      

    Workflow articles

    Workflows for different audience members/outcomes. These should be very practical step by step sections that assume knowledge of the fundamentals in each case, referring back to the previous sections for those who need more fundamental information on any one step. Each should feature a case study or two that can show deconstruction of a real game, for those who like to learn by deconstructing and looking at inner workings.

    *Porting from native to web standards

    For the C++, professional gaming industry people. We need to explain to them how the Web is a viable platform, and how they can get their games up and running on it.

    Article title Rough content summary Potential authors Notes
    *Emscripten      
    *Profiling    
    *Debugging      
    *Really need a proper outline of article titles written here      
           
           
         

    ***Simple step by step tutorial on how to create a game, baby steps for beginners

    This uses Breakout as an example. After each step is implemented, offer a live sample so the reader can see what the new additions look like.

    Article title Rough content summary Potential authors Notes
    ***Setting up the canvas   Andrzej Mazur I started working on this tutorial (and potential workshop material). The Breakout clone game will be drawn on Canvas, every step will have it's working version so people can play and fiddle with it.
    ***Building the brick field   -||-  
    ***Adding a moveable paddle   -||-  
    ***Adding the ball motion mechanics   -||-  
    ***Adding the breaking bricks   -||-  
    ***Adding score keeping and display   -||-  
    ***Losing lives and end game   -||- What happens when you lose the ball at the bottom of the playing field? What happens when all lives are lost?
    ***Sound effects   -||-  

    **Designing your game engine - basic 2D

    This is for existing pro web devs, who are familiar with the technologies and just need to be take a bit further. The game here should be something a bit more interesting and fast moving, such as an asteroids clone.

    Article title Rough content summary Potential authors Notes
    **Setting up the environment     Organizing your files, pulling in libraries, the main game loop, going fullscreen with Fullscreen API, etc.
    **Making the physics more realistic    
    **Collision detection for pros      
    **Input support     Keyboard, gamepad, mouse, etc. Look at how the player ship could be made to respond directly to the mouse with PointerLock.
    Adding multiplayer support     On the same computer, and on different computers using WebRTC.?
    Offline support     Caching your online game, offline install and play on systems like Firefox OS

    **Moving into 3D

    Introducing pro web devs to creating 3D environments. What is required to set up a 3D game? WebGL, libraries, etc.? Choose something interesting like a 3D tank game, or something?

    Article title Rough content summary Potential authors Notes
    Structure still to be written      
         
           
           
           
           
         

    ***Mobile games and UX

    There are many smaller mobile games that are feasible for a single person to make. Mobile games don't necessarily have to be simple 2D affairs, but these lend themselves better to mobile platforms. This section could cover ideas for mobile platforms in terms of footprint and UX; nice for FxOS as well. Also include discussion of mobile app distribution on different platforms?

    Article title Rough content summary Potential authors Notes
    Structure still to be written      
         
           
           
           
           
         

    ***Porting Flash games to web standards

    For the Flash guys...

    Article title Rough content summary Potential authors Notes
    ***Shumway      
    ***Middleware    
    ***What else? Need a proper structure written here.      
           
           
           
         

    Meetings

    We currently don't have regular game development documentation meetings, but the notes for the ones we do have are recorded below:

    Sheppy has also been having some conversations with game industry developers to find out useful feedback from their perspective.

    Potential authors contacted

    • creativejs.com (well, Seb Lee-Delisle)
    • buildnewgames.com (I've contacted bocoup to ask who best to speak to, as they curate the site)
    • Rob Hawkes

    Document Tags and Contributors

    Contributors to this page: end3r, fscholz, chrisdavidmills
    Last updated by: fscholz,
    Hide Sidebar