[2.90.1] Scans, battle beacons, septicycles and anomoly windows
Here is how Thia clarified it in the release notes:
If, during an event with Battle Beacon participation, a Rare Battle Beacon spawned at the end of a Septicycle as a result of Portal Scan Meter will count as a Player-deployed BB for the event.
and also in the comments section:
Example: I could submit 7 Scans ... to trigger the Rare Battle Beacon for the end of the Septicycle.
So, rare battle beacons will spawn at the end of a septicycle. Rare beacons don't flip portals, not usable for extra AP or MU generation, the only time when rare beacons are needed is the anomoly window. Deploy BB to contribute to the team score, and/or to get +1 tick towards anomoly badge. Let's see how that "if, during an event, a rare beacon spawned" unfolds:
Kureze, stage 3: Friday, 18 March - Monday, 21 March. The closest septicycle ends are 16 March and 24 March, *the septicycle end misses the window*
Kythera, stage 1: 16-17 April. The closest septicycle end is 14 April (Thursday UTC), *misses the window*.
Kythera, stage 2: 21-22 May. The closest septicycle end is Saturday 21 May 08:00 UTC. *works if you don't sleep at 08:00 UTC* (where I live, it's 04:00, most of the agents sleep).
Kythera, stage 3: 25-26 June. The closest septicycle end is Sunday 26 June 19:00 UTC. *works if you don't sleep at 19:00 UTC* (works for me).
Thus, technically, agents in remote areas do have a chance to participate in the Kythera for free (no chance for Kureze) by doing scans. Some agents might be lucky to have a second chance, but let's be real, lots of agents have only one, either May or June. My point is: this mechanic produces usable outcome in less than 50% scenarios, and useless outcome in more than 50% scenarios. This mechanic is broken, unless I'm missing something. ??? @NianticBrian @NianticThia #XMA
Couple of ideas:
a) do not tie beacon spawns to the end of septicycle, use anomoly window instead. For example, NIA section 14 spawns anomoly beacons on Saturday, 14:30 - 17:30 local time. Then, spawn the "scanned" beacons next Sunday, 14:30 local time during anomoly window. The spawns will not interfere with Saturday battles, and will give remote agents chance to participate. Or,
b) well, ingress team needs to sell beacons, maybe 10x7 scans is not fair equivalent of $20 (approx. price of beacon pack)? So, do NOT spawn beacons (which cannot be used), let agents buy beacons, and give something more usable for uploaded scans, tie it to septicycles, etc. For example, frackers are cool, but they are kinda useless when remote agents cannot build high level portals. So, instead of beacons, let agents upgrade portals. 7 scans -> end of a septicycle -> all resonators gain +1 level. Or, more conservative upgrade: 7 scans -> end of a septicycle -> only resonators owned by agents who uploaded scans gain +1 level. Remote agents will finally have an opportunity to build high level portals, and nia will get working game mechanic built around scans.
Comments
do not tie beacon spawns to the end of septicycle, use anomoly window instead
The scanning rewards are not a one off thing. Kureze will pass, but the beacon triggering will continue indefinitely. There will not be an 'anomaly window' in the next septicycle, or the one after that, and so on.
If a beacon spawns in the middle of the night, or during working hours, no one is here to enjoy the "battle", and the battle outcome does not count and does not give a tick towards anomaly (or any other) badge - how is it a "reward"?
Maybe there are future plans to make "battle" results more useful in future, idk, haven't heard any. Would rather prefer to see some real rewards instead, like portal upgrades.
I'm guessing Niantic is going to release a Battle Beacon badge. People who enjoy bursting (more than they like building) have long asked for another destroyer badge.
Maybe if there's a badge, some people will scan a portal cluster minutes before a septicycle ends, just to get the +1s on their new badge.
I don't disagree that the scheduling method is simplistic and silly.
I just wanted to point out that your alternative is irrelevant because it only applies... this weekend. Not forever more.
Tying the battle beacon appearance onto the end of the septicycle is unfortunate in my eyes too. It's too inflexible. Also, those battle beacons probably run out without any battle at all making the idea behind it a joke. Just assume, a community would really like to hold a local battle competition. Its a hassle to find a date where the septicycle ends at a suitable time so people could attent.
Also, on that thought:
When a battle beacon gets scheduled by scans the message in the Intel Comm is somewhat like that: "Rare Battle Beacon will be deployed at the end of the septicycle (54195.07.30 00:00 UTC) on <portal>". Now, the time clarification would be awesome, if
Not count for what? What is it they count for anyway?
Is your timezone example an actual time?
Why would cycle Not be short for septicyle??
That count down is in score and the most obvious place under the portal photo 🙎♂️
Time annocement would be nice to see...
54195 seems to be a way of showing the difference in seconds to the beacon being deployed. Essentially, it's the epoch difference. I get 15 hours, 3 minutes and 15 seconds but I wonder if it's just the format display altogether because it's:
sssss.MM.DD hhmm UTC
I'm reminded of Excel parsing dates into a 5 digit number when you don't have the format of the cells defined correctly
Actually BB should have some time choice,as i think. Mine spawned at 2am,kinda useless.
They went at 5pm local time here yesterday, but the next ones will be at midnight on a Thursday. No real interest there from me.
Right now, I’m not seeing the point, but hopeful something will come along that connects the dots a bit… We’ll see 🤷🏼♂️