Skip to content
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

Create "agent" socket type to handle full agent data from clients like discord, etc #55

Open
lalalune opened this issue Apr 2, 2022 · 0 comments

Comments

@lalalune
Copy link

lalalune commented Apr 2, 2022

Right now we are using a purpose-built "Input Desctructure" component to get data from the agent and break it up without needing to define a lot of inputs per graph. This is not ideal. Since we end up using all of the agent data in lots of places, it makes out graph have a lot more sockets and nodes. We want to define a new agent type that passes all of this data in a single socket.

The agent destructure can still existing, and should have a corresponding restructure component even, but it should accept a specific socket type.

We might think about templating these nodes so a single structure / destructure can have a dropdown of template i/o or a custom option

alextitonis added a commit that referenced this issue May 11, 2022
Added the Event Manager Window
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant