From bd13278ec0a331af64af54f4fd8ebd1531b30437 Mon Sep 17 00:00:00 2001
From: Jon Atkins <github@jonatkins.com>
Date: Sat, 13 Jun 2015 10:20:16 +0100
Subject: [PATCH] add comments concerning artifact changes - will double check
 once the flaky niantic update sorts itself out

---
 code/artifact.js | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/code/artifact.js b/code/artifact.js
index 5bbecc19..b5335b8f 100644
--- a/code/artifact.js
+++ b/code/artifact.js
@@ -37,6 +37,20 @@ window.artifact.requestData = function() {
   } else {
     // new API available in stock (2015-05-21) - 'getArtifactPortals'
     // stock still uses this one, and the new method doesn't yet return anything, but they might be changing things soon...
+//2015-06-13 - stock intel update using the new API
+//above method takes no params, returns a list of portals. however, no longer
+//1. a distinction between target portals and artifact portals
+//2. some shard details in the portal summary 'unknown12' variable
+//  a. no sign of fragment numbers in this summary data - only in portal details
+//  b. not sure how resistance/enlightened targets are identified. so far, most portals have
+//    "[[["lightman"]], []]" (fragment at portal?)
+//    aod two have
+//    "[[["lightman"]], [["lightman"]]]"
+//    best guess - first array is a list of artifact types (but not numbers) at a portal
+//               - second array is a list of the target types for a portal
+//    (so "[[[]], [["lightman"]]]" would be for a target without any fragments at it
+
+
     window.postAjax('artifacts', {}, artifact.handleSuccess, artifact.handleError);
   }
 }