[Bug] Renaming a location also renames other locations that contain the first location's name

[hyuri]

Issue

I had two locations that shared part of a name:
SALA
SALA DE JANTAR

Translated to English:
ROOM
DINING ROOM

When I renamed "SALA" to "SALA DE ESTAR", "SALA DE JANTAR" was also affected, being renamed to "SALA DE ESTAR DE JANTAR".

Expectation

Starc should be smarter about keeping and renaming instances of location/character names. The renaming should not be done with a simple find & replace, instead, it should target specific unique objects (in this case, instances of location name).

In programming lingo, my intuition says every location object should keep a list of instances using the location, and then, when renaming that location, only the instances in that list are renamed. But, of course, you'll know better what should be done in your architecture.

[dimkanovikov]

Good find. It’s because of trying to handle anoher case:

HOUSE and HOUSE. ROOM

and Starc thinks that you want to rename complex set