The newer versions of BMBF use a different algorithm to determine if a song pushed to the Quest is “new” or not. Previously, when you made an edit, the new copy would overwrite the other. Now? BMBF sees your level change and makes it a NEW song! So you edit for an hour, get under the Quest and see 40 copies of your song. Worse, you don’t know which one is “the latest” to even test!
The unicorns are aware of the situation and we’re working on a solution.
Meanwhile, 2.9 of BMT will prefix your uploads with an ever-growing number so you can at least see what is the LATEST one. Not ideal – but the only thing we can do until the BMBF issue is addressed.
Roadmap for 3.0 includes the removal of all Beat Map 1.0 song conversion. If you’re not using a Beat Map 2.0 compatible editor (MMA2, Chromaeditor) you’re going to be out of luck. There will be no support for old BeatOn (hopefully nobody is still stuck back that far).
With the addition of 90/360 maps and the community mapper tools not fully supporting these new functions, I’ve spoken with members of the mapping community to find out how I can ease their workflow issues.
Perform various edits on the info.dat (adding difficulties)
Open *.dat file with the 90/360 map and perform search and replace on: “_type”: 12 -> “_type”: 14 “_type”: 13 -> “_type”: 15
Use a Google Spreadsheet to calculate rotational analysis on the map data to figure out which direction the player is facing after each rotational change (ensuring that the map doesn’t spin the “cabled” VR players into a cable-wrap situation)
Quest Folks: Pack and send the map to the Quest for testing.
This was an amazing amount of effort.
With BMT V2.4, we’ve relieved MOST of that manual effort; saving the mappers considerable time and effort (I understand it shaves HALF their mapping time – whooo hooo!).
There are a few more things that could be done to help out, but head over to the Change Log or Download page and get the update.