One box, one button, eight names
Hunter names pick up whatever the local economy does with animals, dead or alive, wild or bred. A fur trapper in Siberia, a deer culler in Scotland and a bounty hunter in a port city all get named differently. The word hunter itself comes from Old English hunta, an occupational label before it was a fantasy class.
A run starts with one sentence. Five of them gave 40 names. Of those, eleven are one word, eighteen are two words and eleven are three words or longer.
Describe what you’re naming
Optional. A people, a landscape, a mood, or the setting it belongs to. The more specific the culture, the more consistent the eight names come back.
Pick a filter if you have one. It narrows the register, not the meaning.
Names, one per line. Nothing is stored.
Names are generated on the server and shown once. Reloading clears them.
Straight from the tool: forty names
Nothing below has been edited except the trailing explanation. Most of these lines came back as a name, a dash and a sentence describing it, and the sentence is cut here so the set can be read as a list.
Northern coast: Kragvek, Thornkal, Brakkund, Grimvuld, Skarnhed, Drakkfell, Vurntak, Hjolgard.
Old order: Varethine the Last Vigil, Molrec of the Hollowed Oath, Sevraith Ashbound, Ordwine the Unanswered, Kaelith Ruin-Sworn, Thenmar the Late Flame, Ysoldre Vault-Keeper, Brenwulf the After-Echo.
Drowned city: The Drowned Bell, Lowmarket Lurker, Saltveil, Our Lady of the Undertow, Cormorant Saint, The Ninth District, Brinewake, Hollowspire.
Border post: Kestrel Vane, Marrow Latch, Sable Orr, Thorn Ebb, Quill Ash, Hollow Reeve, Briar Null, Vesper Strand.
Small court: Wren of the Nine Hedges, Marrow Fen, Tallow Vane, Sable Rook, Hollow Meg of the Split Oak, Cinder Latch, Bracken Sile, Pale Ottoline Ash.
What the numbers say about forty names
Of the forty names, eleven are one word, eighteen are two words and eleven run to three or more. Two of them begin with The and twenty-eight of them arrive with a description attached.
No closing word repeats more than three times, which is why the set reads as forty separate names rather than one name with variations.
Occupational naming is older than surnames, and hunting has left marks on English, German, Slavic and Gaelic name stocks. English gives us Hunter, Hunt, Huntley and Huntington, all built from the same root and spread by parish records. German keeps Jäger, Jaeger and Jager, which survive as surnames and as a job title in forestry and gamekeeping. Scots Gaelic has sitheach and fowling terms, and the Borders produced families named after the deer forests they worked. Russian промысловик names a commercial trapper, and the trade ran on fur tribute and later on state quotas. Bounty hunting is a separate tradition, tied to bail law and to the port towns where reward notices were posted. Inuit, Sami and Cree naming often ties a person to a place or an animal relationship rather than a trade. A hunter may track quarry through mud and pine, but the Celtic God Name Generator draws its names from deities like Lugh and the Morrigan. Japanese hunting names split between matagi mountain hunters and the wild boar specialists of the south. None of these traditions mix cleanly, and a single culture's names should share a sound palette.
Occupational surnames sound like parish records and trade rolls, flat and plausible. Hunter Ashworth. Frontier trapper names run on hard consonants and short vowels, easy to shout across a camp. Jeb Karr. Northern forest names stack two roots and stress the first syllable. Skaldvik. Coastal and bounty names borrow from court and harbour paperwork, often with a place attached. Mara Whitlock. Ritual and clan names carry a title in front, which reads as formal in dialogue. Sitheach of Dunmore. Invented-world names use a consistent vowel set and avoid sounds from the reader's own language. Voreth Kan. Hunters earn their titles through patience in the field, while the Fate/Grand Order Name Generator builds names from Servant classes and Noble Phantasms.
Where the sentence is at fault
a hunter name that is very old and very tired returned Aldrenn the Last Watch, Morn of the Long Vigil, Sereth Kael, Vayth the Undying, Old Halvern, Thessaly Worn, Corvain Ash, Bram the Sleepless. The eight share no ending at all. Every one of them would fit a dozen other things, which is the whole problem: a mood in the sentence does not make a set specific.
a hunter name for something that guards a door returned Doorgate Vigil, Threshold Warden, The Keeper at the Sill, Lintel Watch, Hinge Sentinel, Portal Steward, Barred Way Guardian, The One Who Stands Before. None of the eight ends the way another one does. Every one of those names belongs to the prop. Swap the subject for anything else and the same eight would still come back.
Read the two prompts again and the two failures are exact opposites. One gives the model a tone to imitate and nothing to name. The other gives it a single object to name and no tone at all. Both return eight plausible names, and neither returns eight names for your subject in particular.
Three routes, costed
Three routes get a hunter name. Only one of them is a name generator.
| What matters | By hand | A general chatbot | This generator |
|---|---|---|---|
| Time for eight names | Twenty minutes or more | One prompt, then editing | 838 ms per set, instant on a repeat |
| Same prompt, same eight | Only if you write it down | No, the wording drifts | Yes |
| Explains the choice | You do | Yes, at length | No |
| Cost | Your time | A subscription | Free, no account |
| Checks trademarks | No | No | No |
A first run takes a few seconds. The same sentence again returns in milliseconds, because the backend caches each set by prompt, so a set you liked is reproducible tomorrow and a set you did not like costs nothing to replace.
Names come back without family structure, so you get no siblings, no married names and no inheritance rules. Titles and ranks appear as words, and the generator doesn't know how your world grants them. A description naming a specific published character returns names close to that character's sound, which is a legal risk only if you publish.
How a miss turns into a usable set
The repair is one clause. a hunter name with hard northern consonants names a place and a kind of thing, and the output follows: Kragvek, Thornkal, Brakkund, Grimvuld, Skarnhed.
Your sentence gets read for nouns first: quarry, terrain, weapon, region and era all carry weight. Adjectives like fierce, silent or deadly get noticed but change very little in the output. Names built from two parts, like Ashford or Grimwald, come back more often than single-syllable ones. Proper nouns you supply get reused as a sound reference rather than copied. Numbers, punctuation and stray capital letters are ignored. Short input produces short names, and long input produces longer compound ones. Dialogue markers like "she says" or quotation marks get stripped before anything else happens. Language hints work only if you name the language, since a description without one defaults to a northern European sound. If your description mentions a published character, expect names that sit close to that character's sound without copying it.
Common questions
Can I use these names in a published book?
Yes, since invented names aren't protected by trademark, and the tool only produces text you can edit. The risk is similarity to a published character, so check any name that feels familiar against the source. Changing one vowel or the stress usually moves a name clear of an existing one.
Why do some results sound like real surnames?
Occupational surnames are the source material, and Hunter, Trapper and Jäger are all real family names. That's useful for historical fiction and awkward for a setting that has no parishes or trade records. If your world has no guilds or landholding, the surname sound will read as borrowed.
Do I need to name a language in the description?
Without one, the output defaults to a northern European sound with hard consonants and short vowels. Naming a language, even an invented one, keeps the vowel set consistent across all eight results. Consistency matters more than accuracy if the language is your own invention.
How many names should I keep?
One per culture is usually enough, since a second name from the same culture tends to drift in sound. Keep a second only if you need a family member and can match the stress pattern by hand. Eight results exist to give you options, not to fill a cast list.
What if a name is hard to pronounce?
Say it in a line of dialogue, and if it stalls, the reader will stall too. Cut a consonant from the join or shift the stress to the first syllable. Names that need spelling out loud rarely survive a scene.
