Update several todo comments
This commit is contained in:
+1
@@ -44,6 +44,7 @@ import java.util.concurrent.locks.ReentrantReadWriteLock;
|
||||
* since it stringifies every block and biome name, which is quite bulky.
|
||||
* It might be worth while to have a biome and block ID that then both get mapped
|
||||
* to the data point ID to reduce file size.
|
||||
* And/or it would be good to dynamically remove IDs that aren't currently in use.
|
||||
*
|
||||
* @author Leetom
|
||||
*/
|
||||
|
||||
+1
-1
@@ -35,7 +35,7 @@ public abstract class AbstractNewDataSourceHandler
|
||||
*
|
||||
* @see AbstractNewDataSourceHandler#MIN_SECTION_DETAIL_LEVEL
|
||||
*/
|
||||
public static final byte TOP_SECTION_DETAIL_LEVEL = DhSectionPos.SECTION_MINIMUM_DETAIL_LEVEL + LodUtil.REGION_DETAIL_LEVEL; // TODO add "section" to detail level
|
||||
public static final byte TOP_SECTION_DETAIL_LEVEL = DhSectionPos.SECTION_MINIMUM_DETAIL_LEVEL + LodUtil.REGION_DETAIL_LEVEL;
|
||||
/**
|
||||
* The lowest numerical detail level possible.
|
||||
*
|
||||
|
||||
+2
-1
@@ -156,7 +156,8 @@ public class FullDataFileHandlerV2
|
||||
@Override
|
||||
protected FullDataSourceV2 createNewDataSourceFromExistingDtos(DhSectionPos pos)
|
||||
{
|
||||
// TODO maybe just set children update flags to true?
|
||||
// TODO maybe just set children update flags to true?
|
||||
// TODO is any special logic necessary? All DTOs should be generated using their children via the update system anyway
|
||||
return FullDataSourceV2.createEmpty(pos);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user