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

consistent grenade/missile/plasma shooting rates #417

Merged
merged 3 commits into from
Jul 10, 2024
Merged

Commits on Jul 3, 2024

  1. fix FramesFromNow usage

    many frame number checks were of the form
        if (doSomething < frameNumber) {
            doSomething = FrameFromNow(3)
        }
    
    For classic mode that means to doSomething at most every 4th frame.  But for high-FPS, this code would start
    doing something on frame 13 instead of on frame 16... faster than classic.
    
    Changing code to work across frame rates like this:
        if (doSomething <= frameNumber) {
            doSomething = FrameFromNow(3+1)
        }
    tra committed Jul 3, 2024
    Configuration menu
    Copy the full SHA
    ae3a5c8 View commit details
    Browse the repository at this point in the history

Commits on Jul 5, 2024

  1. fix tests and bugs found by tests

    The HECTOR.Boost* tests had to be fixed because they were actually boosting on frame 1 since boostEndFrame inits to 0.
    tra committed Jul 5, 2024
    Configuration menu
    Copy the full SHA
    c826bb9 View commit details
    Browse the repository at this point in the history
  2. added 1 classic-frame limiter to the plasma shot

    so that all frame rates behave the same on shooting rate
    tra committed Jul 5, 2024
    Configuration menu
    Copy the full SHA
    242cd89 View commit details
    Browse the repository at this point in the history