Alternatives to coroutines -

This example has been used in another question, to describe how to cut the script of the Scottish script in the video game Can be used:

  Bob.Walkato (Jane) Bob.Look (Jane) Bob ("How are you?") Wait (2) Jane ("Right") ...   
 In the main event, each festival yields which does the animation, time, etc. before starting the kerutin. There will be an event queue instead of the code for possible options for the collineins, but then one has to apply the control logic and the loops as incidents. Are there other alternatives of Coronable to be used to implement this type of activity? I have seen the callback mentioned in some articles, but I'm not sure how the code looks.   
 
 
 Correnettes are favorable for this because when you do not have any trouble in all your local state variables i.e. Manually manually without storing it in a context.  
 But I do not see it as an alternative system. The more you would like to be a supplement, you would like to be in addition to the choreotin-based scripting system.  
  Example (in some compatible C ++):   
 You have implemented a behavior using the Korenin with these lines:    Enter the class: Public NPCBavier {Enterhouse (House Theon) {_theHouse = theHouse; } Zero Start () {_theHouse.AddNPC (NPC ()); } Zero Update () {NPC (). Walko (_theHouse.GetDoor (.) Status ()); . NPC (FaceObject (_theHouse.GetDoor ()); . NPC () PlayAnimation (NPC () Animation () Go (eAnimKnockOnDoor) ..); Sleep (1.0f); . NPC (OpenDoor (_theHouse.GetDoor ()); } Zero end () {/ * nothing} private house _theHouse; }   
 Imagine the NPC method itself will create NPC BeahiWeare Objects, push them into any kind of deal pile and return them with a call fulfilling those behaviors.  
  Sleep (1.0F)  Calls will yield to your script scheduler and allow other scripts to run. Call  Sleep  to generate  WalkTo ,  FaceObject ,  PlayAnimation  and  OpenDoor  Based on either a known animation period, to wake up from time to time to wake up to see if the pathfinder and locomotion system is running or whatever.  
 What if NPC faces a situation, then it will have to deal with the door on the door? You do not want to check all these incidents everywhere in your cortine-based code. Having an event system with complement of coratein will make it easier:  
  a garbage cannon : The garbage cans can broadcast an event in a nearby NPC. NPC object decides to go and fix a new behavioral object on its stack.  WalkTo  Behavior is calling  sleep  in any yield, but now the behavior is going to  FixTrashcan  behavior is running. When  meets FixTrashcan   walkto  behavior  will come out of sleep  and never know about the event of garbage but it is still on the door On the way, and under that we are still running  Enterhouse .  
  An explosion occurs : An explosion is similar to an event garbage, but this time the NPC object resets the functioning of it and the  FleeInPanic  behavior Decides to push. He will not return to  EnterHouse   
 I hope you will see what I mean by living together in events and choreinin in the AI ​​system. If you still produce for your script scheduler, then you can use the event to handle obstructions and keep the logic to deal with centralized without polluting your behavior.  
 If you do not already have single-threaded choreotypes in C / C ++ can be implemented, I can highly recommend it.  
 He uses only the smallest bit of inline assembly (single instruction) to save the stack pointer, and the code is easily portable for a whole bunch of platforms. , Was running on PS3 and Wii  
 Another good thing about scheduler / script setup is that it gets offset by applying off-screen or far Ai characters / scripts to objects, if you have resources for something else Need is just a few schedulers with a priority system in you and you have good to go.