Maybe it might be good to error if there are unknown fields

[XeroOl]

I'm not sure if I want to make this change or not.

Sometimes, it's possible that a user mistypes a key, or isn't aware of what keys should be present in which modes. For example, let's look at func:

func {0, function() end, plr = 1}

Func doesn't have a player, so plr= is a bad key here. Currently, it's silently ignored, but func could be changed to cause an error.

This has the potential to make it clearer to people what is going on, but it also might not be good style. I'd love some feedback on what the best practices are.

[NarrikSynthfox]

I'd say error, but only in edit mode, and let the rest of the code still run as well and provide a variable that can be set if someone wants to ignore the warning if they really want to instead of fixing it, as long as it won't cause any issues when actually playing the file.