Welcome to the DFO World Wiki. With many major updates since the release of DFO, many items are missing. Visit Item Database Project to learn more.
Please remember to click "show preview" before saving the page.
Thanks for the updated logo snafuPop!
Epic Quest Format
Hey Dfoplayer. I'd like your opinion on the Epic Quest format for Vilmark - Area 50 (Epic Quests). I added the Hidden Text Template to the dialogue to minimize space. I also added a section for Dungeon Maps for scenario dungeons (if necessary). How does it look? Does it look too clunky? Is it user friendly? Is it too overwhelming? I was thinking about surrounding the quests in the Hidden Text Template, but some of my friends said it was gratuitous.
Anyway, I'm just concerned on what the standard should look like before I start editing on a large scale. I have most of the information ready to input from Abnova to Time Gate. I'll probably have Power Station information ready in two weeks.
It's good to minimize space, and I would just leave it like the way you have it. I'm not sure if we need the dungeon map for the non-noted quests, such as "To Prevent Another Incident" or "Collecting Terranite."
You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page.
Return to Thread:User talk:Dfoplayer/Epic Quest Format/reply (2).
For consistency reasons, I see your point.
If we start to use the table method of dungeon maps, we should think about a template. Over at Mabinogi Wiki, they place everything in Data Templates, which is then used in DataFormat Templates. This allows them to reuse the data in any page. Someone here does not like in-line css.
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:
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.
