I understand your frustration. The issue is already being addressed in the upcoming 0.1.0 update. Since this update is quite large, releasing a separate hotfix isn’t really feasible right now. The update is in its final stage, so it shouldn’t be long. Thanks for your patience
