-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
More generic layers #443
Labels
enhancement
New feature or request
Comments
I agree with this. After I finish some of my current work I'm going to give this a try. |
Closed
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem related to your feature request.
Currently
Layer
are for entity and chunk, it's would be mildly impractical and casse pied if we start creating different layers for each api were we want layer to be use.For all componant that impl a layer solution, we attache ourself to one of the two layers, but we need to use
filter
in our impl which is suboptimale.What solution would you like?
I personally would see :
In the layer entity side ->
LayerMarker
componant that store a message queue (like the current one)[...]LayerData
componantEntityLayerData
storeFxHashMap<ChunkPos, BTreeSet<Entity>>
BossBarLayerData
storeBTreeSet<Entity>
On the other componant side ->
LayerId
componant that store the id of the layer it is onWhat alternative(s) have you considered?
We can use the
EntityLayer
and add the data componant.The text was updated successfully, but these errors were encountered: