Clearly indicate when the client is in an error state.

Clearly indicate when the GPS-signal is lost. Don't give cryptic error messages. Indicate when the client thinks it is travelling too fast or in a speed ban state. Indicate when it will end or at least when it has ended. And fix the speed ban on bringing the client to the foreground.

Comments

  • edited August 2020

    Part of the issue is that it's server determined, so the client doesn't know until it sends a request.

    And the other part is the infuriating logic that Niantic has maintained for 7 years: "If we don't tell you specifics, you can't work out how to subvert it".

    Which is complete **** because when you control for the other variables, you can easily tell what the specific issue being blocked is, so spoofers etc worked out how to subvert it years ago.

    Another situation of "Spoofers unaffected, players confused and disadvantaged".

  • I believe not having a GPS-signal is client-dependent and has not much to do with the server. And the client communicates every now and then with the server. So the client should be quite aware of what state the server thinks it is in. Regardless of that. Error messages that don't mean anything are just infuriating.

    The speed ban happening if the app is brought to the foreground and it first sends it's old position is also a client, not a server, issue?

Sign In or Register to comment.