docs(readme): a short front page, the reference sections moved to docs/ as they were #236
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!236
Loading…
Reference in a new issue
No description provided.
Delete branch "jarynclouatre/Longshot:docs/readme-for-players"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The README is 1,124 lines. Someone who only wants to install the game scrolls past the whole menu reference, the command-line switches and the build instructions to find the four steps that matter to them. This leaves a front page of 215 lines and gives each reference section its own page under
docs/.What changed
README.md: the top, Project status, Install and play (the download links and the four steps), What you need, How it works, Want to help?, License and Credits stay as they are. New: a Guides table. Build from source is one line with links.docs/install.md(On Windows, On Linux, Updating, Release channels, RecompLauncher, Where the files go, What Longshot connects to),docs/troubleshooting.md(If something goes wrong, Low FPS or stutter, AMD texture workaround),docs/menu.md(In-game menu, Controls),docs/mods.md,docs/build-from-source.md,docs/command-line.md,docs/pipeline-list.md.docs/menu.mdwhose "below" pointed at a section that is now another page (the "Save my pipeline list" row and the "ASTC as RGBA8" note): they link to it by name.CONTRIBUTING.md,docs/common-issues.md,docs/development.md,docs/getting-started.md,docs/graphics-and-controls.md,docs/saves-script.md,docs/updates-and-saves.md, and in the udmabuf warning ofhost/hos_main.c("see docs/install.md, On Linux") withtests/test_udmabuf_warning.py.docs/menu.md:tests/test_readme_menu_rows.py(file name kept),tests/test_camera_speed.py,tests/test_stick_dead_zone.py, and the website's settings page (website/src/repo-docs/pages.ts,graphics-settings.tsand their tests).website/src/content/docs/requirements.mdxcopies it) and the anchors other places link (#install-and-play,#project-status,#what-you-need,#build-from-source,#credits).Flags and settings
None.
Measurements
main:
1ef93e79(2026-11-13)this PR: docs/readme-for-players @ 3b92826a
Hardware: none used (game-free checks on a Linux x86-64 PC, Python 3.14.4, Node 24.22.2)
Scene: none, the game was not run
Method:
python3 -I -B tests/run_all.py --jobs 4 --timeout 120, two runs each, interleaved (main, PR, main, PR), both runs of a side gave the same counts; inwebsite/,npm ciandnode --test tests/*.test.tson both,npm run buildandnode scripts/check-site.tson the PR; two scripts of mine for the last two rows (below)How to reproduce: the commands above in a checkout of each commit
1ef93e79README.md, linestests/run_all.py(run 1, run 2)test_bake_portability.py,test_display_pointer.pynode --test tests/*.test.tscheck-site.ts.mdfiles outsidewebsite/andthird_party/test_bake_portability.pyfails here for a missing Python module (zstandard);test_display_pointer.pyfails to link on main as well (undefinedrx_option).Rebased since onto main
0edc1377(this PR @35e835f0): the rebase carried #108's reworded "HDR tone mapper" row intodocs/menu.mdand changed nothing else of this PR. Run again at35e835f0: the six checks that read the moved pages (readme_menu_rows,camera_speed,stick_dead_zone,udmabuf_warning,forge_pr,dev_packs: 6 passed), the two scripts (2 lines, 0 of 211 links), and the website's tests: 40 of 47 on main @0edc1377and on this PR @35e835f0, the same seven failing on both with "names no condition for HDR tone mapper, which the menu shows only on some PCs" (see Reviewer notes).Rebased again onto main
d9648863(this PR @f596718e) after a conflict inREADME.mdandwebsite/tests/graphics-settings.test.ts: the rebase carried the ten README lines main gained since0edc1377into the pages they belong to (the "HDR tone mapper" row of #247, the "Damage taken" row of #138 and the paragraph on the Upscaler keeping its render scale of #55 intodocs/menu.md; the Damage taken text of #138 intodocs/command-line.md), kept main's new website test beside this PR's renamed one, and changed nothing else. Run atf596718e: the suite once, 452 passed, 2 failed, 79 skipped (test_bake_portabilityandtest_menu_i18n, which fail the same way on main @d9648863); the website's tests, 53 of 53; the site build andcheck-site.ts("Site check passed: 14 pages, 788 local links and assets, their anchors and edit links"); a script found each of the ten lines in the new pages. The whole suite was not run again on main @d9648863.Testing
Tested: the game-free suite, the website's tests, the site build and its link check, as in Measurements, on a Linux PC. Every line of main's README was compared by script with the new README and the seven pages. Every relative link and anchor in the tracked Markdown files outside
website/andthird_party/was resolved by script before and after.Not tested: the game was not run, and
host/hos_main.cwas not compiled: its change is the wording inside one string literal, the udmabuf warning's "see README, On Linux". The deployed website: built here, not deployed. How Forgejo renders the new pages was not looked at page by page.Needs other testers: None.
Screenshots
Nothing on screen.
Risk and rollback
An open pull request that adds a row to the README's option table, or edits one of the moved sections, will conflict; its lines belong in
docs/menu.mdor the matching page now, andtests/test_readme_menu_rows.pysays so when a menu row has no line there. Links from outside the repository to a moved README anchor (#in-game-menu,#controls,#if-something-goes-wrong,#on-windows,#on-linux,#mods) land at the top of the README, where the Guides table is. Reverting the commit puts everything back.Reviewer notes
git diff --color-moved=zebra main...HEAD -- README.md docs/.0edc1377seven website tests fail since #108 reworded the "HDR tone mapper" row (its cell no longer has the "(shown only with ...)" form the settings page reads the condition from). They pass since: 53 of 53 on this PR @f596718e.Issues
None.
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above).third_party/untouched (a new folder with aPROVENANCE.mdinstead).If applicable
tests/that reads changed source updated in this PR, not weakened.WIP: docs(readme): a short front page, the reference sections moved to docs/ as they wereto docs(readme): a short front page, the reference sections moved to docs/ as they were35e835f060f596718e08Rebased onto main
d9648863after a conflict inREADME.mdandwebsite/tests/graphics-settings.test.ts(nowf596718e). The rebase carried the ten README lines main gained since0edc1377into the pages they belong to: the "HDR tone mapper" row (#247), the "Damage taken" row (#138) and the Upscaler paragraph (#55) intodocs/menu.md, the Damage taken text (#138) intodocs/command-line.md. Main's new website test is kept beside this PR's renamed one. Nothing else changed. Run atf596718e: suite 452 passed, 2 failed, 79 skipped (test_bake_portability,test_menu_i18n; both fail on main @d9648863too), website tests 53 of 53, site build andcheck-site.tspass. The description has the detail.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.