Description:
In the latest beta version 26.0.29, a new, stricter character or data volume limit has been silently applied to individual pages of written books. When a single page is filled with high-data-volume characters (such as Chinese or Japanese, which typically require more bytes per character in UTF-8 encoding), and the total data size exceeds an unspecified threshold, closing the book causes the game to crash. This issue does not occur with lower-data-volume text (e.g., English) on the same page, nor does it appear in the latest stable release (1.21.132), indicating a regression introduced in the beta.
How to Reproduce:
In beta 26.0.29, acquire a book and quill.
On a single page, write until it is completely filled with high-data-volume characters (e.g., Chinese or Japanese). Do not switch pages mid-writing.
Close the book by exiting the writing interface.
Observe the game's response.
Observed Result:
Writing a full page of Chinese/Japanese characters and closing the book causes the game to crash.
Writing a full page of English (or other low-byte-per-character languages) on the same page does not cause a crash.
Splitting the same high-data-volume text across multiple pages (e.g., writing half on one page, then switching to another) avoids the crash.
This crash is not reproducible in stable version 1.21.132.
Expected Result:
The game should not crash under any normal writing operation within the book's established UI limits.
If a data limit per page is necessary for stability, it should be set high enough to accommodate the maximum number of characters the game's UI allows for any supported language, and the UI should prevent exceeding it (e.g., by stopping text input) rather than crashing.
Behavior should be consistent between stable and beta releases.
Additional Notes:
This crash suggests the new limit is based on raw byte count rather than character count, unfairly penalizing languages with multi-byte characters. It severely impacts players who use books for storytelling, documentation, or data storage in affected languages. The silent introduction of this limit in a beta, without UI warnings or graceful handling (like truncation), constitutes a significant usability and stability regression. The limit must either be removed or adjusted to a safe value that aligns with the visual capacity of a book page.
how funny