Clarify the 4.1.5 Forge upgrade and archive older documentation - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Players coming from the last Forge release, TSC v1.0.8 for SPT 4.0.13, were seeing notes framed as a small v1.3.9-to-v1.3.10 target update. Rewrite the README, release notes, and Forge description around the cumulative additions: cargo transfer, the pre-raid store, redesigned phone and Alt mouse controls, Pilot and the dedicated slot, radar options, payment recovery, A-10 targeting, SIC, and bundled Toolkit.
Separate concise current installation instructions from detailed usage and historical documentation. Distinguish a fresh 4.0.13 migration from a compatible 4.1.x patch update, keep current Fika support explicitly untested, and label older development docs as historical. The archive index documents the three intermediate GitHub prereleases being retained as drafts.
This changes documentation only. The published v1.3.10 tag, ZIP, and checksums remain unchanged.
Validation: release metadata verification, Markdown link checks, source review of feature/control claims, and git whitespace checks.