The entry gates to portal vaults can now set their long feature description via

the desc_long property of the Lua marker.  The lets the portal vault code be
enitrely self contained, rather than having to have a portion of the
description in dat/descript/features.txt.  Also, in theory each different entry
vault could have its own version of the description, or it could even
programatically vary after the entry vault had been generated (since it can be
a function in addition to a string).  Also, since the gate's short feature
description is no longer needed as a key into the features database, the short
description doesn't need to be the same for each entry vault.

The way I put the descriptions into the .des files is a bit clunky, but when I
tried to use the Lua multi-line string quote ([[string]]) each line displayed
by Crawl was indented one space.


git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk@8001 c06c8d41-db1a-0410-9941-cceddc491573

1 files changed, 2 insertions, 0 deletions

diff --git a/crawl-ref/source/mapmark.h b/crawl-ref/source/mapmark.h
index 67b2c23f75..c21cb1e30c 100644
--- a/crawl-ref/source/mapmark.h
+++ b/crawl-ref/source/mapmark.h
@@ -43,6 +43,7 @@ public:
     virtual void read(reader &);
     virtual std::string debug_describe() const = 0;
     virtual std::string feature_description() const;
+    virtual std::string feature_description_long() const;
     virtual std::string property(const std::string &pname) const;
 
     static map_marker *read_marker(reader &);
@@ -115,6 +116,7 @@ public:
     map_marker *clone() const;
     std::string debug_describe() const;
     std::string feature_description() const;
+    std::string feature_description_long() const;
     std::string property(const std::string &pname) const;
 
     bool notify_dgn_event(const dgn_event &e);