• 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
  • entries
  • comments
  • views

So many topics! So little time!

Sign in to follow this  
Followers 0
Norman Barrows


As i work away here, i keep thinking of topics for this journal.

I'll start listing them here so i don't forget

i'll also try to say a few words, then cover it in more depth in a separate journal entry.

game state managers
state transitions are already implicitly defined by the natural flow control of a game. the one place i use a state manager "pattern" is in my rigid body modeler/animator. it has 2 states -- model editor, and animation editor. drawscreen calls one of two routines to draw either the model editor screen or the animation editor screen - depending on the "game state" of the modeler/animator module. it then calls one of two routines to process input as either modeler or animation editor input. this is a true "state system" design. and only natural, since you can jump back and forth between model and animation editor with a single mouse click. you see its really two programs in one, a modeler, and an animation editor. the state determines which one is active - sort of non-preemptive multi tasking - ie task switching. as you can see, it doesn't seem to make much sense to slice up a game into separate "programs" (states) each with its own input and draw routines. well actually it does.! . but a state manager isn't needed unless the relationship between "mini programs" (states) is a flip flop back and forth kind of thing. or jump around between a few. but game states are usually a combo of linear, hierarchy, and loops, not peerless network type things. so the state can usually be handled automatically by call hierarchy and normal flow control methods. Whew! more than a few words! Anyway, more on how you can usually get away without a state manger in a separate post.

writing bug free code.
there are lots of tricks that can help write bug free code. at some point, i'll do an entry on all the ones i know. in a typical large title i do, i've been blessed to average just one non-show stopping code type bug in the release versions. typos in displayed text are another thing however... .

game state managers
there was a recent thread on using game states for menus and such. can't find the post. in it, i said that the natural call hierarchy of games made state driven games overkill. in a later post, i mentioned an application of state driven that i do use: the modeler/animator module. its two programs in one, a modeler, and an animation editor, and you can switch between the two at any time. just now, i realized that caveman is also state driven! its two games in one: rpg, and person sim. so it has two states it runs in: fps/rpg mode, and "The sims" doing an a action mode. each has its own render and input methods. but most games aren't like this, and therefore are not true hybrid multi-state applications. it appears the timeto use state management is when your app is actually two or more apps of equal importance, IE they have a peer 2 peer type relationship, vs a main app and sub/mini app relationship. menus and such are sub-apps of the app that calls them. the main menu is a sub app of main. the game loop is a sub app or the main menu. the in-game menu is a sub-app of the game loop.

main menu
game loop
in-game menu
sub menus, stats screens, maps, etc.

- not -

main menu <---> game loop <----> in-game menu <---> world map <---> etc <----> etc (for every screen/menu in the game!)

natural call hierarchy handles it all for you. no need to manage states. granted, it can be done that way, but encoding the natural call hierarchy as state transitions can get ugly.

here's examples of state systems that seem to make more sense to me:

model <-----> animate

fps/rpg mode <----> person sim mode

Sign in to follow this  
Followers 0


There are no comments to display.

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