A Few Fubar Bugs

Hello, it's Eguy here. I have very much been enjoying Fubar lately, but here are a few bugs that I have found.

Firstly, the gem counter and the timer occupy the same space on the screen, and thus overlap each other and make it very hard to see how many gems there are.

Secondly, whenever I play a level, it only registers that I ascended a level when i click the "continue" button. For example, I was on level fifteen. I played the next level, completed it, then replayed it to get a better time, and it still said I was on level fifteen.

Thanks! Eguy

Hi Eguy,

First issue is a duplicate of marbleblast.com/index.php/forum/mbf-beta-feedback/8507-bugs-motd-blocked-by-main-menu-gui-gem-counter-blocked-by-time - I'm working on a UI layout to avoid this and some more customization options in the next build.

Second issue is known, I'm looking into why the level selector is seemingly hitting random levels instead of the next one in your progression (or the next level after the one completed).

~Aayrl

The second issue you mentioned has been resolved in Beta Build 50000+.

The changes are client-side, so now you will always pick up where you left off in each difficulty tier.

I've reconfigured the way the Mission Lists are constructed, so now it will load the last played mission for each difficulty tier (or the highest level in each difficulty tier, if no level was played in a particular difficulty tier.) These levels are saved to your prefs.cs file, so you can wipe them out and reset the menu to the top level in each difficulty tier if you desire.

If you beat a level, and click the "Continue" button, you will be presented with the next level in the difficulty tier series (unless you are at the max for that difficulty tier, in which case the level will remain the same.)

If you beat a level, but choose to replay the level and click the "Replay" button, the game will still log that you have "progressed" to the next level in the series. So, when you exit the level, you will see the next level in the series.

I've implemented the above based on feedback I received from multiple community members, so that seems the be the anticipated behavior. If anyone has any issues with the new implementation, please post a separate bug report / suggestion thread and I'll review it again.

Thanks,
~Aayrl