#Replacement for mytracks code#

The tracks it contains, the properties those tracks have, the playback speed and much more. This struct contains all the data about the sequence. The sequence instance struct contains a few parameters to control playbackДЄnd things (this is explained in more detail below) as well as the sequence data struct.ДЇinally, as mentioned above, you have the sequence data, which is another struct.

(and any editing done to a sequence object will not be reset by restarting the game or the room using the room_restart() or game_restart() functions). Objects and instances are structs and - unlike regular objects - a sequence object struct can be edited at runtime, which will affect all further instances of that sequence when you create them as elements Think of sequence objects as blueprints and sequence instances as the creation from those blueprints. A sequence object is the base resource as you created it in the Asset Browser or using the function sequence_create(),ДЄnd the sequence instance is the 'copy' of that sequence object that has been placed in a room as an element on a layer. Next you have sequence objects and sequence instances much like you have general objects and instances. The layer element has no real properties other than an element ID value, but this ID is required to use the above mentioned layer functions to change the sequence playback or to access the sequence data.

#Replacement for mytracks code#

This is what you place on a layer in a room, either through the Room Editor or in code using the appropriate layer functions. To start with, at the top level, you have a sequence element. To understand the way that sequences are defined in GameMaker and the different terms that will be used. However, before looking at the functions available, it's important Sequences are usually created in the IDE using the Sequence editor, but they can also be created and edited using code.