Our Wiki outage has been resolved. Thanks for your patience.

- M R Sachs, Administrator 

As you may have already noticed, the FFRPG Wiki is currently unavailable. The most likely cause is that the database server the Wiki is hosted on has been taken down for maintenance — our past outages have all been due to database maintenance, and this one certainly fits the pattern. We don’t have an ETA for a fix yet, but hopefully things should be back up and running in another day or two.

- M R Sachs, Administrator

After several years of development and countless hours of writing, editing, playtesting, and revising, we’re happy to announce that we finally have completed the Third Edition Core Rulebook. Due to the fact that we anticipate the need for further minor tweaks, editorial fixes, and the like, this release is still being designated as “Beta Complete”, but is effectively the finished product. A formal “final” release with minor corrections will be released in another few months, once people have had a chance to extensively test-drive the game and feedback has started filtering back to us.

The Wiki’s Core Rulebook Page has been updated with links to all the individual chapters, and the Wiki pages themselves will be updated to reflect the new changes over the course of the next few days.

To go along with this release, there’ve have been a few significant changes to the site and boards. “RGI Dev Labs,” “Playtesting,” and “Balance Errata” will be merged into a single section devoted strictly to feedback on the Beta release material. A few days ago the Resources page was updated to cull all the old, outdated material and replace it with convenient download links and explanations of the current crop of player aids and GM tools available in the “Players’ Corner” section of the boards.

I think that about sums it up for this announcement. There’s been so much going on behind the scenes recently that it’s hard to keep track, but today is the pay-off for all that hard work. On behalf of all the RGI Devstaff, I’d like to take this moment to thank you all, the loyal and devoted players and fans that have stuck with us this long. Its been a long and rocky road, and we’re not done yet. But with today’s public release of the Beta phase, we’ve made significant progress forward.

- Sam ”NinjaWeazel” Banner,  Lead Developer

If you are reading this on the main page, our latest technological venture has been successful — we’ve integrated the feed from ReturnerBlog, our Wordpress blog, into the main page. As sporadic as our news ‘updates’ have been in the past, all that’s about to change; in future, expect plenty of posts from developers, GMs, and community members on all things FFRPG in this very space.

- M R Sachs,  Administrator

(or at least The End of Mechanical Revisions)

Yes, friends. It is my good fortune to inform you that as of now (well OK, technically as of a few hours ago, but who is counting, really?), there are no further mechanical revisions planned for Chapter 4. We may still change an ability name here and there, tweak a little flavor text if we feel we must, but as of now the Core jobs and all of their mechanics are done. Today’s revisions saw the Thief getting an update to Steal, Mug, and Detect as well as the obligatory revision to their Expertise formula. Go take a look, and I can only hope that you all out there on the player side of the table are as happy as those of us on the Developer side of the house to see this milestone passed.

- Sam ”NinjaWeazel” Banner,  Lead Developer

Today marks the start of some changes to the Expert category of Jobs in Chapter 4.  Certain Job Abilities will be undergoing an overhaul to bring them in-line with established formulas and game mechanics.  Today’s target:  The Invention Creation System.

Significant changes include:

1. A major overhaul of  Positive and Negative Status mechanics
2. A consequential revision of Triggering parts.
3. A trimming of the Targeting Parts list.
4. Small revisions for clarity and terminology.

Coming up next:  The Engineer gets more of a tune-up.

- Sam ”NinjaWeazel” Banner, Lead Developer