Replies: 3 comments 3 replies
-
I'm in the same boat as Keristero. I'm curious about what the "next" branch is and I'd love to know more about it! I'm currently using the "main" branch and I noticed that "next" is far more active and 200 commits ahead of "main". |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, the next branch is a rewrite of bitECS that adds a bunch of new features like prefabs, relationships, queues and ranges while maintaining (mostly) interoperability with bitECS v0.3.4. It will also perform better and suggest current day best practices like using native JS arrays instead of typed arrays. You can get a sneak peak by checking out the in progress docs here. There is no time table for release or even milestones for what we are looking to accomplish before releasing it. The next branch is very much a work in progress, but we will be publishing alphas time to time and move to a beta once things settle. More to come. |
Beta Was this translation helpful? Give feedback.
-
@krispya, is development of the next branch open to external contributors? If one was interested in getting involved, what would be the best way to do so? |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm working on a tiny engine of sorts for my personal projects based on the current master branch, I was poking around to see if there is a way for me to deserialize replace (removing entities that don't exist in the serialized snapshot).
I see there is a very active branch, is there anywhere I can can read about the upcoming changes or inspiration for them?
Beta Was this translation helpful? Give feedback.
All reactions