You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems a few maps contain tags that have invalid values for the selected functions, likely caused by past HEK+ extraction. It just so happens these values don't cause the game to crash on Halo Custom Edition, but can crash other versions of the game. tool.exe does not check these either and will build the invalid tags into maps.
Here is an example; map [1] was used as a source for map [2], and in map [2] the tag characters/marine_armored/flashlight_marine.light became corrupted.
Interesting. Yeah, that isn't particularly great. I'll talk with @MosesofEgypt about implementing a descriptor keyword option for fields that tells the enum_sanitizer to set out of bound values back to default.
It seems a few maps contain tags that have invalid values for the selected functions, likely caused by past HEK+ extraction. It just so happens these values don't cause the game to crash on Halo Custom Edition, but can crash other versions of the game. tool.exe does not check these either and will build the invalid tags into maps.
Here is an example; map [1] was used as a source for map [2], and in map [2] the tag
characters/marine_armored/flashlight_marine.light
became corrupted.[1]http://maps.halonet.net/maps/beryl.zip
[2]http://maps.halonet.net/maps/Beryl_Rescue.zip
The text was updated successfully, but these errors were encountered: