Posted Monday, March 12, 2018
Awhile back I noted that I was beginning to work on a random fantasy setting generation project. This is the first piece of that.
It represents part of the design philosophy of the setting generator: each piece does one thing, it does it well, and it does it in a way that can be shared amongst the ecosystem.
The heraldry generator starts out life, then, with this guiding principle: output an image in a common format that can be programmatically modified, along with the necessary metadata to describe what’s in the image for both humans and machines.
For the image format, I chose SVG. It’s basically just XML, which makes it easy to modify, and it’s relatively small. Also, it’s a vector format, which makes it trivial to scale without degradation.
For rapidity of development, I chose to code the generator in PHP. I may rewrite it in a more performant language later if necessary. For now though, this serves my purposes.
Initially, I used a pre-existing library that handles SVG. However, after I got the initial plain-field version working, I discovered that the library doesn’t support
<mask> elements yet, which meant I wouldn’t be able to easily generate field divisions and clip them.
The second iteration, then, stripped out that library and went straight for raw XML manipulation. This ended up working much better for several other things, including arbitrary attribute manipulation.
Heraldry adheres to certain rules. Coats of arms are basically like modern-day road signs; they exist to communicate clearly at a distance. So here are the rules I’m assuming for the generator:
I may modify this list later, but it’s my guiding set right now.
At the moment, the generator only creates coats of arms with basic fields. It’s either a single color, or includes per fess or per pale divisions, also in colors. Metals are being reserved for charges at the moment, which are not included yet.
Here’s a simple example of a plain field:
The tincture generation is being done at a higher level so that the program is aware of which tinctures are used in the entire design. This is so it can avoid violating the first rule.
However, sometimes the divisions are generated in the same color (e.g., azure next to azure). I’ll need to fix this in the next iteration.
The below image may look identical to the first one, but it’s actually divided, just with both halves being vert.
Still, the basic design looks reasonable thus far. Here’s a simple per fess example:
The source code for the generator is available on GitHub.