You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AssetType::Object(..) and AssetType::Map store SequenceIdMappings in AssetSequenceIdMappings, as they only have one ItemId.
This must be done prior to loading SpawnsSequenceHandles in AssetSequenceComponentLoadingSystem, as objects need to know the sequence ID of the objects they are spawning.
AssetType::Ui loads SequenceIdMappings in AssetSequenceComponentLoadingSystem, as the SequenceIds need to be per BackgroundDefinition or UiDefinition for the indices in sequence component data (e.g. WaitSequenceHandles) to be correct.
This disparity works for now, but may be confusing. The difficulty in shifting the SequenceIdMappings loading for Objects is, Spawns can map from the AssetSlug in spawn config to AssetId, but not to an ItemId / SequenceId within that AssetId -- and ItemId does not exist until afterAssetSequenceComponentLoadingSystem has run.
The text was updated successfully, but these errors were encountered:
In GitLab by @azriel91 on Nov 29, 2019, 12:10
AssetType::Object(..)
andAssetType::Map
storeSequenceIdMappings
inAssetSequenceIdMappings
, as they only have oneItemId
.This must be done prior to loading
SpawnsSequenceHandles
inAssetSequenceComponentLoadingSystem
, as objects need to know the sequence ID of the objects they are spawning.AssetType::Ui
loadsSequenceIdMappings
inAssetSequenceComponentLoadingSystem
, as theSequenceId
s need to be perBackgroundDefinition
orUiDefinition
for the indices in sequence component data (e.g.WaitSequenceHandles
) to be correct.This disparity works for now, but may be confusing. The difficulty in shifting the
SequenceIdMappings
loading forObject
s is,Spawn
s can map from theAssetSlug
in spawn config toAssetId
, but not to anItemId
/SequenceId
within thatAssetId
-- andItemId
does not exist until afterAssetSequenceComponentLoadingSystem
has run.The text was updated successfully, but these errors were encountered: