Elliot,
Yes that would seem to explain the issue. I appreciate you fixing the bug in the next release.
Thanks Devin for reporting this issue as well.
The plugin folder name starts with “custom”, so it should run after ACF. I’m assuming active plugins are loaded alphabetically by there folder name.