Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating Events via GMEdit results in a build fail in 2024.8 #223

Open
Ryemanni opened this issue Sep 6, 2024 · 2 comments
Open

Creating Events via GMEdit results in a build fail in 2024.8 #223

Ryemanni opened this issue Sep 6, 2024 · 2 comments

Comments

@Ryemanni
Copy link

Ryemanni commented Sep 6, 2024

Hello, in gm version 2024.8 if you create new events via GMEdit and not through the IDE, the new events result in a failed build accompanied by the "Cannot load this new project because it, or its linked prefab libraries, need upgrading."

I managed to track down the problem to the .yy file of the object. In the "eventList" array, if an event is created through the IDE it shows:
{"$GMEvent":"v1","%Name":"","collisionObjectId":null,"eventNum":0,"eventType":3,"isDnD":false,"name":"","resourceType":"GMEvent","resourceVersion":"2.0",}
and via GMEDIT:
{"$GMEvent":"","%Name":"","collisionObjectId":null,"eventNum":0,"eventType":3,"isDnD":false,"name":"","resourceType":"GMEvent","resourceVersion":"2.0",}

As you can see, the "v1" is missing in the event created with GMEdit. If I manually add in the "v1" the project builds normally.

This happens consistently in gm 2024.8 with runtime v2024.8.0216, but I can't say for earlier versions as I skipped them and went straight from 2023.11 to 2024.8.
Thank you!

@cauehenrique
Copy link

cauehenrique commented Sep 19, 2024

Same here, was searching if someone found a workaround for this issue...
GameMaker simply wipes out events we create using GMEdit.

@YellowAfterlife
Copy link
Owner

You can try building the latest git version from source code, but more generally 2024.6 and onward became extremely strict towards the YY format - even incorrect field order (as seen here) is now considered a grave mistake and will result in build failure.

I do not know what result these changes pursue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants