Why the draw event types jump from 0 to 64

[faissaloo]

So, someone wrote a certain comment ( https://github.com/IsmAvatar/LateralGM/blob/220dc7da6dc358bde0d691f52100c852283831a3/org/lateralgm/resources/sub/Event.java#L160 ) in the LateralGM source I think I found the reason:

Just thought someone might be interested.

[TheExDeus]

What is the other source from?

[faissaloo]

The other source is an in terminal object editor I'm working on (and the draw events have been a pain in the ass).

[Goombert]

That was me that put that comment in there. I overexaggerated a little bit but it is mostly true how YYG's always fails to plan ahead or think out of the consequences of what they do. There's cases of this nonsense all through GameMaker. While this particular example has not caused anybody any real pain, it's just very confusing. The GMX inconsistencies on the other hand are a recipe for disaster. For example, the last LGM release where I noticed that the background rooms for paths were actually still saved by ID... even though GMX does not save ID's anywhere else. I tested and it is easy to confuse GMS by deleting the room until you get a corrupted GMX. Not really sure what else to do in LGM about it.... as it is not our format to change.

Besides all that, were you having a particular issue with that event?

[faissaloo]

Nah, I just needed the enumbs for the events.

While this particular example has not caused anybody any real pain

Well, it meant that I had to make a macro to convert from the stupid 0,64,65 system to 0,1,2 so I could use an array to store the data for displaying it, made things kinda messy.