-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
- Check the log file —
tf2autoswap.login the tool folder records all errors with timestamps - Try
--dry-runto test without writing any files - Use
--listto verify the tool can find and search models
Message: TF2 not found. Set the path manually with the tf/ directory.
Cause: The tool checked common Steam paths and did not find TF2.
Fix: Set the path manually:
python3 tf2autoswap.py --tf2 "/path/to/steamapps/common/Team Fortress 2/tf"
Message: No matches for 'keyword'.
Cause: The keyword did not match any item in TF2's VPK.
Fix:
- Check the spelling — the tool will suggest alternatives if it finds close matches
- Try searching by the item's full friendly name (e.g. "A Head Full of Hot Air")
- Use
--list keywordto browse matches without building - Look up the internal keyword on backpack.tf:
https://backpack.tf/overview/Item Name
Message: (tf2_schema.py not found — friendly names and clip warnings off)
Cause: tf2_schema.py is missing from the tool folder, or the vdf library failed to install.
Fix: Make sure tf2_schema.py is in the same folder as tf2autoswap.py. The tool works without it but loses friendly names and warnings.
Message: WARNING: The script vpk.exe is installed in '...' which is not on PATH.
Cause: Standard Windows behaviour when pip installs scripts to a location not on PATH.
Fix: Nothing — this warning is harmless and does not affect how the tool works. The libraries install correctly regardless.
Cause: The VPK may not have been imported into the preloader yet, or the preloader needs to be re-run after a TF2 update.
Fix:
- Open the Casual Preloader
- Drag the VPK onto the preloader window
- Tick it in the Addons tab
- Click Install
- Launch TF2
Possible causes:
- Another mod in the same slot is active — untick it in the preloader
- The preloader was not re-run after a TF2 update
- The source and target were the same item (no visual change expected)
Cause: The path may contain characters the OS rejects, or the folder may not be writable.
Fix: The tool will fall back to the default output/ folder and tell you if a path fails. Check the log for details.
The log file is at tf2autoswap.log in the tool folder. It records:
- Every successful build with source, target, and output path
- Every error with a timestamp
- Schema loading warnings
If you need to report a bug, attaching the log file helps significantly.
Open an issue on the [GitHub repository](https://github.com/TF2Autoswap/releases/issues) and include:
- What you were trying to do
- What happened instead
- Your operating system and Python version
- The relevant section of
tf2autoswap.log