seriesoftubes/site/i18n
jvanvik ae78e82ddb Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58)
A regen site added to a fiber that already carries expresses now charges a
regen card for every express channel in that glass, as it does for the
fiber's own channels. One helper, regenAddCost(), prices it for the action,
the fiber panel's button and the MCP dry-run quote, so the three agree.
Lighting an express over existing regen sites already paid its cards
(xpCost); only adding a site later was free for them.

A dirty connector on a fiber is in the glass, so it now dims the expresses
riding that fiber by the same factor (capOf multiplies xpG by xpGlassF over
the express's fibers), and the express's panel names the fiber. The other
link-degrading incidents (MTU mismatch, microbursts, a marginal optic's CRC
errors) belong to the fiber's own routers and optics, which an express
bypasses, as the optic-failure incident already treats them, so they leave
expresses alone. The incident marks the connector with loss.glass=true;
sanitize keeps the flag only when it is true, so an old save's loss loads
as router-side, as it behaved before. A fiber that only carries expresses
can now get the dirty connector too (never the router-side variants), like
the backhoe and amp-hut incidents already find it.
2026-11-09 23:01:46 +01:00
..
de.js Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58) 2026-11-09 23:01:46 +01:00
es.js Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58) 2026-11-09 23:01:46 +01:00
fr.js Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58) 2026-11-09 23:01:46 +01:00
it.js Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58) 2026-11-09 23:01:46 +01:00
pt.js Express lightpaths: regen cards for their channels, and dirty connectors dim them (#58) 2026-11-09 23:01:46 +01:00