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

Import Unity components via BTL #2

Open
eelstork opened this issue Sep 17, 2022 · 2 comments
Open

Import Unity components via BTL #2

eelstork opened this issue Sep 17, 2022 · 2 comments
Labels
good first issue Good for newcomers

Comments

@eelstork
Copy link
Collaborator

Currently BTL imports via a list of designated components in the BTL component inspector; this will not scale when specialized modules refer specialized somponents.

@eelstork eelstork changed the title Import components via BTL import components via BTL Sep 17, 2022
@eelstork eelstork added this to the Alpha milestone Sep 28, 2022
@eelstork
Copy link
Collaborator Author

Removing from alpha for now; if this comes around as a pain point, will review.

@eelstork eelstork removed this from the Alpha milestone Sep 28, 2022
@eelstork eelstork changed the title import components via BTL Import Unity components via BTL Sep 29, 2022
@eelstork
Copy link
Collaborator Author

Relatedly, instead of passing components via the BTL inspector, a list of required components (meaning type names, not hard links) would be neat.

In C# I tend to use Req<T>() statements; these ensure quick setup and mean less clutter in the editor while editing. Currently BT-lang has no equivalent, as a result components need to be added ahead of time.

@eelstork eelstork added the good first issue Good for newcomers label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant