Omitting scripting backend from editor window drawing and build folders #148
-
|
Hey, (and apologies if there's a better place to ask these sorts of questions) I'm adding some Build Platforms for a current project; in particular, they're console platforms, and so their scripting backend can only be set to IL2CPP. Since this is a constant, I'd like to avoid seeing "Mono/IL2CPP" specified in the SUB editor window; likewise, I'd like to avoid that being a component of the build output folder hierarchy – e.g., where Windows might have However, if I omit setting up Is there a way to get SUB to completely omit the scripting backend as a component of both the configuration names in the editor window, and in the build output folder hierarchy? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hey @nickfourtimes, you've just prompted me to enable Discussions for the project so that there is a better place to ask these sorts of questions 🎉 There currently isn't a way to omit the scripting backend from the build configuration key names, and although you can omit them from the build output path by removing the Are you looking to do this for aesthetic purposes, or for another reason? |
Beta Was this translation helpful? Give feedback.
-
|
Oh, lol, when I saw "Issue was converted into a Discussion," I thought I'd totally missed the Discussions tab. Glad to hear you'd just enabled it then! Honestly this was purely aesthetic for the moment, just one extra folder I have to click into to find the build artifact. Not really a problem! Just wanted to make sure I wasn't missing anything obvious. Thanks for the answer! And hoping to contribute more to SUB as we keep working with it. |
Beta Was this translation helpful? Give feedback.
-
|
You're most welcome! I feel you with the annoyance of navigating through build folders, but at the moment I'm prioritising getting the v8.0.0 release wrapped up, so I am unlikely to make any changes around this any time soon. Any contributions are always welcome though 🙏 |
Beta Was this translation helpful? Give feedback.
Hey @nickfourtimes, you've just prompted me to enable Discussions for the project so that there is a better place to ask these sorts of questions 🎉
There currently isn't a way to omit the scripting backend from the build configuration key names, and although you can omit them from the build output path by removing the
$SCRIPTING_BACKENDfrom the build path template, this obviously will cause a output path collisions if you enable Mono and IL2CPP for platforms that support both.Are you looking to do this for aesthetic purposes, or for another reason?