Factorio Forums

canidae wrote:I noticed that it's possible to reference certain localized strings in your mod's localization. For example, you can add a localization like: "test_msg = Test: __ENTITY__coal__" and it'll show up as "Test: Coal" for English localization in the game (and I'm guessing as "Test: Kull" for Norwegian localization).
(Note: I'm currently at work and I might not remember the "__ENTITY__coal__" syntax entirely correct)

In a mod I wish to reuse localization of technology names, but I was unable to find any examples of this. This is what I'm trying:

Code: Select all

[virtual-signal-name]
grenade-damage = [Auto Research] __TECHNOLOGY__grenade-damage__ (signal value sets tech level)
research-speed = [Auto Research] __TECHNOLOGY__research-speed__ (signal value sets tech level)
toolbelt = [Auto Research] __TECHNOLOGY__toolbelt__ (signal value sets tech level)

This also leads me to a 2nd question:
Neither could I find a way to reference earlier localization in the same file, i.e:

Code: Select all

[auto-research]
signal_text_append = (signal value sets tech level)

[virtual-signal-name]
grenade-damage = [Auto Research] __TECHNOLOGY__grenade-damage__ __auto-reseach.signal_text_append__
research-speed = [Auto Research] __TECHNOLOGY__research-speed__ __auto-reseach.signal_text_append__
toolbelt = [Auto Research] __TECHNOLOGY__toolbelt__ __auto-reseach.signal_text_append__

Is this possible, or is it necessary to duplicate the localization from the base game?

[virtual-signal-name]
grenade-damage = [Auto Research] __1__ __2__
research-speed = [Auto Research] __1__ __2__
toolbelt = [Auto Research] __1__2__ __3__

canidae wrote:Thanks for your reply, but I don't think that'll help me. I'm not printing it out to the console and don't supply the localization strings with parameters (i.e. the __1__, __2__, etc).
The localization is used by extended data:

Code: Select all

data:extend({
    {
        type = "virtual-signal",
        name = "grenade-damage",
        icon = "__auto-research__/graphics/icons/signal/grenade-damage.png",
        subgroup = "virtual-signal-number",
        order = "r[auto-research]-[01]"
    }
}

[virtual-signal-name]
grenade-damage = [Auto Research] Grenade damage (signal value sets tech level)
research-speed = [Auto Research] Research speed (signal value sets tech level)
toolbelt = [Auto Research] Toolbelt (signal value sets tech level)

aubergine18 wrote:I'm pretty sure there's a way to do it, but I can't remember the mod where I saw it done.

Localisation strings are nestable, both in suff from control.lua and, to a lesser extent, from prototype definitions and even .cfg files. A good example in .cfg files is the __CONTROL__ keyword.

It looks like the main issue canidae is having is determining which keyword to use. I'll have hunt through my mods folder (it's got over 200 mods in it, so I may be some time)...

aubergine18 wrote:@canidae did you ever find a solution for this?

Code: Select all

my-thing = __some-group.some-name__

It's possible that a mod name is needed, for example:

Code: Select all

my-thing = __ModName__some-group.some.name__

I've not had chance to test any of this yet, but might be worth a try if you have time.

grenade-damage = [Auto Research] Grenade damage __auto-research.signal_append__
grenade-damage = [Auto Research] Grenade damage __auto-research__auto-research.signal_append__
grenade-damage = [Auto Research] Grenade damage __auto-research.auto-research.signal_append__
grenade-damage = [Auto Research] Grenade damage __auto-research__.auto-research.signal_append__

aubergine18 wrote:But what if you want to use existing locale keys from, say, an entity description (rather than a GUI caption)?

{"entity-description.(entity name)"}

aubergine18 wrote:If setting the caption of a GUI element, yes. But what about setting the description of the entity itself, or item, etc. Those are defined in data.lua, not control.lua.

Mooncat wrote:Hi all,

How about the "localised_name" property? I know it is in entity prototype, item prototype and recipe prototype, but haven't tried it on virtual signal prototype myself.

prefix = [Auto Research] __1__
...
signal_text = __1__ (signal value sets tech level, tech will be deprioritized if value is set to 0)

    {
        type = "virtual-signal",
        name = "grenade-damage",
        localised_name = {"auto-research.prefix", {"auto-research.signal_text", {"technology-name.grenade-damage"}}},
        icon = "__auto-research__/graphics/icons/signal/grenade-damage.png",
        subgroup = "virtual-signal-auto-research",
        order = "g[auto-research]"
    },

aubergine18 wrote:Oh wow I didn't realise localised_name could be used in prototype definitions like that. Completely misread Mooncat's earlier comment.

Looking at data.raw it's only used one single time for "dummy-selection-tool" prototype. Great find!

@canidae: Does it change the name or description of the signal? Or something else? (I assume description)