The Art of Game Developer Art Bibles
summary
Argues that a clear art bible reduces iteration and can save millions on large AAA projects, starting as a one‑page elevator pitch and expanding into a Confluence/wiki with concrete chapters (pivots, art pillars, technical rules). Uses Project Alt as an example — three pillars (London Invictus, Mythic Mercs, Prevailing Dissonance), a triangle visual motif, Simplifica typography, GIFs for motion tests, and practical rules for world tech (plasma, rail guns), palette choices and color‑blind accessibility to ensure assets are buildable and consistent.
AI-written summary · about
chapters (17)
- 0:00Introduction to art bibles
- 1:34What are art bibles?
- 3:02Clarity of intent
- 6:08Purpose and evolution
- 7:36Framing the project
- 10:39Project and art pillars
- 13:53Developing the pillars
- 17:01Applying art principles
- 18:41Tone and atmosphere
- 21:58Aesthetic style mapping
- 25:11Visual signatures
- 28:04Semiotics and storytelling
- 31:05Brand identity and color
- 33:48Asset design and motion
- 37:32World law and technology
- 39:50Environmental detail
- 45:32Conclusion and final advice
related talks
23mThe vitality of visual storytelling in games
46mWriting for Games - A Backstory
01h 26mShow Don't Tell: The Intricacies of Metaphors in Visual Media
52mConcept Art Process in Video Games
08mInterview with
28mThe Creative Process in Game Design
39mBringing your concept to life
28mCreating an attractive pitch for your game