![handy note vanilla rares handy note vanilla rares](https://notabledistinction.com/wp-content/uploads/2021/05/Buy-Johnnie-Walker-Blue-Label-Ghost-Rare-Pittyvaich-Online-1.jpg)
Okay, then lets add to the confusion.13 scans gets a Fracker, except that happens immediately and not at the end of the cycle. And if they deployed VR Battle Beacons, that would flip a portal and drop links/fields, which would be a tremendously trolly thing to do, so we don't want that either. Which will come in super handy when a cycle starts at 4 am.ĭoes Niantic think we think Rare Battle Beacons have any value whatsoever outside of anomalies? There's literally zero reason to ever deploy one.
![handy note vanilla rares handy note vanilla rares](https://www.baked-theblog.com/wp-content/uploads/2020/07/Vanilla-Simple-Syrup-4.jpg)
Scan a portal 7 times and.in an unspecified number of days or hours (depending on where in the cycle you are), a random battle beacon appears on a portal. We get that Niantic wants more scans, but the rewards here make no sense. It would be nice to know their reasoning why, but we rarely hear that about many of the decisions made. Niantic still feels that Ingress is best served with the 20m rule or they wouldn't have re-added it when it got broken. Whether they feel that's appropriate, shouldn't affect your submitting of portals, because if they do decide to increase the density, they will already have those portals ready to go. They accept those portals that are "too close" for Ingress, and at any time could enable them all in Ingress. Niantic has a database, and how they want to curate their database is completely on them. The decision to allow closer than 20m portals however, has nothing to do with the tools or the functions in game. The whole point of raising this however, was that we have the tools, and whether people hate them or not, it does allow for the capability of having more dense areas. Moving portals doesn't seem to be affected by it, but that's also always been the case.ĭisambiguation was definitely added after the density rules were at least informally decided by Niantic Labs employees doing reviews, but it's primary purpose at the time was for items on the ground vs portals, since there were very few instances of portals too close together (and all caused by a move).
![handy note vanilla rares handy note vanilla rares](https://s3.amazonaws.com/images.ecwid.com/images/16061030/1039040774.jpg)
"Too close" emails have been going out since they brought in-game submissions on, in 2013, after they stopped accepting the geo-tagged email submissions, so there's always been a density limit.
![handy note vanilla rares handy note vanilla rares](https://www.orchidinsanity.com/wp-content/uploads/2021/04/10_variegated_vanilla_pl_labeled_rszd.jpg)
What I am saying is that the existence of tap disambiguation does not mean it is now OK to put portals right next to each other. (In my experience, Ingress 1.x would always select the portal rather than the item if there was a choice.) We've had portals that were on top of each other (two portals for the same thing, both inaccurately placed, both approved and then both moved to the correct place because moving portals didn't have to obey any proximity rules) and it took quite some skill to select one and not the other.īut just maybe, when I said "I know that tap disambiguation can be very useful in some circumstances", I was referring to scenarios such as the above. I've experienced dropping a cube for someone (yes, one single power cube - probably not L8 either) or dropping a key to the portal so I could hack another one, and having it accidentally land right in the portal so it took 20 minutes of rotating and zooming to try to get it back out again. I've been here almost as long as it's possible to have been without getting a Founder badge. You never experienced the complete inability to click a portal because it was too close to keys dropped on the ground then.