Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Catalog · How the catalog works
Anything · Lazarus or Delphi
Random projectRandom project

Fallout4-Technical-Guides

Practical Fallout 4 modding guides, tested workflows and xEdit tools.

View on GitHub

Member rating

No ratings yet.

Sign in to rate this project.

README

Fallout 4 Technical Guides

Practical Fallout 4 modding guides, tested workflows and xEdit tools.

This repository publishes procedures developed from real modding projects and then rewritten as standalone technical documentation. It focuses on reproducible steps, rollback paths and clear distinctions between tested configurations and general guidance.

Published Guides

Addictol

Animation Tools

BodySlide and Outfit Studio

Graphics and Upscaling

Generation Workflows

Environment and Seasons

Nuka Ride and MSMA

Modlist Evolution

Papyrus and Troubleshooting

Published Tools

xEdit

Planned Topics

Future guides may cover:

  • Creation Kit dialogue and scene authoring;
  • Fallout 4 DDS and BGSM workflows.

Documentation Labels

Each guide identifies its scope:

  • Tested guide: records a procedure that was actually performed and validated on the stated setup.
  • Generic checklist: provides a safe decision framework but is not a universal preset.
  • Historical reference: preserves an older working method that may require adaptation.

Version-specific values must never be assumed to apply to a newer release without checking the current mod description, requirements, file notes and changelog.

Third-Party Projects

This repository does not redistribute third-party mods, binaries, archives, artwork or copied documentation.

Third-party project names belong to their respective authors. External tools and mods are linked for identification and credit. The procedures published here are independent community documentation based on practical testing and original notes.

Support

These guides are provided as practical community references.

They do not guarantee compatibility with every runtime, modlist or load order. Users remain responsible for backups, version checks, testing and rollback preparation. No personalized installation support is guaranteed.


Test first, document what actually happened, and never let an old generated patch quietly become its own input.