Why players read patch notes
Patch notes are often the only marketing an update gets. On Steam they appear as an event on the store page and in every owner's library, and a clear list of fixes tells reviewers you listen. Players skim, so put new content first, group changes and write them as what the player will notice: "Fixed the shop button on small screens" rather than "fix(ui): btn z-index".
How lines are sorted
Conventional commit prefixes are read first: feat becomes New, fix becomes Fixes, perf becomes Improvements, and refactor, chore, ci, test, docs and build are internal and can be dropped. Otherwise keywords decide: add and new, fix and crash, buff, nerf, damage or cooldown for balance, improve and optimize, remove. Korean keywords like 추가, 수정, 개선 and 삭제 work too. Numbers written as 500 -> 420 become 500 → 420. Commit hashes and pull request numbers are removed and every line starts with a capital letter.
Store limits
Google Play allows 500 characters of "What's new" per language, so the Play version keeps new content and the most important fixes and adds "and more fixes" when it runs out of room. The App Store allows 4,000 characters. Discord messages stop at 2,000 characters, so long notes are split into several posts. Steam events take BBCode with headings and lists.
Is anything uploaded?
No. Notes and history are kept only in your browser.