Hello!
I am an engineer working on this and have a question for you all.
I am reading that you are having problems with CodeBlocks and FBS. We really hope to convert more worlds to FBS in the future as it unlocks a lot more possibilities with what we can do. Can you please list issues or bugs you are facing with FBS so we can make it easier for you to convert your worlds?
Thank you
The largest issue and concern is around the way FBS behaves between worlds when saved as a legacy asset. If we save a FBS as a legacy asset and use it elsewhere, any modification impacts all worlds using that asset. This would be expected for a template asset. Additionally, once we pull out a pre-FBS asset it automatically updates not only the script in the world, but also the asset in our folders.
As an example: Let's say I made a game of traditional Yahtzee with five 6-sided die. Then I want to make a new similar game with 12 sided die instead. Since most of the hard work has already been done we would want to take our previous work and modify from there, so we bring that scripted asset from our library as a starting point. Problem is once I modify that script it also breaks every other world with that Yahtzee game.
With FBS that script gizmo turns into a viewport into the actual script as I understand it. When we attempt to save or load this FBS gizmo as a legacy asset, could this instead be an alias to save or load a copy of the FBS rather than a link to the original?
