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.

Sign up for GitHub

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

Jump to bottom

Make sure call_out event are always executed on next available gametick, even when delay is less than game tick interval. #836

Merged
merged 2 commits into from Aug 27, 2021
Merged

Make sure call_out event are always executed on next available gametick, even when delay is less than game tick interval. #836

merged 2 commits into from Aug 27, 2021

Commits on Aug 27, 2021

  1. Make sure call_out event are always executed on next avaiable gametic… 

    …k, even when delay is less than game tick interval.

This behavior was always the intention. Also fix callout0 test to be more visible.
    @thefallentree
    thefallentree committed Aug 27, 2021
    Configuration menu
    Copy the full SHA
    0ec0635 View commit details
    Browse the repository at this point in the history

  2. source formatting

    @thefallentree
    thefallentree committed Aug 27, 2021
    Configuration menu
    Copy the full SHA
    c0535a0 View commit details
    Browse the repository at this point in the history