Hello! I noticed that several items use the same names as the base game and have the same appearances...

I would like to suggest that you reuse the names of these items from the base game, instead of making these names fixed in a new .cfg file. This can be done through a .lua file, passing all the items that have the same default names from the game. This change will cause the game to load appropriate translations according to the player's interface language, reducing the work if you intend to add more similar items.

This will also clean up your .cfg file significantly, leaving the existing translations there more specific to the "new" content.

What are you referring to? All my content is new materials or tweaked machines that run differently. Are you talking about recipes?

Sorry for the confusion, I'm referring to the names of some items, which are similar to the standard names in the game. It's possible to use their own names, referencing the game items instead of writing each item's name again.

Despite being custom items, starting with "foliax-" on .cfg file, for example,
you can write as foliax-cargo-wagon=__ENTITY__cargo-wagon__ instead of foliax-cargo-wagon=Cargo wagon

This will force the game to use the name of the entity/item already present on the base game, according to the game's language, facilitating later localization.

With this change, any item you add will only require you to reference the item's internal name in the base game, if the item has the same name... instead of rewriting it and having to proofread for typos. In return for the extra work, this change will also allow the game to use the interface language for modifications, preventing your mod from being locked into English only.

It can be adapted to other languages ​​without changes, but this modification would benefit everyone, making things much easier since all these items would already be translated by the game engine itself :)

Regarding the .lua file, it's not necessary; the only thing that needs to be modified, if this suggestion is to be followed, is the .cfg file, including the correct references and their names.