User blog:Pgrobban/Crystal Calculator 2.0 beta

Hi everyone, It's beta time for the new version of my Crystal Calculator web app. For those of you who didn't read my last post, it's a somewhat redesigned page with code re-written from scratch.

Please note

 * This is a beta version, so expect (and please report!) any bugs.
 * I still haven't added minification for the code, which means the first time you load the page, the browser will load all the files and images (5-10 MB). Mobile users without unlimited data plans, please be aware of this or use wi-fi.

What's new in this version

 * Treasure data is now saved, so all your treasures will remain the next time you visit the page.
 * Recommendation engine is now in place. Unlike the previous version, this one only lists the top 3 treasures to upgrade instead of top 5. The reason for this is that I'm planning a redesign of this table so that it can perhaps be integrated with the result bar at the bottom.
 * A few more Certificate Treasures have been added.
 * A few more Trophy Treasures have been added (please help fill in this page!)
 * Fixed a bug that made icons huge in Firefox.
 * Fixed a bug that caused recalculations sometimes failing after deleting a Certificate or Trophy treasure.

The link for the new version is the same as it was for the alpha:

Please see the previous post for areas that I'm looking for feedback on, but if you have any other comments as well, I'd be happy to hear them.

Expect a full release within the next 2-3 weeks.

Edit: There seems to be a bug when saving Certificate and Trophy treasures. This problem does not appear for me when testing the site locally, it only appears on Github. I'm investigating the cause.

Edit 2: I still haven't been able to locate the cause of the above-mentioned bug, but I have implemented a few changes in the code to make it somewhat more stable. If you experience the bug, try changing one value in your Chest treasures (like +9 to +8 and back again), it should trigger a recalculation of all remaining treasures. I'm really sorry for the inconvenience and I will try my best to fix it before the final release.

Edit 3: I completely rewrote parts of the code dealing with calculating the results into a separate module for easier testing. The bug should now finally be resolved and saving should work as intended. Sorry for the inconvenience.