Skip to content

v5: character.houses[].paid is one day earlier than v4 (timezone?) #793

Description

@ptxowy

Endpoint: /v5/character/{name}

What happens: character.houses[].paid in v5 is one day earlier than the same field in v4 for the same character, fetched at the same moment.

Example: character Zojbek, fetched 2026-10-20 01:40:18 UTC (same timestamp for both), same result in 5 runs:

  • v4 https://api.tibiadata.com/v4/character/Zojbek → "paid": "2026-10-20"
  • v5 https://api.tibiadata.com/v5/character/Zojbek → "paid": "2026-10-19"

The character no longer has a house (the rent ran out on Oct 20), so this exact example can't be re-checked now, but any character with a house should show it.

Expected: the same date as tibia.com shows ("is paid until …"), like v4.

Guess: the date from tibia.com (CET/CEST, no time) is parsed as local midnight and then converted to UTC, which moves it to the previous day. Keeping it as a plain date without timezone conversion would fix it.

Found in Exiva's side-by-side v4/v5 comparison (Oct 16–21); reported after a chat with @tobiasehlert on Discord.

Activity

  1. self-assigned this
    on Oct 22, 2026
  2. added theissue type on Oct 22, 2026
  3. added this to the v5.0 milestone on Oct 22, 2026
  4. tobiasehlert commented on Oct 22, 2026

    @tobiasehlert
    Member

    Created #795 which should address this, but not merging yet.

    Can you provide a new character so I can verify the fix before merge?

  5. ptxowy commented on Oct 23, 2026

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions