-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better LLM and LLMClient workflow #151
Labels
enhancement
New feature or request
Milestone
Comments
I completely agree! |
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
As of now, you can chat by using only the LLM component. If you want to use multiple characters, you need to add LLMClient components. This makes sense, but I think it's a bit more intuitive if the LLM component does not inherit from LLMClient. Wouldn't it be better if the LLM component was just like a manager?
Basically, what I'm asking is to remove LLMClient functionality from the LLM component. You would then always need at least one LLMClient component to chat with the LLM. This does make it a tiny bit more complicated when setting up a simple chat with one character, but I think it is less confusing.
For a simple chat app, you would then need to add the LLM component and one LLMClient component (which can be on the same gameObject). For more complex games using multiple characters you also need one LLM component but also one LLMClient component per character.
You could also rename the LLM component to LLMManager, but that is not so important, especially because it would break existing projects.
I just think that the LLM component should only control settings that are the same on all LLMClients, such as which model to use. The LLMClient then only has settings that can be different for each character.
Thanks!
The text was updated successfully, but these errors were encountered: