Adds a TODO about changing the quest marker structure

src/main/java/net/knarcraft/dynmapcitizens/trait/QuestsHandler.java

@@ -79,6 +79,15 @@ public class QuestsHandler extends AbstractTraitHandler {
             updateQuestAreas();
         }
 
+        //TODO: The order of operations seems kind of wrong right now. To get an actual overview of which Quests NPCs
+        // are involved in, it's probably best to loop through all NPCs instead, as each NPC can be the start for
+        // several quests. Might be inefficient though. No matter what, NPC-quest-relations should probably be stored
+        // somehow, and only printed once everything's been calculated. For each NPC, store a list of quests they can
+        // be used to start, a list of quests they are used as delivery target for and a list of quests in which they
+        // must be killed. So, a dictionary from unique NPC id to a quest info object. The object stores everything
+        // necessary about quests. When finished, loop through the dictionary, and generate the marker, with all the
+        // quest info. I'm not sure at which point the quest area markers should be generated.
+
         for (IQuest quest : questsAPI.getLoadedQuests()) {
             UUID npcStartId = quest.getNpcStart();
             //TODO: Store locations of NPCs and see if they've moved?