- ensure consistant display based on portal details, by creating portal summary data from details
- pass field count into AP calculation, for accurate destroy amounts
- use portal.options.level, so unclaimed appear as zero
For RLA, the first multiplier is 2x. Subsequent RLAs add 0.5, 0.25, 0.25 to the multiplier. But expressed as a fraction of the initial multiplier, this is 0.25, 0.125, 0.125. Scale array has been updated to reflect this. This means the "-1" in the calculation is no longer required, and that boost is correctly calculated when baseMultiplier is anything other than 2 (eg VRLA, when it is 7).
If there aren't any Link Amps, the multiplier is 1x.
- no GUIDs in chat for players or portal details - so remove player GUID related functions
- remove player guid code from COMM
- update portal_info functions to compare to player name rather than guid
portal-highlighter-bad-deployment-distance: highlight colour based on resonatror range: purple: likely 0m deployment (spoofer?), red <10m, orange under 24m, yellow under 36m otherwise no highlight
Calculates the link range for portals with <8 resonators as well, but uses a dashed circle and a striked-through range value for those.
The tooltip over the range value in the details pane shows base range, link amp boost and total range.
The range for portals with missing resonators can be important because links with shorter lengths might originate here. Those will collapse when the total link range drops below their length, but not as soon as a resonator is destroyed.
- get mods from portal details, filtered by type and sorted by strength
- get mitigation values
TODO: convert existing plugins to use these new functions
- Split the calculations into getAttackApGain. Allows for other
functions to get the AP data.
- Renamed to getAttackApGainText as it isn't just destroying it is also
capturing. Originally the method only calculated the destroy values.
