KnarCraft/DynmapCitizens
KnarCraft/DynmapCitizens
1
0
Fork 0
Code Issues 4 Pull Requests Projects Releases Wiki Activity

Adds a TODO about changing the quest marker structure

Browse Source
This commit is contained in:
Kristian Knarvik 2022-10-26 21:40:06 +02:00
parent 473d643621
commit 2f4ff7314d
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/main/java/net/knarcraft/dynmapcitizens/trait/QuestsHandler.java
View File

@ -79,6 +79,15 @@ public class QuestsHandler extends AbstractTraitHandler {
updateQuestAreas(); 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()) { for (IQuest quest : questsAPI.getLoadedQuests()) {
UUID npcStartId = quest.getNpcStart(); UUID npcStartId = quest.getNpcStart();
//TODO: Store locations of NPCs and see if they've moved? //TODO: Store locations of NPCs and see if they've moved?