package.json

{
  "name": "com.unity.addressables",
  "displayName": "Addressables",
  "version": "4.1.2",
  "unity": "6000.0",
  "description": "The Addressables package provides a user interface in the Unity Editor to organize and manage the assets in your project, to create content builds that you can ship along with a Player build. It also has an API that you can use to load and release assets at runtime.\n\nThe Addressables package was originally designed on top of Unity's AssetBundle system, but is also compatible with the newer content directories system. Addressables automatically manages dependencies, asset locations, and provides simpler workflows for memory management which you otherwise have to handle manually in the AssetBundle and content directories systems.\n\nWhen you make an asset Addressable, you can use that asset's address to load it locally or from a content delivery network, rather than using its file name, AssetBundle location, or content directory location. This means you can change the location of assets in a project without needing to rewrite code.",
  "keywords": [
    "asset",
    "resources",
    "bundle",
    "bundles",
    "assetbundles"
  ],
  "dependencies": {
    "com.unity.scriptablebuildpipeline": "4.0.2",
    "com.unity.modules.assetbundle": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    "com.unity.profiling.core": "1.0.2",
    "com.unity.test-framework": "1.4.5"
  },
  "samples": [
    {
      "displayName": "Addressables Utility",
      "description": "This sample contains a set of utility functions for Addressables.",
      "path": "Samples~/AddressablesUtility"
    },
    {
      "displayName": "ComponentReference",
      "description": "This sample creates an AssetReference that is restricted to having a specific Component. See the ComponentReference sample project located at github.com/Unity-Technologies/Addressables-Sample",
      "path": "Samples~/ComponentReference"
    },
    {
      "displayName": "Custom Analyze Rules",
      "description": "This sample shows how to create custom AnalyzeRules for use within the Analyze window. Both rules follow the recommended pattern for adding themselves to the UI. See the Custom Analyze Rules sample project located at github.com/Unity-Technologies/Addressables-Sample",
      "path": "Samples~/CustomAnalyzeRules"
    },
    {
      "displayName": "Custom Build and Playmode Scripts",
      "description": "Example custom build and play mode scripts provided.  Along with a README discussing how to add them to the Addressables system.",
      "path": "Samples~/CustomBuildAndPlaymodeScripts"
    },
    {
      "displayName": "Disable AssetImport on Build",
      "description": "A script that disables asset importing during a player build.  This improves build performance since AssetBundles are copied into StreamingAssets at build time.",
      "path": "Samples~/DisableAssetImportOnBuild"
    },
    {
      "displayName": "Import Groups Tool",
      "description": "A tool that imports group assets (for example from a custom package) to the current project.",
      "path": "Samples~/ImportExistingGroup"
    },
    {
      "displayName": "Prefab Spawner",
      "description": "A basic script that instantiates and destroys a prefab AssetReference.",
      "path": "Samples~/PrefabSpawner"
    }
  ],
  "_upm": {
    "changelog": "- Update dependency on Scriptable Build Pipeline to 4.0.2\n- Content directory builds run by an Addressables build now appear nested under it in the Build Analysis window.\n- Fixed a `NullReferenceException` when clearing content update flags on a folder entry with a null child.\n- Fixed issue where the AddressableAssetSettings inspector tab would become non intractable if docked with the Groups window inspector when the Shared Bundle Settings is set to Custom Group and a click is detected in the Shared Bundle Settings Group property field, thus changing the window focus.\n- Fixed an issue where in the group selector within the inspector for an Addressable asset would not be able to select Content Directory groups.\n- Fixed a `NullReferenceException` when using \"Add Reports from Folder\" in the Addressables Report window.\n- Fixed an issue where we were running the wrong legacy binary formatter tool to convert files on ARM64 OSX machines\n- Fixed compile errors in the Addressables test assemblies when the MSBuild compilation pipeline is enabled.\n- Fixed the Build Details section of the Build Analysis window not showing the related builds of an Addressables build.\n- Fixed an issue where the Asset Provider and Asset Bundle Provider shown in the AddressableAssetSettings inspector did not match the provider types used in the build when they were set on a BundledAssetGroupSchema through script. (UUM-154191)\n- Fixed an issue where custom provider types deriving from a built-in provider were displayed with the base provider's name in type dropdowns.\n- Fixed an editor crash when exiting Play mode with a scene loaded from a Content Directory.\n- Added the ability to open the Build Analysis Window from the Addressables Report and link it to a specific job.\n- Updated the Addressables Report UX in the Build Analysis window on Unity 6.7+.\n- Fixed an issue where an import worker spawning during a player build would cause the Addressables link.xml to be deleted, thus causing 'Unknown managed type references' errors."
  },
  "upmCi": {
    "footprint": "e90f4bccafeaed269a43b3696adaec43ce85bfd3"
  },
  "documentationUrl": "https://docs.unity3d.com/Packages/com.unity.addressables@4.1/manual/index.html",
  "repository": {
    "url": "https://github.cds.internal.unity3d.com/unity/Addressables.git",
    "type": "git",
    "revision": "f28f6f53b7d14c3b35f0921c1d7a397bd210dfde"
  }
}