Vehicle insurance

Insurance gives players the option to pay BTC for a limited time protection of a specific car, boat, or aircraft. If the insured machine is demonstrably destroyed during the validity period and ownership is retained, the eligible player may claim one replacement per product purchased.

The module is suitable for servers with valuable vehicles: it reduces the frustration of losing, creates a natural use of BTC while maintaining clear rules. It is not an automatic restoration of the previous state of the world or a universal replacement for every missing vehicle.

Where to find it

• Insurance → List - policies and their status.
• Insurance → Settings – enabling the module, reminders and insurance products.
• Insurance → Log - purchases, verification, renewals, events, refunds and errors.
• Insurance → Info - Public text and Discord information message for players.

The administrator sets the menu and monitors the status. The player himself buys, renews, cancels or applies the policy through his logged-in server profile. Admin screen intentionally does not trigger vehicle replacement manually.

How to design insurance products

Each product contains:

• Category: car, boat or plane. It must correspond to the insured machine.
• The price in BTC: the amount will be deducted from the payer only in the controlled purchase process.
• Length of coverage: number of days of one insurance period.
• Number of renewals: zero means no fixed limit. The first purchase does not count towards renewal.
• Replacement type: standard vehicle or permitted modified variant. The full upgrade is only available for cars.
• Status and order: disabled product will stop being offered for new purchases, existing history will be preserved.

Recommended startup procedure

1. Create at most a few easily comparable products. The player must understand the difference between BASIC and PREMIUM at first glance.
2. Set the price, duration and type of replacement. The price should correspond to the value of the vehicle and the income of BTC on the server.
3. Set a reminder before the coverage ends. The player will get it even during automatic recovery, because the lack of BTC can stop the recovery.
4. Prepare public Info: explain that the policy is tied to a specific Vehicle ID and insured Steam player, not just the name of the car.
5. Enable the sale and test the purchase with both valid and invalid vehicles. Paid coverage should not be created with an invalid identity.
6. Check List and Log. An active policy must have a clear period, payer, insured player and verified vehicle.

How the policy works from the player's point of view

1. The player selects a product in the profile and enters the desired vehicle. He can buy the policy for himself or another insured player in a permitted manner; the payer and the beneficiary of the coverage may be different persons.
2. NODERAgent verifies that the vehicle actually exists, belongs to the correct category and matches the insured player. An invalid or duplicate vehicle will not be activated.
3. After successful verification, BTC will be deducted and the insurance period will start.
4. If the system detects the destruction of this exact vehicle during coverage, the policy will change to a state in which compensation can be requested.
5. The insured player files a claim. Successful issuance of one replacement closes the claim.

Destruction during coverage remains an eligible event even if the coverage date has expired in the meantime. Conversely, the mere expiration of an undamaged vehicle will not create a claim. Canceling a period that has already started does not refund BTC.

Example from the Main server

Status of the database as of 1 September 2026.

The reminder was set 24 hours before the end. In the historical summary, there were two canceled policies and one lapsed policy; this number is not an indicator of currently active coverage.

What to check in the event of a problem

• Insurance pending verification: both player and vehicle must be on the correct server and the agent must have a fresh connection. Watch the next planned attempt in detail.
• BTC has not been deducted: the insurance may not have been successfully activated yet. The policy status and accounting history are decisive, not just the submitted form.
• Destruction did not create a claim: check server, Vehicle ID, insured player and time of event against coverage period.
• Renewal failed: most often BTC is missing, the product is no longer allowed, or the renewal limit has been reached.
• The result of the replacement is unclear: do not attempt a second manual release. Such a state belongs to the administrator's evaluation in the Log.