This error only existed on a faulty build I placed up for about 5 minutes, then was immediately replaced with the current build of v0.13.1. Redownloading that will fix the issue.
