Scripting updates, guided tour fixes, and more.
before they used auto incrementing numbers, so what would happen is if you were using source control with multiple ppl, you would run into conflict because it would use the same id for different assets. making the id's random reduces the chances of collisions.
wasn't easier just keep increasing and not reuse numbers? so that way you will always know that a higher number is a newer instance?
that does not work with branching, for example on master the last sprite id was 10. and from master you create a branch and add a sprite which now has an id of 11, but someone else also created a branch from master there last id is still pointing to 10. (becuase your new changes have not been merged yet) so when they create a new sprite, it now has sprite id 11 (same id across multiple branches). now when its time to merge the code, you will have a conflict because both sprites share he same id. making it random reduces the chance of that happening
hold on a momment... you can team work with construct? i thougt it wasnt implemented yet and only one can be using the same file at a time
this issue is only relevant to source control, and working on a team with more than one person.
These are also 'internal' imageSpriteId's generally not visible to developers (e.g. it's not like a UID.)