V2.8, V2.9 and 3.0 Roadmap; Plus, duplicate map uploads to Quest

Worth noting a few things.

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).

BeatMapper Tools V2.4 Release (90/360 Mapper Tools)

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.

Those using Mediocre Map Assistant 2 are performing the following workflows on EACH edit of the map.

  • Duplicate the WIP map folder to edit
  • 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.

BeatMapper Tools V2.2b Released

This is more of a maintenance update to handle 90/360 maps and fix some changes in the mapping scheme parsing.

  • New: Support for 90/360 map recognition.
  • New: App window is now bigger and content scaled a little bit to handle the new 90/360 maps.
  • Fixed: Fixed the song parsing to avoid an issue when _customdata root node is missing (new editors, schema fixes).

Get it here.

Changes to Song Format Validation on BSaber.com

You may be experiencing an error when attempting to upload a song to BSaber.com.

Currently, Mediocre Mapper MK5 doesn’t conform to these new standards (read more about these here).

You will want to change to Mediocre Map Assistant.2. This is a fork of MK5 and has several additional enhancements as well as fixing this info.dat file fix.

I’ll be adding some parsing of the info.dat file to BMT to alert you of invalidity and offer a solution.

Welcome to the new BeatMapper Tools Site!

As you can see, we’ve moved things around a little. Should make it easier to find stuff. I’m still cleaning up a few things, but we should be 100% here shortly.

Big thanks to Maybeemae for helping out during the move!

If you’re a mapper or a tester (or both), you will want to register here. I have some exciting features coming in BMT that will use this code and your user name to provide new services!

Make sure you fill out the Secret Mapper Code under your Profile:

You will probably want to enter your BeastSaber Username as well – I’ll be tying some functionality to that as well in the future.