From d1ce8870bad41316e2dad38c80e028762ebc4ef7 Mon Sep 17 00:00:00 2001
From: Jon Atkins <github@jonatkins.com>
Date: Thu, 29 Aug 2013 00:58:43 +0100
Subject: [PATCH] add legacy data fields to fields and links

---
 code/map_data_render.js | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/code/map_data_render.js b/code/map_data_render.js
index 34d826bb..63f2ab83 100644
--- a/code/map_data_render.js
+++ b/code/map_data_render.js
@@ -260,7 +260,9 @@ window.Render.prototype.createFieldEntity = function(ent) {
     guid: ent[0],
     timestamp: ent[1],
     details: ent[2],
-    data: ent[2]	// LEGACY: we used to be inconsistant - portals used .details, fields .data
+    // LEGACY FIELDS: these duplicate data available via .details, as IITC previously stored it in data and vertices
+    data: ent[2],
+    vertices: ent[2].capturedRegion
   });
 
 
@@ -300,7 +302,9 @@ window.Render.prototype.createLinkEntity = function(ent) {
     clickable: false,
     guid: ent[0],
     timestamp: ent[1],
-    details: ent[2]
+    details: ent[2],
+    // LEGACY FIELDS: these duplicate data available via .details, as IITC previously stored it in data and vertices
+    data: ent[2]
   });
 
   window.links[ent[0]] = poly;