Language

the language file doesn't seem to translate everything is that supposed to be? I would like it to be complete so that it can be translated into German

35 minutes ago, Knusperkeks said:

the language file doesn't seem to translate everything is that supposed to be? I would like it to be complete so that it can be translated into German

Item display names can be translated in data files.

CustomNames_Resources for resources required for craft.
Blueprints for items crafted.

Changed Status from Pending to Not a Bug

15 hours ago, David said:

CustomNames_Resources for resources required for craft.
Blueprints for items crafted.

hi, first of all, thank you, I can't see how I can change the raw material names.. so that they are displayed in German. do you have an example?

2 hours ago, Knusperkeks said:

 

hi, first of all, thank you, I can't see how I can change the raw material names.. so that they are displayed in German. do you have an example?

oxide/data/craftmenu/CustomNames_Resources.json

Can't I also make a long file CraftMenu.json and put it in .../oxide/lang/de

{
  "metal.refined": "HQM",
  "metal.fragments": "Metallfragmente"
  "propanetank": "Propangas Tank",
  "metalpipe": "Metallrohr",
  "wiretool": "Kabel"
}

So I managed it that way, I only had to write the items in the "CraftMenu.cs" because otherwise they would not have been accepted. I added the most important ones to nmun and fixed the metal.pipe error at the same time.

CraftMenu.cs nachtrag

                ["cloth"] = "Cloth",
		["gears"] = "Gears",
                ["gunpowder"] = "Gun Powder",
                ["lowgradefuel"] = "Low Grade Fuel",
                ["metal.refined"] = "HQM",
                ["metal.fragments"] = "Metallfragmente",
                ["metalpipe"] = "Pipes",
                ["propanetank"] = "Propane Tank",
                ["carburetor3"] = "High Quality Carburetor",
                ["riflebody"] = "Rifle Body",
                ["semibody"] = "Semi Automatic Body",
                ["rope"] = "Rope",
                ["sewingkit"] = "Sewingkit",
                ["tarp"] = "Tarp",
                ["targeting.computer"] = "Targeting Computer",
                ["techparts"] = "Tech Trash",
                ["wiretool"] = "Wires",
                ["wood"] = "Wood",

.../oxide/lang/de

{
  "gears": "Zahnräder",
  "metal.refined": "HQM",
  "propanetank": "Propangas Tank",
  "metalpipe": "Metallrohr",
  "wiretool": "Kabel",
  "metal.fragments": "Metallfragmente",
  "cloth": "Stoff",
  "gunpowder": "Schießpulver",
  "lowgradefuel": "Einfacher Kraftstoff",
  "carburetor3": "Hochwertiger Vergaser",
  "riflebody": "Gewehrgehäuse",
  "semibody": "Halbautomatisches Gewehrgehäuse",
  "rope": "Seil",
  "sewingkit": "Nähzeug Set",
  "tarp": "Plane",
  "targeting.computer": "Zielcomputer",
  "techparts": "Technikschrott",
  "wood": "Holz"
}

CraftMenu.json

ops ok  i thought only the team would see the support ticket

1 hour ago, Knusperkeks said:

Can't I also make a long file CraftMenu.json and put it in .../oxide/lang/de

By the time I was making this plugin I didnt realized that lang file can be used to add more messages so scraped whole Lang thing in 1.0.8 version and replaced it with additional data file where you can add items.

I'm assuming you using 1.0.4 version currently which still has old Lang option. You can keep using that version and you will be just fine. Also I'm glad to hear that you figured out how to add lang messages by yourself. 

I bought it yesterday and loaded it using the download button, but strangely enough, it's 1.0.42..... Nothing significant has changed up to 1.0.9, as I can see in the update log, so it really shouldn't be relevant, but I personally find the possibility of the long file actually better and cleaner