That's a known bug, but thanks for reporting. It seems to me to occur when I've got a template set in its styling tab to use that mana font, but it doesn't normally (so it doesn't have the dependancy). The good news is its just a nag, and doesn't do anything. The bad news is its not going anywhere. I still have the problem too, for example. Sorry.

yeah, that's exactly when it occurs. Honestly, though, I'm not entirely sure why you would choose to have the message in the first place. The only thing I can think of it affecting would be sharing the sets.

Perhaps, a better to do that would be to have a single dialog box with a message like "Some of your cards contain fonts that are not listed as dependencies on their templates. If you intend to share this set, make sure to include the fonts needed." or something like that, perhaps with a list of the offending cards?

The actual intent of the dialog is to alert template makers if they've missed a dependancy. In turn, the purpose of dependancies is to alert users if they try to use a template that requires a mana font or other package they don't have. So, that error isn't actually meant for regular users at all, and isn't something about sets.

As for sharing sets, if a user tries to load a set that uses a template they don't have, those cards that use the missing template just default back to magic-new without any fuss.

Ah...that makes sense. Perhaps then, a developer mode that can be turned on/off? I'm sure there are other errors that fit into that category that could be included.

Well, maybe, but instead of including a developer mode, the error could just be dealt with. Most errors, we as developers are supposed to remove. And this particular one is a bug that needs dealt with. Ideally, there shouldn't be a need for a developer mode. And if there was one, how would it be obvious to amateur templaters that they should turn on "developer mode"?

Ah, I'm sorry. I was under the impression that's more of an intended bug than one that needs to be dealt with. Dev mode would be easy to implement though. Just add it as an option in the Preferences. Anyone who would be interested in template development would most certainly have poked around in the Preferences menu at some point.

I'm not contesting that it would be easy to add - I just don't believe there's a point. Any need for a dev mode should be removed by bug checking and satisfying error messages like that.

This same thing has happened to me, and I posted it in the bug report thread a while back.

I believe the problem stems from the fact that magic-new matches all mana symbol fonts, and so can't list them as dependencies. This is most certainly a program bug - there should be some way (implicit or explicit) to disable this warning.

But because its not actually dependant on any of those mana symbol fonts (as they're all in a package choice field), it shouldn't list them as a missing dependancy. Similar to the overlay stuff I just added. There are bunches of overlays, but none are required, so none are depended upon. That's the bug here - intended behavior (and the behavior in previous versions that featured package choices) was that it didn't count them for dependancies. This was probably broke when Twan made the change for me to get the same behavior for my overlays.

I'll speak my mind again - I don't think its a good idea to allow the warning to be disabled. If you do, amateur template makers could miss dependancies when putting their templates up. That's more work for me, as I'll be the one to clean it up - please don't do it. Unless you plan to be more active, download every template, test them, and post corrections as needed.

Is it possible to have MSE bypass the warning only when you change your mana symbol-font?

Well, ideally it would bypass in similar cases. Like foil layers. Or other things that haven't been developed yet, but would use package choice. And MSE used to do this for symbol-fonts. The source of the trouble just has to be found again.