Skip to content

Custom LCF header parsing fails for strings with values >= 0x80 #413

Description

The following game uses a character upper than 7-bit ASCII for a similar approach to "RM Protection Utility" (overwriting "LcfMapTree", "LcfDataBase" and "LcfMapUnit", but likely tailored to display the game name there.
This tool only uses 7-bit ASCII, so all games using this kind of "protection" are not affected.

elvespell.zip

liblcf uses ReadString to compare the value, and 0x80 and upper are affected by the ReadString BER parsing, so this game fails when doing the comparison. A possible solution would be a string comparison without ReadString.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions