search

IITC-CE / ingress-intel-total-conversion

intel.ingress.com total conversion user script with some new features. Should allow easier extension of the intel map.
https://iitc.app
ISC License
285 stars 110 forks source link

Portal history: Ingress's newly-released layers for explorer and pioneer activity #434

Closed lollercopter closed 3 years ago

lollercopter commented 3 years ago

The generic Ingress Intel map now shows a player's visited (explorer) and captured (pioneer) portals using two filters: https://community.ingress.com/en/discussion/13451/portal-history-now-available-on-intel-map

Currently, this feature is not working in IITC. Could you add a feature for these layers? Thanks!

MysticJay commented 3 years ago

@le-jeu :

function summaryPortalData(a) {
return {
level: a[4],
health: a[5],
resCount: a[6],
image: a[7],
title: a[8],
ornaments: a[9],
mission: a[10],
mission50plus: a[11],
artifactBrief: parseArtifactBrief(a[12]),
timestamp: a[13],
visited: (a[18] & 1) === 1,
captured: (a[18] & 2) === 2,
scanned: (a[18] & 4) === 4,
};
};
MysticJay commented 3 years ago

Changing SUMMARY_PORTAL_DATA_LENGTH is wrong and so is the above snip.

We have summary portal details (14) detailed portal details (+4) extended portal detail (+1)

Thus portalDetails returned can be 14, 18 or 19

The xtende portal Details need to be parsed in window.decodeArray.portalDetail

lollercopter commented 3 years ago

Here is the first plugin:

https://github.com/EisFrei/IngressPortalHistoryFlags

I would like to see less clutter on the map though. Maybe change the orange/blue/green portal markers to a alternating orange/blue/green and red/purple color (changing the color every 45 degrees around the circle)?

Also, a portal capture counts as a portal visit. Therefore, the purple dot is redundant if the red dot is there.

Eccenux commented 3 years ago

You should probably merge this with uniques plugin. Just use this data to merge with what user selects. Same as using plexts for marking portals as captured.

Storing this data allows to show state when zoomed out. So that would be better then what Intel has.

Also having user's state allows to correct niantic bugs. I have a portal which I captured almost daily when going to work. And it's marked as not captured.

Conflict resolution of state:

Etc.

MysticJay commented 3 years ago

Attention! At the moment 'scanned' layer is wrongly titled as 'Scout Controlled' in stock intel!