DazaKiwi wrote: ↑Sat Jan 09, 2021 1:57 am
Is it possible to add to this library a correction to when you examine an object which if it has the ability to open and close etc, Adrift will automatically tell the player if the object is open or closed, but it usually outputs this line with an indention of 1 character which looks messy. I can't think off hand if there is other cases like this too?
I see your point and I agree it looks messy. I looked into this, and it turns out that ADRIFT automatically puts two spaces between alternative descriptions unless there is a line-break.
I think I once read in a post that there should sometimes be two spaces between sentences according to English (UK-English?) rules. If anybody knows about this, please comment.
I would personally prefer to decide myself how many spaces I put between sentences. For me only one space seems right, as there is no such rule in Danish to have two spaces between sentences.
I found a method to avoid having two spaces between alternative descriptions. Simply put <del> at the start of each alternative description. Then you will only have one space between sentences. However, in the transcript there will still be two spaces, but I guess the important thing is what is seen on the screen.
This method can be a problem if the first description displayed is an alternative description starting with <del>. In that case, the line-break following the player input is deleted and thus the description is put on the same line as the player input. However, in the standard library I think there is always a default message before alternative descriptions, so it shouldn't be a problem for the library tasks.
Thus, I intend to apply the above solution in the next release of the Combined Library.
However, it may take some time before I make an update. Until then, you can just make a text override, which replaces two spaces with one. So unless you deliberately want two spaces somewhere in your game, this is an easy work-around. You can also apply the <del> to all alternative descriptions in the standard library if you want, but that is quite a job.
Thank you for bringing this up.