• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
commyforce

When to start actually programming

10 posts in this topic

Hi, I'm new here after searching the web for a little help on game development. Let me start by saying I do know a good deal of both C++ and Java experience(Junior Computer Science Major) and plan on writing my game in C++ with the allegro library. I'm not completly new to graphics programming, I've made some basic games such as Breakout and Tetris while doing studies at my university.

Now I plan on doing an independent project, which is more of a complex game. To be more specific a side scroller, almost metroid like game and i am aware of the massive scale of the project and plan to do small iterations and add on. It's mostly just a personal project that I want to do for myself and to build up something for when I'm applying to internships to show my workmanship.

Now for my main concern is not exactly how to program anything (as of yet), but rather when do I stop writing down ideas, concepts and documentations of what I will be programming and when do I actually start programming. I, at times, feel like I'm trying to be far too specific in some of my documentations and writing down every little thing I can imagine. While I know it is important to have a solid and sound idea to work off of, I just feel like I'll trap myself in the design stage and never actually get to the meat and potatos of the project.

Thanks! Edited by commyforce
2

Share this post


Link to post
Share on other sites
Turn your ideas into some technical requirements for your project.
Then wear the developer hat and apply details to each entry, explaining how you will achieve that through programming. (Don't do them all at once)

By that time, you can start implementing bits. Like 0r0d says, [quote name='0r0d' timestamp='1355989695' post='5012732']
The high-level stuff is what will be hardest to change later, so it's worth thinking it through first.
[/quote]
With that in mind, think general game loop, UI, display modes and file I/O.
Then think about the concepts elevating the application into a game. (create a level format etc.)

It's nice to get back to that list. At first it might be a pencil thing, but this could eventually end up as your roadmap.
I love lists...

The time taken to think about something before doing it usually pays off. Edited by SuperVGA
1

Share this post


Link to post
Share on other sites
[quote name='SuperVGA' timestamp='1355989732' post='5012733']
With that in mind, think general game loop, UI, display modes and file I/O.
[/quote]

Yeah, stuff like this. Think about whether you want your code to be platform-independent, how the rendering engine will work (if 3D: low-level thin wrapper around DX/GL, or higher level?), how the object hierarchy works, how you will expose object attributes to editing (if at all), whether you're going to hard-code game logic or use scripting,...

Personally I would start with the definition of what a game object is, and what the hierarchy is. That's the heart of any game engine, and everything else radiates out from there. Once you get a good sense of what game objects are then you start to know how the rendering engine needs to work, how loading, exporting, editing, etc all need to work.
1

Share this post


Link to post
Share on other sites
Thank you both for your replys, this helps me think a little clearer on the design stage. While I know I have much to go on this stage, it also helps to know what I should be thinking about in this process. It's good advice to have to be looking at the ideas I would want to implement and to completely justify implementing them. I will most certainly be back to these forums to discuss further on my game as I flesh it out to obtain opinions and possible ideas as I go. Edited by commyforce
0

Share this post


Link to post
Share on other sites
This problem plagues me all the time, especially because I get anxious and jump the gun sometimes. I think what's most important, especially if you're building things from scratch, is to get the design for all of your classes and major functions done before you write any of them. Do not go coding those without having a specific, clear, implementable strategy first. If you do not heed this warning, you will be going back to change those functions again and again and again, and I mean before you even have a running prototype. It's just a lot easier to miss the forest for the trees in the design of your code when you run in head first.

As for features and all that, I would say as long as you design your base little "engine" code to be easy enough to modify, you should probably try to implement your original conception of the game in as simple a form first before you start making in-depth plans about it. You may play it and say "I don't think this will ever be fun, no matter what else I throw in." Then you can just change things, because you haven't gone through painstakingly building the whole thing up yet.

Most of all, aside from the pre-planning stuff, I'd like to add that you should keep a blog (either your own, or here on game dev) detailing your reflections on the process as you go through it. This will help you learn the most from it, as you'll have an in-depth view of your process later on (something that human memory just can't give you) for critiquing and study. But that's only if you're seriously into bettering yourself as a programmer and a person. Good luck.
1

Share this post


Link to post
Share on other sites
Even more great advice! I actually like that idea of creating a prototype of the broad spectrum of some implementations, I didn't really think about that to be honest. So my question now is should I just start with some broad designs, prototype it, see what's working and what's not and design from there? I feel that would be the best way to go because I notice as I'm going through writing down designs I end up adding more and more to the game and may end up over complicating it. I'm sorry if I come off as a bit naieve on the whole process, I'm a bit new to doing larger self motivated projects.
0

Share this post


Link to post
Share on other sites

Love the Pixar example. I think the rough outline is called the storyreel!?
Most professional artists work the same way. They don't render one part of a drawing after the other ... they go from rough rendering to the details for the whole piece of art.
So I would write the rough game design and the more technical documentation at the same time ... and add details as needed.

The problem is that even with that approach you might fall into the trap mentioned above (having to throw away all the code).

How well do you know the theory behind software architecture?
One approach that might help is developing low-level functionality as libraries that your game project uses.
That way you are less likely to be tempted to write god classes or go for quick/hackish solutions (write code where it doesn't belong).
Of course that complicates the build process.
But if you have to throw away the prototype code of your project ... maybe the functionality in the libraries can still be used.

I'm a fan of this article:
http://www.javacodegeeks.com/2011/10/if-i-had-more-time-i-would-have-written.html

It covers the jumping-the-gun-topic.

 

I personally would probably use a SCRUM based approach:

- Write the features of the game (product backlog).

- Turn the product backlog content into stories.

- Start working on stories in Sprints.

 

Your don't need to implement features right away. But you need to be aware of the features you might want to add in order to write a frame that offers a way to add those features.

If you don't know how to do that ... maybe just work on bringing the most simple versions ("Hello World!"-style) of those features together in a simple project.

2

Share this post


Link to post
Share on other sites

The sooner you can get something working the better. Start with the simplest idea it's possible to implement and implement that. Pick something you have a chance of getting completely prototyped in 2 weeks. This will help you:

 

  • figure out if what you want to do is technically feasible
  • figure out if you actually like it

 

The next step is building enough so that you're comfortable showing it to someone else. Try to reach this step as soon as possible. After all, it's other people who are going to be playing your game the most. Ideally this will happen within a month. This will help you:

 

  • figure out if other people actually like your game
  • help prioritize which of the things you already know need to be done, should be done first

 

I recommend showing it to people who will be both honest and supportive. You need both. Show it to more than one person. This will be scary. Do it anyway.

 

Just because one person doesn't like it, doesn't mean it's not good. Try to listen to the people who don't like it, because you'll learn a lot, but take what they say with a grain of salt. If you think your idea is good, chances are there are at least 100 other people in the world who do, too. Your job is to find them.

 

Find at least one fan, someone who thinks what you're doing is awesome. Show it to them regularly and listen to their feedback. They will keep you motivated and on track. If you can't find anyone in your life like this, use the internet.

 

 

The process described above has most of the core features of Agile Development without all the extra crap designed for managers in a bogus corporate hierarchy.

 

Some notes about this process:

 

It is iterative. You will modify the structure of existing code over and over again, especially the new code, without much affecting it's functionality. This is not a bad thing. It's called Refactoring. Learning to embrace it will make you more productive and help you to discover new things about design, as you code. It is at the moments when you begin a refactor that you should consider the forest and the placement and shape of the tree you are about to plant.

 

When you show your game to people, their suggestions and criticisms will sometimes surprise you. This is good. Some of the surprises will be useful, some won't. Take care to decide which is which. A hint in this area: the useful surprises usually turn out to be very useful. The others usually don't make much difference either way, they're just a time sink distracting you from the useful stuff. Knowing who your audience is will also help with this.

Edited by waylonflinn
2

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
Sign in to follow this  
Followers 0