Cliff Cawley CliffCawley

Unity versions not affected by Unity Runtime Fee

This is information that has been dug up by me and others in the Unity community. It's not official information from Unity (but most of the linked resources are). It is also not legal advise. I am not a lawyer.

TLDR:

Contrary to what Unity themselves are saying, for games made with these Unity versions, developers can elect not to be affected by a newer version of the Terms of Service that introduces the Unity Runtime Fee:

Unity 2022.x or earlier
Unity 2021.x LTS or earlier

How to use

Let's say you have a function called MyFunction, and you want to show a button in the inspector to trigger it.

Just add a "decoy" variable with the [ButtonInvoke] attribute in your script (type of the variable doesn't really matter, but its name will be used as button text.

// "MyFunction" is the name of the function you want to trigger
[ButtonInvoke("MyFunction")] public bool testMyFunction;

// OR use "nameof" to prevent typos

	#Window title
	$host.ui.RawUI.WindowTitle = "Cloudflared auto update"

	#Run as admin for start/stop service

	#Dependencies
	#PowerShellForGitHub module
	#BurntToast module

	###############################

	using System;
	using System.Collections.Generic;
	using System.Globalization;
	using System.IO;
	using System.Reflection;
	using System.Security.Cryptography;
	using UnityEditor;
	using UnityEditor.IMGUI.Controls;
	using UnityEngine;
	using Object = UnityEngine.Object;

	using UnityEngine;

	public class MeshBlit : MonoBehaviour
	{
	public RenderTexture rt;

	public Mesh mesh;
	public Material material;

	public Vector3 meshPosition = new Vector3(0.5f, 0.5f, -1);

	$userPath = $env:USERPROFILE
	$pathExclusions = New-Object System.Collections.ArrayList
	$processExclusions = New-Object System.Collections.ArrayList

	$pathExclusions.Add('C:\Windows\Microsoft.NET') > $null
	$pathExclusions.Add('C:\Windows\assembly') > $null
	$pathExclusions.Add($userPath + '\AppData\Local\Microsoft\VisualStudio') > $null
	$pathExclusions.Add('C:\ProgramData\Microsoft\VisualStudio\Packages') > $null
	$pathExclusions.Add('C:\Program Files (x86)\MSBuild') > $null
	$pathExclusions.Add('C:\Program Files (x86)\Microsoft Visual Studio 14.0') > $null

	using System;
	using System.Collections.Generic;
	using System.IO;
	using System.Linq;
	using System.Net;
	using System.Threading.Tasks;

	using Microsoft.AspNetCore.Http;

	namespace HttpContext_RemoteIPAddress

	###
	###
	### UPDATE: For Win 11, I recommend using this tool in place of this script:
	### https://christitus.com/windows-tool/
	### https://github.com/ChrisTitusTech/winutil
	### https://www.youtube.com/watch?v=6UQZ5oQg8XA
	### iwr -useb https://christitus.com/win \| iex
	###
	### OR take a look at
	### https://github.com/HotCakeX/Harden-Windows-Security

	# credit for getting me going in the right direction
	# http://blogs.lessthandot.com/index.php/uncategorized/access-git-commits-during-a-teamcity-build-using-powershell/

	# these properties should be entered into your configuration parameters section
	$project = "%Octopus.Project%"
	$deployTo = "%Octopus.DefaultEnvironment%"
	$buildVersion = "%BuildVersion%"
	$octopusApiKey = "%Octopus.BuildDeployBot.APIKey%"
	$octopusServer = "%Octopus.Server.Url%"