Skip to content

Time issues #46

@Marisa-Chan

Description

@Marisa-Chan

Ormu:

  1. it doesn't run in real time, I think it's a little bit faster. So if you use a stopwatch, you will get different result. At least part of this issue is due to using 1024 to define "millisecond" instead of 1000 (It's related to an oldschool code optimization trick)
  2. if you enter a completed level and beam out again, the counter is increased by the entire time ever spent on that level, i.e.
    -- play the level for the first time, spend 30 minutes, beam out
    -- the total counter is increased by 30 minutes
    -- enter that level again, spend 5 minutes, beam out
    -- the total counter is increased by 35 minutes
    -- you spent 35 minutes total on the level, but the counter was increased by 65 minutes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions