Comments on: Entity State Machine in 60 Seconds or Less http://www.gamepoetry.com/blog/2008/12/12/entity-state-machine-in-60-seconds-or-less/ The art, science and business of independent game development Sun, 25 Jul 2010 17:51:13 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: urbansquall http://www.gamepoetry.com/blog/2008/12/12/entity-state-machine-in-60-seconds-or-less/comment-page-1/#comment-152 urbansquall Fri, 19 Dec 2008 01:27:41 +0000 http://www.gamepoetry.com/blog/?p=91#comment-152 <p>I've been considering a few approaches that manage the data for the different states. The problem, though, is that it quickly devolves into something that loses a lot of the conciseness of the original solution which is bad.</p> <p>I feel like there is a solution there and I'm grasping but it just sifts through my fingers.</p> I’ve been considering a few approaches that manage the data for the different states. The problem, though, is that it quickly devolves into something that loses a lot of the conciseness of the original solution which is bad.

I feel like there is a solution there and I’m grasping but it just sifts through my fingers.

]]> By: Squize http://www.gamepoetry.com/blog/2008/12/12/entity-state-machine-in-60-seconds-or-less/comment-page-1/#comment-118 Squize Wed, 17 Dec 2008 22:17:21 +0000 http://www.gamepoetry.com/blog/?p=91#comment-118 <p>Check me out posting a comment about my own words on a different site, that's how important I think I am ;)</p> <p>Thanks for your kind words about the state machine approach mate. I've said it a load of times since actually writing that though, that I thought everyone did it that way anyway.</p> <p>You raise a really good point about passing data. For example if you're passing a timestamp to a instance every frame, that's all well and good when that instance needs to know about it ( ie, it's a space invader, and it's moving and wanting to sync itself up ) but when the state changes so that info isn't needed ( The invader is dying, so no movement just animation 'til death ) then it is slightly cumbersome.</p> <p>When it happens that way, I just swallow it, but secretly hate it. At the end of the day, it's only really bugging me, it's not doing any harm in the grand scheme of a running game, couple of lost ms, but nothing to worry about, so it's easier to just secretly hate it :)</p> Check me out posting a comment about my own words on a different site, that’s how important I think I am ;)

Thanks for your kind words about the state machine approach mate. I’ve said it a load of times since actually writing that though, that I thought everyone did it that way anyway.

You raise a really good point about passing data. For example if you’re passing a timestamp to a instance every frame, that’s all well and good when that instance needs to know about it ( ie, it’s a space invader, and it’s moving and wanting to sync itself up ) but when the state changes so that info isn’t needed ( The invader is dying, so no movement just animation ’til death ) then it is slightly cumbersome.

When it happens that way, I just swallow it, but secretly hate it. At the end of the day, it’s only really bugging me, it’s not doing any harm in the grand scheme of a running game, couple of lost ms, but nothing to worry about, so it’s easier to just secretly hate it :)

]]>