If the plugin at right is meant to be a standalone translated version, then everything here is correct. It's the same plugin, with only the name fields altered. The two leading characters of the FormID are the mod's index in the load order, not a difference in the FormID itself.
You can rename the localised version as "MK18.esp" to avoid creating a duplicate set of weapons in your game if both plugins are enabled. Doing that would safely replace the original.
The alternative is to delete all the records in the localised plugin except for the weapon, object modification, and miscellaneous item records that have localised name fields, then add the original plugin as a master and flag the localised plugin as a .esl in the plugin header.
Yeah no clue. Running both plugins does not create duplicates of any kind, the strings have the same ID, just different translation and should work with a proper load order. Yet people claim that it does not and causes duplication or some other bs which I could not reproduce with what's available in the files.
I think this is a misunderstanding of the information presented and how plugins are separated and identified by filename than it is any indication of an actual error. The key thing to understand is that changing the plugin file name creates a wholly distinct plugin in your load order, even if all information in it is identical to the original version.
The FormID itself is dynamic according to the load order; although changing the plugin's position in your load order mid-game won't cause any problems (because the actual FormID is order-agnostic, and the first two characters are the dynamic part), if you want to create a localisation plugin, you either need to name it identically to the original version and replace the original, or copy the localised records into a new plugin with the original as its master, then compact the FormIDs of the localisation plugin and flag it as an ESL.
Having a second dependent and ESL-flagged plugin for localisation is better for compatibility and updates, as well, because you can simply pass changes from the updated master instead of having to remake the whole thing from scratch.
3 comments
If the plugin at right is meant to be a standalone translated version, then everything here is correct. It's the same plugin, with only the name fields altered. The two leading characters of the FormID are the mod's index in the load order, not a difference in the FormID itself.
You can rename the localised version as "MK18.esp" to avoid creating a duplicate set of weapons in your game if both plugins are enabled. Doing that would safely replace the original.
The alternative is to delete all the records in the localised plugin except for the weapon, object modification, and miscellaneous item records that have localised name fields, then add the original plugin as a master and flag the localised plugin as a .esl in the plugin header.
The FormID itself is dynamic according to the load order; although changing the plugin's position in your load order mid-game won't cause any problems (because the actual FormID is order-agnostic, and the first two characters are the dynamic part), if you want to create a localisation plugin, you either need to name it identically to the original version and replace the original, or copy the localised records into a new plugin with the original as its master, then compact the FormIDs of the localisation plugin and flag it as an ESL.
Having a second dependent and ESL-flagged plugin for localisation is better for compatibility and updates, as well, because you can simply pass changes from the updated master instead of having to remake the whole thing from scratch.