[CF-Devel] More Lore

[crossfire-devel-admin at archives.real-time.com]

Todd wrote:
>
     
      Changes made to lore fields in the editor do go into the maps now, as do 
     
     >
     
      changes to any arch field.  You'll have to fix that if you do not want 
     
     >
     
      any lore in the map files outside the header, and since this is the way 
     
     >
     
      arches are designed to work (archetypes) you are introducing new 
     
     >
     
      problems IMHO.
     
     
  The problem is that by collecting data from the maps that is used before run 
time, we are heading into something that was never done before.  This entire 
premise could very well be introducing various problems.

  I'd really not want to far down this path - the number of things I could 
potentially see collected could get quite large, and quite messy (this is even 
true with lore, eg, map one adds some lore about 'Sam'.  Map 2, completely 
unrelated, also has lore entries for 'Sam', and the data is unrelated or perhaps 
contradictory - map1: Sam is immune to magic, and needs to be hit with weapons. 
  map2: Sam is afraid of fire and lightning, and avoids it like the plague).

  Is this likely?  Probably not.  And even that may not be terrible.  But think 
if you go down this path and you collect treasure lists from the maps, and you 
have two treasurelists of the same name, etc.  I'd really like to re-inforce the 
notion that data in the maps really won't be examine.  If lore is in the map 
header but not in the objects, and we don't process the objects, people will 
quickly see it won't work.

  It would in fact be possible to make it impossible to modify the lore on an 
object level.

>
     
      I though this forum was to discuss new features fully *before* 
     
     >
     
      implementing them.  I am sure you could have written code to implement 
     
     >
     
      lore much sooner, so could I.
     
     
  It is.  But at some point, discussion has to stop and things more along.

  However, in this particular case, it seems like an impasse had been reach.

My belief: lore data in the map header makes more sense.
Your belief: lore data should be in lore objects

  I didn't see any signs that these beliefs were going to change in either way. 
  I really got the feeling we could discus this for weeks and we'd still be at 
the same point.  And my point was sort of that putting the lore in the map 
header really isn't as complicate as you make it sound - 5-10 minutes to modify 
the load/save routine for the map header, 5-10 minutes to write a script (or 
modify the existing one) to collect the data.  So my point on that being that 
having it in the map header isn't really any more complicated or more difficult 
to right.




_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel