https://minetweaker3.aizistral.com/api.php?action=feedcontributions&feedformat=atom&user=AizistralMineTweaker3 Wiki - User contributions [en]2026-05-08T16:30:04ZUser contributionsMediaWiki 1.24.0https://minetweaker3.aizistral.com/index.php?title=Main_Page&diff=1501Main Page2025-08-26T22:54:17Z<p>Aizistral: Update preface</p>
<hr />
<div>= Preface =<br />
This is a functional backup of the '''MineTweaker 3 Wiki''' formerly hosted at https://minetweaker3.powerofbytes.com. It is maintained by '''[https://aizistral.com Aizistral]'''.<br />
<br />
As it happens, shortly before the original wiki went down I have made a dump of its contents using the '''[https://github.com/WikiTeam/wikiteam WikiTeam]''' tool. You can download the dump itself from here: https://files.aizistral.com/random/MineTweaker3-Wiki-Dump.zip<br />
<br />
The purpose of this backup is purely archival. It will not be updated with new content or altered in any way, save for adding this preface. For that reason public editing access and account creation is disabled.<br />
<br />
If you have any questions, or find that some part of this wiki is broken - feel free to reach out to me directly at '''[mailto:admin@aizistral.com admin@aizistral.com]'''.<br />
<br />
== MineTweaker3 ==<br />
<br />
Welcome to the MineTweaker 3 wiki! The aim of MineTweaker is to provide modpack creators, server administrators and map makers with the capability of customizing Minecraft without having to write a custom mod for it. All functionality is provided through an easy-to-use scripting language. (no prior knowledge or programming experience required!)<br />
<br />
Using MineTweaker, you can...<br />
* Add and remove any crafting recipe<br />
* Add and remove mod machine recipes for supported mods<br />
* Modify the ore dictionary<br />
<br />
Additionally, all scripts are sent from server to client, and thus only need to be stored server-side. They can be altered and reloaded without having to restart anything.<br />
<br />
Forge Mods can also execute scripts in MineTweaker. [[Mod Script Execution]]<br />
<br />
== Comparison with MineTweaker 2 ==<br />
<br />
* [[guide:Comparison_with_MineTweaker_2|Comparison with MineTweaker 2]]<br />
<br />
== Tutorials (1.7.X) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:Item_Renaming|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures|Loops]]<br />
* Lesson 10: [[tutorial:Localization|Localization]]<br />
<br />
== Tutorials (1.6.4) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes_164|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary_164|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace_164|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes_164|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:item_Renaming_164|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips_164|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot_164|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures_164|Loops]]<br />
* Lesson 10: [[tutorial:Localization_164|Localization]]<br />
<br />
== Guides ==<br />
<br />
* [[guide:Script_Introduction|Script Introduction]]<br />
* [[guide:Script_Statements|Script Statements]]<br />
* [[guide:Script_Expression|Script Expressions]]<br />
* [[guide:Script_Function|Script Functions]]<br />
<br />
== Mod Support ==<br />
<br />
* BetterStorage: [[Mods:BetterStorage|BetterStorage Support]]<br />
* Blood Magic: [[Mods:Blood Magic Support|Blood Magic Support]]<br />
* BuildCraft: [[mods:BuildCraft_Support|BuildCraft Support]]<br />
* GregTech: [[mods:GregTech_Support|GregTech Support]]<br />
* Harvest Festival: [[Mods:Harvest Festival Support|Harvest Festival Support]]<br />
* IC2: [[mods:IC2_Support|IC2 Support]]<br />
* Immersive Engineering: [[mods:Immersive_Engineering_Support|Immersive Engineering Support]]<br />
* Magneticraft: [[mods:Magneticraft_Support|Magneticraft Support]]<br />
* MineFactory Reloaded: [[mods:MFR Support|MFR Support]]<br />
* NEI: [[mods:NEI_Support|NEI Support]]<br />
* Tinkers' Steelworks: [[mods:TSteelworks_Support|Tinkers' Steelworks Support]]<br />
* Witching Gadgets: [[mods:Witching_Gadgets_Support|Witching Gadgets Support]]<br />
<br />
* Additional Support: [[ModTweaker|ModTweaker]]<br />
<br />
* Additional Content: [[ContentTweaker|ContentTweaker]]<br />
<br />
== Known incompatibilities ==<br />
<br />
* CraftingManager isn't compatible - crafting recipes can't load properly upon starting a game. (A manual reload does fix this, though, but it's not very practical)<br />
* Some of the Sync recipes don't get modified properly. A manual reload fixes this. The issue is most likely due to Sync changing its own recipes depending on the server configuration, after MineTweaker did its work.<br />
<br />
If you encounter any other incompatibilities, let me know, so I can add them to the list and save modpack authors a lot of time.<br />
<br />
Although these mods should be compatible, it is not allowed to change RotaryCraft, ReactorCraft, ElectriCraft and ChromatiCraft recipes, or add recipes that modify the tech tree. The mod author, Reika, has explicitly stated that such modifications are forbidden.<br />
<br />
== References ==<br />
<br />
The following wiki pages provide useful references:<br />
<br />
* [[NBT Tag formats]]<br />
<br />
== Extending MineTweaker ==<br />
<br />
More than ever before, you can extend MineTweaker with your own functionality.<br />
<br />
There are various things you can do:<br />
<br />
* You can register global variables with minetweaker.MineTweakerAPI.registerGlobalSymbol(IZenSymbol). Use MineTweakerAPI.getJavaStaticGetterSymbol to get a static getter symbol or MineTweakerAPI.getJavaStaticFieldSymbol to get a static field symbol.<br />
* You can register bracket handlers with minetweaker.MineTweakerAPI.registerBracketHandler(IBracketHandler). Bracket handlers can make it possible to create your own namespace for items/things in specific mods. See the minetweaker.mc17.brackets for example implementations.<br />
* You can register custom classes with minetweaker.MineTweakerAPI.registerClass. Classes must have either a @ZenClass or @ZenExpansion annotation. Classes can be imported and called (handy for mod machines) and expansions can extend existing types (see minetweaker.data for examples, as well as minetweaker.item.IItemStack)<br />
* In large projects, you can use the gradle RegisterZenClassesTask (see GitHub source in buildSrc) to generate a class containing a list of all registerable classes in your project. You can then submit the class name to MineTweakerAPI to make it register all those classes. All MineTweaker subproject use this system, so read those gradle build scripts to see how it's done. (or contact me)<br />
<br />
== Changelog & Planned Versions ==<br />
<br />
[[Changelog]]<br />
<br />
[[Planned_Versions|Planned Versions]]<br />
<br />
== Credits ==<br />
<br />
Me (Stan Hebben) as mod creator. Thanks to Jaredlll08 for helping me fix bugs and get that 1.8 version going!<br />
<br />
All those who reported bugs on GitHub, for otherwise I'd not be able to fix them.<br />
<br />
The beta testers: Ravin6666, Peach774, AnodeCathode, Dyonovan, Joshiejack</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Main_Page&diff=1500Main Page2025-08-26T22:28:51Z<p>Aizistral: Add preface</p>
<hr />
<div>= Preface =<br />
This is a functional backup of a '''MineTweaker 3 Wiki''' formerly hosted at https://minetweaker3.powerofbytes.com. It is maintained by '''[https://aizistral.com Aizistral]'''.<br />
<br />
As it happens, shortly before the original wiki went down I have made a dump of its contents using the '''[https://github.com/WikiTeam/wikiteam WikiTeam]''' tool. You can download the dump itself from here: https://files.aizistral.com/random/MineTweaker3-Wiki-Dump.zip<br />
<br />
The purpose of this backup is purely archival. It will not be updated with new content or altered in any way, save for adding this preface. For that reason public editing access and account creation is disabled.<br />
<br />
In the event that you have any questions, or find that some part of this wiki is broken - feel free to reach out to me directly at '''[mailto:admin@aizistral.com admin@aizistral.com]'''.<br />
<br />
== MineTweaker3 ==<br />
<br />
Welcome to the MineTweaker 3 wiki! The aim of MineTweaker is to provide modpack creators, server administrators and map makers with the capability of customizing Minecraft without having to write a custom mod for it. All functionality is provided through an easy-to-use scripting language. (no prior knowledge or programming experience required!)<br />
<br />
Using MineTweaker, you can...<br />
* Add and remove any crafting recipe<br />
* Add and remove mod machine recipes for supported mods<br />
* Modify the ore dictionary<br />
<br />
Additionally, all scripts are sent from server to client, and thus only need to be stored server-side. They can be altered and reloaded without having to restart anything.<br />
<br />
Forge Mods can also execute scripts in MineTweaker. [[Mod Script Execution]]<br />
<br />
== Comparison with MineTweaker 2 ==<br />
<br />
* [[guide:Comparison_with_MineTweaker_2|Comparison with MineTweaker 2]]<br />
<br />
== Tutorials (1.7.X) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:Item_Renaming|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures|Loops]]<br />
* Lesson 10: [[tutorial:Localization|Localization]]<br />
<br />
== Tutorials (1.6.4) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes_164|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary_164|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace_164|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes_164|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:item_Renaming_164|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips_164|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot_164|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures_164|Loops]]<br />
* Lesson 10: [[tutorial:Localization_164|Localization]]<br />
<br />
== Guides ==<br />
<br />
* [[guide:Script_Introduction|Script Introduction]]<br />
* [[guide:Script_Statements|Script Statements]]<br />
* [[guide:Script_Expression|Script Expressions]]<br />
* [[guide:Script_Function|Script Functions]]<br />
<br />
== Mod Support ==<br />
<br />
* BetterStorage: [[Mods:BetterStorage|BetterStorage Support]]<br />
* Blood Magic: [[Mods:Blood Magic Support|Blood Magic Support]]<br />
* BuildCraft: [[mods:BuildCraft_Support|BuildCraft Support]]<br />
* GregTech: [[mods:GregTech_Support|GregTech Support]]<br />
* Harvest Festival: [[Mods:Harvest Festival Support|Harvest Festival Support]]<br />
* IC2: [[mods:IC2_Support|IC2 Support]]<br />
* Immersive Engineering: [[mods:Immersive_Engineering_Support|Immersive Engineering Support]]<br />
* Magneticraft: [[mods:Magneticraft_Support|Magneticraft Support]]<br />
* MineFactory Reloaded: [[mods:MFR Support|MFR Support]]<br />
* NEI: [[mods:NEI_Support|NEI Support]]<br />
* Tinkers' Steelworks: [[mods:TSteelworks_Support|Tinkers' Steelworks Support]]<br />
* Witching Gadgets: [[mods:Witching_Gadgets_Support|Witching Gadgets Support]]<br />
<br />
* Additional Support: [[ModTweaker|ModTweaker]]<br />
<br />
* Additional Content: [[ContentTweaker|ContentTweaker]]<br />
<br />
== Known incompatibilities ==<br />
<br />
* CraftingManager isn't compatible - crafting recipes can't load properly upon starting a game. (A manual reload does fix this, though, but it's not very practical)<br />
* Some of the Sync recipes don't get modified properly. A manual reload fixes this. The issue is most likely due to Sync changing its own recipes depending on the server configuration, after MineTweaker did its work.<br />
<br />
If you encounter any other incompatibilities, let me know, so I can add them to the list and save modpack authors a lot of time.<br />
<br />
Although these mods should be compatible, it is not allowed to change RotaryCraft, ReactorCraft, ElectriCraft and ChromatiCraft recipes, or add recipes that modify the tech tree. The mod author, Reika, has explicitly stated that such modifications are forbidden.<br />
<br />
== References ==<br />
<br />
The following wiki pages provide useful references:<br />
<br />
* [[NBT Tag formats]]<br />
<br />
== Extending MineTweaker ==<br />
<br />
More than ever before, you can extend MineTweaker with your own functionality.<br />
<br />
There are various things you can do:<br />
<br />
* You can register global variables with minetweaker.MineTweakerAPI.registerGlobalSymbol(IZenSymbol). Use MineTweakerAPI.getJavaStaticGetterSymbol to get a static getter symbol or MineTweakerAPI.getJavaStaticFieldSymbol to get a static field symbol.<br />
* You can register bracket handlers with minetweaker.MineTweakerAPI.registerBracketHandler(IBracketHandler). Bracket handlers can make it possible to create your own namespace for items/things in specific mods. See the minetweaker.mc17.brackets for example implementations.<br />
* You can register custom classes with minetweaker.MineTweakerAPI.registerClass. Classes must have either a @ZenClass or @ZenExpansion annotation. Classes can be imported and called (handy for mod machines) and expansions can extend existing types (see minetweaker.data for examples, as well as minetweaker.item.IItemStack)<br />
* In large projects, you can use the gradle RegisterZenClassesTask (see GitHub source in buildSrc) to generate a class containing a list of all registerable classes in your project. You can then submit the class name to MineTweakerAPI to make it register all those classes. All MineTweaker subproject use this system, so read those gradle build scripts to see how it's done. (or contact me)<br />
<br />
== Changelog & Planned Versions ==<br />
<br />
[[Changelog]]<br />
<br />
[[Planned_Versions|Planned Versions]]<br />
<br />
== Credits ==<br />
<br />
Me (Stan Hebben) as mod creator. Thanks to Jaredlll08 for helping me fix bugs and get that 1.8 version going!<br />
<br />
All those who reported bugs on GitHub, for otherwise I'd not be able to fix them.<br />
<br />
The beta testers: Ravin6666, Peach774, AnodeCathode, Dyonovan, Joshiejack</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Recipe_leggings_iron_brackets.png&diff=1498File:Recipe leggings iron brackets.png2025-08-21T00:44:30Z<p>Aizistral: Aizistral uploaded File:Recipe leggings iron brackets.png</p>
<hr />
<div>Leggings recipe in bracket notation.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Recipe_leggings_iron.png&diff=1497File:Recipe leggings iron.png2025-08-21T00:44:06Z<p>Aizistral: Aizistral uploaded File:Recipe leggings iron.png</p>
<hr />
<div>Iron leggings recipe</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Grammar_scriptelement.png&diff=1496File:Grammar scriptelement.png2025-08-21T00:41:12Z<p>Aizistral: Created blank page</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Grammar_importedscript.png&diff=1495File:Grammar importedscript.png2025-08-21T00:41:02Z<p>Aizistral: Created blank page</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Grammar_script.png&diff=1494File:Grammar script.png2025-08-21T00:39:25Z<p>Aizistral: Created blank page</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:ContentTweakerLogo.jpg&diff=1493File:ContentTweakerLogo.jpg2025-08-21T00:38:42Z<p>Aizistral: Aizistral uploaded File:ContentTweakerLogo.jpg</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:ModTweaker_logo.png&diff=1492File:ModTweaker logo.png2025-08-21T00:37:24Z<p>Aizistral: Aizistral uploaded File:ModTweaker logo.png</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Main_Page&diff=1491Main Page2025-08-21T00:22:27Z<p>Aizistral: Revert to older revision</p>
<hr />
<div>= MineTweaker3 =<br />
<br />
Welcome to the MineTweaker 3 wiki! The aim of MineTweaker is to provide modpack creators, server administrators and map makers with the capability of customizing Minecraft without having to write a custom mod for it. All functionality is provided through an easy-to-use scripting language. (no prior knowledge or programming experience required!)<br />
<br />
Using MineTweaker, you can...<br />
* Add and remove any crafting recipe<br />
* Add and remove mod machine recipes for supported mods<br />
* Modify the ore dictionary<br />
<br />
Additionally, all scripts are sent from server to client, and thus only need to be stored server-side. They can be altered and reloaded without having to restart anything.<br />
<br />
Forge Mods can also execute scripts in MineTweaker. [[Mod Script Execution]]<br />
<br />
== Comparison with MineTweaker 2 ==<br />
<br />
* [[guide:Comparison_with_MineTweaker_2|Comparison with MineTweaker 2]]<br />
<br />
== Tutorials (1.7.X) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:Item_Renaming|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures|Loops]]<br />
* Lesson 10: [[tutorial:Localization|Localization]]<br />
<br />
== Tutorials (1.6.4) ==<br />
<br />
* Lesson 1: [[tutorial:Introduction|Introduction]]<br />
* Lesson 2: [[tutorial:Basic_Recipes_164|Basic Recipes]]<br />
* Lesson 3: [[tutorial:Ore_Dictionary_164|Ore Dictionary]]<br />
* Lesson 4: [[tutorial:Furnace_164|Furnace]]<br />
* Lesson 5: [[tutorial:Advanced_Recipes_164|Advanced Recipes]]<br />
* Lesson 6: [[tutorial:item_Renaming_164|Item Renaming]]<br />
* Lesson 7: [[tutorial:Tooltips_164|Tooltips]]<br />
* Lesson 8: [[tutorial:Loot_164|Loot and seeds]]<br />
* Lesson 9: [[tutorial:Control_Structures_164|Loops]]<br />
* Lesson 10: [[tutorial:Localization_164|Localization]]<br />
<br />
== Guides ==<br />
<br />
* [[guide:Script_Introduction|Script Introduction]]<br />
* [[guide:Script_Statements|Script Statements]]<br />
* [[guide:Script_Expression|Script Expressions]]<br />
* [[guide:Script_Function|Script Functions]]<br />
<br />
== Mod Support ==<br />
<br />
* BetterStorage: [[Mods:BetterStorage|BetterStorage Support]]<br />
* Blood Magic: [[Mods:Blood Magic Support|Blood Magic Support]]<br />
* BuildCraft: [[mods:BuildCraft_Support|BuildCraft Support]]<br />
* GregTech: [[mods:GregTech_Support|GregTech Support]]<br />
* Harvest Festival: [[Mods:Harvest Festival Support|Harvest Festival Support]]<br />
* IC2: [[mods:IC2_Support|IC2 Support]]<br />
* Immersive Engineering: [[mods:Immersive_Engineering_Support|Immersive Engineering Support]]<br />
* Magneticraft: [[mods:Magneticraft_Support|Magneticraft Support]]<br />
* MineFactory Reloaded: [[mods:MFR Support|MFR Support]]<br />
* NEI: [[mods:NEI_Support|NEI Support]]<br />
* Tinkers' Steelworks: [[mods:TSteelworks_Support|Tinkers' Steelworks Support]]<br />
* Witching Gadgets: [[mods:Witching_Gadgets_Support|Witching Gadgets Support]]<br />
<br />
* Additional Support: [[ModTweaker|ModTweaker]]<br />
<br />
* Additional Content: [[ContentTweaker|ContentTweaker]]<br />
<br />
== Known incompatibilities ==<br />
<br />
* CraftingManager isn't compatible - crafting recipes can't load properly upon starting a game. (A manual reload does fix this, though, but it's not very practical)<br />
* Some of the Sync recipes don't get modified properly. A manual reload fixes this. The issue is most likely due to Sync changing its own recipes depending on the server configuration, after MineTweaker did its work.<br />
<br />
If you encounter any other incompatibilities, let me know, so I can add them to the list and save modpack authors a lot of time.<br />
<br />
Although these mods should be compatible, it is not allowed to change RotaryCraft, ReactorCraft, ElectriCraft and ChromatiCraft recipes, or add recipes that modify the tech tree. The mod author, Reika, has explicitly stated that such modifications are forbidden.<br />
<br />
== References ==<br />
<br />
The following wiki pages provide useful references:<br />
<br />
* [[NBT Tag formats]]<br />
<br />
== Extending MineTweaker ==<br />
<br />
More than ever before, you can extend MineTweaker with your own functionality.<br />
<br />
There are various things you can do:<br />
<br />
* You can register global variables with minetweaker.MineTweakerAPI.registerGlobalSymbol(IZenSymbol). Use MineTweakerAPI.getJavaStaticGetterSymbol to get a static getter symbol or MineTweakerAPI.getJavaStaticFieldSymbol to get a static field symbol.<br />
* You can register bracket handlers with minetweaker.MineTweakerAPI.registerBracketHandler(IBracketHandler). Bracket handlers can make it possible to create your own namespace for items/things in specific mods. See the minetweaker.mc17.brackets for example implementations.<br />
* You can register custom classes with minetweaker.MineTweakerAPI.registerClass. Classes must have either a @ZenClass or @ZenExpansion annotation. Classes can be imported and called (handy for mod machines) and expansions can extend existing types (see minetweaker.data for examples, as well as minetweaker.item.IItemStack)<br />
* In large projects, you can use the gradle RegisterZenClassesTask (see GitHub source in buildSrc) to generate a class containing a list of all registerable classes in your project. You can then submit the class name to MineTweakerAPI to make it register all those classes. All MineTweaker subproject use this system, so read those gradle build scripts to see how it's done. (or contact me)<br />
<br />
== Changelog & Planned Versions ==<br />
<br />
[[Changelog]]<br />
<br />
[[Planned_Versions|Planned Versions]]<br />
<br />
== Credits ==<br />
<br />
Me (Stan Hebben) as mod creator. Thanks to Jaredlll08 for helping me fix bugs and get that 1.8 version going!<br />
<br />
All those who reported bugs on GitHub, for otherwise I'd not be able to fix them.<br />
<br />
The beta testers: Ravin6666, Peach774, AnodeCathode, Dyonovan, Joshiejack</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:Mod&diff=1431Template:Mod2025-08-21T00:17:40Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>{{infobox<br />
| bodyclass = geography vcard<br />
| bodystyle = width:23em<br />
<br />
| headerstyle = text-align:left<br />
<br />
| abovestyle = font-size:1.25em; white-space:nowrap<br />
| above = <span class="fn org">{{#if:{{{name|}}}|{{{name}}}|{{#if:{{{official_name|}}}|{{{official_name}}}|{{PAGENAME}}}}}}</span>{{#if:{{{native_name|}}}|<br /><span class="nickname" {{#if:{{{native_name_lang|}}}|lang="{{{native_name_lang}}}"}}>{{{native_name}}}</span>}}{{#if:{{{other_name|}}}|<br /><span class="nickname" style="font-size:78%">{{{other_name}}}</span>}}<!--<br />
** names, type, and transliterations **<br />
-->{{infobox|child=yes|decat=yes<!-- Remove from [[Category:Articles which use infobox templates with no data rows]] --><br />
<br />
| subheaderstyle = background-color:#cddeff; font-weight:bold;<br />
| subheader = {{#if:{{both|{{{name|}}}{{{official_name|}}}|{{{settlement_type|{{{type|}}}}}}}}|<span class="category">{{{settlement_type|{{{type}}}}}}</span>}}<br />
<br />
| rowclass1 = mergedtoprow<br />
| header1 = {{#if:{{{name|}}}|{{{official_name|}}}}}<br />
<br />
| rowclass2 = mergedtoprow<br />
| header2 = {{#if:{{{translit_lang1|}}}|{{{translit_lang1}}}&nbsp;transcription(s)<!-- <br />
***Transliteration language 1*** <br />
-->{{infobox|child=yes<br />
|rowclass1 = {{#if:{{{translit_lang1_type1|}}}|mergedrow|mergedbottomrow}}<br />
|label1 = &nbsp;•&nbsp;{{{translit_lang1_type}}}<br />
|data1 = {{#if:{{{translit_lang1_type|}}}|{{{translit_lang1_info|}}}}}<br />
<br />
|rowclass2 = {{#if:{{{translit_lang1_type2|}}}|mergedrow|mergedbottomrow}}<br />
|label2 = &nbsp;•&nbsp;{{{translit_lang1_type1}}}<br />
|data2 = {{#if:{{{translit_lang1_type1|}}}|{{{translit_lang1_info1|}}}}}<br />
<br />
|rowclass3 = {{#if:{{{translit_lang1_type3|}}}|mergedrow|mergedbottomrow}}<br />
|label3 =&nbsp;•&nbsp;{{{translit_lang1_type2}}}<br />
|data3 = {{#if:{{{translit_lang1_type2|}}}|{{{translit_lang1_info2|}}}}}<br />
<br />
|rowclass4 = {{#if:{{{translit_lang1_type4|}}}|mergedrow|mergedbottomrow}}<br />
|label4 = &nbsp;•&nbsp;{{{translit_lang1_type3}}}<br />
|data4 = {{#if:{{{translit_lang1_type3|}}}|{{{translit_lang1_info3|}}}}}<br />
<br />
|rowclass5 = {{#if:{{{translit_lang1_type5|}}}|mergedrow|mergedbottomrow}}<br />
|label5 = &nbsp;•&nbsp;{{{translit_lang1_type4}}}<br />
|data5 = {{#if:{{{translit_lang1_type4|}}}|{{{translit_lang1_info4|}}}}}<br />
<br />
|rowclass6 = {{#if:{{{translit_lang1_type6|}}}|mergedrow|mergedbottomrow}}<br />
|label6 = &nbsp;•&nbsp;{{{translit_lang1_type5}}}<br />
|data6 = {{#if:{{{translit_lang1_type5|}}}|{{{translit_lang1_info5|}}}}}<br />
<br />
|rowclass7 = mergedbottomrow<br />
|label7 = &nbsp;•&nbsp;{{{translit_lang1_type6}}}<br />
|data7 = {{#if:{{{translit_lang1_type6|}}}|{{{translit_lang1_info6|}}} }}<br />
}} }}<br />
<br />
| rowclass3 = mergedtoprow<br />
| header3 = {{#if:{{{translit_lang2|}}}|{{{translit_lang2}}}&nbsp;transcription(s)<!-- <br />
***Transliteration language 2*** <br />
-->{{infobox|child=yes<br />
|rowclass1 = {{#if:{{{translit_lang2_type1|}}}|mergedrow|mergedbottomrow}}<br />
|label1 = &nbsp;•&nbsp;{{{translit_lang2_type}}}<br />
|data1 = {{#if:{{{translit_lang2_type|}}}|{{{translit_lang2_info|}}}}}<br />
<br />
|rowclass2 = {{#if:{{{translit_lang2_type2|}}}|mergedrow|mergedbottomrow}}<br />
|label2 = &nbsp;•&nbsp;{{{translit_lang2_type1}}}<br />
|data2 = {{#if:{{{translit_lang2_type1|}}}|{{{translit_lang2_info1|}}}}}<br />
<br />
|rowclass3 = {{#if:{{{translit_lang2_type3|}}}|mergedrow|mergedbottomrow}}<br />
|label3 =&nbsp;•&nbsp;{{{translit_lang2_type2}}}<br />
|data3 = {{#if:{{{translit_lang2_type2|}}}|{{{translit_lang2_info2|}}}}}<br />
<br />
|rowclass4 = {{#if:{{{translit_lang2_type4|}}}|mergedrow|mergedbottomrow}}<br />
|label4 = &nbsp;•&nbsp;{{{translit_lang2_type3}}}<br />
|data4 = {{#if:{{{translit_lang2_type3|}}}|{{{translit_lang2_info3|}}}}}<br />
<br />
|rowclass5 = {{#if:{{{translit_lang2_type5|}}}|mergedrow|mergedbottomrow}}<br />
|label5 = &nbsp;•&nbsp;{{{translit_lang2_type4}}}<br />
|data5 = {{#if:{{{translit_lang2_type4|}}}|{{{translit_lang2_info4|}}}}}<br />
<br />
|rowclass6 = {{#if:{{{translit_lang2_type6|}}}|mergedrow|mergedbottomrow}}<br />
|label6 = &nbsp;•&nbsp;{{{translit_lang2_type5}}}<br />
|data6 = {{#if:{{{translit_lang2_type5|}}}|{{{translit_lang2_info5|}}}}}<br />
<br />
|rowclass7 = mergedbottomrow<br />
|label7 = &nbsp;•&nbsp;{{{translit_lang2_type6}}}<br />
|data7 = {{#if:{{{translit_lang2_type6|}}}|{{{translit_lang2_info6|}}} }}<br />
}} }}<br />
}}<!-- end ** names, type, and transliterations ** --><br />
<br />
<!-- ***Skyline Image*** --><br />
| imagestyle = padding:0.7em 0.8em<br />
| image = {{#if:{{{image_skyline|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_skyline}}}|size={{{imagesize|}}}|sizedefault=250px|alt={{{image_alt|}}}|title={{{image_caption|Skyline of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}}}}{{#if:{{{image_caption|}}}|<br /><small>{{{image_caption}}}</small>}}}}<br />
<br />
<!-- ***Other Image*** --><br />
| image2 = {{{image|}}}<br />
<br />
<!-- ***Flag, Seal, Shield and Coat of arms*** --><br />
| rowclass1 = mergedtoprow<br />
| class1 = maptable<br />
| data1 = {{#if:{{{image_flag|}}}{{{image_seal|}}}{{{image_shield|}}}{{{image_blank_emblem|}}}{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}<br />
|{{Infobox settlement/columns<br />
| 1 = {{#if:{{{image_flag|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_flag}}}|size={{{flag_size|}}}|sizedefault={{#if:{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}|85px|100px}}|border={{yesno |{{{flag_border|}}}|yes=yes|blank=yes}}|alt={{{flag_alt|}}}|title=Flag of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}<br /><small>'''{{Infobox settlement/link|type=Flag|link={{{flag_link|}}}|name={{{official_name}}}}}'''</small>}}<br />
| 2 = {{#if:{{{image_seal|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_seal|}}}|size={{{seal_size|}}}|sizedefault={{#if:{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}|85px|100px}}|alt={{{seal_alt|}}}|title=Official seal of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}<br /><small>'''{{Infobox settlement/link|type={{#if:{{{seal_type|}}}|{{{seal_type}}}|Seal}}|link={{{seal_link|}}}|name={{{official_name}}}}}'''</small>}}<br />
| 3 = {{#if:{{{image_shield|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_shield|}}}||size={{{shield_size|}}}|sizedefault={{#if:{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}|85px|100px}}|alt={{{shield_alt|}}}|title=Coat of arms of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}<br /><small>'''{{Infobox settlement/link|type=Coat of arms|link={{{shield_link|}}}|name={{{official_name}}}}}'''</small>}}<br />
| 4 = {{#if:{{{image_blank_emblem|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_blank_emblem|}}}|size={{{blank_emblem_size|}}}|sizedefault={{#if:{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}|85px|100px}}|alt={{{blank_emblem_alt|}}}|title=Official logo of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}<br /><small>'''{{Infobox settlement/link|type={{#if:{{{blank_emblem_type|}}}|{{{blank_emblem_type}}}|Logo}}|link={{{blank_emblem_link|}}}|name={{{official_name}}}}}'''</small>}}<br />
| 5 = {{#if:{{{image_map|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_map}}}|size={{{mapsize|}}}|sizedefault=100px|alt={{{map_alt|}}}|title={{{map_caption|Location of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}}}}{{#if:{{{map_caption|}}}|<br /><small>{{{map_caption}}}</small>}} }}<br />
| 0 = {{#if:{{{pushpin_map_narrow|}}}|{{#if:{{both| {{{pushpin_map|}}} | {{both|{{{latd|}}}|{{{longd|}}}}} }}|<br />
<center><br />
{{location map|{{{pushpin_map|}}}<br />
|border = none<br />
|alt = {{{pushpin_map_alt|}}}<br />
|caption =<br />
|float = none<br />
|width = {{#if:{{{pushpin_mapsize|}}}|{{{pushpin_mapsize}}}|150}}<br />
|default_width = 250<br />
|relief= {{{pushpin_relief|}}}<br />
|AlternativeMap = {{{pushpin_image|}}}<br />
|label = {{#ifeq: {{lc: {{{pushpin_label_position|}}} }} | none | | {{#if:{{{pushpin_label|}}}|{{{pushpin_label}}}|{{#if:{{{name|}}}|{{{name}}}|{{{official_name|}}}}}}} }}<br />
|lat = {{#if:{{{latm|}}}{{{latNS|}}}| |{{{latd|}}} }}<br />
|long = {{#if:{{{longm|}}}{{{longEW|}}}| |{{{longd|}}} }}<br />
|lat_deg={{#if:{{{latm|}}}{{{latNS|}}}|{{{latd|}}} }}<br />
|lat_min={{#if:{{{latm|}}}{{{latNS|}}}|{{{latm|}}} }}<br />
|lat_sec={{#if:{{{lats|}}}{{{latNS|}}}|{{{lats|}}} }}<br />
|lat_dir={{{latNS|}}}<br />
|lon_deg={{#if:{{{longm|}}}{{{longEW|}}}|{{{longd|}}} }}<br />
|lon_min={{#if:{{{longm|}}}{{{longEW|}}}|{{{longm|}}} }}<br />
|lon_sec={{#if:{{{longs|}}}{{{longEW|}}}|{{{longs|}}} }}<br />
|lon_dir={{{longEW|}}}<br />
|marksize =6<br />
|position = {{{pushpin_label_position|}}}<br />
}}{{#if:{{{pushpin_map_caption|}}}|<small>{{{pushpin_map_caption}}}</small>|{{#if:{{{map_caption|}}}|<small>{{{map_caption}}}</small>}}}}<br />
</center>}} }}<br />
}} }}<br />
<!-- ***Nickname*** --><br />
| rowclass2 = mergedrow<br />
| data2 = {{#if:{{{nickname|}}}|Nickname(s): <span class="nickname">{{{nickname}}}</span>}}<br />
<!-- ***Motto*** --><br />
| rowclass3 = mergedrow<br />
| data3 = {{#if:{{{motto|}}}|Motto: {{{motto}}} }}<br />
<!-- ***Anthem*** --><br />
| rowclass4 = mergedrow<br />
| data4 = {{#if:{{{anthem|}}}|Anthem: {{{anthem}}} }}<br />
<!-- ***Map*** --><br />
| rowclass5 = mergedrow<br />
| data5 = {{#if:{{both|{{{pushpin_map_narrow|}}}|{{{pushpin_map|}}}}}||{{#if:{{{image_map|}}}<br />
|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_map}}}|size={{{mapsize|}}}|sizedefault=250px|alt={{{map_alt|}}}|title={{{map_caption|Location of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}}}}{{#if:{{{map_caption|}}}|<br /><small>{{{map_caption}}}</small>}}<br />
}}}}<br />
| rowclass6 = mergedrow<br />
| data6 = {{#if:{{{image_map1|}}}|{{#invoke:InfoboxImage|InfoboxImage|image={{{image_map1}}}|size={{{mapsize1|}}}|sizedefault=250px|alt={{{map_alt1|}}}|title={{{map_caption1|Location of {{#if:{{{name|}}}|{{{name}}}|{{{official_name}}}}}}}}}}{{#if:{{{map_caption1|}}}|<br /><small>{{{map_caption1}}}</small>}} }}<br />
<br />
<!--***Dot Map*** --><br />
| rowclass7 = mergedrow<br />
| data7 = {{#if:{{{image_dot_map|}}}<br />
|<center>{{superimpose<br />
|base = {{{image_dot_map|}}}<br />
|base_width = {{{{{|safesubst:}}}#if:{{{dot_mapsize|}}}<br />
|{{{dot_mapsize}}}{{#iferror:{{#expr:{{{dot_mapsize}}}>0}}||px}}<br />
|180px}}<br />
|base_alt = {{{dot_map_base_alt|}}}<br />
|base_caption = {{#if:{{{official_name|}}}|{{{official_name|}}}|{{{name}}}}}<br />
|float = Red pog.svg<br />
|float_width = 6px<br />
|float_alt = {{{dot_map_alt|}}}<br />
|float_caption = {{{dot_map_caption|}}}<br />
|x = {{{dot_x|}}}<br />
|y = {{{dot_y|}}}<br />
}}{{#if:{{{dot_map_caption|}}}|<small>{{{dot_map_caption}}}</small>}}</center><br />
}}<br />
<br />
<!-- ***Pushpin Map*** --><br />
| rowclass8 = mergedtoprow<br />
| data8 = {{#if:{{{pushpin_map_narrow|}}}||{{#if:{{both| {{{pushpin_map|}}} | {{both|{{{latd|}}}|{{{longd|}}}}} }}|<br />
<center><br />
{{location map|{{{pushpin_map|}}}<br />
|border = none<br />
|alt = {{{pushpin_map_alt|}}}<br />
|caption =<br />
|float = none<br />
|width = {{{pushpin_mapsize|}}}<br />
|default_width = 250<br />
|relief= {{{pushpin_relief|}}}<br />
|AlternativeMap = {{{pushpin_image|}}}<br />
|label = {{#ifeq: {{lc: {{{pushpin_label_position|}}} }} | none | | {{#if:{{{pushpin_label|}}}|{{{pushpin_label}}}|{{#if:{{{name|}}}|{{{name}}}|{{{official_name|}}}}}}} }}<br />
|lat = {{#if:{{{latm|}}}{{{latNS|}}}| |{{{latd|}}} }}<br />
|long = {{#if:{{{longm|}}}{{{longEW|}}}| |{{{longd|}}} }}<br />
|lat_deg={{#if:{{{latm|}}}{{{latNS|}}}|{{{latd|}}} }}<br />
|lat_min={{#if:{{{latm|}}}{{{latNS|}}}|{{{latm|}}} }}<br />
|lat_sec={{#if:{{{lats|}}}{{{latNS|}}}|{{{lats|}}} }}<br />
|lat_dir={{{latNS|}}}<br />
|lon_deg={{#if:{{{longm|}}}{{{longEW|}}}|{{{longd|}}} }}<br />
|lon_min={{#if:{{{longm|}}}{{{longEW|}}}|{{{longm|}}} }}<br />
|lon_sec={{#if:{{{longs|}}}{{{longEW|}}}|{{{longs|}}} }}<br />
|lon_dir={{{longEW|}}}<br />
|marksize =6<br />
|position = {{{pushpin_label_position|}}}<br />
}}{{#if:{{{pushpin_map_caption|}}}|<small>{{{pushpin_map_caption}}}</small>|{{#if:{{{map_caption|}}}|<small>{{{map_caption}}}</small>}}}}<br />
</center>}} }}<br />
<br />
| rowclass9 = mergedrow<br />
| data9 = {{#if:{{both|{{{pushpin_map1|}}}|{{both|{{{latd|}}}|{{{longd|}}}}}}}|<br />
<center><br />
{{location map|{{{pushpin_map1|}}}<br />
|border = none<br />
|alt = {{{pushpin_map_alt1|}}}<br />
|caption =<br />
|float = none<br />
|width = {{{pushpin_mapsize1|}}}<br />
|default_width = 250<br />
|relief= {{{pushpin_relief1|}}}<br />
|AlternativeMap = {{{pushpin_image1|}}}<br />
|label = {{#ifeq: {{lc: {{{pushpin_label_position1|}}} }} | none | | {{#if:{{{pushpin_label1|}}}|{{{pushpin_label1}}}|{{#if:{{{name|}}}|{{{name}}}|{{{official_name|}}}}}}} }}<br />
|lat = {{#if:{{{latm|}}}{{{latNS|}}}| |{{{latd|}}} }}<br />
|long = {{#if:{{{longm|}}}{{{longEW|}}}| |{{{longd|}}} }}<br />
|lat_deg={{#if:{{{latm|}}}{{{latNS|}}}|{{{latd|}}} }}<br />
|lat_min={{#if:{{{latm|}}}{{{latNS|}}}|{{{latm|}}} }}<br />
|lat_sec={{#if:{{{lats|}}}{{{latNS|}}}|{{{lats|}}} }}<br />
|lat_dir={{{latNS|}}}<br />
|lon_deg={{#if:{{{longm|}}}{{{longEW|}}}|{{{longd|}}} }}<br />
|lon_min={{#if:{{{longm|}}}{{{longEW|}}}|{{{longm|}}} }}<br />
|lon_sec={{#if:{{{longs|}}}{{{longEW|}}}|{{{longs|}}} }}<br />
|lon_dir={{{longEW|}}}<br />
|marksize =6<br />
|position = {{{pushpin_label_position1|}}}<br />
}}{{#if:{{{pushpin_map_caption1|}}}|<small>{{{pushpin_map_caption1|}}}</small>|{{#if:{{{map_caption|}}}|<small>{{{map_caption}}}</small>}}}}<br />
</center><br />
}}<br />
<br />
<!-- ***Coordinates*** --><br />
| rowclass10 = mergedbottomrow<br />
| data10 = {{#if:{{both|{{{latd|}}}|{{{longd|}}}}}<br />
|Coordinates{{#if:{{{coor_pinpoint|{{{coor_type|}}}}}}|&#32;({{{coor_pinpoint|{{{coor_type|}}}}}})|}}: {{Geobox coor|{{{latd|}}}|{{{latm|}}}|{{{lats|}}}|{{{latNS|}}}|{{{longd|}}}|{{{longm|}}}|{{{longs|}}}|{{{longEW|}}}|{{#if:{{{coordinates_type|}}}|{{{coordinates_type}}}|type:city{{#if:{{{population_total|}}}|{{#iferror:{{#expr:{{formatnum:{{{population_total}}}|R}}+1}}||({{formatnum:{{{population_total}}}|R}})}}|}}{{#if:{{{coordinates_region|}}}|_region:{{{coordinates_region}}}|{{#if:{{{subdivision_name|}}}|_region:{{CountryAbbr|{{{subdivision_name|}}}|{{{subdivision_name1|}}} }} }} }} }}|{{#ifeq:{{{coordinates_display|}}}|inline|μ|{{#if:{{{coordinates_display|}}}|title|μ}}}}={{{coordinates_display|}}}|{{#if:{{{coordinates_format|}}}|format|μ}}={{{coordinates_format|}}}}}{{{coordinates_footnotes|}}}<br />
}}<br />
<br />
<!-- ***Subdivisions*** --><br />
| rowclass11 = mergedtoprow<br />
| label11 = {{{subdivision_type}}}<br />
| data11 = {{#if:{{{subdivision_type|}}}|{{{subdivision_name|}}} }}<br />
<br />
| rowclass12 = mergedrow<br />
| label12 = {{{subdivision_type1}}}<br />
| data12 = {{#if:{{{subdivision_type1|}}}|{{{subdivision_name1|}}} }}<br />
<br />
| rowclass13 = mergedrow<br />
| label13 = {{{subdivision_type2}}}<br />
| data13 = {{#if:{{{subdivision_type2|}}}|{{{subdivision_name2|}}} }}<br />
<br />
| rowclass14 = mergedrow<br />
| label14 = {{{subdivision_type3}}}<br />
| data14 = {{#if:{{{subdivision_type3|}}}|{{{subdivision_name3|}}} }}<br />
<br />
| rowclass15 = mergedrow<br />
| label15 = {{{subdivision_type4}}}<br />
| data15 = {{#if:{{{subdivision_type4|}}}|{{{subdivision_name4|}}} }}<br />
<br />
| rowclass16 = mergedrow<br />
| label16 = {{{subdivision_type5}}}<br />
| data16 = {{#if:{{{subdivision_type5|}}}|{{{subdivision_name5|}}} }}<br />
<br />
| rowclass17 = mergedrow<br />
| label17 = {{{subdivision_type6}}}<br />
| data17 = {{#if:{{{subdivision_type6|}}}|{{{subdivision_name6|}}} }}<br />
<br />
<!--***Established*** --><br />
| rowclass18 = mergedtoprow<br />
| label18 = {{{established_title}}}<br />
| data18 = {{#if:{{{established_title|}}}|{{{established_date|}}} }}<br />
<br />
| rowclass19 = mergedrow<br />
| label19 = {{{established_title1}}}<br />
| data19 = {{#if:{{{established_title1|}}}|{{{established_date1|}}} }}<br />
<br />
| rowclass20 = mergedrow<br />
| label20 = {{{established_title2}}}<br />
| data20 = {{#if:{{{established_title2|}}}|{{{established_date2|}}} }}<br />
<br />
| rowclass21 = mergedrow<br />
| label21 = {{{established_title3}}}<br />
| data21 = {{#if:{{{established_title3|}}}|{{{established_date3|}}} }}<br />
<br />
| rowclass22 = mergedrow<br />
| label22 = {{{established_title4}}}<br />
| data22 = {{#if:{{{established_title4|}}}|{{{established_date4|}}} }}<br />
<br />
| rowclass23 = mergedrow<br />
| label23 = {{{extinct_title}}}<br />
| data23 = {{#if:{{{extinct_title|}}}|{{{extinct_date|}}} }}<br />
<br />
| rowclass24 = mergedrow<br />
| label24 = Founded by<br />
| data24 = {{{founder|}}}<br />
<br />
| rowclass25 = mergedrow<br />
| label25 = [[Namesake|Named for]]<br />
| data25 = {{{named_for|}}}<br />
<br />
<!-- ***Seat of government and subdivisions within the settlement*** --><br />
| rowclass26 = mergedtoprow<br />
| label26 = {{#if:{{{seat_type|}}}|{{{seat_type}}}|Seat}}<br />
| data26 = {{{seat|}}}<br />
<br />
| rowclass27 = mergedrow<br />
| label27 = {{#if:{{{seat1_type|}}}|{{{seat1_type}}}|Former seat}}<br />
| data27 = {{{seat1|}}}<br />
<br />
| rowclass28 = {{#if:{{{seat|}}}{{{seat1|}}}|mergedrow|mergedtoprow}}<br />
| label28 = {{#if:{{{parts_type|}}}|{{{parts_type}}}|Boroughs}}<br />
| data28 = {{#if:{{{parts|}}}{{{p1|}}}<br />
|{{#ifeq:{{{parts_style|}}}|para<br />
|<b>{{{parts|}}}{{#if:{{both|{{{parts|}}}|{{{p1|}}}}}|&#58;&nbsp;|}}</b>{{comma separated entries|{{{p1|}}}|{{{p2|}}}|{{{p3|}}}|{{{p4|}}}|{{{p5|}}}|{{{p6|}}}|{{{p7|}}}|{{{p8|}}}|{{{p9|}}}|{{{p10|}}}|{{{p11|}}}|{{{p12|}}}|{{{p13|}}}|{{{p14|}}}|{{{p15|}}}|{{{p16|}}}|{{{p17|}}}|{{{p18|}}}|{{{p19|}}}|{{{p20|}}}|{{{p21|}}}|{{{p22|}}}|{{{p23|}}}|{{{p24|}}}|{{{p25|}}}|{{{p26|}}}|{{{p27|}}}|{{{p28|}}}|{{{p29|}}}|{{{p30|}}}|{{{p31|}}}|{{{p32|}}}|{{{p33|}}}|{{{p34|}}}|{{{p35|}}}|{{{p36|}}}|{{{p37|}}}|{{{p38|}}}|{{{p39|}}}|{{{p40|}}}|{{{p41|}}}|{{{p42|}}}|{{{p43|}}}|{{{p44|}}}|{{{p45|}}}|{{{p46|}}}|{{{p47|}}}|{{{p48|}}}|{{{p49|}}}|{{{p50|}}}}}<br />
|{{#if:{{{p1|}}}|{{Collapsible list|title={{{parts|}}}|expand={{#switch:{{{parts_style|}}}|coll=|list=y|{{#if:{{{p6|}}}||y}}}}|1={{{p1|}}}|2={{{p2|}}}|3={{{p3|}}}|4={{{p4|}}}|5={{{p5|}}}|6={{{p6|}}}|7={{{p7|}}}|8={{{p8|}}}|9={{{p9|}}}|10={{{p10|}}}|11={{{p11|}}}|12={{{p12|}}}|13={{{p13|}}}|14={{{p14|}}}|15={{{p15|}}}|16={{{p16|}}}|17={{{p17|}}}|18={{{p18|}}}|19={{{p19|}}}|20={{{p20|}}}|21={{{p21|}}}|22={{{p22|}}}|23={{{p23|}}}|24={{{p24|}}}|25={{{p25|}}}|26={{{p26|}}}|27={{{p27|}}}|28={{{p28|}}}|29={{{p29|}}}|30={{{p30|}}}|31={{{p31|}}}|32={{{p32|}}}|33={{{p33|}}}|34={{{p34|}}}|35={{{p35|}}}|36={{{p36|}}}|37={{{p37|}}}|38={{{p38|}}}|39={{{p39|}}}|40={{{p40|}}}|41={{{p41|}}}|42={{{p42|}}}|43={{{p43|}}}|44={{{p44|}}}|45={{{p45|}}}|46={{{p46|}}}|47={{{p47|}}}|48={{{p48|}}}|49={{{p49|}}}|50={{{p50|}}}}}<br />
|{{{parts}}}<br />
}}<br />
}} }}<br />
<br />
<!-- ***Government type and Leader*** --><br />
| rowclass29 = mergedtoprow<br />
| header29 = {{#if:{{{government_type|}}}{{{governing_body|}}}{{{leader_name|}}}{{{leader_name1|}}}{{{leader_name2|}}}{{{leader_name3|}}}{{{leader_name4|}}}|Government<span style="font-weight:normal">{{{government_footnotes|}}}</span>}}<br />
<!-- ***Government*** --><br />
| rowclass30 = mergedrow<br />
| label30 = &nbsp;•&nbsp;Type<br />
| data30 = {{{government_type|}}}<br />
<br />
| rowclass31 = mergedrow<br />
| label31 = &nbsp;•&nbsp;Body<br />
| class31 = agent<br />
| data31 = {{{governing_body|}}}<br />
<br />
| rowclass32 = mergedrow<br />
| label32 = &nbsp;•&nbsp;{{{leader_title}}}<br />
| data32 = {{#if:{{{leader_title|}}}|{{{leader_name|}}} {{#if:{{{leader_party|}}}|({{Polparty|{{{subdivision_name}}}|{{{leader_party}}}}})}}}}<br />
| rowclass33 = mergedrow<br />
| label33 = &nbsp;•&nbsp;{{{leader_title1}}}<br />
| data33 = {{#if:{{{leader_title1|}}}|{{{leader_name1|}}}}}<br />
| rowclass34 = mergedrow<br />
| label34 = &nbsp;•&nbsp;{{{leader_title2}}}<br />
| data34 = {{#if:{{{leader_title2|}}}|{{{leader_name2|}}}}}<br />
| rowclass35 = mergedrow<br />
| label35 = &nbsp;•&nbsp;{{{leader_title3}}}<br />
| data35 = {{#if:{{{leader_title3|}}}|{{{leader_name3|}}}}}<br />
| rowclass36 = mergedrow<br />
| label36 = &nbsp;•&nbsp;{{{leader_title4}}}<br />
| data36 = {{#if:{{{leader_title4|}}}|{{{leader_name4|}}}}}<br />
<br />
<!-- ***Geographical characteristics*** --><br />
<!-- ***Area*** --><br />
| rowclass37 = mergedtoprow<br />
| header37 = {{#if:{{{area_total_km2|}}}{{{area_total_ha|}}}{{{area_total_acre|}}}{{{area_total_sq_mi|}}}{{{area_total_dunam|}}}{{{area_land_km2|}}}{{{area_land_ha|}}}{{{area_land_acre|}}}{{{area_land_sq_mi|}}}{{{area_water_km2|}}}{{{area_water_ha|}}}{{{area_water_acre|}}}{{{area_water_sq_mi|}}}{{{area_urban_km2|}}}{{{area_urban_ha|}}}{{{area_urban_acre|}}}{{{area_urban_sq_mi|}}}{{{area_rural_sq_mi|}}}{{{area_rural_ha|}}}{{{area_rural_acre|}}}{{{area_rural_km2|}}}{{{area_metro_km2|}}}{{{area_metro_ha|}}}{{{area_metro_acre|}}}{{{area_blank1_km2|}}}{{{area_blank1_ha|}}}{{{area_blank1_acre|}}}{{{area_metro_sq_mi|}}}{{{area_blank1_sq_mi|}}}<br />
|{{#if:{{both|{{#ifeq:{{{total_type}}}|&nbsp;|1}}|{{{area_total_km2|}}}{{{area_total_ha|}}}{{{area_total_acre|}}}{{{area_total_sq_mi|}}}{{{area_total_dunam|}}}}}<br />
|<!-- displayed below --><br />
|Area<span style="font-weight:normal">{{{area_footnotes|}}}</span><br />
}}<br />
}}<br />
<br />
| rowclass38 = {{#if:{{both|{{#ifeq:{{{total_type}}}|&nbsp;|1}}|{{{area_total_km2|}}}{{{area_total_ha|}}}{{{area_total_acre|}}}{{{area_total_sq_mi|}}}{{{area_total_dunam|}}}}}|mergedtoprow|mergedrow}}<br />
| label38 = {{#if:{{both|{{#ifeq:{{{total_type}}}|&nbsp;|1}}|{{{area_total_km2|}}}{{{area_total_ha|}}}{{{area_total_acre|}}}{{{area_total_sq_mi|}}}{{{area_total_dunam|}}}}}<br />
|Area<span style="font-weight:normal">{{{area_footnotes|}}}</span><br />
|&nbsp;•&nbsp;{{#if:{{{total_type|}}}|{{{total_type}}}|{{#if:{{{area_metro_km2|}}}{{{area_metro_sq_mi|}}}{{{area_urban_km2|}}}{{{area_urban_sq_mi|}}}{{{area_rural_km2|}}}{{{area_rural_sq_mi|}}}{{{population_metro|}}}{{{population_urban|}}}{{{population_rural|}}}|{{#if:{{{settlement_type|{{{type|}}}}}}|{{{settlement_type|{{{type}}}}}}|City}}|Total}}}}<br />
}}<br />
| data38 = {{#if:{{{area_total_km2|}}}{{{area_total_ha|}}}{{{area_total_acre|}}}{{{area_total_sq_mi|}}}{{{area_total_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_total_km2|}}}<br />
|ha ={{{area_total_ha|}}}<br />
|acre ={{{area_total_acre|}}}<br />
|sqmi ={{{area_total_sq_mi|}}}<br />
|dunam={{{area_total_dunam|}}}<br />
|link ={{#switch:{{{dunam_link|}}}||on|total=on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
|mag ={{{area_magnitude|}}}<br />
}}}}<br />
<br />
| rowclass39 = mergedrow<br />
| label39 = &nbsp;•&nbsp;Land<br />
| data39 = {{#if:{{{area_land_km2|}}}{{{area_land_ha|}}}{{{area_land_acre|}}}{{{area_land_sq_mi|}}}{{{area_land_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_land_km2|}}}<br />
|ha ={{{area_land_ha|}}}<br />
|acre ={{{area_land_acre|}}}<br />
|sqmi ={{{area_land_sq_mi|}}}<br />
|dunam={{{area_land_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|land|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
| rowclass40 = mergedrow<br />
| label40 = &nbsp;•&nbsp;Water<br />
| data40 = {{#if:{{{area_water_km2|}}}{{{area_water_ha|}}}{{{area_water_acre|}}}{{{area_water_sq_mi|}}}{{{area_water_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_water_km2|}}}<br />
|ha ={{{area_water_ha|}}}<br />
|acre ={{{area_water_acre|}}}<br />
|sqmi ={{{area_water_sq_mi|}}}<br />
|dunam={{{area_water_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|water|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}} {{#if:{{{area_water_percent|}}}| &nbsp;{{{area_water_percent}}}%}}}}<br />
| rowclass41 = mergedrow<br />
| label41 = &nbsp;•&nbsp;Urban<span style="font-weight:normal">{{{area_urban_footnotes|}}}</span><br />
| data41 = {{#if:{{{area_urban_km2|}}}{{{area_urban_ha|}}}{{{area_urban_acre|}}}{{{area_urban_sq_mi|}}}{{{area_urban_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_urban_km2|}}}<br />
|ha ={{{area_urban_ha|}}}<br />
|acre ={{{area_urban_acre|}}}<br />
|sqmi ={{{area_urban_sq_mi|}}}<br />
|dunam={{{area_urban_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|urban|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass42 = mergedrow<br />
| label42 = &nbsp;•&nbsp;Rural<span style="font-weight:normal">{{{area_rural_footnotes|}}}</span><br />
| data42 = {{#if:{{{area_rural_km2|}}}{{{area_rural_ha|}}}{{{area_rural_acre|}}}{{{area_rural_sq_mi|}}}{{{area_rural_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_rural_km2|}}}<br />
|ha ={{{area_rural_ha|}}}<br />
|acre ={{{area_rural_acre|}}}<br />
|sqmi ={{{area_rural_sq_mi|}}}<br />
|dunam={{{area_rural_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|rural|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
| rowclass43 = mergedrow<br />
| label43 =&nbsp;•&nbsp;Metro<span style="font-weight:normal">{{{area_metro_footnotes|}}}</span><br />
| data43 = {{#if:{{{area_metro_km2|}}}{{{area_metro_ha|}}}{{{area_metro_acre|}}}{{{area_metro_sq_mi|}}}{{{area_metro_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_metro_km2|}}}<br />
|ha ={{{area_metro_ha|}}}<br />
|acre ={{{area_metro_acre|}}}<br />
|sqmi ={{{area_metro_sq_mi|}}}<br />
|dunam={{{area_metro_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|metro|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<!-- ***Area rank*** --><br />
| rowclass44 = mergedrow<br />
| label44 = Area rank<br />
| data44 = {{{area_rank|}}}<br />
<br />
| rowclass45 = mergedrow<br />
| label45 = &nbsp;•&nbsp;{{{area_blank1_title}}}<br />
| data45 = {{#if:{{{area_blank1_km2|}}}{{{area_blank1_ha|}}}{{{area_blank1_acre|}}}{{{area_blank1_sq_mi|}}}{{{area_blank1_title|}}}{{{area_blank1_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_blank1_km2|}}}<br />
|ha ={{{area_blank1_ha|}}}<br />
|acre ={{{area_blank1_acre|}}}<br />
|sqmi ={{{area_blank1_sq_mi|}}}<br />
|dunam={{{area_blank1_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|blank1|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass46 = mergedrow<br />
| label46 = &nbsp;•&nbsp;{{{area_blank2_title}}}<br />
| data46 = {{#if:{{{area_blank2_km2|}}}{{{area_blank2_ha|}}}{{{area_blank2_acre|}}}{{{area_blank2_sq_mi|}}}{{{area_blank2_title|}}}{{{area_blank2_dunam|}}}<br />
|{{infobox_settlement/areadisp<br />
|km2 ={{{area_blank2_km2|}}}<br />
|ha ={{{area_blank2_ha|}}}<br />
|acre ={{{area_blank2_acre|}}}<br />
|sqmi ={{{area_blank2_sq_mi|}}}<br />
|dunam={{{area_blank2_dunam|}}}<br />
|link ={{#ifeq:{{{dunam_link|}}}|blank2|on}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass47 = mergedrow<br />
| label47 = &nbsp;<br />
| data47 = {{#if:{{{area_note|}}}|<small>{{{area_note}}}</small>}}<br />
<br />
<!-- ***Dimensions*** --><br />
| rowclass48 = mergedtoprow<br />
| header48 = {{#if:{{{length_km|}}}{{{length_mi|}}}{{{width_km|}}}{{{width_mi|}}}|Dimensions<span style="font-weight:normal">{{{dimensions_footnotes|}}}</span>}}<br />
<br />
| rowclass49 = mergedrow<br />
| label49 = &nbsp;•&nbsp;Length<br />
| data49 = {{#if:{{{length_km|}}}{{{length_mi|}}}<br />
| {{infobox_settlement/lengthdisp<br />
|km ={{{length_km|}}}<br />
|mi ={{{length_mi|}}}<br />
|pref={{{unit_pref}}}<br />
|name={{{subdivision_name}}}<br />
}} }}<br />
<br />
| rowclass50 = mergedrow<br />
| label50 = &nbsp;•&nbsp;Width<br />
| data50 = {{#if:{{{width_km|}}}{{{width_mi|}}}<br />
|{{infobox_settlement/lengthdisp<br />
|km ={{{width_km|}}}<br />
|mi ={{{width_mi|}}}<br />
|pref={{{unit_pref}}}<br />
|name={{{subdivision_name}}}<br />
}} }}<br />
<br />
<!-- ***Elevation*** --><br />
| rowclass51 = mergedtoprow<br />
| label51 = Elevation<span style="font-weight:normal">{{{elevation_footnotes|}}}</span><br />
| data51 = {{#if:{{{elevation_m|}}}{{{elevation_ft|}}}<br />
|{{infobox_settlement/lengthdisp<br />
|m ={{{elevation_m|}}}<br />
|ft ={{{elevation_ft|}}}<br />
|pref={{{unit_pref}}}<br />
|name={{{subdivision_name}}}<br />
}} }}<br />
<br />
| rowclass52 = mergedtoprow<br />
| label52 = Highest&nbsp;elevation<span style="font-weight:normal">{{{elevation_max_footnotes|}}}</span><br />
| data52 = {{#if:{{{elevation_max_m|}}}{{{elevation_max_ft|}}}<br />
|{{infobox_settlement/lengthdisp<br />
|m ={{{elevation_max_m|}}}<br />
|ft ={{{elevation_max_ft|}}}<br />
|pref={{{unit_pref}}}<br />
|name={{{subdivision_name}}}<br />
}} }}<br />
<!-- ***Elevation max rank*** --><br />
| rowclass53 = mergedrow<br />
| label53 = &nbsp;•&nbsp;Rank<br />
| data53 = {{#if:{{{elevation_max_m|}}}{{{elevation_max_ft|}}}| {{{elevation_max_rank|}}} }}<br />
<br />
| rowclass54 = {{#if:{{{elevation_min_rank|}}}|mergedrow|mergedbottomrow}}<br />
| label54 = Lowest&nbsp;elevation<span style="font-weight:normal">{{{elevation_min_footnotes|}}}</span><br />
| data54 = {{#if:{{{elevation_min_m|}}}{{{elevation_min_ft|}}}<br />
|{{infobox_settlement/lengthdisp<br />
|m ={{{elevation_min_m|}}}<br />
|ft ={{{elevation_min_ft|}}}<br />
|pref={{{unit_pref}}}<br />
|name={{{subdivision_name}}}<br />
}} }}<br />
<!-- ***Elevation min rank*** --><br />
| rowclass55 = mergedrow<br />
| label55 = &nbsp;•&nbsp;Rank<br />
| data55 = {{#if:{{{elevation_min_m|}}}{{{elevation_min_ft|}}}|{{{elevation_min_rank|}}}}}<br />
<br />
<!-- ***Population*** --><br />
| rowclass56 = mergedtoprow<br />
| label56 = Population <span style="font-weight:normal">{{#if:{{{population_as_of|}}}|({{{population_as_of}}})}}{{{population_footnotes|}}}</span><br />
| data56 = {{#if:{{{population|}}}<br />
| {{formatnum:{{{population}}}}}<br />
| {{#ifeq:{{{total_type}}}|&nbsp;<br />
| {{#if:{{{population_total|}}}<br />
| {{formatnum:{{{population_total}}}}}<br />
}}<br />
}}<br />
}}<br />
<br />
| rowclass57 = mergedtoprow<br />
| header57 = {{#if:{{{population|}}}<br />
|<br />
|{{#ifeq:{{{total_type}}}|&nbsp;<br />
|<br />
|{{#if:{{{population_total|}}}{{{population_urban|}}}{{{population_rural|}}}{{{population_metro|}}}{{{population_blank1|}}}{{{population_blank2|}}}{{{population_est|}}}<br />
|Population <span style="font-weight:normal">{{#if:{{{population_as_of|}}}|({{{population_as_of}}})}}{{{population_footnotes|}}}</span><br />
}}<br />
}}<br />
}}<br />
<br />
| rowclass58 = mergedrow<br />
| label58 = &nbsp;•&nbsp;{{#if:{{{total_type|}}}|{{{total_type}}}|{{#if:{{{population_metro|}}}{{{population_urban|}}}{{{population_rural|}}}{{{area_metro_km2|}}}{{{area_metro_sq_mi|}}}{{{area_urban_km2|}}}{{{area_urban_sq_mi|}}}{{{area_rural_km2|}}}{{{area_rural_sq_mi|}}}|{{#if:{{{settlement_type|{{{type|}}}}}}|{{{settlement_type|{{{type}}}}}}|City}}|Total}}}}<br />
| data58 = {{#if:{{{population|}}}<br />
|<br />
|{{#ifeq:{{{total_type}}}|&nbsp;<br />
|<br />
|{{#if:{{{population_total|}}}<br />
| {{formatnum:{{{population_total}}}}}<br />
}}<br />
}}<br />
}}<br />
<br />
| rowclass59 = mergedrow<br />
| label59 = &nbsp;•&nbsp;Estimate&nbsp;<span style="font-weight:normal">({{{pop_est_as_of}}}){{{pop_est_footnotes|}}}</span><br />
| data59 = {{#if:{{{population_est|}}}|{{formatnum:{{{population_est}}}}} }}<br />
<br />
<!-- ***Population rank*** --><br />
| rowclass60 = mergedrow<br />
| label60 =&nbsp;•&nbsp;Rank<br />
| data60 = {{{population_rank|}}}<br />
<br />
| rowclass61 = mergedrow<br />
| label61 = &nbsp;•&nbsp;Density<br />
| data61 = {{#if:{{{population_density_km2|}}}{{{population_density_sq_mi|}}}{{{population_total|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_km2|}}}<br />
|/sqmi={{{population_density_sq_mi|}}}<br />
|pop ={{{population_total|}}}<br />
|dunam={{{area_total_dunam|}}}<br />
|ha ={{{area_total_ha|}}}<br />
|km2 ={{{area_total_km2|}}}<br />
|acre ={{{area_total_acre|}}}<br />
|sqmi ={{{area_total_sq_mi|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
<!-- ***Population density rank*** --><br />
| rowclass62 = mergedrow<br />
| label62 = &nbsp;•&nbsp;Density&nbsp;rank<br />
| data62 = {{{population_density_rank|}}}<br />
<br />
| rowclass63 = mergedrow<br />
| label63 = &nbsp;•&nbsp;[[Urban area|Urban]]<span style="font-weight:normal">{{{population_urban_footnotes|}}}</span><br />
| data63 = {{#if:{{{population_urban|}}}| {{formatnum:{{{population_urban}}}}} }}<br />
<br />
| rowclass64 = mergedrow<br />
| label64 = &nbsp;•&nbsp;Urban&nbsp;density<br />
| data64 = {{#if:{{{population_density_urban_km2|}}}{{{population_density_urban_sq_mi|}}}{{{population_urban|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_urban_km2|}}}<br />
|/sqmi={{{population_density_urban_sq_mi|}}}<br />
|pop ={{{population_urban|}}}<br />
|ha ={{{area_urban_ha|}}}<br />
|km2 ={{{area_urban_km2|}}}<br />
|acre ={{{area_urban_acre|}}}<br />
|sqmi ={{{area_urban_sq_mi|}}}<br />
|dunam={{{area_urban_dunam|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass65 = mergedrow<br />
| label65 = &nbsp;•&nbsp;[[Rural area|Rural]]<span style="font-weight:normal">{{{population_rural_footnotes|}}}</span><br />
| data65 = {{#if:{{{population_rural|}}}|{{formatnum:{{{population_rural}}}}}}}<br />
<br />
| rowclass66 = mergedrow<br />
| label66 = &nbsp;•&nbsp;Rural&nbsp;density<br />
| data66 = {{#if:{{{population_density_rural_km2|}}}{{{population_density_rural_sq_mi|}}}{{{population_rural|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_rural_km2|}}}<br />
|/sqmi={{{population_density_rural_sq_mi|}}}<br />
|pop ={{{population_rural|}}}<br />
|ha ={{{area_rural_ha|}}}<br />
|km2 ={{{area_rural_km2|}}}<br />
|acre ={{{area_rural_acre|}}}<br />
|sqmi ={{{area_rural_sq_mi|}}}<br />
|dunam={{{area_rural_dunam|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass67 = mergedrow<br />
| label67 =&nbsp;•&nbsp;[[Metropolitan area|Metro]]<span style="font-weight:normal">{{{population_metro_footnotes|}}}</span><br />
| data67 = {{#if:{{{population_metro|}}}| {{formatnum:{{{population_metro}}}}} }}<br />
<br />
| rowclass68 = mergedrow<br />
| label68 = &nbsp;•&nbsp;Metro&nbsp;density<br />
| data68 = {{#if:{{{population_density_metro_km2|}}}{{{population_density_metro_sq_mi|}}}{{{population_metro|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_metro_km2|}}}<br />
|/sqmi={{{population_density_metro_sq_mi|}}}<br />
|pop ={{{population_metro|}}}<br />
|ha ={{{area_metro_ha|}}}<br />
|km2 ={{{area_metro_km2|}}}<br />
|acre ={{{area_metro_acre|}}}<br />
|sqmi ={{{area_metro_sq_mi|}}}<br />
|dunam={{{area_metro_dunam|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass69 = mergedrow<br />
| label69 = &nbsp;•&nbsp;{{{population_blank1_title|}}}<span style="font-weight:normal">{{{population_blank1_footnotes|}}}</span><br />
| data69 = {{#if:{{{population_blank1|}}}|{{formatnum:{{{population_blank1}}}}}}}<br />
<br />
| rowclass70 = mergedrow<br />
| label70 = &nbsp;•&nbsp;{{#if:{{{population_blank1_title|}}}|{{{population_blank1_title}}} density|Density}}<br />
| data70 = {{#if:{{{population_density_blank1_km2|}}}{{{population_density_blank1_sq_mi|}}}{{{population_blank1|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_blank1_km2|}}}<br />
|/sqmi={{{population_density_blank1_sq_mi|}}}<br />
|pop ={{{population_blank1|}}}<br />
|ha ={{{area_blank1_ha|}}}<br />
|km2 ={{{area_blank1_km2|}}}<br />
|acre ={{{area_blank1_acre|}}}<br />
|sqmi ={{{area_blank1_sq_mi|}}}<br />
|dunam={{{area_blank1_dunam|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass71 = mergedrow<br />
| label71 = &nbsp;•&nbsp;{{{population_blank2_title|}}}<span style="font-weight:normal">{{{population_blank2_footnotes|}}}</span><br />
| data71 = {{#if:{{{population_blank2|}}}|{{formatnum:{{{population_blank2}}}}}}}<br />
<br />
| rowclass72 = mergedrow<br />
| label72 = &nbsp;•&nbsp;{{#if:{{{population_blank2_title|}}}|{{{population_blank2_title}}} density|Density}}<br />
| data72 = {{#if:{{{population_density_blank2_km2|}}}{{{population_density_blank2_sq_mi|}}}{{{population_blank2|}}}<br />
|{{infobox_settlement/densdisp<br />
|/km2 ={{{population_density_blank2_km2|}}}<br />
|/sqmi={{{population_density_blank2_sq_mi|}}}<br />
|pop ={{{population_blank2|}}}<br />
|ha ={{{area_blank2_ha|}}}<br />
|km2 ={{{area_blank2_km2|}}}<br />
|acre ={{{area_blank2_acre|}}}<br />
|sqmi ={{{area_blank2_sq_mi|}}}<br />
|dunam={{{area_blank2_dunam|}}}<br />
|pref ={{{unit_pref}}}<br />
|name ={{{subdivision_name}}}<br />
}}}}<br />
<br />
| rowclass73 = mergedrow<br />
| label73 = &nbsp;<br />
| data73 = {{#if:{{{population_note|}}}|<small>{{{population_note}}}</small>}}<br />
<br />
| rowclass74 = mergedtoprow<br />
| label74 = [[Demonym]]<br />
| data74 = {{{population_demonym|}}}<br />
<br />
| rowclass75 = mergedtoprow<br />
| header75 = {{#if:{{{demographics_type1|}}}<br />
|{{{demographics_type1}}}<span style="font-weight:normal">{{{demographics1_footnotes|}}}</span><!-- <br />
***Demographics 1*** <br />
-->{{infobox|child=yes<br />
<br />
| rowclass1 = mergedrow<br />
| label1 = &nbsp;•&nbsp;{{{demographics1_title1}}}<br />
| data1 = {{#if:{{{demographics1_title1|}}}|{{{demographics1_info1}}}}}<br />
| rowclass2 = mergedrow<br />
| label2 = &nbsp;•&nbsp;{{{demographics1_title2}}}<br />
| data2 = {{#if:{{{demographics1_title2|}}}|{{{demographics1_info2}}}}}<br />
| rowclass3 = mergedrow<br />
| label3 = &nbsp;•&nbsp;{{{demographics1_title3}}}<br />
| data3 = {{#if:{{{demographics1_title3|}}}|{{{demographics1_info3}}}}}<br />
| rowclass4 = mergedrow<br />
| label4 = &nbsp;•&nbsp;{{{demographics1_title4}}}<br />
| data4 = {{#if:{{{demographics1_title4|}}}|{{{demographics1_info4}}}}}<br />
| rowclass5 = mergedrow<br />
| label5 = &nbsp;•&nbsp;{{{demographics1_title5}}}<br />
| data5 = {{#if:{{{demographics1_title5|}}}|{{{demographics1_info5}}}}}<br />
}}}}<br />
<br />
| rowclass76 = mergedtoprow<br />
| header76 = {{#if:{{{demographics_type2|}}}<br />
|{{{demographics_type2}}}<span style="font-weight:normal">{{{demographics2_footnotes|}}}</span><!-- <br />
***Demographics 2*** <br />
-->{{infobox|child=yes<br />
| rowclass1 = mergedrow<br />
| label1 = &nbsp;•&nbsp;{{{demographics2_title1}}}<br />
| data1 = {{#if:{{{demographics2_title1|}}}|{{{demographics2_info1}}}}}<br />
| rowclass2 = mergedrow<br />
| label2 = &nbsp;•&nbsp;{{{demographics2_title2}}}<br />
| data2 = {{#if:{{{demographics2_title2|}}}|{{{demographics2_info2}}}}}<br />
| rowclass3 = mergedrow<br />
| label3 = &nbsp;•&nbsp;{{{demographics2_title3}}}<br />
| data3 = {{#if:{{{demographics2_title3|}}}|{{{demographics2_info3}}}}}<br />
| rowclass4 = mergedrow<br />
| label4 = &nbsp;•&nbsp;{{{demographics2_title4}}}<br />
| data4 = {{#if:{{{demographics2_title4|}}}|{{{demographics2_info4}}}}}<br />
| rowclass5 = mergedrow<br />
| label5 = &nbsp;•&nbsp;{{{demographics2_title5}}}<br />
| data5 = {{#if:{{{demographics2_title5|}}}|{{{demographics2_info5}}}}}<br />
}}}}<br />
<br />
<!-- ***Time Zones*** --><br />
| rowclass77 = mergedtoprow<br />
| label77 = {{#if:{{{timezone2|}}}|[[Time zone]]s|[[Time zone]]}}<br />
| data77 = {{#if:{{{timezone1|{{{timezone|}}}}}}|{{{timezone1|{{{timezone}}}}}} {{#if:{{{utc_offset1|{{{utc_offset|}}} }}}|([[UTC{{{utc_offset1|{{{utc_offset}}}}}}]])}} }}<br />
<br />
| rowclass78 = mergedrow<br />
| label78 = <nowiki /><br />
| data78 = {{#if:{{{timezone1|{{{timezone|}}}}}}|{{#if:{{{timezone2|}}}|{{{timezone2}}} {{#if:{{{utc_offset2|{{{utc_offset2|}}} }}}|([[UTC{{{utc_offset2|{{{utc_offset2}}}}}}]])}} }} }}<br />
<br />
| rowclass79 = mergedrow<br />
| label79 = <span style="white-space:nowrap">&nbsp;•&nbsp;Summer ([[Daylight saving time|DST]])</span><br />
| data79 = {{#if:{{{timezone1|{{{timezone|}}}}}}|{{#if:{{{timezone1_DST|{{{timezone_DST|}}}}}}|{{{timezone1_DST|{{{timezone_DST|}}}}}} ([[UTC{{{utc_offset1_DST|{{{utc_offset_DST|}}}}}}]])}} }}<br />
<br />
| rowclass80 = mergedrow<br />
| label80 = <nowiki /><br />
| data80 = {{#if:{{{timezone1|{{{timezone|}}}}}}|{{#if:{{{timezone1_DST|{{{timezone_DST|}}}}}}|{{#if:{{{timezone2_DST|}}}|{{{timezone2_DST}}} ([[UTC{{{utc_offset2_DST|}}}]])}} }} }}<br />
<br />
<!-- ***Postal Code(s)*** --><br />
| rowclass81 = mergedtoprow<br />
| label81 = {{{postal_code_type}}}<br />
| class81 = adr<br />
| data81 = {{#if:{{{postal_code_type|}}}|{{#if:{{{postal_code|}}}|<span class="postal-code">{{{postal_code}}}</span>}}}}<br />
<br />
| rowclass82 = mergedbottomrow<br />
| label82 = {{{postal2_code_type}}}<br />
| class82 = adr<br />
| data82 = {{#if:{{{postal_code_type|}}}|{{#if:{{{postal2_code_type|}}}|{{#if:{{{postal2_code|}}}|<span class="postal-code">{{{postal2_code}}}</span>}} }} }}<br />
<br />
<!-- ***Area Code(s)*** --><br />
| rowclass83 = mergedrow<br />
| label83 = {{#if:{{{area_code_type|}}}|{{{area_code_type}}}|[[Telephone numbering plan|Area code(s)]]}}<br />
| data83 = {{{area_code|}}}<br />
<br />
<!-- Geocode--><br />
| rowclass84 = mergedrow<br />
| label84 = [[Geocode]]<br />
| class84 = nickname<br />
| data84 = {{{geocode|}}}<br />
<br />
<!-- ISO Code--><br />
| rowclass85 = mergedrow<br />
| label85 = [[ISO 3166|ISO 3166 code]]<br />
| class85 = nickname<br />
| data85 = {{{iso_code|}}}<br />
<br />
<!-- Vehicle registration plate--><br />
| rowclass86 = mergedrow<br />
| label86 = [[Vehicle registration plate|Vehicle registration]]<br />
| data86 = {{{registration_plate|}}}<br />
<br />
<br />
| rowclass87 = mergedtoprow<br />
| header87 = {{#if:{{{twin1|}}}<br />
|[[List of twin towns and sister cities|Twin cities]]<!-- <br />
***Twin Cities*** <br />
-->{{infobox|child=yes<br />
<br />
| rowclass1 = mergedrow<br />
| label1 = &nbsp;•&nbsp;{{{twin1}}}<br />
| data1 = {{#if:{{{twin1|}}}|{{{twin1_country}}}}}<br />
| rowclass2 = mergedrow<br />
| label2 = &nbsp;•&nbsp;{{{twin2}}}<br />
| data2 = {{#if:{{{twin2|}}}|{{{twin2_country}}}}}<br />
| rowclass3 = mergedrow<br />
| label3 = &nbsp;•&nbsp;{{{twin3}}}<br />
| data3 = {{#if:{{{twin3|}}}|{{{twin3_country}}}}}<br />
| rowclass4 = mergedrow<br />
| label4 = &nbsp;•&nbsp;{{{twin4}}}<br />
| data4 = {{#if:{{{twin4|}}}|{{{twin4_country}}}}}<br />
| rowclass5 = mergedrow<br />
| label5 = &nbsp;•&nbsp;{{{twin5}}}<br />
| data5 = {{#if:{{{twin5|}}}|{{{twin5_country}}}}}<br />
| rowclass6 = mergedrow<br />
| label6 = &nbsp;•&nbsp;{{{twin6}}}<br />
| data6 = {{#if:{{{twin6|}}}|{{{twin6_country}}}}}<br />
| rowclass7 = mergedrow<br />
| label7 = &nbsp;•&nbsp;{{{twin7}}}<br />
| data7 = {{#if:{{{twin7|}}}|{{{twin7_country}}}}}<br />
| rowclass8 = mergedrow<br />
| label8 = &nbsp;•&nbsp;{{{twin8}}}<br />
| data8 = {{#if:{{{twin8|}}}|{{{twin8_country}}}}}<br />
| rowclass9 = mergedrow<br />
| label9 = &nbsp;•&nbsp;{{{twin9}}}<br />
| data9 = {{#if:{{{twin9|}}}|{{{twin9_country}}}}}<br />
}} }}<br />
<br />
<!-- ***Blank Fields (two sections)*** --><br />
| rowclass88 = mergedtoprow<br />
| label88 = {{{blank_name_sec1|{{{blank_name|}}}}}}<br />
| data88 = {{#if:{{{blank_name_sec1|{{{blank_name|}}}}}}|{{{blank_info_sec1|{{{blank_info|}}}}}}}}<br />
<br />
| rowclass89 = mergedrow<br />
| label89 = {{{blank1_name_sec1|{{{blank1_name|}}}}}}<br />
| data89 = {{#if:{{{blank1_name_sec1|{{{blank1_name|}}}}}}|{{{blank1_info_sec1|{{{blank1_info|}}}}}}}}<br />
<br />
| rowclass90 = mergedrow<br />
| label90 = {{{blank2_name_sec1|{{{blank2_name|}}}}}}<br />
| data90 = {{#if:{{{blank2_name_sec1|{{{blank2_name|}}}}}}|{{{blank2_info_sec1|{{{blank2_info|}}}}}}}}<br />
<br />
| rowclass91 = mergedrow<br />
| label91 = {{{blank3_name_sec1|{{{blank3_name|}}}}}}<br />
| data91 = {{#if:{{{blank3_name_sec1|{{{blank3_name|}}}}}}|{{{blank3_info_sec1|{{{blank3_info|}}}}}}}}<br />
<br />
| rowclass92 = mergedrow<br />
| label92 = {{{blank4_name_sec1|{{{blank4_name|}}}}}}<br />
| data92 = {{#if:{{{blank4_name_sec1|{{{blank4_name|}}}}}}|{{{blank4_info_sec1|{{{blank4_info|}}}}}}}}<br />
<br />
| rowclass93 = mergedrow<br />
| label93 = {{{blank5_name_sec1|{{{blank5_name|}}}}}}<br />
| data93 = {{#if:{{{blank5_name_sec1|{{{blank5_name|}}}}}}|{{{blank5_info_sec1|{{{blank5_info|}}}}}}}}<br />
<br />
| rowclass94 = mergedrow<br />
| label94 = {{{blank6_name_sec1|{{{blank6_name|}}}}}}<br />
| data94 = {{#if:{{{blank6_name_sec1|{{{blank6_name|}}}}}}|{{{blank6_info_sec1|{{{blank6_info|}}}}}}}}<br />
<br />
| rowclass95 = mergedrow<br />
| label95 = {{{blank7_name_sec1|{{{blank7_name|}}}}}}<br />
| data95 = {{#if:{{{blank7_name_sec1|{{{blank7_name|}}}}}}|{{{blank7_info_sec1|{{{blank7_info|}}}}}}}}<br />
<br />
| rowclass96 = mergedtoprow<br />
| label96 = {{{blank_name_sec2}}}<br />
| data96 = {{#if:{{{blank_name_sec2|}}}|{{{blank_info_sec2|}}}}}<br />
<br />
| rowclass97 = mergedrow<br />
| label97 = {{{blank1_name_sec2}}}<br />
| data97 = {{#if:{{{blank1_name_sec2|}}}|{{{blank1_info_sec2|}}}}}<br />
<br />
| rowclass98 = mergedrow<br />
| label98 = {{{blank2_name_sec2}}}<br />
| data98 = {{#if:{{{blank2_name_sec2|}}}|{{{blank2_info_sec2|}}}}}<br />
<br />
| rowclass99 = mergedrow<br />
| label99 = {{{blank3_name_sec2}}}<br />
| data99 = {{#if:{{{blank3_name_sec2|}}}|{{{blank3_info_sec2|}}}}}<br />
<br />
| rowclass100 = mergedrow<br />
| label100 = {{{blank4_name_sec2}}}<br />
| data100 = {{#if:{{{blank4_name_sec2|}}}|{{{blank4_info_sec2|}}}}}<br />
<br />
| rowclass101 = mergedrow<br />
| label101 = {{{blank5_name_sec2}}}<br />
| data101 = {{#if:{{{blank5_name_sec2|}}}|{{{blank5_info_sec2|}}}}}<br />
<br />
| rowclass102 = mergedrow<br />
| label102 = {{{blank6_name_sec2}}}<br />
| data102 = {{#if:{{{blank6_name_sec2|}}}|{{{blank6_info_sec2|}}}}}<br />
<br />
| rowclass103 = mergedrow<br />
| label103 = {{{blank7_name_sec2}}}<br />
| data103 = {{#if:{{{blank7_name_sec2|}}}|{{{blank7_info_sec2|}}}}}<br />
<br />
<!-- ***Website*** --><br />
| rowclass104 = mergedtoprow<br />
| label104 = Website<br />
| data104 = {{#if:{{{website|}}}|{{{website}}}}}<br />
<br />
<!-- ***Footnotes*** --><br />
| belowstyle = text-align:left; font-size:smaller<br />
| belowrowclass = mergedtoprow<br />
| below = {{{footnotes|}}}<br />
}}<!--For deprecated parameter names--><includeonly>{{#ifeq:{{{coor_type|♠}}}{{{city_logo|♠}}}{{{area_total|♠}}}{{{area_land|♠}}}{{{area_water|♠}}}{{{TotalArea_sq_mi|♠}}}{{{LandArea_sq_mi|♠}}}{{{WaterArea_sq_mi|♠}}}{{{area_urban|♠}}}{{{UrbanArea_sq_mi|♠}}}{{{area_metro|♠}}}{{{MetroArea_sq_mi|♠}}}{{{elevation|♠}}}{{{population_density|♠}}}{{{population_density_mi2|♠}}}{{{population_density_metro_mi2|♠}}}{{{population_density_urban_mi2|♠}}}|♠♠♠♠♠♠♠♠♠♠♠♠♠♠♠♠♠||[[Category:Settlement articles requiring maintenance]]}}{{#switch:{{{coordinates_region|}}}|CA-X|US-X|IN-X=[[Category:Infobox settlement uses with imprecise region codes]]}}{{#if:{{{image_dot_map|}}}{{{dot_mapsize|}}}{{{dot_map_base_alt|}}}{{{dot_map_alt|}}}{{{dot_map_caption|}}}{{{dot_x|}}}{{{dot_y|}}}<br />
|[[Category:Settlement articles with dot maps]]<br />
}}</includeonly><noinclude><br />
{{documentation}}<br />
</noinclude></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:ModNavigation&diff=1434Template:ModNavigation2025-08-21T00:17:40Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>{{Navbox<br />
| name = ModSupport<br />
| title = [[ModSupport|ModSupport]]<br />
| listclass = hlist<br />
<br />
| group1 = Minetweaker Supported Mods<br />
| list1 =<br />
* [[Test]]<br />
<br />
| group2 = Modtweaker Supported Mods<br />
| list2 =<br />
* [[Test2]]<br />
<br />
| group3 = Native Mod Support<br />
| list3 =<br />
* [[Test3]]<br />
}}<br />
<br />
@Stan haaalp!</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:ModTweakerNavigation&diff=1470Template:ModTweakerNavigation2025-08-21T00:17:40Z<p>Aizistral: 35 revisions imported</p>
<hr />
<div><br />
<br />
----<br />
<br />
{| class="wikitable"<br />
! style="text-align: center; font-weight: bold;" | [[ModTweaker]] Supported Mods<br />
|-<br />
| <br />
[[ModTweaker:Applied_Energistics_2_Support|Applied Energistics 2]] | <br />
[[Aura Cascade]] | <br />
[[Botania]] | <br />
[[ModTweaker:Chisel_2_Support|Chisel 2]] | <br />
[[Ex Nihilo]] | <br />
[[ModTweaker:Extra_Utilities_Support|Extra Utilities]] | <br />
[[Factorization]] | <br />
[[ModTweaker:Flaxbeard_Steam_Power_Support|Flaxbeard's Steam Power Support]] | <br />
[[ModTweaker:Forestry Support|Forestry]] | <br />
[[Mariculture]] | <br />
[[Mekanism]] | <br />
[[Metallurgy 4]] | <br />
[[PneumaticCraft]] | <br />
[[Railcraft]] | <br />
[[Thaumcraft 4]] | <br />
[[ModTweaker:Thermal Expansion Support|Thermal Expansion]] | <br />
[[Tinker's Construct]]<br />
|}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:ModTweakerNavigation_1.10.2&diff=1479Template:ModTweakerNavigation 1.10.22025-08-21T00:17:40Z<p>Aizistral: 8 revisions imported</p>
<hr />
<div>----<br />
<br />
{| class="wikitable"<br />
! style="text-align: center; font-weight: bold;" | [[ModTweaker]] Supported Mods<br />
|-<br />
| <br />
[[ModTweaker:Actually_Additions_Support_1.10.2|Actually Additions Support]]| <br />
[[ModTweaker:Blood_Magic_Support_1.10.2|Blood Magic Support]]| <br />
[[ModTweaker:Botania_Support_1.10.2|Botania Support]]| <br />
[[ModTweaker:Chisel_2_Support_1.10.2|Chisel 2 Support]]| <br />
[[ModTweaker:Embers_Support_1.10.2|Embers Support]]| <br />
[[ModTweaker:Extra_Utilities_Support_1.10.2|Extra Utilities Support]]| <br />
[[ModTweaker:Forestry_Support_1.10.2|Forestry Support]]| <br />
[[ModTweaker:Random_Things_Support_1.10.2|Random Things Support]]| <br />
[[ModTweaker:Refined_Storage_Support_1.10.2|Refined Storage Support]]| <br />
[[ModTweaker:TConstruct_Support_1.10.2|Tinker's Construct Support]]<br />
|}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:ModTweakerNavigation_1.11.2&diff=1487Template:ModTweakerNavigation 1.11.22025-08-21T00:17:40Z<p>Aizistral: 7 revisions imported</p>
<hr />
<div>----<br />
<br />
{| class="wikitable"<br />
! style="text-align: center; font-weight: bold;" | [[ModTweaker]] Supported Mods<br />
|-<br />
| <br />
[[ModTweaker:Actually_Additions_Support_1.11.2|Actually Additions Support]] | <br />
[[ModTweaker:Chisel_Support_1.11.2|Chisel Support]] | <br />
[[ModTweaker:Forestry_Support_1.11.2|Forestry Support]] | <br />
[[ModTweaker:Refined_Storage_Support_1.11.2|Refined Storage Support]]<br />
|}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:Navbox&diff=1490Template:Navbox2025-08-21T00:17:40Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Talk:Tutorial:Localization&diff=1377Talk:Tutorial:Localization2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>Following the given code returns error saying no such member. Correcting "localisation" to "localization" fixes the error.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=User:Voidi&diff=1398User:Voidi2025-08-21T00:17:39Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>The shared script directory: the scripts directory, directly inside your minecraft directory. Scripts stored in this directory (excluded in the subdirectory 'disabled') will apply to all worlds hosted by that minecraft instance - including Single-player games. They will NOT apply when you join another server, as scripts are always loaded from the server.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=User_talk:Yulife&diff=1409User talk:Yulife2025-08-21T00:17:39Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:ContentTweakerLogo.jpg&diff=1411File:ContentTweakerLogo.jpg2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Grammar-annotations.png&diff=1413File:Grammar-annotations.png2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>ZenCode grammar: annotations</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Grammar-genericparameters.png&diff=1415File:Grammar-genericparameters.png2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>ZenCode grammar: generic parameters.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:ModTweaker_logo.png&diff=1417File:ModTweaker logo.png2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Recipe_leggings_iron.png&diff=1419File:Recipe leggings iron.png2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>Iron leggings recipe</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=File:Recipe_leggings_iron_brackets.png&diff=1421File:Recipe leggings iron brackets.png2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>Leggings recipe in bracket notation.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:ContentTweakerNavigation&diff=1423Template:ContentTweakerNavigation2025-08-21T00:17:39Z<p>Aizistral: 1 revision imported</p>
<hr />
<div><br />
<br />
----<br />
<br />
{| class="wikitable"<br />
! style="text-align: center; font-weight: bold;" | [[ContentTweaker]] Supported Mods & Vanilla<br />
|-<br />
| <br />
[[ContentTweaker:BlockItem_Support|Blocks and Items Support]] | <br />
|}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:Infobox&diff=1426Template:Infobox2025-08-21T00:17:39Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Template:Infobox_settlement&diff=1429Template:Infobox settlement2025-08-21T00:17:39Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div></div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Localization_164&diff=1183Tutorial:Localization 1642025-08-21T00:17:37Z<p>Aizistral: 3 revisions imported</p>
<hr />
<div>Since MineTweaker 3.0.8, it is possible to change localization strings.<br />
<br />
Two variants of the function exist - one that sets the translation no matter the current language, and one that overrides a translation but only when the given language matches the current language:<br />
<br />
// Set translation but only if language is en_US<br />
game.setLocalisation("en_US", "nei.inventory.prev", "Past");<br />
<br />
//KEY, TEXT - You will want to use this one most of the time, it overrides no matter the language<br />
game.setLocalisation("nei.inventory.next", "Future");<br />
<br />
To find localizations, check the localization files in the assets of Minecraft or the mods you want to alter.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Loot&diff=1186Tutorial:Loot2025-08-21T00:17:37Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>== Chest Loot ==<br />
<br />
Since 3.0.8, it is possible to change any kind of dungeon loot. Loot can be changed for dungeon chests, mineshaft chests or any other kind of vanilla or mod chest.<br />
<br />
This line would make diamonds very likely to appear:<br />
<br />
vanilla.loot.addChestLoot("dungeonChest", <minecraft:diamond>.weight(100));<br />
<br />
// Spawn 1-5 sticks with a probability of 100<br />
vanilla.loot.addChestLoot("dungeonChest", <minecraft:stick>.weight(100), 1, 5);<br />
<br />
It's also possible to remove chest loot:<br />
<br />
vanilla.loot.removeChestLoot("dungeonChest", <minecraft:enchanted_book>);<br />
<br />
Both items and ore dictionary entries work, as does the wildcard pattern to remove everything (<*>).<br />
<br />
Use /mt loot to dump the list of chests and their contents. <br />
<br />
== Seeds ==<br />
<br />
You can now also modify the seeds that are dropped when you break tall grass:<br />
<br />
vanilla.seeds.addSeed(<minecraft:planks>.weight(100));<br />
vanilla.seeds.removeSeed(<Natura:barley.seed:*>);<br />
<br />
This functionality existed in ModTweaker before and has now been integrated into MineTweaker.<br />
<br />
Use /mt seeds to see what's already registered.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Loot_164&diff=1189Tutorial:Loot 1642025-08-21T00:17:37Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>== Chest Loot ==<br />
<br />
Since 3.0.8, it is possible to change any kind of dungeon loot. Loot can be changed for dungeon chests, mineshaft chests or any other kind of vanilla or mod chest.<br />
<br />
This line would make diamonds very likely to appear:<br />
<br />
vanilla.loot.addChestLoot("dungeonChest", <item.diamond>.weight(100));<br />
<br />
// Spawn 1-5 sticks with a probability of 100<br />
vanilla.loot.addChestLoot("dungeonChest", <item.stick>.weight(100), 1, 5);<br />
<br />
It's also possible to remove chest loot:<br />
<br />
vanilla.loot.removeChestLoot("dungeonChest", <minecraft:enchanted_book>);<br />
<br />
Both items and ore dictionary entries work, as does the wildcard pattern to remove everything (<*>).<br />
<br />
Use /mt loot to dump the list of chests and their contents.<br />
<br />
== Seeds ==<br />
<br />
You can now also modify the seeds that are dropped when you break tall grass:<br />
<br />
vanilla.seeds.addSeed(<tile.wood>.weight(100));<br />
vanilla.seeds.removeSeed(<Natura:barley.seed:*>);<br />
<br />
This functionality existed in ModTweaker before and has now been integrated into MineTweaker.<br />
<br />
Use /mt seeds to see what's already registered.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Ore_Dictionary&diff=1196Tutorial:Ore Dictionary2025-08-21T00:17:37Z<p>Aizistral: 6 revisions imported</p>
<hr />
<div>= Ore Dictionary =<br />
<br />
Now that we've gotten our feet wet (you did follow the previous tutorials, right?), let's try this recipe: (IC2 required)<br />
<br />
val copper = <IC2:itemIngotCopper>;<br />
val tin = <IC2:itemIngotTin>;<br />
val iron = <minecraft:iron_ingot>;<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<IC2:itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
If you try the recipe, it's going to work... but not if you use the copper ingots from, say, Thermal Expansion or Tinkers Construct! The items are different!<br />
<br />
Luckily, this issue exists for quite a while already and has been solved through the use of the '''ore dictionary'''. In essence, the ore dictionary groups items by their meaning and allows mods to add their own items to the ore dictionary. For instance, the copper ore dictionary is named <code><ore:ingotCopper></code>.<br />
<br />
These ore dictionary entries can be used in recipes easily:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <ore:ingotIron>;<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<IC2:itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
... and that should fix it! Try installing a few mods that add copper ore, and all of their ingots should now be compatible.<br />
<br />
The ore dictionary is used for more than just ores and ingots. Many ingredients have their own ore dictionary entry, allowing multiple substitutes for a specific ingredient.<br />
<br />
== Modifying the ore dictionary ==<br />
<br />
Not satisfied with the contents that mods put into the ore dictionary? Did some mod forget to add an item to the proper entry? Or do you believe a certain ingredient substitute makes recicpes too cheap? MineTweaker makes it possible to alter the contents of the ore dictionary.<br />
<br />
Once you retrieve an ore dictionary entry, you can modify it by adding or removing ores. Let's modify our script a bit:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <ore:ingotIron>;<br />
iron.add(<minecraft:coal>);<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<IC2:itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
If you reload the scripts and check the recipe, you will notice that iron can now be substituted with coal.<br />
<br />
Likewise, you could even remove iron from its entry:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <ore:ingotIron>;<br />
iron.add(<minecraft:coal>);<br />
iron.remove(<minecraft:iron_ingot>);<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<IC2:itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
Now this ore dictionary modification may not be very useful, but it does illustrate how the ore dictionary can be modified easily.<br />
<br />
If you ever come across a mod dictionary entry of which you believe they should both actually be the same, it's now possible to mirror ore dictionary entries:<br />
<br />
<ore:ingotIron>.mirror(<ore:ingotTin>);<br />
<br />
Now doing that will link iron to be the same as tin. Iron will then essentially be overridden by tin, and any changes made to tin will automatically reflect in iron.<br />
<br />
== Adding new ore dictionary entries ==<br />
<br />
When you use an ore dictionary entry, it doesn't matter if it already exists or not. If you use one that doesn't exist, it will simply return an empty one. Thus, all you need is to reference the ore dictionary you want to make as if it already exists, and add items to it:<br />
<br />
val myEntry = <ore:myOwnEntry>;<br />
myEntry.add(<minecraft:coal>);<br />
myEntry.add(<minecraft:iron_ingot>);<br />
<br />
== Merging and unifying two ore dictionary entries ==<br />
<br />
When playing with many mods, you'll find them reimplementing similar ores, similar items and yet register them in different ore dictionaries. Now you can unify the ore dictionary entries to a certain extent. Let's say multiple mods add salt ores to the game, and have chosen to register them under different names. Now, you ensure that the two dictionaries contain the exact same items, by executing these two commands. <br />
<br />
<ore:dustSalt>.addAll(<ore:foodSalt>);<br />
<ore:foodSalt>.mirror(<ore:dustSalt>); <br />
<br />
Now each mod can utilise the others' items in its own recipes. This allows easier cross-mod interactions in recipes (no more hoarding of items), and a fluid gameplay overall. <br />
<br />
== Using ore entries in recipe removal ==<br />
<br />
Ore dictionary entries can also be used to remove recipes containing ore entries, or as wildcard meaning "you can match any item in the ore entry". Note that an ore dictionary entry with a single item is considered equivalent to the item. (this in contrast with MineTweaker 2)<br />
<br />
== Iterating over the values in an oredict entry ==<br />
<br />
Sometimes there is need to perform a certain action for every item in the ore dictionary. This is possible with a simple for loop:<br />
<br />
for item in <ore:ingotCopper>.items {<br />
doSomething();<br />
}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Ore_Dictionary_164&diff=1200Tutorial:Ore Dictionary 1642025-08-21T00:17:37Z<p>Aizistral: 3 revisions imported</p>
<hr />
<div>= Ore Dictionary =<br />
<br />
Now that we've gotten our feet wet (you did follow the previous tutorials, right?), let's try this recipe: (IC2 required)<br />
<br />
val copper = <ic2.itemIngot:0>;<br />
val tin = <ic2.itemIngot:1>;<br />
val iron = <item.ingotIron>;<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<ic2.itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
If you try the recipe, it's going to work... but not if you use the copper ingots from, say, Thermal Expansion or Tinkers Construct! The items are different!<br />
<br />
Luckily, this issue exists for quite a while already and has been solved through the use of the '''ore dictionary'''. In essence, the ore dictionary groups items by their meaning and allows mods to add their own items to the ore dictionary. For instance, the copper ore dictionary is named <code><ore:ingotCopper></code>.<br />
<br />
These ore dictionary entries can be used in recipes easily:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <ore:ingotIron>;<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<ic2.itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
... and that should fix it! Try installing a few mods that add copper ore, and all of their ingots should now be compatible.<br />
<br />
The ore dictionary is used for more than just ores and ingots. Many ingredients have their own ore dictionary entry, allowing multiple substitutes for a specific ingredient.<br />
<br />
== Modifying the ore dictionary ==<br />
<br />
Not satisfied with the contents that mods put into the ore dictionary? Did some mod forget to add an item to the proper entry? Or do you believe a certain ingredient substitute makes recicpes too cheap? MineTweaker makes it possible to alter the contents of the ore dictionary.<br />
<br />
Once you retrieve an ore dictionary entry, you can modify it by adding or removing ores. Let's modify our script a bit:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <item.ingotIron>;<br />
tin.add(<item.coal>);<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<ic2.itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
If you reload the scripts and check the recipe, you will notice that tin can now be substituted with coal.<br />
<br />
Likewise, you could even remove iron from its entry:<br />
<br />
val copper = <ore:ingotCopper>;<br />
val tin = <ore:ingotTin>;<br />
val iron = <item.ingotIron>;<br />
tin.add(<item.coal>);<br />
tin.remove(<ic2.itemIngot:1>);<br />
<br />
// actually IC2 uses bronze and not copper. but that doesn't matter since this is just for demonstration<br />
recipes.addShaped(<ic2.itemPartAlloy>, [[iron, iron, iron], [copper, copper, copper], [tin, tin, tin]]);<br />
<br />
Now this ore dictionary modification may not be very useful, but it does illustrate how the ore dictionary can be modified easily.<br />
<br />
If you ever come across a mod dictionary entry of which you believe they should both actually be the same, it's now possible to mirror ore dictionary entries:<br />
<br />
<ore:ingotCopper>.mirror(<ore:ingotTin>);<br />
<br />
Now doing that will link copper to be the same as tin. Copper will then essentially be overridden by tin, and any changes made to tin will automatically reflect in copper, and vice versa.<br />
<br />
== Using ore entries in recipe removal ==<br />
<br />
Ore dictionary entries can also be used to remove recipes containing ore entries, or as wildcard meaning "you can match any item in the ore entry". Note that an ore dictionary entry with a single item is considered equivalent to the item. (this in contrast with MineTweaker 2)</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Tooltips&diff=1205Tutorial:Tooltips2025-08-21T00:17:37Z<p>Aizistral: 4 revisions imported</p>
<hr />
<div>Since MineTweaker 3.0.8, you can now add tooltips to items.<br />
<br />
Adding tooltips can be done directly on any kind of ingredient:<br />
<br />
<ore:plankWood>.addTooltip("These are wood planks");<br />
<minecraft:stick>.addTooltip("These are sticks");<br />
<br />
Two kinds of tooltips are available: regular tooltips and tooltips that only appear when the shift key is being pressed:<br />
<br />
<minecraft:stick>.addShiftTooltip("Only appears with shift");<br />
<br />
== Markup ==<br />
<br />
Tooltips can be colored and styled using the format functions:<br />
<br />
<minecraft:stick>.addTooltip(format.green("This is green text"));<br />
<br />
The following formatting functions are available:<br />
<br />
format.black<br />
format.darkBlue<br />
format.darkGreen<br />
format.darkAqua<br />
format.darkRed<br />
format.darkPurple<br />
format.gold<br />
format.gray<br />
format.darkGray<br />
format.blue<br />
format.green<br />
format.aqua<br />
format.red<br />
format.lightPurple<br />
format.yellow<br />
format.white<br />
<br />
format.obfuscated<br />
format.bold<br />
format.strikethrough<br />
format.underline<br />
format.italic<br />
<br />
Strings (and formatted strings) can be concatenated and nested easily:<br />
<br />
<minecraft:stick>.addTooltip(format.green(format.italic("This is a stick") + " with " + format.strikethrough("text")) + " in multiple styles");<br />
<br />
Be careful to match the brackets properly!</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Tooltips_164&diff=1208Tutorial:Tooltips 1642025-08-21T00:17:37Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>Since MineTweaker 3.0.8, you can now add tooltips to items.<br />
<br />
Adding tooltips can be done directly on any kind of ingredient:<br />
<br />
<ore:plankWood>.addTooltip("These are wood planks");<br />
<item.stick>.addTooltip("These are sticks");<br />
<br />
Two kinds of tooltips are available: regular tooltips and tooltips that only appear when the shift key is being pressed:<br />
<br />
<item.stick>.addShiftTooltip("Only appears with shift");<br />
<br />
== Markup ==<br />
<br />
Tooltips can be colored and styled using the format functions:<br />
<br />
<minecraft:stick>.addTooltip(format.green("This is green text"));<br />
<br />
The following formatting functions are available:<br />
<br />
format.black<br />
format.darkBlue<br />
format.darkGreen<br />
format.darkAqua<br />
format.darkRed<br />
format.darkPurple<br />
format.gold<br />
format.gray<br />
format.darkGray<br />
format.blue<br />
format.green<br />
format.aqua<br />
format.red<br />
format.lightPurple<br />
format.yellow<br />
format.white<br />
<br />
format.obfuscated<br />
format.bold<br />
format.strikethrough<br />
format.underline<br />
format.italic<br />
<br />
Strings (and formatted strings) can be concatenated and nested easily:<br />
<br />
<item.stick>.addTooltip(format.green(format.italic("This is a stick") + " with " + format.strikethrough("text")) + " in multiple styles");<br />
<br />
Be careful to match the brackets properly!</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:item_Renaming_164&diff=1211Tutorial:item Renaming 1642025-08-21T00:17:37Z<p>Aizistral: 2 revisions imported</p>
<hr />
<div>Not happy with an item name? Want to correct a <strike>type</strike> typo made by the mod author? Did some translation go missing?<br />
<br />
Although a resource pack can fix that, it may be less cumbersome to use MineTweaker instead:<br />
<br />
print(<tile.chest>.displayName); // prints the original name<br />
<tile.chest>.displayName = "Storage Box";<br />
<br />
That's all it takes!<br />
<br />
Note that there exist some mod items with broken internal names. These cannot have their names modified with this method. Neither can they be modified through translation files, and as such these mod items should be considered bugged. If NEI is installed, you can still use the NEI.overrideName function, which will change the name in most places.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Vanilla&diff=1213Vanilla2025-08-21T00:17:37Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>#REDIRECT [[ModTweaker:Vanilla_Support]]</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=ZenCode_specification&diff=1225ZenCode specification2025-08-21T00:17:37Z<p>Aizistral: 11 revisions imported</p>
<hr />
<div>ZenCode is a multi-purpose scripting and programming language intended for a far wider use than just MineTweaker. In future, the scripting system will be hosted on a separate website, but for now, its complete specification will be available here.<br />
<br />
= Introduction =<br />
<br />
The purpose of ZenCode is to make it possible for non-programmers (or programmers with little experience) to use a simple scripting language while allowing more experienced programmers to take advantage of all the speed and features offered by modern object-oriented languages. Currently, ZenCode compiles at runtime to java bytecode, but in future, other target platforms should be supported.<br />
<br />
The idea of ZenCode is that it can be used by a wide range of people. While experienced programmers can easily understand every detail that goes on under the hood, less experienced programmers and non-programmers could simply follow the tutorials and magically "have everything work" without having to bother about the details. For instance, ZenCode can be written with or without specifying data types. When used without types, the scripting engine can infer the types in most cases and use runtime-typed values in cases where it couldn't. It wouldn't be optimal in terms of speed, but it would work without having to teach the non-programmer all the details about everything in the language.<br />
<br />
Meanwhile, more advanced programmers can specify types for those places where it can't be inferred, know everything that goes on under the hood, and write code that's both fast and clean. They would be able to write their advanced logic and make it available in the form of easily used APIs for less experienced users. This is particularly interesting in the modding world, where there is a mix of users with different skill levels. Making a Minecraft mod requires knowledge of both Java and Forge, which can be hard to learn for a non-programmer. However, many people would like to make simple modifications to the game - modifications that are difficult to provide with a graphical user interface. A scripting language would be needed, but shouldn't need a user to know what classes and interfaces, be aware of the difference between a float and double or about the language's casting rules.<br />
<br />
= Scripts =<br />
<br />
ZenCode projects are organized as a set of scripts (ending with the .zs extension). Each script may contain:<br />
<br />
- Code statements, such as function and method calls, variable assignments and control flow statements<br />
- Function definitions<br />
- Class, interface, struct and enum definitions<br />
- Include statements for other scripts<br />
<br />
Additionally, at the beginning of a script, a package declaration can be provided. Adding a package declaration makes any public and exported functions available to other scripts. If there is no package declaration, every declaration will only be visible to the script itself.<br />
<br />
Example script 1: (prints the text "Hello world")<br />
<br />
var text = "Hello world";<br />
print(text);<br />
<br />
Example script 2: (makes a function add publicly available in the package myserver.util)<br />
<br />
package myserver.util;<br />
<br />
export function add(x, y)<br />
{<br />
return x + y;<br />
}<br />
<br />
Example script 3: (includes a second script)<br />
<br />
package myserver.util;<br />
<br />
include "otherscript.zsi";<br />
<br />
[[File:grammar_script.png]]<br />
<br />
[[File:grammar_importedscript.png]]<br />
<br />
[[File:grammar_scriptelement.png]]<br />
<br />
= Types =<br />
<br />
ZenCode knows the following types:<br />
<br />
* All signed types as available in java: byte, short, int, long<br />
* Unsigned variants of these type: ubyte, ushort, uint, ulong<br />
* Two floating-point types: float and double<br />
* The string type: string<br />
* Arrays; <type>[]<br />
* Associative arrays (dictionaries, maps): <valuetype>[<keytype>]<br />
* Classes: can contain fields, methods and operators, can extend a superclass, and implement any number of interfaces<br />
* Interfaces: can contain interface methods and static methods, implement other interfaces and provide default implementations for some of its methods<br />
* Structs: value types grouping a number of fields - can contain methods but can't extend classes or implement interfaces<br />
* The special type void, indicating "no value"<br />
<br />
Classes and interfaces can have generic type parameters.<br />
<br />
== Primitive types ==<br />
<br />
The following primitive types are available:<br />
<br />
* byte: signed integer value, can contain values from -128 to 127<br />
* short: signed integer value, can contain values from -32768 to 32767<br />
* int: signed integer value, can contain values from –2147483648 to 2147483647<br />
* long: signed integer value, can contain values from -9223372036854775808 to 9223372036854775807<br />
* ubyte: unsigned integer value, can contain values from 0 to 255<br />
* ushort: unsigned integer value, can contain values from 0 to 65535<br />
* uint: unsigned integer value, can contain values from 0 to 4294967295<br />
* ulong: unsigned integer value, can contain values from 0 to 18446744073709551615<br />
* float: contains a single-precision floating-point value<br />
* double: contains a double-precision floating-point value<br />
* char: contains a single unicode character<br />
* string: contains a string value (supports any unicode character)<br />
* void: means the same as "no value", cannot contain any value but used to indicate that a method doesn't return a value<br />
<br />
== Arrays ==<br />
<br />
Arrays (lists) contain a series of values. Arrays can be constructed with the array expression (e.g. [value1, value2]) and can be nested.<br />
<br />
A single-dimensional array type can be defined by adding [] to its base type:<br />
<br />
- ubyte[] defines an array of unsigned bytes (essentially a bytestream)<br />
- int[] defines an array of signed ints<br />
<br />
Two kinds of multidimensional arrays can be defined:<br />
<br />
- int[][] defines a two-dimensional array of integers. Each element in the outer array can be of different length, for example [[1, 2], [3, 4, 5]] is a correct value. Each element of the outer array is a reference to a smaller array.<br />
- int[,] defines a rectangular array. For example, [[1, 2, 3], [4, 5, 6]] would be a valid rectangular array but [[1, 2], [3, 4, 5]] isn't. Internally, there is only one array.<br />
<br />
Arrays can be modified after creation:<br />
<br />
var array = [];<br />
array += ["Hello"];<br />
<br />
To make an array unmodifyable, use the .fixed accessor:<br />
<br />
var array = [1, 2].fixed;<br />
<br />
== Associative Arrays ==<br />
<br />
Being a very common structure, the ability to define dictionaries mapping values of one type to values of another type is a first-class language feature in ZenCode. They are called associative arrays and can be created with the {} notation.<br />
<br />
== The any type ==<br />
<br />
A special type exists called "any". This is a dynamically typed value. Any value can be cast to the any type. When a value has been cast to any, all fields and methods will be kept - the value will keep the exact same behavior as the original value.<br />
<br />
Variables of the any type are not statically checked: accessing methods or fields that do not actually exist will result in a runtime exception.<br />
<br />
The any values can also be cast to its original type, as well as any of its superclasses or implemented interfaces, without needing an explicit cast. Trying to pass an invalid value will throw an exception as soon as it is converted.<br />
<br />
== Type handling ==<br />
<br />
Specifying the type of a variable, field or function parameter is always optional. The type will be inferred from its initialization value whenever possible and will default to the any type when unspecified.<br />
<br />
Types and generic type arguments will be inferred from their context whenever possible. In a return statement, the type will be inferred from the method in which it resides and in a function call the method parameters are inferred from tje function being called (if there are no overloaded methods).<br />
<br />
For arrays and associative arrays for which no type can be inferred, any[] and any[any] will be used by default. This means that creating an array of a specific type requires the following construct:<br />
<br />
var myArray = ["Hello", "world"] as string[];<br />
<br />
But if the type can be inferred, this is not needed:<br />
<br />
doStrings(["Hello", "world"]);<br />
<br />
Arrays can be passed to functions if the array base type is different. When such conversion is made, the converted array will always reflect the values in the original array: if the original is modified, the converted array will return the new values. If both base types can be converted to each other, the resulting array will be read-write. If not, the array will be read-only. Conversion between the array values is performed only when needed. This means that conversion errors will come up only when the values are actually being accessed:<br />
<br />
function printInts(values as int[])<br />
{<br />
for element in values {<br />
println(element);<br />
}<br />
}<br />
<br />
var myArray = [1, "Hello"];<br />
printInts(myArray);<br />
<br />
The code above will print 1 and then crash, complaining that "Hello" is not an int value.<br />
<br />
Likewise, consider the following example:<br />
<br />
functions addValues(values as any[])<br />
{<br />
values += [1];<br />
values += ["Hi"];<br />
}<br />
<br />
var myArray = [] as int[];<br />
addValues(myArray);<br />
<br />
This snippet will successfully add 1 to the array but crash when "Hi" is added to it, complaining that "Hi" cannot be converted to an int.<br />
<br />
This kind of behavior makes it possible to write a script quickly without ever having to bother about types whereas more complex applications, APIs and performance-critical code can use a static type system.<br />
<br />
= Statements =<br />
<br />
The traditional statements can be used in scripts and function bodies:<br />
<br />
var a = 1; // declares a variable a and intitalizes it to 1. The variable type is int.<br />
val b = 2; // same as above, except b cannot be modified after initialization<br />
a = 10;<br />
if a > 2 { // conditional execution. No brackets needed.<br />
print("a is greater that 2");<br />
}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Advanced_Recipes&diff=1121Tutorial:Advanced Recipes2025-08-21T00:17:36Z<p>Aizistral: 13 revisions imported</p>
<hr />
<div>So far we have learned about how to add or remove simple recipes. But what if the inputs and outputs also involve damage values or NBT tags?<br />
<br />
== NBT Tag in output ==<br />
<br />
It is possible to define both damage or an NBT tag as output. Let's take a pickaxe as our toy for this tutorial:<br />
<br />
val stick = <minecraft:stick>;<br />
val pick = <minecraft:stone_pickaxe>;<br />
val damagedPick = pick.withDamage(10);<br />
val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});<br />
<br />
recipes.addShaped(damagedPick, [[pick, stick]<nowiki>]</nowiki>);<br />
recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);<br />
<br />
Crafting the pick with 1 or 3 sticks as in the recipe will give you an item with the appropriate damage and name/lore on it, respectively.<br />
<br />
== Input conditions ==<br />
<br />
You can also require the input to contain certain NBT tags. Say, you make a recipe that requires our sticked pick. Let's modify our file:<br />
<br />
val stick = <minecraft:stick>;<br />
val pick = <minecraft:stone_pickaxe>;<br />
val damagedPick = pick.withDamage(10);<br />
val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});<br />
<br />
recipes.addShaped(damagedPick, [[pick, stick]<nowiki>]</nowiki>);<br />
recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);<br />
<br />
val stonedPick = pick.withTag({display: {Name: "Stoned pick", Lore: ["This pick", "Has been experimenting too much"]}});<br />
val onlyStickedPick = pick.onlyWithTag({display: {Name: "Sticked pick"}});<br />
val cobble = <minecraft:cobblestone>;<br />
recipes.addShaped(stonedPick, [[onlyStickedPick, cobble], [cobble, cobble]]);<br />
<br />
What about the lore part in our sticked pick? Since your condition only contains the name, the lore part is ignored - when setting a condition on the data tag, MineTweaker only cares about the contents that you specified and ignores everything else.<br />
<br />
'''''Note the difference between withTag and onlyWithTag. withTag is for an output and is the exact tag that will be output. onlyWithTag is for input and sets a condition. Applying withTag on an input has no effect on the recipe.'''''<br />
<br />
Other conditions exist too:<br />
<br />
myItem.onlyDamaged(); // only accepts damaged items<br />
myItem.onlyDamageAtLeast(15); // only accepts items with a damage of at least 15<br />
myItem.onlyDamageAtMost(100); // only accepts items with a damage of at most 100<br />
myItem.onlyDamageBetween(15, 100); // only accepts items with a damage between 15 and 100<br />
<br />
Multiple conditions can be added to a single ingredient, too:<br />
<br />
myItem.onlyDamaged().onlyWithTag({display: {Name: "Sticked pick"}});<br />
<br />
== Output reuse and transformations ==<br />
<br />
Since MineTweaker 3.0.2, it is now possible to reuse items, return empty buckets to the crafting grid (or whatever item you want) or damage items upon crafting.<br />
<br />
We could for instance make a recipe to get more sticks out of wood by using an axe:<br />
<br />
recipes.addShapeless(<minecraft:stick> * 3, [<minecraft:stone_axe>, <ore:woodPlanks>]);<br />
<br />
Nice. But the stone axe gets consumed, and that is sort of annoying. We can fix this with the reuse modifier:<br />
<br />
recipes.addShapeless(<minecraft:stick> * 3, [<minecraft:stone_axe>.reuse(), <ore:plankWood>]);<br />
<br />
Great! We can reuse the axe. Now what if we also wanted the axe to be damaged when you use it?<br />
<br />
recipes.addShapeless(<minecraft:stick> * 3, [<minecraft:stone_axe>.transformDamage(), <ore:plankWood>]);<br />
<br />
We can also deal more than 1 damage upon crafting:<br />
<br />
recipes.addShapeless(<minecraft:stick> * 3, [<minecraft:stone_axe>.transformDamage(4), <ore:plankWood>]);<br />
<br />
Imagine we'd want to make a recipe to turn dirt into grass by combining dirt, a water bucket and wheat. We could make this recipe:<br />
<br />
recipes.addShapeless(<minecraft:grass>, [<minecraft:dirt>, <minecraft:water_bucket>, <minecraft:wheat>]);<br />
<br />
However, crafting this will consume the bucket. We can tell MineTweaker to return the empty bucket afterwards:<br />
<br />
recipes.addShaped(<minecraft:grass>, [[<br />
<minecraft:dirt>,<br />
<minecraft:water_bucket>.transformReplace(<minecraft:bucket>),<br />
<minecraft:wheat><br />
]]);<br />
<br />
Now, crafting a grass block will return the empty crafting bucket in the crafting grid.<br />
<br />
Sometimes mods define their own behavior when you use their items while crafting. Likewise, Minecraft will return you an empty bucket when you use it in a crafting recipe. If you don't want that, you can tell the item to not return anything at all:<br />
<br />
recipes.addShaped(<minecraft:grass>, [[<br />
<minecraft:dirt>,<br />
<minecraft:water_bucket>.noReturn(),<br />
<minecraft:wheat><br />
]]);<br />
<br />
If you want to give something back, but not in the crafting inventory, you can also use giveBack. GiveBack can be used without arguments, in which case it will return the original item, or it can be used with an item, in which case that item will be given back into the player inventory:<br />
<br />
recipes.addShaped(<minecraft:grass>, [[<br />
<minecraft:dirt>,<br />
<minecraft:water_bucket>.giveBack(<minecraft:iron_ore> * 3),<br />
<minecraft:wheat><br />
]]);<br />
<br />
GiveBack will usually also have the side-effect of suppressing mod item return behavior. It may thus be a handy alternative to the transformReplace modifier in those cases.<br />
<br />
== Function recipes ==<br />
<br />
When adding a recipe, you may also supply an additional argument, which is a custom function. This function can programmatically determine the output of your recipe.<br />
<br />
To demonstrate how this works, let's make a recipe that repairs a stone pickaxe when you craft it with cobblestone. The output of our recipe depends on the pickaxe that is provided (its damage), thus a regular recipe won't work in this case.<br />
<br />
Let's start by adding the function to it:<br />
<br />
recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>, <minecraft:cobblestone>], function(output, inputs, crafting) {<br />
// to be implemented<br />
}<br />
<br />
Now we need to look at the value of the pickaxe. In order to retrieve the actual values of the inputs, we need to mark them with a name, and MineTweaker will store it in the inputs list:<br />
<br />
recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {<br />
// to be implemented. inputs.pick now contains the pickaxe used as input<br />
}<br />
<br />
Then it's just a matter of writing the code to fix the pickaxe:<br />
<br />
recipes.addShapeless(<minecraft:stone_pickaxe>, [<minecraft:stone_pickaxe>.anyDamage().marked("pick"), <minecraft:cobblestone>], function(output, inputs, crafting) {<br />
// the max is there to make sure that the damage doesn't go negative<br />
// fixes 25 damage per cobblestone<br />
return inputs.pick.withDamage(max(0, inputs.pick.damage - 25));<br />
});<br />
<br />
More will come to function recipes later!</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Advanced_Recipes_164&diff=1126Tutorial:Advanced Recipes 1642025-08-21T00:17:36Z<p>Aizistral: 4 revisions imported</p>
<hr />
<div>So far we have learned about how to add or remove simple recipes. But what if the inputs and outputs also involve damage values or NBT tags?<br />
<br />
== NBT Tag in output ==<br />
<br />
It is possible to define both damage or an NBT tag as output. Let's take a pickaxe as our toy for this tutorial:<br />
<br />
val stick = <item.stick>;<br />
val pick = <item.pickaxeStone>;<br />
val damagedPick = pick.withDamage(10);<br />
val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});<br />
<br />
recipes.addShaped(damagedPick, [[pick, stick]]);<br />
recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);<br />
<br />
Crafting the pick with 1 or 3 sticks as in the recipe will give you an item with the appropriate damage and name/lore on it, respectively.<br />
<br />
== Input conditions ==<br />
<br />
You can also require the input to contain certain NBT tags. Say, you make a recipe that requires our sticked pick. Let's modify our file:<br />
<br />
val stick = <item.stick>;<br />
val pick = <item.pickaxeStone>;<br />
val damagedPick = pick.withDamage(10);<br />
val stickedPick = pick.withTag({display: {Name: "Sticked pick", Lore: ["This pick", "Has been sticked"]}});<br />
<br />
recipes.addShaped(damagedPick, [[pick, stick]]);<br />
recipes.addShaped(stickedPick, [[pick, stick], [stick, stick]]);<br />
<br />
val stonedPick = pick.withTag({display: {Name: "Stoned pick", Lore: ["This pick", "Has been experimenting too much"]}});<br />
val onlyStickedPick = pick.onlyWithTag({display: {Name: "Sticked pick"}});<br />
val cobble = <tile.stonebrick>;<br />
recipes.addShaped(stonedPick, [[onlyStickedPick, cobble], [cobble, cobble]]);<br />
<br />
What about the lore part in our sticked pick? Since your condition only contains the name, the lore part is ignored - when setting a condition on the data tag, MineTweaker only cares about the contents that you specified and ignores everything else.<br />
<br />
'''''Note the difference between withTag and onlyWithTag. withTag is for an output and is the exact tag that will be output. onlyWithTag is for input and sets a condition. Applying withTag on an input has no effect on the recipe.'''''<br />
<br />
Other conditions exist too:<br />
<br />
myItem.onlyDamaged(); // only accepts damaged items<br />
myItem.onlyDamageAtLeast(15); // only accepts items with a damage of at least 15<br />
myItem.onlyDamageAtMost(100); // only accepts items with a damage of at most 100<br />
myItem.onlyDamageBetween(15, 100); // only accepts items with a damage between 15 and 100<br />
<br />
Multiple conditions can be added to a single ingredient, too:<br />
<br />
myItem.onlyDamaged().onlyWithTag({display: {Name: "Sticked pick"}});<br />
<br />
== Output reuse and transformations ==<br />
<br />
Since MineTweaker 3.0.2, it is now possible to reuse items, return empty buckets to the crafting grid (or whatever item you want) or damage items upon crafting.<br />
<br />
We could for instance make a recipe to get more sticks out of wood by using an axe:<br />
<br />
recipes.addShapeless(<item.stick> * 3, [<item.hatchetStone>, <ore:woodPlanks>]);<br />
<br />
Nice. But the stone axe gets consumed, and that is sort of annoying. We can fix this with the reuse modifier:<br />
<br />
recipes.addShapeless(<item.stick> * 3, [<item.hatchetStone>.reuse(), <ore:plankWood>]);<br />
<br />
Great! We can reuse the axe. Now what if we also wanted the axe to be damaged when you use it?<br />
<br />
recipes.addShapeless(<item.stick> * 3, [<item.hatchetStone>.transformDamage(), <ore:plankWood>]);<br />
<br />
We can also deal more than 1 damage upon crafting:<br />
<br />
recipes.addShapeless(<item.stick> * 3, [<item.hatchetStone>.transformDamage(4), <ore:plankWood>]);<br />
<br />
Imagine we'd want to make a recipe to turn dirt into grass by combining dirt, a water bucket and wheat. We could make this recipe:<br />
<br />
recipes.addShapeless(<tile.grass>, [<tile.dirt>, <item.bucketWater>, <item.wheat>]);<br />
<br />
However, crafting this will consume the bucket. We can tell MineTweaker to return the empty bucket afterwards:<br />
<br />
recipes.addShaped(<tile.grass>, [[<br />
<tile.dirt>,<br />
<item.bucketWater>.transformReplace(<item.bucket>),<br />
<item.wheat><br />
]]);<br />
<br />
Now, crafting a grass block will return the empty crafting bucket in the crafting grid.<br />
<br />
Sometimes mods define their own behavior when you use their items while crafting. Likewise, Minecraft will return you an empty bucket when you use it in a crafting recipe. If you don't want that, you can tell the item to not return anything at all:<br />
<br />
recipes.addShaped(<minecraft:grass>, [[<br />
<tile.dirt>,<br />
<item.bucketWater>.noReturn(),<br />
<item.wheat><br />
]]);<br />
<br />
If you want to give something back, but not in the crafting inventory, you can also use giveBack. GiveBack can be used without arguments, in which case it will return the original item, or it can be used with an item, in which case that item will be given back into the player inventory:<br />
<br />
recipes.addShaped(<minecraft:grass>, [[<br />
<tile.dirt>,<br />
<item.bucketWater>.giveBack(<item.ingotIron> * 3),<br />
<item.wheat><br />
]]);<br />
<br />
GiveBack will usually also have the side-effect of suppressing mod item return behavior. It may thus be a handy alternative to the transformReplace modifier in those cases.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Basic_Recipes&diff=1139Tutorial:Basic Recipes2025-08-21T00:17:36Z<p>Aizistral: 12 revisions imported</p>
<hr />
<div>== Using MineTweaker RecipeMaker ==<br />
<br />
If you want to create or remove recipes without having to code, you can also check out this nice mod by DoubleDoorDevelopment: http://minecraft.curseforge.com/mc-mods/226294-minetweaker-recipemaker<br />
<br />
== Using recipe notation ==<br />
<br />
The most basic modifications you can perform in MineTweaker are recipe addition and removal. There is no visual editor, only a scripting language, so you have to understand how to write your recipes as text.<br />
<br />
In order to define its functionality, you have to call functions. An example function is print, which you have seen before, and which takes a single argument:<br />
<br />
print("My text");<br />
<br />
This was easy. A more useful function, for instance, is the function to add a shaped recipe:<br />
<br />
recipes.addShaped('''recipe output''', '''recipe contents''');<br />
<br />
This line essentially means "call the addShaped function on the recipes object". The recipes object is a special object that is available from anywhere in your code and contains all the functions related to adding and removing crafting recipes. Note that only crafting recipes are managed by the recipes object - furnace recipes, for instance, are managed by the furnace object (which you will learn about in a later tutorial) and mods machines have yet different methods to manage recipes.<br />
<br />
Now, how do we call the addShaped function with proper arguments? We need to tell it what the output should be and what the recipe should be like.<br />
<br />
Let's take, for instance, the recipe for iron leggings, which is this one:<br />
<br />
[[File:recipe_leggings_iron.png]]<br />
<br />
The MineTweaker notation for this recipe is the following one:<br />
<br />
[[<minecraft:iron_ingot>, <minecraft:iron_ingot>, <minecraft:iron_ingot>],<br />
[<minecraft:iron_ingot>, null, <minecraft:iron_ingot>],<br />
[<minecraft:iron_ingot>, null, <minecraft:iron_ingot>]]<br />
<br />
This may look cryptic if you haven't been programming before, but the principle is quite simple. You can visualize the recipe as follows:<br />
<br />
[[File:recipe_leggings_iron_brackets.png]]<br />
<br />
Each item in minetweaker has its own name - surrounded by the angled brackets to tell it "retrieve me the item with this name". This angled bracket notation will be used in many places - from retrieving items to ore dictionary entries to liquid names. The item name for the iron ingot is <minecraft:iron_ingot> and iron leggings is <minecraft:iron_leggings>.<br />
<br />
What about the empty spots? You cannot just skip the entries - you have to put something to indicate "this is empty". MineTweaker has a special word for such objects, and it's "null".<br />
<br />
We can thus define the leggings recipe with the following code:<br />
<br />
recipes.addShaped(<minecraft:iron_leggings>,<br />
[[<minecraft:iron_ingot>, <minecraft:iron_ingot>, <minecraft:iron_ingot>],<br />
[<minecraft:iron_ingot>, null, <minecraft:iron_ingot>],<br />
[<minecraft:iron_ingot>, null, <minecraft:iron_ingot>]]);<br />
<br />
Or you can split the line differently for readability, since MineTweaker doesn't care how you split your code into lines. You could also retrieve the iron ingot once, assign it to a variable and then reuse it, as will be described at the end of this tutorial.<br />
<br />
= Basic Recipes =<br />
<br />
There is no visual editor, so you have to understand how to write your recipes as text.<br />
<br />
As a little introduction, let's consider the recipe for sticks. In vanilla minecraft, it takes 2 wood planks to make 4 sticks, and they have to put above each other. But what if we want to change that? What if, say, we find it more logical to put the two wood block diagonally instead? (this stick is diagonal, right?)<br />
<br />
Modifying the sticks recipe is wonderfully easy. Make a script with the following contents:<br />
<br />
recipes.remove(<minecraft:stick>);<br />
recipes.addShaped(<minecraft:stick> * 4, [[<minecraft:planks>, null], [null, <minecraft:planks>]]);<br />
<br />
Open a new game (or reload scripts, if you are already in a game). Now take 2 oak wood planks and test your recipe.<br />
<br />
It works? Great! But now you may have noticed a flaw in the recipe: if you put birch or spruce wood, it doesn't work!<br />
<br />
Why doesn't it work? The "planks" item has subitems that are distinguished by not only the item name, but also by its meta value. By default, if you retrieve an item with the bracket syntax, MineTweaker assumes you want the item with meta value 0. And that's what it returned - the "oak planks" item. But we want an ingredient which essentially means "any kind of wood".<br />
<br />
Luckily, this is easy to fix. When using the bracket syntax, besides the name, we can also define a meta value. For instance, <code><minecraft:planks:1></code> refers to spruce wood. We can also use the wildcard (*) to get an item meaning "any meta value is good": <code><minecraft:planks:*></code>.<br />
<br />
Thus, change your recipe and reload:<br />
<br />
recipes.remove(<minecraft:stick>);<br />
recipes.addShaped(<minecraft:stick> * 4, [[<minecraft:planks:*>, null], [null, <minecraft:planks:*>]]);<br />
<br />
Fixed! Of course, you should use the ore dictionary entry for planks, which would be even better as it would be compatible with mod-added planks :)<br />
<br />
If need the full name of an item, you can hold it in your hand and use the /minetweaker hand command. It will print the name and copy it to the clipboard, so you can just paste it directly in your script.<br />
<br />
== Other kinds of recipes ==<br />
<br />
Shaped recipes are recipes where the ingredients must be placed in the right shape in order for it to work. Not all Minecraft recipes are shaped - some don't care about the shape. MineTweaker supports those with the addShapeless function:<br />
<br />
recipes.addShapeless(<minecraft:stick> * 4, [<ore:plankWood>, <ore:plankWood>]);<br />
<br />
Now it doesn't matter how you place your planks - you can always craft sticks. Note that in this example, though, you can no longer craft the wooden pressure plate.<br />
<br />
Since 3.0.7, it's also possible to register mirrored recipes. Continuing with our sticks (make sure to remove the previous recipes first):<br />
<br />
recipes.addShapedMirrored(<minecraft:stick> * 4, [[<minecraft:planks:*>, null], [null, <minecraft:planks:*>]]);<br />
<br />
Now it doesn't matter if you mirror the recipe - it still works!<br />
<br />
== Specific recipe removal ==<br />
<br />
So far we decided that we would be removing all recipes for the stick. In vanilla minecraft, there is also only one, so that's not an issue. But what if we want to be more specific? Often there are multiple recipes for the same item, and we may want to remove one yet keep the others.<br />
<br />
It is possible to be more specific in that case:<br />
<br />
recipes.removeShaped(<minecraft:stick>, [[<minecraft:planks:*>], [<minecraft:planks:*>]]);<br />
<br />
This will remove only a single recipe - even if there are other recipes.<br />
<br />
It is also possible to remove all recipes that are shaped, or all recipes that are shapeless, by simply calling:<br />
<br />
recipes.removeShaped(<minecraft:stick>);<br />
recipes.removeShapeless(<minecraft:stick>);<br />
<br />
Also, wildcard patterns can be used to indicate that any kind of item would match for a certain position, as long as it's not empty:<br />
<br />
recipes.removeShaped(<minecraft:stick>, [[<*>], [<*>]]);<br />
<br />
Likewise, when removing shapeless recipes, it is possible to only specify one or more ingredients of the shapeless recipe and then tell minetweaker that the remainder of the recipe may contain anything:<br />
<br />
recipes.removeShapeless(<minecraft:wool:*>, [<minecraft:wool>]); // removes all wool coloring recipes<br />
<br />
== Subitems and damage values ==<br />
<br />
Quite often, items have multiple subitems. A very well-known example are coal and charcoal. Both have the same ID (minecraft:coal) but have a different meta value.<br />
<br />
When loading an item, you can specify the meta value for the subitem:<br />
<br />
var coal = <minecraft:coal:0>; // same as <minecraft:coal><br />
var charcoal = <minecraft:coal:1>;<br />
<br />
When the subitem is not specified, :0 is filled in for the subitem.<br />
<br />
If you want a recipe to match any subitem, you can use the wildcard syntax:<br />
<br />
var anyCoal = <minecraft:coal:*>;<br />
<br />
<br />
Many kinds of items can also be damaged. When using such item as ingredient for a recipe, by default, no damage is allowed. For instance:<br />
<br />
var pick = <minecraft:stone_pickaxe>;<br />
var iron = <minecraft:iron_ingot>;<br />
// upgrade pick recipe :)<br />
recipes.addRecipe(<minecraft:iron_pickaxe>, [[iron, iron, iron], [null, pick, null]]);<br />
<br />
In the recipe above, a damaged pickaxe would not be accepted. This can be changed easily with the .anyDamage() modifier:<br />
<br />
var pick = <minecraft:stone_pickaxe>.anyDamage();<br />
var iron = <minecraft:iron_ingot>;<br />
// upgrade pick recipe :)<br />
recipes.addShaped(<minecraft:iron_pickaxe>, [[iron, iron, iron], [null, pick, null]]);<br />
<br />
== Reloading and recipes ==<br />
<br />
When you reloaded the scripts, you may have noticed that if you reloaded a script, the recipe is not duplicated. Likewise, if a recipe addition is removed from the script and the script is reloaded, the recipe is effectively removed from the game even though there may be no statement explicitly requesting such removal.<br />
<br />
MineTweaker remembers actions such as recipe addition and removal. When a script is reloaded (or loaded by joining a different server), MineTweaker will first undo all the recorded changes that were made before it executes the new script.<br />
<br />
Many mod machines, however, do not support such recipe removal. In that case, the recipe will be "stuck" in the game until the entire game is reloaded. For a server, this means that the recipe will be stuck in the list until the server is restarted; for a client, it means that the recipe will be shown and acted upon as if it existed, though when a crafting attempt is made, actual crafting would fail. There is no fix to such behavior; it is up to the respective mod authors to provide a sufficient API to ensure that recipe removal is possible.<br />
<br />
== Using variables ==<br />
<br />
Do you find yourself looking up the same item over and over again using the bracket syntax? It may be handy to remember the value for later; which can be done with the val and var statements:<br />
<br />
val stick = <minecraft:stick>;<br />
val planks = <minecraft:planks:*>;<br />
recipes.remove(stick);<br />
recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);<br />
<br />
In this example, var can be used to:<br />
<br />
var stick = <minecraft:stick>;<br />
var planks = <minecraft:planks:*>;<br />
recipes.remove(stick);<br />
recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);<br />
<br />
The difference between var and val is that a val cannot be modified after it is declared:<br />
<br />
val stick = <minecraft:stick>;<br />
stick = <minecraft:bread>; // fails</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Basic_Recipes_164&diff=1144Tutorial:Basic Recipes 1642025-08-21T00:17:36Z<p>Aizistral: 4 revisions imported</p>
<hr />
<div>= Basic Recipes =<br />
<br />
The most basic modifications you can perform in MineTweaker are recipe addition and removal.<br />
<br />
As a little introduction, let's consider the recipe for sticks. In vanilla minecraft, it takes 2 wood planks to make 4 sticks, and they have to put above each other. But what if we want to change that? What if, say, we find it more logical to put the two wood block diagonally instead? (this stick is diagonal, right?)<br />
<br />
Modifying the sticks recipe is wonderfully easy. Make a script with the following contents:<br />
<br />
recipes.remove(<item.stick>);<br />
recipes.addShaped(<item.stick> * 4, [[<tile.wood>, null], [null, <tile.wood>]]);<br />
<br />
Open a new game (or reload scripts, if you are already in a game). Now take 2 oak wood planks and test your recipe.<br />
<br />
It works? Great! But now you may have noticed a flaw in the recipe: if you put birch or spruce wood, it doesn't work!<br />
<br />
Why doesn't it work? The "tile.wood" item has subitems that are distinguished by not only the item name, but also by its meta value. By default, if you retrieve an item with the bracket syntax, MineTweaker assumes you want the item with meta value 0. And that's what it returned - the "oak planks" item. But we want an ingredient which essentially means "any kind of wood".<br />
<br />
Luckily, this is easy to fix. When using the bracket syntax, besides the name, we can also define a meta value. For instance, <code><tile.wood:1></code> refers to spruce wood. We can also use the wildcard (*) to get an item meaning "any meta value is good": <code><tile.wood:*></code>.<br />
<br />
Thus, change your recipe and reload:<br />
<br />
recipes.remove(<item.stick>);<br />
recipes.addShaped(<item.stick> * 4, [[<tile.wood:*>, null], [null, <tile.wood:*>]]);<br />
<br />
Fixed! Of course, you should use the ore dictionary entry for planks, which would be even better as it would be compatible with mod-added planks :)<br />
<br />
== Other kinds of recipes ==<br />
<br />
Shaped recipes are recipes where the ingredients must be placed in the right shape in order for it to work. Not all Minecraft recipes are shaped - some don't care about the shape. MineTweaker supports those with the addShapeless function:<br />
<br />
recipes.addShapeless(<item.stick> * 4, [<ore:plankWood>, <ore:plankWood>]);<br />
<br />
Now it doesn't matter how you place your planks - you can always craft sticks. Note that in this example, though, you can no longer craft the wooden pressure plate.<br />
<br />
Since 3.0.7, it's also possible to register mirrored recipes. Continuing with our sticks (make sure to remove the previous recipes first):<br />
<br />
recipes.addShapedMirrored(<item.stick> * 4, [[<ore:plankWood>, null], [null, <ore:plankWood>]]);<br />
<br />
Now it doesn't matter if you mirror the recipe - it still works!<br />
<br />
== Specific recipe removal ==<br />
<br />
So far we decided that we would be removing all recipes for the stick. In vanilla minecraft, there is also only one, so that's not an issue. But what if we want to be more specific? Often there are multiple recipes for the same item, and we may want to remove one yet keep the others.<br />
<br />
It is possible to be more specific in that case:<br />
<br />
recipes.removeShaped(<item.stick>, [[<tile.wood:*>], [<tile.wood:*>]]);<br />
<br />
This will remove only a single recipe - even if there are other recipes.<br />
<br />
It is also possible to remove all recipes that are shaped, or all recipes that are shapeless, by simply calling:<br />
<br />
recipes.removeShaped(<item.stick>);<br />
recipes.removeShapeless(<item.stick>);<br />
<br />
Also, wildcard patterns can be used to indicate that any kind of item would match for a certain position, as long as it's not empty:<br />
<br />
recipes.removeShaped(<item.stick>, [[<*>], [<*>]]);<br />
<br />
Likewise, when removing shapeless recipes, it is possible to only specify one or more ingredients of the shapeless recipe and then tell minetweaker that the remainder of the recipe may contain anything:<br />
<br />
recipes.removeShapeless(<tile.cloth:*>, [<tile.cloth>]); // removes all wool coloring recipes<br />
<br />
Don't be fooled by the item name - it is the wool block.<br />
<br />
== Subitems and damage values ==<br />
<br />
Quite often, items have multiple subitems. A very well-known example are coal and charcoal. Both have the same ID (item.coal) but have a different meta value.<br />
<br />
When loading an item, you can specify the meta value for the subitem:<br />
<br />
var coal = <item.coal:0>; // same as <item.coal><br />
var charcoal = <item.coal:1>;<br />
<br />
When the subitem is not specified, :0 is filled in for the subitem.<br />
<br />
If you want a recipe to match any subitem, you can use the wildcard syntax:<br />
<br />
var anyCoal = <item.coal:*>;<br />
<br />
<br />
Many kinds of items can also be damaged. When using such item as ingredient for a recipe, by default, no damage is allowed. For instance:<br />
<br />
var pick = <item.pickaxeStone>;<br />
var iron = <item.ingotIron>;<br />
// upgrade pick recipe :)<br />
recipes.addRecipe(<item.pickaxeIron>, [[iron, iron, iron], [null, pick, null]]);<br />
<br />
In the recipe above, a damaged pickaxe would not be accepted. This can be changed easily with the .anyDamage() modifier:<br />
<br />
var pick = <item.pickaxeStone>.anyDamage();<br />
var iron = <item.ingotIron>;<br />
// upgrade pick recipe :)<br />
recipes.addShaped(<item.pickaxeIron>, [[iron, iron, iron], [null, pick, null]]);<br />
<br />
== Reloading and recipes ==<br />
<br />
When you reloaded the scripts, you may have noticed that if you reloaded a script, the recipe is not duplicated. Likewise, if a recipe addition is removed from the script and the script is reloaded, the recipe is effectively removed from the game even though there may be no statement explicitly requesting such removal.<br />
<br />
MineTweaker remembers actions such as recipe addition and removal. When a script is reloaded (or loaded by joining a different server), MineTweaker will first undo all the recorded changes that were made before it executes the new script.<br />
<br />
Many mod machines, however, do not support such recipe removal. In that case, the recipe will be "stuck" in the game until the entire game is reloaded. For a server, this means that the recipe will be stuck in the list until the server is restarted; for a client, it means that the recipe will be shown and acted upon as if it existed, though when a crafting attempt is made, actual crafting would fail. There is no fix to such behavior; it is up to the respective mod authors to provide a sufficient API to ensure that recipe removal is possible.<br />
<br />
== Using variables ==<br />
<br />
Do you find yourself looking up the same item over and over again using the bracket syntax? It may be handy to remember the value for later; which can be done with the val and var statements:<br />
<br />
val stick = <item.stick>;<br />
val planks = <tile.wood:*>;<br />
recipes.remove(stick);<br />
recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);<br />
<br />
In this example, var can be used too:<br />
<br />
var stick = <item.stick>;<br />
var planks = <tile.wood:*>;<br />
recipes.remove(stick);<br />
recipes.addShaped(stick * 4, [[planks, null], [null, planks]]);<br />
<br />
The difference between var and val is that a val cannot be modified after it is declared:<br />
<br />
val stick = <item.stick>;<br />
stick = <item.bread>; // fails<br />
<br />
== Using item IDs ==<br />
<br />
Find yourself having issues with Item IDs? You can still use the old bracket syntax with item IDs, but only in the 1.6.4 version:<br />
<br />
var rottenFlesh = <367>;<br />
var charcoal = <263:1>;</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Control_Structures&diff=1151Tutorial:Control Structures2025-08-21T00:17:36Z<p>Aizistral: 6 revisions imported</p>
<hr />
<div>The MineTweaker scripting engine (ZenScript) is still under heavy development. Control structures are currently only partially implemented, but it is already possible to use looping structures to aid you in your development.<br />
<br />
When we make use of looping structures, we generally have to store some variables first. When storing items or ingredients into variables, you never had to worry about item types. Likewise, when you use arrays or dictionaries in recipes or tag values, you could just provide the right syntax and everything worked.<br />
<br />
However, MineTweaker is *strongly typed*. As long as it can infer the type from your expression, you don't have to provide any typing information, but when you declare such a thing as an array it won't work anymore. This would fail:<br />
<br />
var myItems = [<minecraft:stick>, <minecraft:stone>];<br />
<br />
The problem is that MineTweaker doesn't know your array type. It did in all the examples given before, since it could infer the array type from the function you were calling, but when you assign it to a variable it can't do that since it doesn't know your type yet. To fix this, you need to cast the array to a specific type, as such:<br />
<br />
import minetweaker.item.IItemStack;<br />
<br />
var myItems = [<minecraft:stick>, <minecraft:stone>] as IItemStack[];<br />
<br />
IItemStack is the type that you get when you resolve an item variable such as <minecraft:stick>. IItemStack denotes a specific object and can be used either as a crafting ingredient or as crafting output, as you very likely already did.<br />
<br />
Its friends is IIngredient, which is more general than an item. Ore dictionary entries, for instance, are ingredients. They cannot be used as output, but they can be used as input for crafting. Additionally, if you add transformations or conditions to an IItemStack, it will become an IIngredient:<br />
<br />
import minetweaker.item.IIngredient;<br />
<br />
var myIngredients = [<ore:plankWood>, <minecraft:stick>.onlyWithTag({display:{Name: "Something"}})] as IIngredient[];<br />
var myIngredients2 = [<minecraft:stick>, <ore:plankWood>] as IIngredient[]; // will work since an IItemStack can be casted to an IIngredient<br />
<br />
When you define arrays of items, you can use looping operators on them to make your scripts shorter. For instance, let's say we want default log to wood recipes to have low yield yet improve it when crafting it with axes, and have the type of axe determine the amount of planks we have:<br />
<br />
import minetweaker.item.IItemStack;<br />
<br />
var myLogs = [<minecraft:log:0>, <minecraft:log:1>, <minecraft:log:2>, <minecraft:log:3>, <minecraft:log:4>, <minecraft:log:5>] as IItemStack[];<br />
var myPlanks = [<minecraft:planks:0>, <minecraft:planks:1>, <minecraft:planks:2>, <minecraft:planks:3>, <minecraft:planks:4>, <minecraft:planks:5>] as IItemStack[];<br />
<br />
var stoneAxe = <minecraft:stone_axe>.anyDamage().transformDamage();<br />
var ironAxe = <minecraft:iron_axe>.anyDamage().transformDamage();<br />
var goldenAxe = <minecraft:golden_axe>.anyDamage().transformDamage();<br />
var diamondAxe = <minecraft:diamond_axe>.anyDamage().transformDamage();<br />
<br />
for i, log in myLogs {<br />
var plank = myPlanks[i];<br />
<br />
recipes.removeShapeless(plank, [log]);<br />
recipes.addShapeless(plank * 2, [log]);<br />
recipes.addShapeless(plank * 3, [log, stoneAxe]);<br />
recipes.addShapeless(plank * 4, [log, ironAxe]);<br />
recipes.addShapeless(plank * 5, [log, goldenAxe]);<br />
recipes.addShapeless(plank * 6, [log, diamondAxe]);<br />
}<br />
<br />
Now you can put all of your mod-added planks into the array, as well as their logs, and have the for loop do the heavy lifting for you!<br />
<br />
Sometimes you may find the need to assign NBT tags inside a for loop. You can define an NBT value in a variable outside the loop, but only when you cast it to IData. IData is the datatype for an NBT tag. Expanding our former example a little bit:<br />
<br />
import minetweaker.data.IData;<br />
import minetweaker.item.IItemStack;<br />
<br />
var myData = {display: {Name: "Axed plank"}} as IData;<br />
var myLogs = [<minecraft:log:0>, <minecraft:log:1>, <minecraft:log:2>, <minecraft:log:3>, <minecraft:log:4>, <minecraft:log:5>] as IItemStack[];<br />
var myPlanks = [<minecraft:planks:0>, <minecraft:planks:1>, <minecraft:planks:2>, <minecraft:planks:3>, <minecraft:planks:4>,<minecraft:planks:5>] as IItemStack[]; <br />
<br />
var stoneAxe = <minecraft:stone_axe>.anyDamage().transformDamage();<br />
var ironAxe = <minecraft:iron_axe>.anyDamage().transformDamage();<br />
var goldenAxe = <minecraft:golden_axe>.anyDamage().transformDamage();<br />
var diamondAxe = <minecraft:diamond_axe>.anyDamage().transformDamage();<br />
<br />
for i, log in myLogs {<br />
var plank = myPlanks[i].withTag(myData);<br />
<br />
recipes.removeShapeless(plank, [log]);<br />
recipes.addShapeless(plank * 2, [log]);<br />
recipes.addShapeless(plank * 3, [log, stoneAxe]);<br />
recipes.addShapeless(plank * 4, [log, ironAxe]);<br />
recipes.addShapeless(plank * 5, [log, goldenAxe]);<br />
recipes.addShapeless(plank * 6, [log, diamondAxe]);<br />
}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Control_Structures_164&diff=1153Tutorial:Control Structures 1642025-08-21T00:17:36Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>The MineTweaker scripting engine (ZenScript) is still under heavy development. Control structures are currently only partially implemented, but it is already possible to use looping structures to aid you in your development.<br />
<br />
When we make use of looping structures, we generally have to store some variables first. When storing items or ingredients into variables, you never had to worry about item types. Likewise, when you use arrays or dictionaries in recipes or tag values, you could just provide the right syntax and everything worked.<br />
<br />
However, MineTweaker is *strongly typed*. As long as it can infer the type from your expression, you don't have to provide any typing information, but when you declare such a thing as an array it won't work anymore. This would fail:<br />
<br />
var myItems = [<280>, <1>];<br />
<br />
The problem is that MineTweaker doesn't know your array type. It did in all the examples given before, since it could infer the array type from the function you were calling, but when you assign it to a variable it can't do that since it doesn't know your type yet. To fix this, you need to cast the array to a specific type, as such:<br />
<br />
import minetweaker.item.IItemStack;<br />
<br />
var myItems = [<280>, <1>] as IItemStack[];<br />
<br />
IItemStack is the type that you get when you resolve an item variable such as <minecraft:stick>. IItemStack denotes a specific object and can be used either as a crafting ingredient or as crafting output, as you very likely already did.<br />
<br />
Its friends is IIngredient, which is more general than an item. Ore dictionary entries, for instance, are ingredients. They cannot be used as output, but they can be used as input for crafting. Additionally, if you add transformations or conditions to an IItemStack, it will become an IIngredient:<br />
<br />
import minetweaker.item.IIngredient;<br />
<br />
var myIngredients = [<ore:plankWood>, <280>.onlyWithTag({display:{Name: "Something"}})] as IIngredient[];<br />
var myIngredients2 = [<280>, <ore:plankWood>] as IIngredient[]; // will work since an IItemStack can be casted to an IIngredient<br />
<br />
When you define arrays of items, you can use looping operators on them to make your scripts shorter. For instance, let's say we want default log to wood recipes to have low yield yet improve it when crafting it with axes, and have the type of axe determine the amount of planks we have:<br />
<br />
import minetweaker.item.IItemStack;<br />
<br />
var myLogs = [<17:0>, <17:1>, <17:2>, <17:3>, <17:0>, <17:1>] as IItemStack[];<br />
var myPlanks = [<5:0>, <5:1>, <5:2>, <5:3>, <5:4>, <5:5>] as IItemStack[];<br />
<br />
var stoneAxe = <275>.anyDamage().transformDamage();<br />
var ironAxe = <258>.anyDamage().transformDamage();<br />
var goldenAxe = <286>.anyDamage().transformDamage();<br />
var diamondAxe = <279>.anyDamage().transformDamage();<br />
<br />
for i, log in myLogs {<br />
var plank = myPlanks[i];<br />
<br />
recipes.removeShapeless(plank, [log]);<br />
recipes.addShapeless(plank * 2, [log]);<br />
recipes.addShapeless(plank * 3, [log, stoneAxe]);<br />
recipes.addShapeless(plank * 4, [log, ironAxe]);<br />
recipes.addShapeless(plank * 5, [log, goldenAxe]);<br />
recipes.addShapeless(plank * 6, [log, diamondAxe]);<br />
}<br />
<br />
Now you can put all of your mod-added planks into the array, as well as their logs, and have the for loop do the heavy lifting for you!<br />
<br />
Sometimes you may find the need to assign NBT tags inside a for loop. You can define an NBT value in a variable outside the loop, but only when you cast it to IData. IData is the datatype for an NBT tag. Expanding our former example a little bit:<br />
<br />
import minetweaker.data.IData;<br />
import minetweaker.item.IItemStack;<br />
<br />
var myData = {display: {Name: "Axed plank"}} as IData;<br />
var myLogs = [<17:0>, <17:1>, <17:2>, <17:3>, <17:0>, <17:1>] as IItemStack[];<br />
var myPlanks = [<5:0>, <5:1>, <5:2>, <5:3>, <5:4>, <5:5>] as IItemStack[];<br />
<br />
var stoneAxe = <275>.anyDamage().transformDamage();<br />
var ironAxe = <258>.anyDamage().transformDamage();<br />
var goldenAxe = <286>.anyDamage().transformDamage();<br />
var diamondAxe = <279>.anyDamage().transformDamage();<br />
<br />
for i, log in myLogs {<br />
var plank = myPlanks[i].withTag(myData);<br />
<br />
recipes.removeShapeless(plank, [log]);<br />
recipes.addShapeless(plank * 2, [log]);<br />
recipes.addShapeless(plank * 3, [log, stoneAxe]);<br />
recipes.addShapeless(plank * 4, [log, ironAxe]);<br />
recipes.addShapeless(plank * 5, [log, goldenAxe]);<br />
recipes.addShapeless(plank * 6, [log, diamondAxe]);<br />
}</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Control_Structurs&diff=1155Tutorial:Control Structurs2025-08-21T00:17:36Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>#REDIRECT [[Tutorial:Control Structures]]</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Furnace&diff=1159Tutorial:Furnace2025-08-21T00:17:36Z<p>Aizistral: 3 revisions imported</p>
<hr />
<div>MineTweaker also allows modifying furnace recipes and furnace fuels using a few simple commands.<br />
<br />
Do you believe smelting ores in a furnace is too easy? You can fix it as such:<br />
<br />
furnace.remove(<minecraft:gold_ingot>);<br />
<br />
// alternatively, you can specify the input item<br />
furnace.remove(<*>, <minecraft:iron_ore>);<br />
<br />
Found it sad you can't turn charcoal into real coal? Easy fix:<br />
<br />
furnace.addRecipe(<minecraft:coal:0>, <minecraft:coal:1>);<br />
<br />
// or, if you want to generate 0.5 XP by doing so<br />
furnace.addRecipe(<minecraft:coal:0>, <minecraft:coal:1>, 0.5);<br />
<br />
Want to make items burnable? Set their fuel value wit the setFuel function:<br />
<br />
furnace.setFuel(<minecraft:rotten_flesh>, 100);<br />
<br />
The same method can be used to set existing fuel - EXCEPT for vanilla fuels since those are, sadly, hard-coded. Additionally (with the exception of vanilla fuels) you can remove fuels by setting their fuel value to 0.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Furnace_164&diff=1161Tutorial:Furnace 1642025-08-21T00:17:36Z<p>Aizistral: 1 revision imported</p>
<hr />
<div>MineTweaker also allows modifying furnace recipes and furnace fuels using a few simple commands.<br />
<br />
Do you believe smelting ores in a furnace is too easy? You can fix it as such:<br />
<br />
furnace.remove(<item.ingotIron>);<br />
<br />
// alternatively, you can specify the input item<br />
furnace.remove(<*>, <tile.oreIron>);<br />
<br />
Found it sad you can't turn charcoal into real coal? Easy fix:<br />
<br />
furnace.addRecipe(<item.coal:0>, <item.coal:1>);<br />
<br />
// or, if you want to generate 0.5 XP by doing so<br />
furnace.addRecipe(<item.coal:0>, <item.coal:1>, 0.5);<br />
<br />
Want to make items burnable? Set their fuel value wit the setFuel function:<br />
<br />
furnace.setFuel(<item.rottenFlesh>, 100);<br />
<br />
The same method can be used to set existing fuel - EXCEPT for vanilla fuels since those are, sadly, hard-coded. Additionally (with the exception of vanilla fuels) you can remove fuels by setting their fuel value to 0.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Introduction&diff=1170Tutorial:Introduction2025-08-21T00:17:36Z<p>Aizistral: 8 revisions imported</p>
<hr />
<div>= Introduction =<br />
<br />
Ever went into building a modpack and then found that just throwing in a bunch of mods didn't give you an integrated experience? As mods are developed relatively independently from each other, one may feel overpowered in comparison to the other. Or you may believe that there would be a better recipe for some of the items. Or perhaps you'd want to remove an item from the game without having to remove the entire mod. Or you may discover that some ore dictionary entries have too many or too few items. Now you can do all of that - each with just a single instruction to MineTweaker.<br />
<br />
In addition to the core functionality provided to support Vanilla minecraft, mod integration libraries are provided with the mod to enable you to not only modify vanilla recipes, but also the mod machine recipes and mod behavior.<br />
<br />
== Scripts ==<br />
<br />
To make the functionality available in a clear and concise manner, a custom scripting language is provided. The language is easy to learn - and for basic operations you can just follow the tutorials.<br />
<br />
For multiplayer games, scripts are always stored server-side. That means you will never have to worry about keeping scripts up-to date with your friends! This makes MineTweaker a great modpack and server admin tool - it makes it possible to wrap a modpack with a certain set of mods and have different servers use MineTweaker to alter the details according to the preferences of the server owners.<br />
<br />
Likewise, scripts can be bundled with worlds, making it possible to make modifications available to specific worlds only - handy if you want to do some playtesting in a certain world. Also handy for mapmakers wanting to have specific behavior programmed with their map.<br />
<br />
MineTweaker has two script directories:<br />
* The shared script directory: the scripts directory, directly inside your minecraft directory. Scripts stored in this directory will apply to all worlds hosted by that minecraft instance - including Single-player games. They will NOT apply when you join another server, as scripts are always loaded from the server.<br />
* The world-specific script directory: this directory is also called scripts, but is stored in the savegame directory (world/scripts if you are setting up a dedicated server)<br />
<br />
Inside these directories, any file with the '''.zs''' extension is considered a MineTweaker script and will be ran automatically when a game is started. Any number of script files can be stored in these directories - they will all be executed, in no particular order.<br />
<br />
== Writing a first script ==<br />
<br />
To get used to the scripting system in MineTweaker, we can create a very basic file. Create a file hello.zs in your .minecraft/scripts directory (create it if it doesn't already exist) with the following line:<br />
<br />
print("Hello world!");<br />
<br />
Now open Minecraft and start a new game (or open an existing one).<br />
<br />
The script should have run now. Now where did MineTweaker print its text?<br />
<br />
== The Minetweaker log ==<br />
<br />
When you put a print statement in MineTweaker, it will output to the minetweaker.log file in your minecraft directory. Open this log and you should see the output:<br />
<br />
INFO: Hello world!<br />
<br />
Cool, huh? Although printing a test string to the log is not so interesting in and by itself, it is good to know that any errors and warnings will print to this file. Additionally, many in-game commands output to this file since the in-game console simply cannot hold much data.<br />
<br />
Do you still have the game open? Try the following command in the in-game console:<br />
<br />
/minetweaker names<br />
<br />
This command dumps a list of each and every item in the game to the minetweaker log. If you have a lot of mods installed, expect a huge list. But since it outputs to the log, you can open the file with your favorite editor and search for a specific item name. (still stuck with Notepad? Try notepad++!)<br />
<br />
== Reloading ==<br />
<br />
While developing, there is no need to restart minecraft for every change you are making. You can reload scripts in-game.<br />
<br />
Change your printed text to something else, such as:<br />
<br />
print("Hello guys!");<br />
<br />
Now, in-game, enter the command <tt>/minetweaker reload</tt>.<br />
<br />
This will append the following line in the MineTweaker log:<br />
<br />
INFO: Hello guys!<br />
<br />
MineTweaker reloaded your scripts from disk and executed it again. Handy! There is more to script reloading, as it will not only reload the script but also any recipes that have been changed. More about that in the next tutorial.<br />
<br />
== Comments ==<br />
<br />
To document your scripts, MineTweaker supports 3 styles of comments:<br />
<br />
// this is a single line comment<br />
# this is a single line comment<br />
/* this is<br />
a<br />
multiline comment */<br />
<br />
Use these to make your scripts more understandable!</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Item_Renaming&diff=1174Tutorial:Item Renaming2025-08-21T00:17:36Z<p>Aizistral: 3 revisions imported</p>
<hr />
<div>Not happy with an item name? Want to correct a <strike>type</strike> typo made by the mod author? Did some translation go missing?<br />
<br />
Although a resource pack can fix that, it may be less cumbersome to use MineTweaker instead:<br />
<br />
print(<minecraft:chest>.displayName); // prints the original name<br />
<minecraft:chest>.displayName = "Storage Box";<br />
<br />
That's all it takes!<br />
<br />
Note that there exist some mod items with broken internal names. These cannot have their names modified with this method. Neither can they be modified through translations files, and as such these mod items should be considered bugged. If NEI is installed, you can still use the NEI.overrideName function, which will change the name in most places.<br />
<br />
<br />
Unlike most script types, renaming requires a client restart, and not simply a script reload.</div>Aizistralhttps://minetweaker3.aizistral.com/index.php?title=Tutorial:Localization&diff=1179Tutorial:Localization2025-08-21T00:17:36Z<p>Aizistral: 4 revisions imported</p>
<hr />
<div>Since MineTweaker 3.0.8, it is possible to change localization strings.<br />
<br />
Two variants of the function exist - one that sets the translation no matter the current language, and one that overrides a translation but only when the given language matches the current language:<br />
<br />
// Set translation but only if language is en_US<br />
game.setLocalization("en_US", "nei.inventory.prev", "Past");<br />
<br />
//KEY, TEXT - You will want to use this one most of the time, it overrides no matter the language<br />
game.setLocalization("nei.inventory.next", "Future");<br />
<br />
To find localizations, check the localization files in the assets of Minecraft or the mods you want to alter.</div>Aizistral