Releases: PassivePicasso/ThunderKit
7.1.1
Fixes
- Fix StageAssemblies using facilities not available in Unity 2019
7.1.0
Improvements
- Improve StageAssemblies error reporting to provide build errors with a context for each build error in the log entry
- Improve formatting of StageAssembly error reports to include source file links for errors
Fixes
- Fix Assemblies not building correctly on Unity 2020.x
7.0.0
Big thanks to @Nebby1999 for this building the majority of this update
Possible Breaking Change
-
Fix ScriptingSymbolManager using
-
instead of_
for spaces in symbols due
to-
not being supported by Visual Studio or .NET in defined symbols.This is only a breaking change if your project has used Define Constraints
in Assembly Definitions, otherwise this should have no impact.
Improvements
-
Added PackageSource.InstallPackages for ImportExtensions that need to install
multiple packages. This allows for a significant improvement in install time
for these types of extensions.
Improvements to the ThunderKit Package Manager related to this have not been
made but are planned. -
Add Post import prompt requesting the user restarts unity. A restart avoids a
class of erronous experiences where the Unity environment has not loaded
entirely after an import. -
Add a Beep when the importing process has completed (Default ON)
-
Add a toggle to disable post import beep in ThunderKit Settings.
Fixes
- Fix ImportConfiguration not updating correctly when new ImportExtensions are
loaded into the environment.
6.1.1
Fix Package.json Version
6.1.0
- Update ExecuteProcess to be a FlowPipelineJob instead of a PipelineJob
allowing it to utilize manifest data
6.0.2
- Fix exception when scanning for types in the Add Component menu preventing it
from opening (@Nebby1999)
6.0.1
Fixes
- Fix ThunderKit's package.json to reflect the current version
6.0.0
BREAKING CHANGES
This update includes breaking changes to how GUIDs are generated for assemblies.
Before updating to ThunderKit 6.0.0 you should be sure that your project's
assemblies are using the Stabilized Assembly GUID mode.
If you're not using the Stabilized Assembly GUID mode, or if you're unsure if
you are, open up ThunderKit Settings
and navigate to Import Configuration.
In the ImportConfiguration screen, locate the Import Assemblies entry and then
select "Stabilized" from the dropdown menu and finally press Update.
This will convert any assemblies managed by ThunderKit to use the Stabilized
GUID mode and should limit the impact of updating to ThunderKit 6.0.0
Improvements
-
Utilize blacklist and whitelist AssemblyProcessors for processing plugins in
addition to managed assemblies during import -
Remove Original and <2.0.0 AssetRipper GUID generation modes
This can be a breaking change for some projects
(Thanks to @Nebby1999 for this contribution) -
Modify ImportConfiguration to load ImportExtensions more defensively
-
Improve PathReference to minimize calls to AssetDatabase.FindAssets()
This significantly improves CPU and RAM costs durting pipeline execution
(Thanks to @KingEnderBrine for this contribution) -
Rework the Copy PipelineJob to allow non-overwriting copies, this chagne is
setup to be backwards compatible.
(Thanks to @KYPremco for this contribution)
Fixes
-
Fix installing latest package version from a PackageSource causing
invalid Version information to propogate in a project
(Thanks to @Nebby1999 for this contribution) -
Clean up ChangeLog entries with widths over 80 characters
5.4.5
Fixes
- Fix issue where loading scenes from the AddressableBrowser would fail even when in play mode
5.4.4
Fixes
- Fix issue where the Import button would launch the LocateGame function and require the user to import the game to close the dialog.