That will create an *.qb file at the game folder. The name of the file will be the same name of the building. The screen below (from my game folder) shows the build named lala got exported as lala.qb, while the building shown in the previous screenshot had no name, so it got its number, as 1.qb
You know, a class (like a toy maker) who’s only purpose is creating mini toy houses, so you can play a city builder game where your citizens play with city building toys!
I expect the functionality to dump a region into a QB file is still in the engine. Someone would just need to hook it up to extract the new building system’s region. Perhaps something that ACE could do? @DaniAngione
Indeed, it wasn’t too hard to implement. I did it in a bit of an awkward way (accessing the building status UI view to grab the current building entity reference) so I’ll probably be tweaking it a bit before committing it to unstable (probably I’ll call a client command and not pass the entity in from the UI, and the client call handler can call the client building service to check what the selected building is, then call a server function to do the dumping on that building entity).
