The way it would work would be:
1) A mission waits on an event by calling $this->wait_for_action()
2) $this->wait_for_action calls the mission engine and asks to have one
of its methods called back when the action is performed by the user
3) the mission engine adds a row in the database containing: the action
to wait for, the user id of the player who has to perform the action,
and the mission identifier
4) Right before the end of the request processing, the mission engine
serializes the mission object and stores it
[vlad] I started to work on it. I modified the database structure and
took the opportunity to do a make release.
The mysql-diff was a pain to get over, i tried all methods in the help
and only the last one worked :)
But it seems that it worked, in the sense that i can see the updated
db_hackit.sql and db_hackit_test.sql
Can you guys try to do a make upgrade and see if it works correctly?
_______________________________________________
Farsides mailing list - [email protected]
Wiki: http://farsides.com/
List: http://farsides.com/ml/
Forum: http://farsides.com/forum/
Ideas: http://farsides.com/ideas/
Chat: http://farsides.com/chat/
