I'd decided that I'd had enough of re-inventing the wheel when it comes to hashing passwords. Previously, my engine came with a roll-your-own password hashing system that, whilst it worked, it wasn't the more secure option. So, I've switched to PHP's very own password_hash().
The good thing is, if you were using the passHash() function I originally supplied with MTG Engine, you can simply overwrite the files that require password input (currently, auth.php, settings.php and signup.php) with the new system and the old hashes will work - why? Simply said, because of the way I designed the previous hashing system. It was, more or less, identical to how PHP handles it.
So why change? Ah, well that's simple; PHP's constantly evolving! With each new iteration of code released, the methodologies change. That includes how PHP handled hashes.
All-in-all, when it comes to PHP, their own tried-and-tested password hashing method is the way to go. 1-way algorithms for the win!