<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Ok, more thoughts on lore:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For generic lore in the arches I believe
it is established that it is sufficient to populate the lore <> endlore
field with weighted values, e.g.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>arch orc</FONT></DIV>
<DIV><FONT face=Arial size=2><..></FONT></DIV>
<DIV><FONT face=Arial size=2>lore</FONT></DIV>
<DIV><FONT face=Arial size=2>@5 Orcs are the foul brethern to
goblins.</FONT></DIV>
<DIV><FONT face=Arial size=2>@4 Dwarves and Orcs have a strong hatred of one
another.</FONT></DIV>
<DIV><FONT face=Arial size=2>...</FONT></DIV>
<DIV><FONT face=Arial size=2>endlore</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Whereby the object name, level and other
information could be grabbed from the arch if necessary too. If you
customize a creature you need to grab this out of the maps however, e.g. if you
make a special dragon, you can put in special lore, it is stored on the
map. This has to be picked up during the map lore collection
however. This would capture the arch name and name if the object had one
(have to remember to check for no name...) but I don't know how stuff like level
and such can be easily snagged with a script if it has not been changed (look up
the arch?- yuck)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>For map and quest type information this is not
going to work, some maps have nothing of interest, and some like the city
maps have many many points of interest. If you were to go with a
header file, you would need to account for different
topics. Also this information can be more tricky to manage since it
is more specific. This is why I think a specific maplore arch object would
be good in addition to the lore field. As an invisible object, map makers
can put many different maplore arches on the map and they can be
pretty chock full of info. Say name is primary key, the mesg field
can be used for a list of other key words perhaps. Other fields
can be assigned for holding information too, the level field for level
information, or title field for location information or
whatever.</FONT></DIV>
<DIV><FONT face=Arial size=2>This can be easily collected via script into a
messages type file for actual use in the game, (even collected via dm command if
need be), the main point of storing the lore with the maps being
portability and customization.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The only thing is that both types of lore should
follow the same data format, style guidelines (including truth and falsehood,
weighting and level and key word information) and be accessable through the
same 'lore engine', although not perhaps in the same
way...</FONT></DIV></BODY></HTML>