Inconsistent tire wear on server depending on month/day settings (distance not respected)

[Squallqt]

Description

We noticed an inconsistency in tire wear behavior on a dedicated server when changing the number of days per month.

Tire wear seems to be calculated based on the server time configuration rather than actual driven distance, which leads to unrealistic results.

Observed Behavior

• If 1 month = 3 days, tires reach 100% wear
• If 1 month = 5 days, tires reach ~60% wear

This means that simply changing the calendar settings significantly alters tire wear, even if the driven distance is the same.

Expected Behavior

Tire wear should primarily depend on:

• Driven distance
• Driving conditions (load, speed, terrain, etc.) - Yes, it's a dream :D

Calendar settings (days per month) should not affect tire wear in such a drastic way.

Problem

With the current behavior, the notion of distance-based wear is lost, making tire degradation inconsistent and hard to balance on servers.

Question

Is this behavior intended, or is it a bug in how tire wear is calculated on servers?

If intended, could this be documented or reconsidered for better realism and server balancing?

Environment

• Version 0.9.5.7
• Context: Dedicated server
• Issue reproducible by changing server month/day settings