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

OOD- Abusing States?

1 post in this topic

Say I have a player class. This player is made up of a few things: A bounding box, a moveable entity, and animations.

When this player moves left, what is actually happening is a force pushing the moveable entity in the negative direction. A bounding box detects any on-coming obstacles. On the case of contact, the force applied needs to be halted immediately. Also, the animation state knows that RUN_LEFT should be playing as the player moves.

Cool.

But what about when the player jumps? The animation consists of an elaborate transition from a squat to an upright launch and finally the "in the air jumping" pose is reached. During this time of the animation, the user cannot make the player move or do anything else. When the player is "in the air" he can do something again.

Okay.

I thought about breaking up the player into pieces, or states. One state consists of the update moving left and checking for all left-stuff. Another state for moving right. Another state for mid-jump, and when the jump is completed; a final state for being in the air ( abs(Y velocity) > 0 && no_contact ).

If each state is represented as a class that the player can "be in", would this be over kill? The pros would be that it will 1) be easy to debug. We'd know exactly what state it is in if the logic breaks. 2) The pre-jump animation would play and move onto the next state satisfying the condition of the player being unable to do anything until this animation is completed and 3) the player's logic function doUpdate() will be very clean and not cluttered with flags.

The cons: More classes. Perhaps overkill.

If I choose to break the animation system into states instead, the player class would still be a tad bloated (but not too much) and I'd still have to clutter it with animation checks (i.e. if(inputRecieved() && !animation->is(PLAYER_PRE_JUMP) then ... )

So overkill? Or is there a better way to do this?

Thanks! :D
0

Share this post


Link to post
Share on other sites
It really depends on the scope of your project. If you know 100% that your player file won't get very complex, you're probably
best off defining a simple enumerated state and maybe defining some transition functions. If your player may get expansive,
I'd suggest using a more complex state system.

This prompted me to look up some of my old game source, in one of my games I found a polymorphic state machine.
Knowing what I know now, I would probably expand the state machine to use these states like a map, strictly defining
possible state transitions. In this example code, states transition themselves. I would maintain that behavior, but restrict
it to sibling nodes.

Using states like these are a great way to switch from hard-coded to scripted behavior. Instead of defining an object for
every state, you can have a ScriptedState object with a loaded script reference.

The global state defines character interactions with the world regardless of what state they are in.
You may be better off omitting this state and maintaining that behavior within the player class, it's up to you.

BaseObject.h
[CODE]
template <class ENTITY_TYPE>
class IBaseObjectState
{
public:
IBaseObjectState(){}
virtual ~IBaseObjectState(){}

virtual void Begin(ENTITY_TYPE*)=0;
virtual void Execute(ENTITY_TYPE*)=0;
virtual void End(ENTITY_TYPE*)=0;
};
[/CODE]

CharacterStateIdle.h
[CODE]

class CharacterStateIdle : public IBaseObjectState<PlayerObject>
{
private:
float m_fTimeSpent; // The time we've been idle (to trigger the "waiting" animation)
SCTimer *m_pTimer;

// Constructor List
CharacterStateIdle();
~CharacterStateIdle();
CharacterStateIdle(const CharacterStateIdle &ref);
CharacterStateIdle &operator=(const CharacterStateIdle &ref);

public:
void Begin(PlayerObject *pOwner);
void Execute(PlayerObject *pOwner);
void End(PlayerObject *pOwner);
};
[/CODE]

IObjectStateMachine.h
[CODE]
template <class ENTITY_TYPE>
class IObjectStateMachine
{
private:
ENTITY_TYPE* m_pOwner;
IBaseObjectState<ENTITY_TYPE>* m_pCurrentState;
IBaseObjectState<ENTITY_TYPE>* m_pPreviousState;
IBaseObjectState<ENTITY_TYPE>* m_pGlobalState;

public:
IObjectStateMachine(ENTITY_TYPE* owner) : m_pOwner(owner), m_pCurrentState(0),
m_pPreviousState(0), m_pGlobalState(0);

void SetCurrentState(IBaseObjectState<ENTITY_TYPE>* s){m_pCurrentState = s;}
void SetGlobalState(IBaseObjectState<ENTITY_TYPE>* s) {m_pGlobalState = s;}
void SetPreviousState(IBaseObjectState<ENTITY_TYPE>* s){m_pPreviousState = s;}

void Update() const
{
if (m_pGlobalState) m_pGlobalState->Execute(m_pOwner);
if (m_pCurrentState) m_pCurrentState->Execute(m_pOwner);
}

void ChangeState(IBaseObjectState<ENTITY_TYPE>* pNewState)
{
if (pNewState == m_pCurrentState) return;
m_pPreviousState = m_pCurrentState;
m_pCurrentState->End(m_pOwner);
m_pCurrentState = pNewState;
m_pCurrentState->Begin(m_pOwner);
}

void RevertState() { ChangeState(m_pPreviousState); }

IBaseObjectState<ENTITY_TYPE>* CurrentState() const{return m_pCurrentState;}
IBaseObjectState<ENTITY_TYPE>* GlobalState() const{return m_pGlobalState;}
IBaseObjectState<ENTITY_TYPE>* PreviousState() const{return m_pPreviousState;}
bool isInState(const IBaseObjectState<ENTITY_TYPE>& st) const;
};
[/CODE]
1

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