• 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
Nairou

Is separate past/present game state always necessary?

1 post in this topic

By game state, I just mean data, such as object positions and attributes, active players, etc.

I know for FPS games, having separate past/present (or, more likely, current/next) states is useful, because things happen so fast and you want to allow multiple things to happen at once rather than sequentially. For example, two players shoot each other at the exact same time. If you have only one game state, player 2's shot could get ignored, since it gets processed after player 1's shot, by which time player 2 is marked as dead. If you have separate current/next game states, the shots fired are read from the "current" state but the players are marked as dead in the "next" state, which doesn't go into effect until the next cycle.

However, for other games such as RTS games, things happen at a much slower pace, and I can think of situations where separate game states might be weird. For example, two units are gathering a resource. If you have separate states, and both units happen to arrive at the resource at the same time, they will both get it, since there is no immediate knowledge if the resource being removed. Whereas with a single game state, one of the units would grab it and the other would find it missing and need to look for another.

I always assumed separate game states would be necessary, no matter what, to maintain the integrity of the simulation, but now I'm not so sure if that is true. Thoughts?
0

Share this post


Link to post
Share on other sites
It's really a design issue more than anything -- double-buffering the state is one way of dealing with it, a careful ordering of update events is another, keeping things decoupled is yet another.

For example, most projectiles in most FPS games today aren't instantaneous (meaning, they travel and are affected by drop, and aren't just a simple ray-test) so they should be entities in their own right, and continue to exist even if the player that fired them has died. That's an example of de-coupling.
0

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