Update

Well what a week this has been.

Last Friday I found out that the host of the Pathbuilder 1e online shared builds database had messed up a server migration.  My database was left with most of its data and tables missing. I immediately released an update which temporarily closed down those functions on the app. However, to do this I had to update the app to androidx to comply with google requirements.  Reports start coming in that the stat increase radio buttons and traits were missing. Google have got a bug with androidx where inflated linear layouts don't keep their weight in certain conditions. So I had to fix that and release two more updates over the weekend. 

Most of this week was spend restoring that database to its new location pathbuilder2e.com/legacy.  It's a pretty massive database, with 11,000 shared builds and a number of other huge tables of data, so none of the usual methods of importing a database would work.  I had to learn how to use SSH remote access and do it via command line. I then had to update all the php scripts and app calls to those php scripts and test those. I'm not great with any of that web or database stuff, so it was slow progress.

On top of that I also realised that the Pathbuilder 1e backup and restore function was no longer working due to google deprecating the library it depended upon (to be fair they did warn me about this and like the Steward of Gondor, I did nothing), so I also spent a day repogramming that with the new code.  

Finally, just to do something positive I also added Omdura and its archetypes to Pathbuilder 1e.

I also released a publish for Pathbuilder 2e I've been working on for the last two weeks with a number of improvements including language selection dialog, options from APs, megafauna companions, folders for local storage, weapon trait filters for damage buffs, temporary hp buff system, armored skirt option, misc bug fixes.

Next week:

More work on Pathbuilder 1e. I want to fix its file system to use an sql database rather than the random noob madness it relies upon at the moment. This would leave the character database intact if a user reinstalls the app, provide a faster load experience, and fix and issue where the app crashes if you have more than 300 builds.