LHDF Data

1.0.4

## [1.0.4] - 2026-10-17

### Fixed

- A failed world status check (the website is down, or no longer has that route) is tried again 10 minutes later, instead of in the next frame. Before, the check came first in every frame and each failure put it straight back, so no heartbeat or other report was sent after the first one of a start and the server showed as offline on the website. The heartbeat and the other items are no longer held back by it.

1.0.3

## [1.0.3]

### Changed

- The heartbeat goes every 2 minutes by default (`heartbeatSeconds` 120, was 30). A server whose `Data.json` sets `heartbeatSeconds` keeps its value.

1.0.2

## [1.0.2]

### Added

- The performance report, from LHDF Core 1.0.19: "Write performance report" is in the Data section of the LHDF tab now, and the uplink asks for it as report kind `report.perf` as before. The page is still `Core/PerformanceReport.html` in the LHDF profile folder; Core still collects the figures.

1.0.1

## [1.0.0]

### Added

- World export for the website's 3D map, replacing the temporary probes of `_tools/worldmap_report`: terrain every 40 m, trees and bushes from 5 m, static objects (rocks from 10 m), the road network, inland water every 20 m and Core's world index, collected in Core's work queue (47 s on Nizla) and sent in parts (44 on Nizla). Sent only when the website does not have this map yet (a hash of the world file, its bounds and the terrain), or when the website asks (`worldExport` command).
- Active missions: whatever a mod publishes through `LHDF_Reports.Publish` (LHDF Encounters: `missions`, on every mission start and end) goes to the website as one small item.
- Placeables for the map: every LHDF placeable (traders, safe and no-build zones, vehicle spots and spawners, also Game Master placed), once after the start.
- Settings `worldExport` (on) and `startupReports` (`report.encounters`, `report.shop`, `report.loot`).

1.0.0