24-hour notation of time is inaccurate

Open
#187 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
game-dev

Research direction

Start by locating the CommandBook code that formats the 24-hour time notation and reproduce the time tick 0 case described in the issue. Compare the displayed 8 am value with the expected 6 am value; done means the notation uses the correct mapping for this tick.

Written by the indexing model from the issue text.

Description

CMDBOOK-2231 - Reported by .

0 in time tick is normally considered as 6 am, but this plugin shows time tick 0 as 8 am.

Dominant language
Java
Stars
151
Forks
104
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EngineHub/CommandBook

All issues in EngineHub/CommandBook

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.