From 02775e52c43dbc82e08b6af8b87d8f320c05cb73 Mon Sep 17 00:00:00 2001
From: mathiascode <8754153+mathiascode@users.noreply.github.com>
Date: Thu, 24 Aug 2017 12:19:40 +0300
Subject: Minor changes (#3909)

---
 dev-docs/Cubeset file format.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'dev-docs/Cubeset file format.html')

diff --git a/dev-docs/Cubeset file format.html b/dev-docs/Cubeset file format.html
index 6ead2e700..02a1ef861 100644
--- a/dev-docs/Cubeset file format.html	
+++ b/dev-docs/Cubeset file format.html	
@@ -21,7 +21,7 @@
 <p>We're seeing an increased need to store "prefabs" - little areas with predefined block contents, such as village houses or fortress rooms - in collections. We have one collection of village houses for the plains village, one collection for the desert village, one collection for the nether fortress... And there are plans in the future to use even more collections - trees, overworld fortresses, more village types and even custom structures. The point that they have in common is that they need to store not only the prefabs, but also metadata for those prefabs - how often they generate, how they connect together. There's even need for metadata for the entire collection, such as what the accepted biomes are, what block should village roads use, and various other generator parameters. So we need a file format that could store all this information together.</p>
 <p>There are some existing formats available to consider first:
 <ul>
-<li><a href="http://minecraft.gamepedia.com/Schematic_file_format"><b>schematic</b></a> - file format native to MCEdit / Bukkit / WorldEdit communities. Can store the prefab, the block entities and regular entities, and any metadata. Cannot store multiple prefabs. No effort to read or write, there's already code to do that (except for the entities) in the server.</li>
+<li><a href="https://minecraft.gamepedia.com/Schematic_file_format"><b>schematic</b></a> - file format native to MCEdit / Bukkit / WorldEdit communities. Can store the prefab, the block entities and regular entities, and any metadata. Cannot store multiple prefabs. No effort to read or write, there's already code to do that (except for the entities) in the server.</li>
 <li><a href="https://dev.bukkit.org/projects/terrain-control"><b>bob / bo2 / bo3</b></a> - file format created for prefabs in the Terrain Control mod. Can store the prefab and any metadata. Support for block entities and regular entities is unknown. Cannot store multiple prefabs. Medium difficulty for reading and writing, would need new parser and serializer. Unknown (but assumed true) whether the format truly supports any metadata.</li>
 <li><a href="https://github.com/cuberite/cuberite/tree/master/src/Generating/Prefabs"><b>cpp</b></a> - export from our Gallery server directly into C++ source files. Can store the prefab and any metadata, block entities and regular entities currently not implemented but could be added. Very difficult for reading, writing already implemented. Only usable when compiling directly into the server. Can store multiple prefabs and metadata for the entire set.</li>
 </ul>
-- 
cgit v1.2.3