(I think I'll also change the but both are present wording to something a little less clunky`.) The detail string would be ignored for everything apart from incompatibility message generation. This would then generate a message like This plugin is incompatible with Foo's Bar, but both are present.
name: foo.espĭetail: 'A compatibility patch is available ().' For example, if there's a patch available, you could link to the patch in this additional message string. I'm considering adding a new key to the File data structure that would allow another string to be appended to the message, so that additional details about resolving the incompatibility can be provided. Using the display key, a mod name or any other Markdown text can be used instead of the name of the plugin checked for, but while that's helpful for requirement messages (you can supply a link to the required mod that way), it's not so helpful for incompatibility messages.
The moment, incompatibility metadata generates messages of the form This plugin is incompatible with X, but both are present.
