Name Filter Settings
nameFilterSettingsKeyed map of name replacement rules. Each key is a name to avoid; its value lists the names that may be used instead. When generation reaches for a disallowed name, one of its replacements is used.
"Replacement rules for names that should not appear in generated or player-created characters."
- Editor location
- Files → Other → Name Filter Settings
- Editor type
- Edit in Studio + View JSON
- Size limits
nameFilterSettings(entire section) — 150,000nameFilterSettings.*.replacements.*(each replacement) — 64
Schema
{
"nameFilterSettings": {
"<key>": {
"replacements": [
"string"
]
}
}
}Example
{
"nameFilterSettings": {
"Marcus": {
"replacements": ["Alex", "Ethan", "Jason", "Ryan", "Owen", "Nathaniel", "Adrian", "Colin"]
},
"Elara": {
"replacements": ["Thea", "Cora", "Nova", "Vega", "Astra", "Selene", "Orion", "Cassie"]
},
"Ironfoot": {
"replacements": ["Anvildrang", "Broadback", "Coalvein", "Cragmor", "Deepholm", "Redforge"]
}
}
}Entry shapes
Leave as {} if you have no naming constraints.
An entry maps one disallowed name to the names that may be used instead: the key is the name to avoid, and replacements lists what the world may pick from in its place. The seeded defaults are the clearest guide to the intent — each one takes a name that generation reaches for too often and offers alternatives, Marcus giving way to Alex, Ethan, Jason and the rest.
Nothing validates the contents, so any string decodes. Keep entries to names: a key that is a word or a phrase, or a replacements list of [""], is not what the field is built to do and there is no evidence it reaches prose in the story.
Fields
replacements
The names that may be used in place of this entry's disallowed name. When generation produces the disallowed name, one of these is picked at random instead. Voyage's own defaults use it to swap overused names for alternatives.