32b43cfeb3
* Most resource types now have unique identifiers. * Applies to text, binary and imported resources. * File formats reference both by text and UID (when available). UID always has priority. * Resource UIDs are 64 bits for better compatibility with the engine. * Can be represented and used textually, example `uuid://dapwmgsmnl28u`. * A special binary cache file is used and exported, containing the mappings. Example of how it looks: ```GDScript [gd_scene load_steps=2 format=3 uid="uid://dw86wq31afig2"] [ext_resource type="PackedScene" uid="uid://bt36ojelx8q6c" path="res://subscene.scn" id="1_t56hs"] ``` GDScript, shaders and other special resource files can't currently provide UIDs, but this should be doable with special keywords on the files. This will be reserved for future PRs. |
||
---|---|---|
.. | ||
config | ||
crypto | ||
debugger | ||
error | ||
extension | ||
input | ||
io | ||
math | ||
object | ||
os | ||
string | ||
templates | ||
variant | ||
core_bind.cpp | ||
core_bind.h | ||
core_builders.py | ||
core_constants.cpp | ||
core_constants.h | ||
core_string_names.cpp | ||
core_string_names.h | ||
doc_data.cpp | ||
doc_data.h | ||
register_core_types.cpp | ||
register_core_types.h | ||
SCsub | ||
typedefs.h | ||
version.h |