How a maintenance menu becomes part of the driving model
In a real engine, oil forms a thin lubricating layer between moving parts. As oil degrades or runs low, friction and heat can increase, raising the risk of wear. A game cannot reproduce that physical process inside a digital car, so it represents it with rules and changing values.
A simulation may track oil condition alongside other maintenance variables. Driving the car changes those values; servicing it restores them. The game can then connect poor condition to outcomes such as reduced engine performance or greater wear. The oil itself is not doing anything—the important link is the rule the game assigns to its condition.
Why make routine upkeep matter?
Maintenance gives driving a longer arc than simply accelerating and steering. Players may need to decide whether to spend time or in-game money on service now, or keep driving and accept the consequences. That turns an ordinary workshop task into a tradeoff: a car that feels strong today may become less effective if its upkeep is ignored.
Designers also have to decide how demanding that tradeoff should be. If maintenance has no effect, it is busywork; if neglect becomes costly too quickly, it can interrupt the fun of driving. The result is usually an abstraction rather than a full mechanical simulation: a few readable condition states stand in for a complicated engine.
That is why a digital supercar can still need an oil change. The service is not necessary for the code to run; it is necessary because the game has made upkeep part of how the car behaves.
