Release v3.0.0

[amakropoulos]

No description provided.

[Draco18s]

Downloaded this to see if it solves any of the problems I've been having.

Some issues:

• Sample chat bot scene has a missing script on the LLMCharacter object and the ChatBot monobehavior has no reference for its LLMAgent, so that will throw an NRE
• LLMAgent.Warmup calls ChatAsync before the Lama llmAgent.llmAgent field is set (by SetupLLMClient), throwing a NRE, even if not using a Lama based model.
• Using a coroutine to wait for the field to be non-null before calling Warmup just straight up crashes the Unity editor.
• Ended up just waiting for the field to be non-null and calling WarmupCallback directly instead.
• Whether or not the response is streamed has gone missing. Seems to always be in stream mode, chatbot demo doesn't populate the chat bubble, just constantly replaces with the next token.

[Leuconoe]

Hello,

I recently synced my repository with the release/v3.0.0 branch to proceed with PR #374. While cherry-picking the relevant commits to continue development, I encountered a few errors related to LlamaLib . I wanted to reach out to check if these are known issues or if the branch is perhaps still in progress.

Duplicate AssemblyInfo Attributes: It appears that LlamaLib is auto-generating AssemblyInfo, which leads to duplicate attribute errors (e.g., AssemblyCompanyAttribute) during the build process.
Missing Unity Preprocessor Directives: In LlamaLib.cs, Unity-specific preprocessor directives (such as UNITY_ANDROID) seem to be missing. As a result, mobile projects incorrectly reference the desktop source.
I'm cautiously asking whether this is an intentional action.

Thank you for your hard work.

[amakropoulos]

@Leuconoe thanks for the info!
I haven't yet tested it on mobile, probably today. I'll look into the preprocessor directives.
I'm not sure how the duplicate AssemblyInfo happens. I'll try on a new project to test it out.