Fanfield Planner

An anchor-based fanfield planning plugin for IITC on Niantic's Ingress Intel Map.

Fanfield Planner helps Ingress agents build anchor-based fanfields and pincushion-style operations. It scans portals inside a planning triangle, lets you curate the base portal set, and generates a two-phase execution plan with overlays, route summaries, and optional SBUL-aware limits.

View this plugin directory on GitHub | See all IITC plugins

Who This Plugin Is For

This plugin is useful for agents who plan structured anchor-based fielding rather than ad hoc link throwing. It is especially helpful when you want a curated fanfield base, a clear split between setup and reflection phases, and a plan that respects outgoing link budgets.

Current focus: Phase 1 builds a non-crossing base graph from the curated portal list. Phase 2 returns to the anchor and reflects into that graph. You can either ignore outgoing-link limits, or enable SBUL cap mode and let the planner maximize fields within the configured limit.

Key Features

Triangle-based planning: Select one anchor and two outer corners to define the working triangle.
Portal curation: Scan currently loaded portals inside the triangle and move them between Included and Excluded lists.
Phase-based execution: Generate a non-crossing Phase 1 base graph, then a Phase 2 reflection plan from the anchor.
SBUL-aware limits: Optionally cap Phase 2 with 0 to 4 SBUL and maximize fields inside the outgoing-link budget.
Map overlays: Draw dedicated Phase 1 and Phase 2 link and field layers, plus highlight layers.
Readable output: Export step-by-step text instructions, route summaries, and key requirements.

Planning Workflow

Open Fanfield Planner from the IITC toolbox.
Select the anchor portal and two outer triangle corners.
Press Scan Triangle to collect all currently loaded portals inside the triangle.
Move portals between Included and Excluded until the base set matches your intended fanfield.
If needed, enable Limit Phase 2 by SBUL and choose a value from 0 to 4.
Press Plan Fanfield to generate overlays, summaries, and key requirements.

Algorithm Overview

Phase 1

Base portals are sorted around the anchor and traversed in the shorter direction. Each visited base links to the anchor and then greedily backlinks to earlier bases while rejecting any crossing link. The resulting graph is the actual structure used by Phase 2.

Phase 2

The planner returns to the anchor and reflects links into the Phase 1 graph. In unrestricted mode it throws as many anchor links as possible. In SBUL cap mode it limits outgoing links to 8 + 8 * SBUL and greedily picks the subset and order that closes the most supported fields inside that cap.

Map Layers

Fanfield Plan (Links Phase 1)
Fanfield Plan (Fields Phase 1)
Fanfield Plan (Links Phase 2)
Fanfield Plan (Fields Phase 2)
Fanfield Plan (Highlights)

FAQ

What is the difference between Phase 1 and Phase 2? Phase 1 builds the non-crossing base graph. Phase 2 returns to the anchor and reflects into that finished structure to close fields.
Why use Included and Excluded lists? They let you refine the exact base portal set without redrawing the whole triangle or manually selecting every portal one by one.
What does the SBUL limit do? It restricts the available outgoing links from the anchor in Phase 2, and the planner tries to maximize field count inside that budget.

Changelog

Version 2.3.1

Expanded the optional Phase 2 SBUL selector from 0-2 to 0-4 for coordinated team setups.

Version 2.3.0

Added optional Phase 2 SBUL cap mode that maximizes fields inside a configured outgoing-link limit.

Version 2.2.0 to 2.2.1

Added triangle-based portal discovery with Included and Excluded lists.
Removed the obsolete manual base selection mode.

Version 2.1.7 to 2.1.10

Improved Phase 2 reflection behavior against the full Phase 1 base graph.
Added summary improvements and SBUL requirement warnings.

Version 2.1.3 to 2.1.6

Fixed IITC dialog rendering and improved crosslink validation logic.
Made Phase 1 backlinking more complete while remaining non-crossing.