hi. @JasonL
Thanks for the link.
Thanks to you, I checked many schemas.

The problem is that if I don't set the script to true , the response is returned as below:

"'scripts' component must be true when the 'meta' component is true."

components: {
meta: true,
scripts: false,
files: false,
customEntities: false,
legacyFiles: false,
},
options: {
meta: {
excludes: {
itemCatalog: false,
productPricing: false,
pushCertificates: true,
integrations: true,
myServers: true,
lobbies: true,
leaderboardsTournaments: true,
independentLeaderboards: true,
migratableGlobalEntities: true,
selfServiceBranding: true,
},
},
scripts: {},
},
allowLiveUpdate: true,

Hi @jesgonzalez ,

Yes - unfortunately, you need to use AuthenticateExternal. We do not have official middleware status with Xbox. We've been trying for years - but as anyone who has dealt with Xbox in recent years knows, they are extremely resource-constrained.

Paraphrasing our most recent interactions

Due to extremely limited resources and a couple of years of re-orgs, Microsoft won't adopt or support new tools or technologies unless we can prove there’s a clear and active need from developers working on officially approved Xbox titles.

(We actually had been making progress on this a few months ago - but then the personnel we were working with got laid off... So now we're at the back of the bus again.)

Unfortunately, our lack of status means we can't provide clear details on how to do it, but we do have some service partners / contractors / consultants we can refer you to who can quickly connect you. If you want to reach out to us via our Support widget, we can put you in touch with them.

Oh - and be sure to mention this situation to your Xbox account rep (if you are lucky enough to have one). It's only via pressure from the dev community that we're going to get unblocked in this area!

Paul.

Thanks for reaching out and for raising the question.

At the moment, the VS Code extension does not support targeting or importing from a specific directory. Its primary purpose is to synchronize Cloud Scripts stored in brainCloud and provide a convenient way to edit them using standard VS Code workflows and tooling.

We have created an internal task to review this limitation and discuss potential improvements to the extension so that it better supports directory-based workflows in the future.

In the meantime, one practical workaround is to export your Cloud Scripts directly from the brainCloud portal. Once exported, all scripts can be reviewed locally. You can then organize them into a folder structure that mirrors your desired layout, including the use of subfolders and .ccjs files. From there, you can zip the contents and import them back into your app, which can significantly reduce the need for repetitive copy and paste actions across individual files.

Please let us know if this approach works for your use case or if you have additional feedback on how you would like to see the extension evolve.

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.