Skip to content

Omnisprint (A): False movement calculation detection #38

Description

@rodolfoorlandajr

As you can see, the Omnisprint is poorly coded and needs to be fix and updated. It causes false-postive sometimes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions