Player Activity Log

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.
• Recorded capture age in toolbox: For owned portals, the toolbox can show Activity Log（xxD） based on the last recorded capture age from local COMM history.
• Import and export: Supports JSON and CSV export, plus merge-style import with de-duplication.

Recorded Portal Capture Age

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 last 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.

Portal Capture Age Notice

When the toolbox shows a value such as Activity Log（20D）, it means the last recorded capture event for the selected portal was about 20 days ago in your local COMM history.

It does not mean that all current resonators on that portal have existed for 20 days. If some resonators naturally decayed and were later redeployed while the portal stayed under the same faction, the displayed capture age may still point to the original recorded capture event.

Please treat this value as a local activity hint, not as an authoritative portal state record.

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 recorded capture age display in the form Activity Log（xxD） for selected owned portals.
• Improved update behavior when switching portals and hid the capture-age label for neutral portals.
• Added disclaimer text in the Activity Log window and documentation.

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.
• Does the capture age show the real age of all resonators? No. It only shows when the plugin last recorded a capture event for the selected portal, and it does not track each resonator individually.
• Why can capture age be wrong or missing? The calculation depends on your own locally recorded capture history. If your client did not see the relevant event, COMM history was not loaded, or some resonators decayed and were later redeployed without the portal becoming neutral, the result can be missing or misleading.

Related Plugins

• Recharge Monitor complements activity history with portal health and decay tracking.
• Portal DB is useful when you want stronger local portal data infrastructure alongside COMM history.
• Portal Afterimage adds visual portal memory while Activity Log focuses on player and event history.