From a83688a4c26f64384cd9eeea16e17f88704af9cf Mon Sep 17 00:00:00 2001 From: Jon Atkins Date: Fri, 30 May 2014 22:42:00 +0100 Subject: [PATCH] niantic have removed all munging from the network protocol, so update IITC to match improvements could be made to our version handling (currently we just take their version string and assume it'll work, with no checks for changes - needs some thoughts on sensible handling) --- code/artifact.js | 2 +- code/boot.js | 11 -- code/chat.js | 14 +- code/map_data_request.js | 4 +- code/munge.js | 279 --------------------------------------- code/utils_misc.js | 12 +- main.js | 2 +- 7 files changed, 14 insertions(+), 310 deletions(-) delete mode 100755 code/munge.js diff --git a/code/artifact.js b/code/artifact.js index 2d8a31d3..2424c521 100644 --- a/code/artifact.js +++ b/code/artifact.js @@ -35,7 +35,7 @@ window.artifact.requestData = function() { if (isIdle()) { artifact.idle = true; } else { - window.postAjax('getArtifactInfo', {}, artifact.handleSuccess, artifact.handleError); + window.postAjax('artifacts', {}, artifact.handleSuccess, artifact.handleError); } } diff --git a/code/boot.js b/code/boot.js index 2e5f2ecc..e3d1dffb 100644 --- a/code/boot.js +++ b/code/boot.js @@ -640,17 +640,6 @@ function boot() { window.iitcLoaded = true; window.runHooks('iitcLoaded'); - if (!haveDetectedMungeSet()) { - dialog({ - title:'IITC unavailable', - html:'

IITC failed to detect the appropriate network protocol "munge" parameters from the standard intel site. ' - +'This can happen when Niantic make changes to the standard intel site.

' - +'

The IITC developers are made aware of these problems and will be working on a fix. Please see the following for news/updates.

' - +'