Re: [crossfire] Map logical linking
Hello. Looks good to me. It may be worthwhile to define how that information is used, and thus perhaps other fields. As I see it, information is only used for mapper, to generate map information. No ingame link - at least, none that I plan to do, maybe others? :) The idea to split quests from maps could be interesting, though, someday (so you could distribute map packs containing a quest). As for the format of the field, I'd suggest: HTML, without anything fancy, and no h1/h2 headers (so they can be used for other things on the page). Nicolas -- http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de l'aléatoire !] signature.asc Description: This is a digitally signed message part. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Map logical linking
Nicolas Weeger wrote: much snipped If needed we'll extend that further on (thinking about linking to other quests, or maps, or whatever) Opinions? Looks good to me. It may be worthwhile to define how that information is used, and thus perhaps other fields. If it is just for mapmakers, then no big deal. OTOH, it could be nice to tie it into the region, so that folks in scorn may talk about some aspects (The king of scorn is looking for heroes to solve some problems - go to the scorn castle) type of thing. Or maybe other snippets appear randomly in scrolls or books - that makes a lot of sense for things like forgotten ruins - a scrap referencing a ruined castle in a book found in a dungeon makes some sense. Or maybe all of this is driven by files in the map directory that cover these broader aspects of quests (like a scorn_royalty.qi file that determines what info shows up in books, shows up in NPC conversations, etc) ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
[crossfire] Map logical linking
Hello. One issue I have with maps is that sometimes you have no clue what quest or thing they are linked to. Example: I was browsing (in the editor) maps in Navar, and discovered some quest spawning various maps, with keys in one or the other, but no idea where to find other maps. So I'd like to be able to easily find what maps are linked together for a quest. For this, I suggest to use the lore field in the maps, which is totally unused (it's loaded with other headers, but never displayed). Proposal for logically linking maps: * in one of the maps, probably the one with quest starting point or quest end, describe the quest in the lore field, and include what maps are linked to the quest, maybe more information like player level or reward? Minimum is the linked maps * in each quest map, add in the lore a reference to the quest and the map with all the information Since I'm (after all!) a developer, I could suggest to create an easy format for this lore field to be able to automatically extract information and make nice spoiler pages. But well, maybe not that necessarily to go that far :) Opinions? Suggestions? Nicolas -- http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de l'aléatoire !] signature.asc Description: This is a digitally signed message part. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
