Exploring the feasibility of the concept

[Incrementis]

There are two concept ideas, which are as follows:

• [x] As the player reads the book, a narrative sequence with appropriate music plays.
• [x] The item description image is large enough ~to be scrolled down~ and symbolizes the story being written.

[Incrementis]

This may not be a real problem, but it is worth noting that the size specified in the iesdp documentation does not appear to be correct. However, because the Testtest.txt file is 32.1 KB, the text size for the item description is set to 4 bytes.

Note: When a new character is added to the specified content from Texttext.txt, the text does not appear in the item's description (the textfile is not present in this issue).

It would be informative to know whether this is a misunderstanding on my part or whether the documentation here is incorrect.

[Incrementis]

It appears that the item description image is a fixed size. Anything outside this size will be cropped (see next image below for an example):

The maximum size of the description image may be 280 x 335 pixels (see next image below):

This eliminates the ability to scroll the image while reading. However, the size could be large enough to include a narrative image to accompany the story in the book.

[Incrementis]

There are some topics about dream/narrative sequences that could help for better understanding:

• [x] http://www.shsforums.net/topic/28109-chapter-text-screen-tutorial/
• [x] https://www.gibberlings3.net/forums/topic/32558-modding-chapter-transitions-and-dream-sequences-in-bgee-edited/#comment-293792

Regarding scripting, the answer to this question needs to be examined in detail:

• [x] 7) How can I link a script with an item?

[Incrementis]

The Chapter text Screen for every game is different: https://github.com/users/Incrementis/projects/8/views/1?pane=issue&itemId=79318015

[Incrementis]

To display the required button text in the item description windows(see image below for an example), there are two 2DA files that are interesting to look at:

• [x] enginest.2da
• [x] itemdial.2da

[Incrementis]

The usage of itemdial.2da will be used because a dialog can execute any kind of scripting.

The idea is as follows

Item description windows:

• Contains only book content in text and image(e.g. drawn without color) form only

Dialogue windows:

• Contains external information about the book, such as the author and appearance of the book, ~as well as confirmation whether it should be opened~

Reading the book:

• Contains the same information as the description windows, but with music, colored images and spoken text