Closed TheAfroOfDoom closed 3 months ago
18d3631 should solve your issue, let me know if it doesn't.
@SnaveSutit that commit is working after i make some minor changes to adjust to the new blueprint format, so that's good!
but it looks like when i load a "fake model" into blockbench and export it, it saves the file now? this is a change in behavior from AJ v0
basically we:
loadModelFile()
exportProject
haven't looked into exactly what's saving that loaded file to disk on export, but i'm guessing it's related to the new meta.save_location
property. is this intentional/required behavior?
(this is definitely an issue that's specific to my project that is totally fair if you deem i'll just have to find a work-around somehow, but:)
this .ajblueprint
file saving after the exporter runs is new. you can see the properties i injected during runtime to the model in memory (NOT to the model on disk)
I've added an optional argument that allows you to disable the forced save.
my hero
Is your feature request related to a problem? Please describe. I have some tooling setup for my map's repository so I only need to commit changes to the model source file (
.ajmodel
/.ajblueprint
). I can safely.gitignore
AJ's exported files to minimize diffs and headache while committing.To support this workflow in AJ v0, my team created a fork of AJ that exposed the
safeExportProject
method to the API. This allowed us to create a tool that enabled the following behavior:yarn start export
in terminal.ajmodel
in the repo and callssafeExportProject
Describe the solution you'd like Expose a function to AJ's API that, when called, exports the currently-open Blockbench project as-is.
exportProject
is the specific method I want exposed.Describe alternatives you've considered N/A
Additional context N/A