Share-code workflow
Use this hub for tune-code intent without publishing fake numbers. Apex Tune Hub starts with shareable calculator links, preset pages, and car notes, then can add real in-game share codes after verification.
A tune code should have a car, class, route use, creator or source, and last-tested date. If any of those are missing, keep it as a baseline preset link instead.
Open the tune calculator or a preset URL that already matches class, drivetrain, race type, and handling issue.
Run the same route twice, then adjust one setting group at a time before calling the setup finished.
Attach every usable setup to a car page, class hub, or manufacturer hub so the tune code has context.
Do not publish invented share codes. Use transparent placeholders until a real in-game code is verified.
This page is prepared for tune-code and share-code demand, but it does not publish invented in-game codes. Until a code is verified, it links to transparent calculator presets and car-specific setup notes.
A tune code is an in-game share code after a setup is saved and shared. A preset URL is an Apex Tune Hub calculator state that documents the baseline inputs and makes the setup easy to refine.
Add the exact car, class, drivetrain, route type, share code, creator/source, last-tested date, and matching preset page. Keep old codes labelled if a patch changes the setup.
Update list
Get verified FH6 tune-code updates, preset URLs, and car-specific setup notes as testing expands.
No spam. Just new presets, tested car notes, and release updates.