Portal Coverage Layers

Who This Plugin Is For

This plugin is for agents who want a direct action map instead of a density map. If your goal is to quickly find missing uniques, mop up uncaptured portals, or route cleanup work after an operation, this view is often easier to read than a heatmap.

Key Features

• Two dedicated layer views: Adds Unvisited Portals and Uncaptured Portals as separate IITC layers.
• History-driven filtering: Uses the visited and captured records managed by Uniques Tools, or by the stock Uniques plugin as a fallback.
• Cleaner decision-making: Hides finished portals so the remaining visible portals are your next targets.
• Shared filter behavior: If both layers are enabled, a portal stays visible when it matches either active filter.
• Live updates: Refreshes when map data changes or when either supported uniques plugin updates a portal state.

What Each Layer Shows

• Unvisited Portals: Shows only portals that are neither marked visited nor captured.
• Uncaptured Portals: Shows portals that are not marked captured, including portals you may have visited but never captured.
• Both layers enabled: A portal remains visible if it matches either condition, which is useful when you want to preserve all uncaptured opportunities while still seeing fully untouched targets.

How to Use Portal Coverage Layers

1. Install and enable Uniques Tools, or use the stock IITC Uniques plugin if that is already part of your setup.
2. Make sure your portal history is populated in your chosen uniques plugin, either manually or by using its import or sync features.
3. Install and enable Portal Coverage Layers.
4. Open the IITC layer chooser and enable Unvisited Portals, Uncaptured Portals, or both.
5. Use the visible portals as your action list for route planning, cleanup, or fieldwork.

Why Use This Instead of a Heatmap

Heatmaps are useful for identifying general clusters and coverage patterns, but they still require you to visually interpret intensity and overlap. Portal Coverage Layers is more literal: it removes already completed portals from view so the map becomes a direct list of targets.

That makes it especially effective for tasks like last-mile uniques cleanup, revisiting old operation areas, or checking whether a block still contains portals that have never been visited or never been captured.

Requirements and Limits

This plugin requires either Uniques Tools or the stock Uniques plugin. It does not fetch official history on its own and does not maintain a separate database. It only interprets the portal history already stored by local-plugins/uniques-tools or plugins/uniques.js.

Because it works from currently loaded portal markers and the local history available to your IITC client, the output reflects your saved state and current map data rather than the complete live game world.

FAQ

• Does this plugin work without Uniques Tools? Yes, if you use the stock IITC Uniques plugin. It needs one of those two plugins for visited and captured history data.
• What is the difference between Unvisited and Uncaptured? Unvisited hides both visited and captured portals. Uncaptured hides only captured portals.
• Do I need to maintain data in two plugins? No. Maintain history in whichever uniques plugin you use; Portal Coverage Layers simply reads and displays that data.

Related Plugins

• Uniques Tools is the preferred source of visited and captured history, with fallback support for the stock IITC Uniques plugin.
• Portal Afterimage can complement this plugin when you want local visibility improvements for known portals.
• Player Activity Log pairs well with portal coverage cleanup by adding local activity context.