Overclock-button is not disabled in remote portal/recharge view

daawgdaawg ✭✭✭
edited January 5 in Report a Bug

The title pretty much says it all, but this is an infuriating bug especially when you're trying to defend a portal and keep accidentally hitting 'overclock' while charging the portal.

If I am not within 20 meters proximity of a portal, the overclock button must be disabled IN ALL VIEWS.

To reproduce this bug, find any key in your inventory to a portal which is not in your range, click on the key and the portal until you are in recharge view, and click 'overclock' in the bottom right corner. You'll get an annoying prompt "Insufficient portal data - Overclock is disabled. Overclock at this Portal can be enabled by. uploading Portal Scans. [Cancel] [Scan portal]".

If you click on a portal in your current view from which you are further than 20 meters, you will get a notify dialog that says "Enable overclock by moving within 20m of the Portal core." This is obviously better already, but it would not be the desired behavior for recharge view. The overclock button needs to be entirely gone from the recharge view.

Ingress version 2.132.1-bc733046

iOS 17.2.1 (but this concerns all platforms)


Tagged:
18
18 votes

Active · Last Updated

Comments

  • Yes indeed very frustrating ”feature”

  • starwortstarwort ✭✭✭✭✭

    click on the key and the portal until you are in recharge view

    If I want to recharge from a key then I go: key carousel -> click on the key -> click on the Charge button. There's no Overclock button in any of these views.

    If you go: key carousel -> click on the key -> click on the photo -> click on the portal, then you get to the Portal screen with the Overclock button on it. But that's a slightly perverse route if you just wanted to recharge the portal.

    If you receive an alert and go: alerts -> click on the alert -> click on the portal, then you also get the view with the Overclock button. This would be quite a common route for responding to an attack alert (but I defended an attacked portal just the other day and never once clicked on the Overclock button by accident).

    I think it would make sense to disable the buttons that definitely wouldn't work from a remotely viewed portal, but I assume that the internal workings of this are that it's basically the same thing as a locally viewed portal, so actually removing the button might make the code a bit messy. (A bit more messy, I mean.) That having been said, the 'key' button already doesn't work for unknown reasons when remotely viewing a portal so it seems they can at least make some differentiation between the two UIs.

Sign In or Register to comment.