Intel has nothing to do with Prime. If you’re seeing it on intel, then the client you are using, which at current be Prime by default, is just reporting the information it’s being given. It’s a server side issue. Also read: got nothing to do with the client [Prime].
This game has so many problems I really don't play anymore since redacted was shut off, the biggest being the game freezing. I am tired of force quitting and reopening the game. They tried fixing something that wasn't broken and made it bad.
Here's something even better, a video on Youtube detailing a Xfac cross-link and cross-field art op that took place this past December using solely the Redacted scanner, Op Name: Marshmallow Man:
There are two different phenomena that can create crossing links / fields:
Synchronized creation of links as was done in OP Marshmallow, Cause is a race condition when the links are created. If the link creation is timed correctly, the system just doesn't prohibit the second link because it cannot see the first link yet.
Ghost fields. This is the result of an error while links are destroyed. The system for some reasons skips deleting the field when the links are removed. You can then afterwards link through the borders of the field, because the link isn't there anymore but the field is still there and will also be shown on the map and the scanner.
There are currently a lot of ghost fields happening. Now combined with the coincidence of push-notifications not working, I see 3 possible reasons for this:
This is a side-effect of the high load on the Ingress back-end.
They changed something in the back-end code (maybe to ease the high load issue) which causes these issues
Some-one had the task to disable stuff in the back-end that would not be needed any longer after Redacted is gone but disabled by accident some stuff that would still be needed.
My bet would be on 2. The effects started mid last week a short time before the anomaly. Maybe they did roll out changes in the back-end in preparation for high load during the anomaly, but these changes cause more ghost fields and the missing push notifications.
Comments
Intel has nothing to do with Prime. If you’re seeing it on intel, then the client you are using, which at current be Prime by default, is just reporting the information it’s being given. It’s a server side issue. Also read: got nothing to do with the client [Prime].
This game has so many problems I really don't play anymore since redacted was shut off, the biggest being the game freezing. I am tired of force quitting and reopening the game. They tried fixing something that wasn't broken and made it bad.
As an Ingress player with almost 5 years in-game history I could explain why Prime is OK but I'm busy at the moment catching some Pokemon...
Here's something even better, a video on Youtube detailing a Xfac cross-link and cross-field art op that took place this past December using solely the Redacted scanner, Op Name: Marshmallow Man:
Reddit discussion:
Marshmallow Man took a lot of rethrows to get those crosses though with synchronized timing app.
(I was part of the team that made them, design kudos to 57cell).
There are two different phenomena that can create crossing links / fields:
What we have seen in the last two weeks are ghost fields. Ghost fields have always been a thing. See this 3 year old discussion on reddit: https://www.reddit.com/r/Ingress/comments/55n63e/ghost_field_over_24_hrs/
There are currently a lot of ghost fields happening. Now combined with the coincidence of push-notifications not working, I see 3 possible reasons for this:
My bet would be on 2. The effects started mid last week a short time before the anomaly. Maybe they did roll out changes in the back-end in preparation for high load during the anomaly, but these changes cause more ghost fields and the missing push notifications.
We kept track of Primecrashes at the anomoly on saturday and on sunday for mission day was worse.