We’re excited to share that Custom Templates have officially landed in the latest Unity Hub3.18 Beta! This update provides a standardized, built-in way to create, manage, and share your project templates directly within the Hub.
Feature Highlights:
Generate new templates directly from an existing project or via the new Templates page.
Define your template’s name, description, version, thumbnail, and signing organization.
Link your templates directly to GitHub, GitLab, or Unity Version Control (UVCS) repositories.
A brand-new Templates page lets you view, search, and filter all your templates by Editor version.
We’d love to hear your thoughts! Try it out in the beta and drop your feedback, questions or suggestions in the thread below.
Custom Templates are now officially supported, providing a standardized way to create and share project templates directly in Unity Hub.
New custom templates can be created from an existing project by selecting Save project as custom template from the project menu or from the New template button on the new Templates page.
Template creation supports defining a name, description, version, thumbnail image, and signing organization.
Template signing and verification are supported to improve trust and consistency when sharing templates across teams.
Custom templates can optionally be linked to GitHub, GitLab, or Unity Version Control (UVCS) repositories.
A new Templates page displays all templates in the selected template directory, and templates can be searched for by name or filtered by Editor.
Existing templates can be added to Unity Hub by moving them into the selected template directory, or by updating the directory in Settings > Templates to point to the local template location.
stupid part is, long time ago when templates started being a thing i swear the unity announcement was you can make your own, and people worked out how, but when I found a bug i was told it wasnt feasible… and was therefore a feature request.
I know this is not directly related, but what about supporting Git packages in manifest file when uploading assets for the Template category on the Asset Store?
They are ignored for now, so when the user downloads such a template from UAS, they need separately and manually download the requested Git packages.
Example with Getting Started tutorial to install such a package correctly.
I’m on CachyOs Linux (non-supported) so I won’t see these changes for a long-long time. I’m really glad for this feature, we’re waiting for this for an even longer time. So, thank you!
I have a question though: how this feature handles private repos? Do you store the required credentials or do you ask for it one by one when the template is used on a machine the credentials were not yet used?
Especially when it comes to the git-packages in use.
I’d be stoked if Asset Store assets could provide custom Hub templates. Even if that means to create a project first, install the asset, and use the asset’s “template installer” option.
Super useful feature. I was getting tired of doing the same thing over and over again.
The only things I’m missing are the ability to include other root files (like .gitignore, .gitattributes, .editorconfig and etc) and project name placeholders
Templates are interesting and useful but two problems that I don’t see any documentations or answers for:
What is the process to update templates? You ask for a version number in the template (and it’s stored in the json file) but there’s no apparent way to update a template to a newer version.
Templates are stored on the system drive by default. Any way to change this location? I don’t see a setting anywhere. It could be done with a symbolic link but I’d rather avoid that and don’t want to save these on my system drive.
And I have a question about templates as well. The creation says the Source Control is optional. But I can’t choose a non-source-control in the setting.
So how can I save my template without source control? And especially, without Cloud? It doesn’t allow me to unselect either version control provider or cloud project.
Thanks. I missed the template location setting so that’s good.
As for source control, you can just skip that as it’s optional. Make a local project and save it as a template and you don’t have to worry about cloud or source provider.
Nope. But I guess it is mandatory if you choose source control.
Wow.
(#@$&@^TGRFK! Argh. Who made this UX decision?! Please still add a “No source control” to the list or leave it disabled by default. I’m not particularly easily oversee these types of things, now I did. This is simply bad UX.
Hi, Whatever I do when I try to create a template, I get “Template signature error” during the process. Whether using Unity Version control, Github, or no source control at all, I can’t get past this error and there is no other information as to wh this is happening. Is it a known bug? Looks like nobodfy else is having this issue
Yes this is a known issue and we have some fixes on the way in 3.18.1! I can’t commit to an exact release date, but we hope to have it out within a week.
