Working With Silversmiths Of Georgia: What It Actually Does and How to Use It
I ran into this last year when I needed a clean way to pull asset metadata from a project without opening the full editor. Silversmiths Of Georgia is a lightweight toolkit for managing and exporting silversmithing-related assets, mostly used by indie devs and modders who work with crafting systems. It isn't a massive suite, which is exactly why it stuck around. It's a set of Python-based utilities that batch-process silver-themed assets — textures, normals, material definitions — into usable formats for engines like Unity, Unreal, or Godot. The core value is the conversion pipeline and the metadata tags it attaches along the way. You drop a folder of source files in, run a config, and out comes a structured export with PBR values pre-filled where they make sense. The project lives on GitHub under the name Silversmiths Of Georgia. It's not actively maintained right now, which matters because newer engines drop support for older Python versions faster than older tools get updated.
Installation and first run
Grab the latest release from the repo. You'll need Python 3.9 or 3.10 — anything above that and the dependencies start quietly breaking on their own. Clone it, run pip install -r requirements.txt, and you're two minutes away from your first export. There's a sample config at config/default.yaml. Don't skip reading it. The file defines input directories, output paths, material presets, and which texture channels to keep. I changed three lines and the whole pipeline shifted from a 45-second run to under eight. To run it from the command line:
python silversmith.py --config config/default.yaml --input ./source_assets --output ./exports That's the basic command. Add --verbose if you want to watch each step instead of waiting in silence, which I usually do the first time with a new folder.
Get the Full Details
Common pitfall: texture channel mismatches
Most beginners mess this up. The tool assumes your source textures use premultiplied alpha for the metalness/roughness workflow unless you tell it otherwise. If you feed in straight alpha files without updating the config, your exported materials come out milky at the edges on anything that uses transparency. I spent an afternoon chasing a render issue before I realized the alpha handling flag was still on the default setting. The fix is in the config file. Set alpha_mode: premultiplied if your textures are already premultiplied, or switch to straight if they're not. Double-check that your roughness maps are grayscale, not colored — the tool won't warn you if they aren't, it just passes them through and you wonder why everything looks plastic.
A workaround I use for batch naming
There's no built-in rename pass, so I wrote a small helper script that runs before the export. It scans the input folder and renames files based on a pattern like {material}_{variant}_{size}.png. This saves a lot of time later when you're hunting for a specific texture inside the engine. Here's roughly what mine looks like: import os, re for f in os.listdir("input/"):
if re.match(r".*\.png$", f): parts = f.split("_") new_name = f"_".join(parts[:3]) + ".png"
os.rename(os.path.join("input/", f), os.path.join("input/", new_name)) Rough and fast. It does the job without adding a dependency.
When Silversmiths Of Georgia falls apart
The tool struggles with anything over 4K resolution on older machines — it loads all channels into memory at once. If you're pushing heavy exports, split your folders and run smaller batches. Also, it has zero support for GPU-accelerated conversions right now, so everything is CPU-bound. On a modern chip a full batch still takes minutes rather than seconds, which is acceptable for occasional use but painful if you're iterating constantly. Another hard limit: no Blender or Substance integration. You export to standard formats like PNG, TGA, or KTX, but if your pipeline expects .bsdf or .sbsar files, you're on your own. I ended up using a separate batch converter for those cases.
Alternatives worth knowing
If you don't need the silver-specific presets, Blender's asset pipelines and Aseprite batch exports cover a lot of the same ground. For pure PBR material generation from raw textures, xNormal is still the fastest option and handles normal map baking without the config overhead. If you're deep in Unity, the PolkaPBR or PBRT exporter workflows might save you from dealing with this tool entirely. Silversmiths Of Georgia is best suited for people who already have a folder of properly prepared silver/crafting assets and just need a repeatable way to push them through an export chain without manual steps. It's not a general-purpose asset tool, and it doesn't pretend to be. Know that going in and it'll do exactly what you need.
Download
The source code and releases are available on the official GitHub repository for Silversmiths Of Georgia. Look for the latest tagged release rather than the main branch, since the branch occasionally picks up experimental commits that haven't been tested against the current Python versions. Check the README for engine-specific notes, particularly if you're targeting Unreal 5 or Godot 4, because the supported versions shift when the tool stops keeping up with upstream changes.
