You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just an idea about item naming that could reduce the number of lines in the translation file.
Some blocks, for example the new chests, barrels, tool rack, fence and fence door could be named "Chest", "Barrel"... etc. and have their wood type in tooltip, as it is done with the dirt and sand. We would only need 1 line for every 17 type of wood and 1 line for each item.
I'm including chest in this idea as I don't remember seeing them in the localization file yet.
For example, if we do it for 5 items, it would require 22 lines instead of 85.
Items could still be searched by their material name in creative menu (you can find dirt and sand by searching stone names). I guess it would also work in NEI.
It mostly simplify the translation job, and it does not hurt gameplay. After that it's only a question of do you prefer items like "Oak Barrel" or just "Barrel"
The text was updated successfully, but these errors were encountered:
Just an idea about item naming that could reduce the number of lines in the translation file.
Some blocks, for example the new chests, barrels, tool rack, fence and fence door could be named "Chest", "Barrel"... etc. and have their wood type in tooltip, as it is done with the dirt and sand. We would only need 1 line for every 17 type of wood and 1 line for each item.
I'm including chest in this idea as I don't remember seeing them in the localization file yet.
For example, if we do it for 5 items, it would require 22 lines instead of 85.
Items could still be searched by their material name in creative menu (you can find dirt and sand by searching stone names). I guess it would also work in NEI.
It mostly simplify the translation job, and it does not hurt gameplay. After that it's only a question of do you prefer items like "Oak Barrel" or just "Barrel"
The text was updated successfully, but these errors were encountered: