A live raw-character display is useful for pacing a manuscript only after you know its scope and counting rule. Confirm whether it refers to the active file, a selection, or the whole project, and test how it treats spaces, line breaks, and ASCII. Then verify that the saved file returns the same count after reopening.
Every displayed number has a scope
With several tabs open, a count may follow the active tab rather than the whole book. Selection counts and document counts also answer different questions. Write the scope beside any progress note so yesterday’s chapter number is not compared with today’s project total.
Raw count is not page count. A publishing layout can turn the same characters into different page totals, and prose quality cannot be inferred from either number.
Build a mixed sample
Use 900 Japanese characters, 100 ASCII characters, 80 spaces, and 20 line breaks. Compare the expected components with the editor’s result. Remove one category at a time if they do not align; this reveals which elements the counter includes.
Once the rule is understood, add a paragraph and observe the difference. The useful signal for daily writing is often the change from yesterday, not fixation on a single total.
Reopen before treating the total as final
A controlled large sample returned 300,324 characters before and after reopening, with the saved content unchanged. That confirms count preservation for the sample. The graphical placement of the count was not captured in that check, so do not assume a particular on-screen location without checking the current application.
For a submission number, save the delivery file, close it, reopen it, and count the same scope. A live count from an unsaved tab can remain a progress signal, but it is not the final delivery measurement.
Record counts as a sequence
Do not overwrite the starting number in your notes. Keep the value before each editing step, the expected change, and the value after reopening the file. A same-length substitution may leave the raw count unchanged even though the text changed, while an inserted paragraph should produce a predictable increase. If a value is surprising, inspect only the most recent operation first. Rune Studio’s count is most useful as a checkpoint alongside search results and a review of the changed passage, not as proof that every character is correct.
Use the display for pacing, not judgment
Weekly differences can show whether a draft is expanding or tightening. They cannot tell whether a scene works. Keep editorial review separate from count tracking.
Rune Studio is useful when manuscript context and raw counts belong in one workspace. Review current behavior on the Rune Studio product page, then establish the rule with the mixed sample before relying on the display for a deadline.
