From af639918b925427239c30989aa61af868dd57c8e Mon Sep 17 00:00:00 2001 From: Justin Aquadro Date: Tue, 2 Jul 2013 21:40:57 -0400 Subject: [PATCH] Any new fields (including compound subfields) need to be either OPTIONAL or CREATE_ON_MISSING. Only entries that are part of a compound when it is first introduced need not be optional. --- SubstrateCS/Source/Level.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SubstrateCS/Source/Level.cs b/SubstrateCS/Source/Level.cs index 671e174..5da3205 100644 --- a/SubstrateCS/Source/Level.cs +++ b/SubstrateCS/Source/Level.cs @@ -159,7 +159,7 @@ namespace Substrate new SchemaNodeScaler("initialized", TagType.TAG_BYTE, SchemaOptions.OPTIONAL), new SchemaNodeScaler("allowCommands", TagType.TAG_BYTE, SchemaOptions.OPTIONAL), new SchemaNodeScaler("DayTime", TagType.TAG_LONG, SchemaOptions.OPTIONAL), - new SchemaNodeCompound("GameRules") + new SchemaNodeCompound("GameRules", SchemaOptions.OPTIONAL) { new SchemaNodeScaler("commandBlockOutput", TagType.TAG_STRING), new SchemaNodeScaler("doFireTick", TagType.TAG_STRING),