[Question] Lua scripting. about edelstein HOT 3 CLOSED

this is the important part were registering an entire conversation interface for 2 speakers

this exposes the accessibility to lua to call the func with params

so the interface is loaded in the script globals and then the entire source is evaluated if it finds reference to the global it can call the C# function.

the heavy lifting is done by moonsharp, thats where the magic of converting a DynValue result which is placeholder for lua types gets auto converted to CLR type.

from edelstein.

On top of what @Bia10 said,

The whole request/response system is called Conversations in the project. Do check out FieldUser::Converse and FieldUser::Prompt to see where the logic flow starts for script dialogs.

Essentially, there is a Channel<object> in each conversation context which is basically an async queue that handles request and responses from the client. This creates the stateless 'awaiting' mechanism that powers every dialog that requires user input.

Every time a method like Self.AskMenu(..) is called, the conversation context reads from the async queue and if its empty, it waits.. forever. And on the packet handling side, whenever a response is received by the server, the server pushes into the async queue which finally unblocks the read and continues on with the conversation.

See:

1. https://github.com/Kaioru/Edelstein/blob/dev/src/common/Edelstein.Common.Gameplay.Game/Conversations/ConversationContext.cs#L26
2. https://learn.microsoft.com/en-us/dotnet/core/extensions/channels

from edelstein.

Closing this issue, feel free to continue the discussion under the 'Discussions' tab.

from edelstein.