Re: [Adonthell-devel] What's next?

[Sasha Kushnirenko]

Hi, Kai!

> But if we'd store the event data with the event and pass it to the 
> script at runtime, we could do with a single instance of the script 
> that'll work for all teleports. Like this:

Sounds like a very constructive idea.  I'm probably missing somethig, but
would not be there a potential problem if an event data becomes huge and
moving it around could be complicated?

>   - Each action is detailed in a script of its own, so that actions can be
>     reused between characters. (That means, the parameters for actions are
>     defined in the master schedule)

Sounds like using your nice adea again.  

>   - Characters can receive messages that override the master schedule. A
>     message will simply start a certain action. Messages may come from
>     game events, other NPCs, etc ...

Good!  Is it something v0.4 specific, or continuation of v0.3 ideas? Though
who is going to superwise orderly behaviour of "cron-like" events and
message-triggered events?

> * dialogue engine: no need to change that, I think. 

Agreed.  This is a very good tool.  It does take some time to get used to
it, but overall it covers a lot of possible situations.

> 
>   What will be further refined is the dialogue editor, however. If I 
> manage,
>   I'll finally implement the subdialogue feature, which means that 
> pieces of
>   dialogue can also be reused, either for different dialogues of the 
> same
>   character or even for different characters. But that'll come last ...

I wouldn't.....  How often do we need this?  We can endup with boring
dialogues, which consists of "standard subdialogues"

> Okay, I think that covers everything I have originally worked on. 
> Porting it to v0.4 may take a while, as there are a few things to 
> rewrite. But once it is done, we'll have a good foundation for building 
> the v0.4 demo.

What is the CVS status.  How should one checkout the code to get latest and
greatest?

Sasha.