Reserved "Alterable Values" for Object Instance

ASTER uses some instance variables of object instances registered with the controller as reserved variables.

CF25::Object::Active::Properties::Values -Screen Shot- CF25::Object::Active::Properties::Values -Screen Shot-


In ASTER rev 1.0.0, two variable spaces are treated as reserved, and one of these values needs to be handled with care.

Defalut Name Name Description Overwrite
Alterable Value A id Sequential number, auto-assigned during alignment, multiple uses Safe
Alterable Value B motyp Database search optimization, non-writable Danger
Détails
Event Detection mechanism has significantly reduced the number of reserved variables since the ASTER Beta Version.

Purpose of Using Reserved Variables

Aside from motyp, which is reserved for search efficiency, there are no values of importance to ASTER.

id is a sequential number that ASTER automatically assigns to the instance variable during the alignment of instances or when registering with the controller. While not essential for ASTER, preassigning sequential numbers makes it convenient when creating events in CF25.

id is used in CF25’s condition judgment processing as a number to distinguish and identify instances.

Caution Regarding; motyp

Althogh motyp is still reserved, but currently, Alterable Value B is not actually used.

Regarding motyp, since ASTER Rev.0.9.15, experiments have been conducted in which extension developers repurpose part of the instance memory area related to Clickteam’s standard features, under the assumption that users are unlikely to utilize it.

Notice
motyp is reserved as a fallback in case this experiment causes critical issues, allowing for quick reversion to its original state.
Warning :: Non-Overwritable

motyp is a magic number used by ASTER for database search optimization, so please do not overwrite this value.