Version 1.2.7

v1.2.7 — Security filter bugfixes

Bugs fixed

Lowsec systems appearing in highsec/nullsec-only results
During SDE import, sec_class was assigned by rounding the raw security value (round($sec, 1)) before comparing against the 0.5 highsec threshold. EVE Online uses floor, not standard rounding — systems with a true security in the range 0.45–0.4999 were stored as highsec in the database despite EVE displaying them as 0.4 (lowsec). This caused systems such as Uchoshi to pass through highsec-only or nullsec-only SQL filters. Fixed by comparing the raw true security value directly against the exact game thresholds.

Security status display rounding
Security status was displayed using ceil instead of floor for positive values, causing some systems to show one step higher than EVE does (e.g. Hophib showing 0.2 instead of 0.1). Display now matches EVE exactly, with a floor to 1 decimal place and a minimum of 0.1 for any positive-security system.

Lowsec/Nullsec filters unchecked on initial page load
The shortcode PHP template rendered Lowsec and Nullsec checkboxes as checked, but the JS config still defaulted to highsec-only, immediately unchecking them on load. The default sec class in the JS config now matches the template.

⚠️ Action required after updating

Re-run the SDE import from the plugin admin panel so affected systems are reclassified with the corrected sec_class logic.