At points of clarity, I realize that my life on earth is meaningless, and that I am merely a pawn in a bigger game. A game I cannot possible understand or have control of. Thankfully, before depression sets in, I drift back into my cloudy, bewildered daily routine.
- Joel Patrick Warneke
It's been a while, but RM4DF isn't dead - it's just pining for the fjords! This version has a few minor fixes, and some new features on the back-end that build on existing functionality. I've also devised a (admittedly a kludge) solution to URL-filtering preventing dynamic signatures from being used, for those who need the feature. Basically, now you can deep-link the cached image and force RM4DF to refresh the image cache each time the roster's updated, rather than doing it on-demand (which is more efficient).
Enjoy!
Roster Master for Dragonfly (RM4DF) 6.3.1:
Get it and development news from the RM4DF Project Page. - Fixed horizontal avatar margins when LEFT alignment directive is used. Bug reported and fixed by Seagoat.
- Added "Optimize Tables" administrative command to delete all widowed and orphaned claims all at once.
- Added Rise of Kunark Raid Flagging Timeline to the Access Quest Tracker.
- Added link to cached signature image (when it is present in the cache) to the Edit Character Claim page. This is to help people work around URL filtering that some CMSes perform.
- The reap_sigcache() function now checks the cache for files that are excluded by the $config['exclude_ranks'] array.
- Added "Fill Signature Block Cache" administrative command to pregenerate the signature block cache for all valid characters.
- CONFIG CHANGE: Added $config['force_sig_cache'] directive to allow the selective regeneration of the signature block cache to be forced every time the roster data is updated. NOTE: Using this feature may cause Roster Master to exceed the maximum script execution time (see source for explanation)
- CONFIG CHANGE: Roster Master no longer allows upgrades from versions older than 6.0.0 (Any versions prior to 6.2.0 aren't functional due to the EQ2Players structure changes anyway.) Users upgrading from a version prior to 6.0.0 must uninstall the previous version, then install 6.3.1. NOTE: Character claims will not be preserved (as per a fresh install).