Add world.spawn() #27
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was almost able to spawn the breakout ball with the script, but we can't have reflected bundles yet, and when trying to add the components one by one we were missing reflected Default implementations on
ComputedVisiblityandSprite, and I'm not sure how to go about creating a typedHandle<T>from scratch in a script. :/It seems like reflected bundles might be the best way to go about spawning things like sprites. If the bundle implemented Reflect then you could just set/patch the fields you wanted to modify on the default bundle, so we wouldn't have to worry about creating a
Handle<T>, because we can just set the Handle.id from the script.