You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting this message when opening in latest GameMaker monthly version (2023.11.1.129 runtime 2023.11.1.160)
and trying to run it.
Object: oPlayerT Event: User Event 15 at line 53 : "move_and_collide" is read-only function
Object: oPlayerD Event: User Event 15 at line 47 : "move_and_collide" is read-only function
Object: oPlayerT Event: User Event 15 at line 53 : malformed assignment statement
Object: oPlayerD Event: User Event 15 at line 47 : malformed assignment statement
GM Version
Temporary fix (at least I was able to run it) search and replace all
serach:move_and_collide
replace:_move_and_collide
Wondering if its a case where GM actually implemented the function move_and_collide in a later version
The text was updated successfully, but these errors were encountered:
allende
changed the title
Object: oPlayerT Event: User Event 15 at line 53 : "move_and_collide" is read-only function
Object: oPlayerT Event: User Event 15 at line 53 : "move_and_collide" is read-only function in latest GameMaker monthly version
Feb 17, 2024
I'm getting this message when opening in latest GameMaker monthly version (2023.11.1.129 runtime 2023.11.1.160)
and trying to run it.
Object: oPlayerT Event: User Event 15 at line 53 : "move_and_collide" is read-only function
Object: oPlayerD Event: User Event 15 at line 47 : "move_and_collide" is read-only function
Object: oPlayerT Event: User Event 15 at line 53 : malformed assignment statement
Object: oPlayerD Event: User Event 15 at line 47 : malformed assignment statement
GM Version
![image](https://private-user-images.githubusercontent.com/662577/305587856-9f7271b9-4ec1-4f13-89ec-3c626557cb5e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwNzU2NDIsIm5iZiI6MTcyNTA3NTM0MiwicGF0aCI6Ii82NjI1NzcvMzA1NTg3ODU2LTlmNzI3MWI5LTRlYzEtNGYxMy04OWVjLTNjNjI2NTU3Y2I1ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgzMVQwMzM1NDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNDk1OGNjZGE5NWIzNzBiZTY4ZWQzOTI0M2M5YjNlYzY0ZjUxNDcxZTZhOTNjZDExY2MxYTZiYzdjOTMyNDk0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.A9xLezbBena7q2rKEIYIbxEFkWN_zN6uCF8ag3BtmTE)
Temporary fix (at least I was able to run it) search and replace all
serach:move_and_collide
replace:_move_and_collide
Wondering if its a case where GM actually implemented the function move_and_collide in a later version
The text was updated successfully, but these errors were encountered: