Player Activity Log

A local COMM history and movement review plugin for IITC on Niantic's Ingress Intel Map.

Player Activity Log listens to public COMM, stores supported activities in your browser, lets you review agent history over time, and visualizes movement trails for local analysis and planning.

View this plugin directory on GitHub | See all IITC plugins

Who This Plugin Is For

This plugin is useful for agents who want a local record of public COMM events, movement history, and portal interaction timing. It is especially helpful if you review operations after the fact, compare activity windows, or want to merge local logs between trusted users.

Key Features

Automatic logging from COMM: Passively records supported public COMM actions such as capture, deploy, link, and field events. MACHINA is ignored.
Interactive activity viewer: Browse players, search by name or ID, and inspect detailed activity entries from the IITC toolbox.
Movement trail review: Visualize movement paths over time to understand local action flow and repeated activity routes.
Portal Held Time in toolbox: For owned portals, the toolbox can show Activity Log（xxD） based on the latest local capture record.
Import and export: Supports JSON and CSV export, plus merge-style import with de-duplication.

Portal Held Time

When you select a currently owned portal, the toolbox link can change to Activity Log（xxD）. The value reflects how many full days have passed since the latest locally recorded capture event for that portal.

If there is no matching local capture record, or if the portal is neutral, the toolbox simply remains Activity Log.

How It Works

Player Activity Log reads public COMM messages already visible to your client and parses supported activity events into a local history database. It does not promise a complete global record, because its usefulness depends on what your local client actually saw and stored.

This means the plugin is valuable for timeline reconstruction and local review, but it should always be treated as partial history rather than authoritative ground truth.

What's New in 0.8.3

Added toolbox Portal Held Time display in the form Activity Log（xxD） for selected owned portals.
Improved update behavior when switching portals and hid the held-time label for neutral portals.
Added disclaimer text in the Activity Log window and documentation.

Important: All data stays local to your browser and is not synced across devices or accounts. Back up regularly with export features if the history matters to you.

Disclaimer: The plugin works from locally recorded COMM history, so the data may be incomplete or inaccurate.

Compatibility note: Trail drawing overlaps with the IITC-CE bundled Player activity tracker layer. Disable one of them if you do not want duplicate visual paths.

FAQ

Does this plugin read private or hidden data? No. It works from public COMM activity already visible to your local client.
Can I move history between devices? Yes, but only manually. Use export and import to back up or merge local activity records.
Why can held time be wrong or missing? The calculation depends on your own locally recorded capture history. If your client did not see the relevant event, the result can be missing or incomplete.