Epic Quest Format

I understand your point. However, I only add notes about Quest Item drop rates, APCs, or helpful hints/strategies. I feel there could be certain scenarios where the notes would be unnecessary such as straightforward clear the dungeon quests. The dungeon map still may be necessary for completion.

In the cases of Vilmark - Area 50, City of Noire Ferra, and Reshpon Village of Pain, the dungeon map pretty much stays the same, so it seems a bit redundant. But in actuality, it may differ from the actual dungeon. (<- I may have to review my notes on the quests.) Special Dungeons are an exception to this. I could remove the maps on those two aforementioned quests and put a note stating that the map does not change for the rest of the quest line; if that helps.

However, in most major epic quest lines, scenario dungeons alter the map to fit the objective. Most don't require notes. For the most part, I recommend that we should keep the maps for consistency reasons.

Altair (talk)

Dfoplayer (talk)

Makes sense. Manually using the table method could result in some pretty messy and extraneous code.

As a suggestion for the template, it could take in as parameters the number of rows and columns. Then it could fill in spaces with image files of corresponding map sections from the given tuples locations. These images probably would include:

• End Points: , , ,
• Straight Path: ,
• Corner Point: , , ,
• 3-Way Junction: , , ,
• 4-Way Junction:
• Boss:
• Empty:

Altair (talk)

Yes. Hopefully we can find a template someone already created on the internet.

Dfoplayer (talk)

I would look to semantic holding a "map", and then {#ask:}ing for it.

The whole DataTemplate thing gets really cyclical real quick, and a pain in the ass to debug or use outside of those templates. I was hoping to transition from that, over to semantic which does all the things we want much easier.