This was fixed yesterday (Monday) morning EST time. Sorry for the trouble, something got overwritten when 2018.1.0f1 got released.