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

[Documentation] Guarantee Collision Events in Event Order #5494

Closed
ParodyKnaveBob opened this issue Apr 15, 2024 · 1 comment
Closed

[Documentation] Guarantee Collision Events in Event Order #5494

ParodyKnaveBob opened this issue Apr 15, 2024 · 1 comment
Assignees
Labels
feature request New feature (or a request for one)

Comments

@ParodyKnaveBob
Copy link

Is your feature request related to a problem?

For the longest time, I had the mistaken idea (don't ask me how, I can't recall,) that the unwritten order of GM events went...

(after Begin Step and timing events)
Keyboard (and other input events)
Collision
Step
move instances
End Step

...and I thought this was terrible; I've hated trying to work with Collision Events because I figured the only truly logical place for them would be to take place immediately after instances were automatically moved.

Describe the solution you'd like

Fortunately, I just recently learned I've been wrong for well over a decade, that that's how GM has operated this entire time. Unwritten, unguaranteed order:

Step
move instances
Collisions
End Step

The GM8 manual said a lot more about order (which I'd forgotten) which is mostly irrelevant now because you don't want to nail down most events' order, and I 100% understand the reasons you all have given, but the fact that this is guaranteed:

Step
move instances
End Step

...and the ..most? the only? logical place for the Collision Events to take place (due to the built-in speed system, path system, and the way solid works) would be to take place immediately (or very soon) after moving instances, which is what currently happens anyway, I request you please also guarantee the placement of Collision order (between moving instances and End Step):

Begin Step
Timelines
Time Sources
Alarms
Step
move instances
Collisions
End Step

Describe alternatives you've considered

No response

Additional context

No response

@ParodyKnaveBob ParodyKnaveBob added the feature request New feature (or a request for one) label Apr 15, 2024
@stuckie stuckie moved this from Triage to Backlog in Team Workload Apr 16, 2024
@YYBartT YYBartT self-assigned this Jun 26, 2024
YYBartT added a commit to YoYoGames/GameMaker-Manual that referenced this issue Jun 26, 2024
YoYoGames/GameMaker-Bugs#5494
YoYoGames/GameMaker-Bugs#5687

* Documented the precise order of events on the Event Order page
* Mentioned the differences when using Collision Compatibility Mode
@YYBartT
Copy link

YYBartT commented Jun 26, 2024

Listed this order of events on the manual's Event Order page. The changes to this page will be in the next manual release.

@YYBartT YYBartT moved this from Backlog to Ready for QA in Team Workload Jun 26, 2024
gurpreetsinghmatharoo pushed a commit to YoYoGames/GameMaker-Manual that referenced this issue Aug 8, 2024
YoYoGames/GameMaker-Bugs#5494
YoYoGames/GameMaker-Bugs#5687

* Documented the precise order of events on the Event Order page
* Mentioned the differences when using Collision Compatibility Mode

(cherry picked from commit 690c7c0)
@github-project-automation github-project-automation bot moved this from Ready for QA to Done in Team Workload Feb 3, 2025
@gurpreetsinghmatharoo gurpreetsinghmatharoo moved this from Done to Ready for QA in Team Workload Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature (or a request for one)
Projects
Status: Ready for QA
Development

No branches or pull requests

2 participants