Feature Request: Support ISharedComponentData generation about gdk-for-unity

[zeroZshadow]

Could you explain a little bit more about the usecase behind this?

[No3371]

For example, I now have a component to be monster tier/type, it contains a value to indicate what it is.
This purpose is very simple so I don't want to use Metadata(string) for this, and entities with different values may have same Metadata, like: T1Fish is "Fish", T2Fish is also "Fish".

component Fish {
    id = n;
    int tier = 1;
}

If the component being generated to a ISharedComponentData, I can simply add the filter to the EntityQuery I made, then ECS gives me all the entities, it's efficient because entities are already put int different chunks based on the value.

But now I have to add additional ECS components like FishT1, FishT2, FishT3... or another custom ISharedComponentData FishTier the entities when they are checked out for this purpose (more ECS components also means less entities could fit into a chunks)

Well, since we have limited resource available on GCP, every bit of performance is important, isn't it?

[zeroZshadow]

This is not a feature we'll currently be able to support.

However it should be trivial to implement yourself if you'd like.
You can add a system that runs just after the SpatialOSReceiveGroup and checks for entities with components you'd like to group on, and are missing the grouping component. Then you can add the shared component with the right value to group your entities. I'd recommend using an entity command buffer to keep things fast.

[No3371]

OK, thanks for replying 😄