Amplify Shader Editor
* Please use Dropbox, Google Drive, WeTransfer, or an equivalent service to share your package.
Submission Terms
We welcome, and encourage, all user submissions but we must first agree on some submission terms in order to avoid possible conflicts or legal issues. Must be submitted using Unity 5.5 or higher, you own any content created using the Amplify Shader Editor, or any content created for the editor such as nodes or additional extensions, you are completely free to sell any assets that you create. However, you must agree to waive certain rights when a submitted package is accepted into the official ASE package or website.
1. Subject to acceptance, submission does not guarantee integration into the official Amplify Shader Editor package.
2. Submitted content will be fully credited, including comments in the actual source Shader or Node files.
3. You agree to waive any ownership rights over submitted content that is accepted and distributed with the official Amplify Shader Editor package.
4. Amplify Creations reserves the right to alter, adapt, and exploit any submitted content under the terms set above.You may still distribute submitted content, you own all the rights over created content. The waiver applies exclusively to the actual content integrated and distributed in the Amplify Shader Editor package.
Requirements
Included assets NOT created with the Amplify Shader Editor must be royalty free and not subject to 3rd-party attribution licenses, or completely owned by you.
File Upload
Please use a common file hosting service such as Dropbox, WeTransfer, GoogleDrive, or similar; zipped package preferred.
Credits
Be sure to include the name and website, or social link, that should be used in the credits section of the submitted content. You may list them in the description box of the submission form or simply in the Creator URL section.
Shader Samples
- Working shader(s)
- Use comment nodes whenever possible
- 1 example material and mesh per-shader.
- Use simple names without special symbols, complex prefixes or suffixes.
Node Samples
- Working Node(s)
- Commented code
- If applicable, 1 example shader.
- If applicable, 1 example material and mesh per-shader.
- Use simple names without special symbols, complex prefixes or suffixes.
File Structure
Shaders
Assets\AmplifyShaderEditor\Samples\ShaderName(Your files go here)
Avoid using SubFolders for Material or Textures, unless absolutely necessary.Nodes
Specify your node category in the description box of the submission form. Nodes will be adjusted and integrated on our side.