A team management problem we've had this week:
In order to implement enemy AI in the system they'd designed, our programmers needed Finite State Machines (FSMs) to describe enemy behaviour. Unfortunately, our team's designer, Shea, hadn't ever heard of an FSM.This is what he was able to supply us at first:
I organised a meeting, so that Shea could describe his vision of enemy behaviour to the programmers in-depth. However when it came to implementing the behaviour, we found that we still didn't have enough information.
Rather than making behaviours and conditions up myself, I figured it would be worth it to teach him the ins and outs of FSMs so that we could continue to work through that pipeline in the future.
Shea's first attempt:


No comments:
Post a Comment