• Advertisement

Recommended Posts

Advertisement

There are many ways to build games.

As a direct answer to your question:  Virtually none.  Basic gameplay mechanics should be fleshed out with only the most vague ideas of a story. Mechanics should be identified which are fun and compelling in their own right, not forced into a story.

Longer answer:

In my experience in the professional world, the story tends to be far down the list and relatively late in the process.  Often the people writing the game are told a general theme and told the rest will be fitted to the mechanics.

There are mechanics and gameplay experiments long before stories are ever considered.  Developers experiment with the mechanics, try a wide range of mechanics, try to find ways to make the mechanics work together or break when used in combination. If there is a hint of a story at this point it is only the most vague framework to explain how the mechanics interconnect, more of providing a genre rather than plot points.

I've worked on and worked with others on many projects where the studio builds mechanics to be played with based only on the most vague specifications.  We have an early project like that right now at my job where a small group of people have been assigned to implement a range of mechanics for games that don't even have a genre.  Questions like "Is this going to be more of a tactical game or more of a strategy game?" are answered with "here are some more mechanics that look good on paper mockups, depending on how they feel at computer speed we might be able to answer that."  

As a large suite of mechanics is developed the beginnings of a story can be built that can leverage the mechanics. As the mechanics are being pruned down to the essence of the game, the story pieces can start to form built around the mechanics. A full plot should wait until the mechanics are realized and gameplay is fun.  A fun game system can be used to tell many varied stories, but good stories tend to be specific to the game systems they are in.  And many amazing games have no story at all.

 

In my observations of the hobby world, the many games based around stories will write the story and the plot, they'll have all kinds of numbers for their supposed tuning long before any code is written. 

I've seen design notebooks filled with specific game items, specific armors, specific weapons, all with a long list of (meaningless) values. Often there is a teen-focused adventure story full of plot twists and bad writing where the teen overcomes the school bully and vanquishes the world. There are drawings of the characters, their faces, descriptions about how charismatic or crude each party member should be.  There are intricate sketches of weapons and armor, and full descriptions of how Epic Armor of Awesomeness has 1337 defense plus 40% defense against undead monsters and school administrators, but there is no definition of the math those numbers plug into.

These projects tend to fall down long before code is ever written or actual game art is ever created. A few will have some experimental code written around them, or some white-box levels written in Unity or Unreal. But when they realize just how much work is involved, that they've created a project that would require thousands of work-years to implement, it will be abandoned by the wayside.

 

Share this post


Link to post
Share on other sites

I fully agree about hobby games that tackle complex or new gameplay mechanics. These should go on the back burner until the hobbyist has a lot of experience.

Twine/Inklewriter games, visual novels, and RPG Maker games, however, are within the reach of even first-time hobbyists, and they're a good way to hone interactive writing skills as well as general game design skills.

So when you finally have an idea for a story down, you might consider choosing an existing gameplay genre (such as a visual novel) that fits your story and your current level of experience.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By nick1
      Hello,

      I have limited programming experience in C++, but have always had a passion for games.  Where do I start?  I have a rough idea of the type of game I want to develop and am ready to commit the time necessary to learn new languages.  Are mobile games too difficult to begin with? Should I begin learning the basics of keyboard controls before attempting touch screens?  I would appreciate any input or advice!
      Thanks!
      Nick1
    • By khawk
      Dene Carter, Managing Directory @ Fluttermind LLC (@fluttermind)
      From Indie to Fable and Back. 30 Years of Wisdom.
      Started writing games in 1984 when he was 14 years old. What has he done in 33 years?
      Druid - Commodore 64 Original Dungeon Keeper core team Fable franchise and more Indie through AAA.
      "I am an idiot" - first learned in 1984, and every year after.
      Rockman - made $7500 for 2 weeks of work. Figured he could make 26 games a year, or $438k in today's money.
      Takeaway: Really stupid at 14.
      Even in 1980's, developer only got 12-14% royalties.
      (Side note: Dene is fun to listen to. Recommend this on the Vault when it goes online.)

      You are not your players.
      Made a black and white game on a Spectrum, which was color. Did it because he was poor. Problem is his audience were not poor, and had color TV's. Reviews were not nice. Players see things completely different to you. Do not forget that your players have not seen the game as much as you. Avoid difficulty/complexity-creep. The real world has distractions and beer - they don't care about your game as much as you do. Test your mobile game on the toilet - that's what your real players do. Fundamentally, players live inside their own brains, not yours. Those you ignore will ignore you in return. Design for your players' minds, not for you. Generalizing is Really useful
      "An expert who is too narrow has difficulty colaborationg" - Valve Employee Manual Did a lot of things over the course of his career. Everyone did everything in the 1980's and 1990's. Most developers generalized. Developing a broad skill-set aids communication. Large teams require collaboration and clear communication. Knowledge breeds respect (never say 'JUST'). 'Just' suggests a task is easy. It might not be. Ignorance is an energy. Don't forget you are human. You are designed to adapt and can do anything if you put your mind to it. Be a human. Learn a skill outside your area. Programmer learn how to 3D model. Artist learn how to code. Learn music, theater. Think of yourself as an artist. Rapid Team Growth is Dangerous
      "If your team can eat more than two pizzas, it's too large." Werner Vogels, Amazon VP/CTO Early Fable - 3 developers. Communication very easy. Later Fable, team grew bigger. At 12 people rumor mill started to develop. Can't have everyone in every meeting at same time. Pockets and cliques develop. Fred Brooks. Communication paths don't grow linearly. Team communication grows exponentially. [n * (n-1)] / 2 8 people on team, 28 connections. Ringelmann Effect - "Larger groups lead to less motivation & coordination & productivity." Decreased motivation - larger group, start to feel like a cog in the machine. Decreased coordination - communication pathways explode. Suggestion: Increase identifiability. Make sure everyone knows everyone's contribution. Most of all: think before growing your team. Blandness Has Its Uses
      Pursuit of excellence can be wasteful. Sounds counterintuitive. Blandness helps disguise repetition. Think reusing assets. Players notice the patterns. When asking for something to be made, communicate the context of assets - how will they be seen or heard? Often find they need to be bland. Prototypes Can Be Misleading
      Experiential games are difficult to prototype. More useful for mechanical games. Fable only came together at the very end - threw away at least one entire combat system. Looking back, it wasn't polished not necessarily bad. Bland prototypes are better than ugly ones for experiential. Keep prototype completely separate. Define prototypes success criteria. Art Style is More Important Than You Think
      Curate rather than create Style can hide the fact you can't draw. Restrict complexity. Style is marketing. Unique style tells players there may be something unique about your game. Streamline Your Process
      What is your iteration cost? Recognize your cost to try something and learn from it. Making your life easier is real work. Resist self-sabotage. (context of making tools) Closing Thoughts
      Don't let technology dictate your game's core promise. Static screenshots have to look good, too. No 1 pixel lines. Don't worry about the things people don't ever get to see. Don't panic if your game sucks - fix it. Editor thought: Really enjoyed this talk. Dene is a fun speaker, and his advice was raw, real world advice for anyone aspiring to make it in game development.
    • By Bokchee 88
      I am animator by hard, and i am doing game animation for at least 8 years so far. During the last 2 years, i came with a idea for game and maybe some day, i want to start indie game company. As i am thinking to start game company, i am also thinking what kind of value i can give to the company. For example, am experience in animation,sales(I was selling web development services, before i jumped to gaming), bit of rigging- just not for production, i am learning on the side as well. The rest of the gaming production, like modeling, concept art, texturing, i am total noob or to say better, i am no near interest to do modeling for example, don't have such a patience to do it. But before characters and things are made for animating, what the hell i am would do?
      Also, what is the ideal size of the founding team of a game company? Positions to be filled mostly are, Concept artist, Modeler/Texture artist, programmer, animator-rigger. And later would need more people to join, like more animators, programmers, sound, fx,etc.
       
      And lastly, do i need to have something,like a prototype, to show people and get them interest, or should i ask someone i know, for skill that i lack, for example, Modeling would be great, texturing and rigging, and to start all together from scratch?  
    • By bakchoi
      This is the 1st game we built by Cocos Creator! We need your feedback about this game on:
      Is this game fun?  How is the graphic performance (laggy?) How can we improve the game? https://itunes.apple.com/us/app/color-block-game/id1347502739?ls=1&mt=8
      Thank you =)
       
       




      App Preview - Color Block - 886x1920.mp4
    • By HouseAndMoon
      I make a game on my own. I do not use forums (until now) or social media programs to talk about it, I just do it. So the problem is: I finished the game, I published the game for android, no one (ok, 3 persons) check the game. So I see 2 possibilities: either the game is really, really bad (I suck) or I have no idea how to promote my game (this one is true for sure). I really think the game is rather fun but maybe I completely wrong. So, how the hell I check if my game is good or not and how the hell can I do some little promotion of my game for free. I would stop caring about the game if the game is really bad, but I sincerely think it is not. I would be grateful if someone post an opinion about this.
      Thanks.
  • Advertisement