rozzingit
commented
5 years ago FYI you could already write super-long books using the template code.
Open dvoraen opened 5 years ago
rozzingit
commented
5 years ago FYI you could already write super-long books using the template code.
Is your feature request related to a problem? Please describe. The problem pertains to writing way too much for a book object, that you have to split it into multiple books with matching and/or sequential titles. The issue I have lies in the fact that if you write a LOT for a given subject, you have to split it into multiple books and keep track of those. This becomes increasingly problematic over time, as eventually the more book objects you write (and store in the same room), the more spam you create when you or any other player makes the mistake of looking for which bookcase you put them on. An example of this would be some of the bookcases in the Great Archive; there are multiple works on the same subject in there ("vol 1, vol 2" etc.)
The purpose is mostly to consolidate large text quantities into one object, rather than having to use multiple objects. In essence, the object type references multiple text buffers that are in the database, rather than it being one book for one buffer as it is now.
Describe the solution you'd like A new object type (that I'm tentatively calling an anthology) that allows you to write multiple sections. In essence, it would support the following:
look \<object> read \<object> When either of these commands are used on an "anthology" object, it returns text similar to the following:
\<object name> \<object desc> <- optional, maybe pointless?
read \<object>/\<chapter title or #> write \<object>/\<chapter title or #>=\<text> Self-explanatory. In write's case, the syntax is to support correcting errors in the text before you write/finish it.
write/addchapter \<object>/\<chapter title>=\<text> This creates a new entry at the bottom of the Table of Contents for the object referencing that text.
Describe alternatives you've considered Writing a lot of book objects and creating a similarly-titled container to hold them all when they're the same topic. :(