Last year we took an important step in becoming more transparent with our Developer community by releasing the Developer Roadmap. We are continuing that tradition this year by updating it with upcoming features for 2019.
This roadmap is not meant to be a comprehensive list, but will give you an idea of the major features that are planned for this year. Over the course of this year we will continue to update this list and post in this announcement thread when changes are made.
Please keep in mind that our goal is to provide you with the best updates possible. On occasion, bugs or technical issues may cause us to move the release dates. We do this to ensure we are shipping amazing features that will improve your Roblox experience.
Looking forward to Script Collaboration, should make group projects even easier, hopefully that gets implemented quickly upon reaching the 3rd quarter!
“Streaming on by default” is concerning considering that we still have no way to explicitly define what gets streamed in together. This is a necessity before developers can take this feature seriously. Having only certain parts of a model streamed in just isn’t useful in a lot of cases.
I also want more control to be given to developers over what is streamed. At the very least, there’ll be a guarantee of instances within a minimum radius being streamed:
Really great things coming to the platform this year. Happy to see Streaming – Stability Improvements on the list. A very good service when creating really large worlds while still running smoothly on multiple types of devices. It would be helpful however if more documentation was provided on this feature as well as options for how the developer best sees fit to use it.
A lot of these updates will really improve the platform, it’s great to know what might be coming this year! I hope all of these updates ship on time, keep up the good work.
I’m really stoked for typed lua. I think there’s a lot of type richness unique with Lua in particular because of metatables. Specifically, it would be awesome of types could include metatable information in type relation. Things like overloaded operators, __call, __index, and __newindex are very versatile, and should be typed as such. Overloaded signatures, generics, proper handling of tuples are all must-haves for lua’s dynamic environment.
Please don’t mess this one up. I’d love to hear more about how this is going to be designed. For a while, I was contributing to lunar with this vision in mind.
Hope they come fast and are bugs-free.
