In this update I added the strict field in the main plugin config.yml. The strict field defaults to true when no field is provided. When using the plugin, you may want to execute abilities that do not share a common ability context, now in previous versions, this simply was not possible and you would be given a warning in console, this is no longer the case. If the strict field is set to false, it will replace any missing fields will fallback values to make sure the ability can execute smoothly, this being said, it may result in unintended interactions and is unsafe, so it is highly suggested to keep the strict field as true if possible.