docs: clarify PFS/PFSC image and container workflows in README #71
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-drakmor/ShadowMountPlus!71
Loading…
Reference in a new issue
No description provided.
Delete branch "unknown repository"
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?
Summary
This PR improves the PFS-related documentation in
README.md.What changed
.ffpfs) and PFSC nested-image containers (.ffpfsc)pfs_image.datis treated as a nested PFS image only when located inside a mounted PFSC containerWhy
The previous README text made the direct PFS and PFSC container flows easy to confuse, especially in the packing examples. These updates make the intended layouts and usage clearer and align the docs with the current implementation.
Scope
Documentation only. No code behavior changes.
Summary by CodeRabbit
No actionable comments were generated in the recent review. 🎉
ℹ️ Recent review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID:
678543d4-8279-4e40-aac6-f3211d2a1bb8📥 Commits
Reviewing files that changed from the base of the PR and between
2bd8b75566and53e266d446.📒 Files selected for processing (1)
README.md🚧 Files skipped from review as they are similar to previous changes (1)
📝 Walkthrough
Walkthrough
This PR revises the README to consolidate the intro, clarify support for experimental compressed PFS formats
.ffpfsand.ffpfsc, explain nested-container behavior, and addmkpfs-based packing workflows for exFAT→.ffpfsc, folder→pfs_image.dat→.ffpfsc, and experimental.ffpfsone-pass packing.Changes
Compressed PFS Format Documentation
README.md.ffpfsand.ffpfscrows; adds guidance recommending experimentation with.ffpfscand preferring nested exFAT layout.README.mdpfs_image.datis treated as a PFS image inside.ffpfscand how outer vs innerimg_typeapply; replaces compressed-PFS packing docs withmkpfsexFAT→.ffpfsccommands, adds folder→pfs_image.dat→.ffpfscworkflow, and documents experimental direct.ffpfsone-pass packing example.Estimated code review effort
🎯 3 (Moderate) | ⏱️ ~20 minutes
Poem
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment
@coderabbitai helpto get the list of available commands and usage tips.Pull request overview
Updates the README to clarify ShadowMountPlus image-type semantics and to expand/modernize documentation around compressed PFS workflows (especially
.ffpfscand.ffpfs).Changes:
.ffpfs/.ffpfsc..ffpfs(direct) guidance.💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
@ -243,20 +216,60 @@ make_image.bat "C:\images\PPSA12345.exfat" "C:\payload\PPSA12345-app"The exFAT image must contain the game files at the image root, without an extraThe section title calls
.ffpfs“Folders”, but the section body describes it as a direct compressed PFS image format. Renaming the heading to match the terminology used elsewhere (e.g., “Direct compressed PFS images (.ffpfs)” or “Compressed PFS images (.ffpfs)”) would reduce ambiguity.Earlier examples used explicit options like
--verify,--version PS5, and--inode-bits 32, but the updated commands omit them. If these flags are still required/recommended for PS5 images, the README should either include them here as well or state that the currentmkpfsdefaults are equivalent; otherwise readers may end up producing images with different parameters than intended.The text says the output is a
.ffpfsccontainer, but the example command produces./PPSA12345.exfat.ffpfsc(double extension). This is likely to confuse users and also conflicts with earlier examples that implyPPSA12345.ffpfsc. Consider updating the output filename to./PPSA12345.ffpfsc(or explicitly stating why the double extension is recommended). Also remove the trailing space at the end of the comment line to avoid markdown/style noise.@ -243,20 +216,60 @@ make_image.bat "C:\images\PPSA12345.exfat" "C:\payload\PPSA12345-app"The exFAT image must contain the game files at the image root, without an extraDefaults are already made with the correct flags.
@ -243,20 +216,60 @@ make_image.bat "C:\images\PPSA12345.exfat" "C:\payload\PPSA12345-app"The exFAT image must contain the game files at the image root, without an extraSolved
Solved
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.