Alpha Release v3.0.5

[Moon Wizard]

Please see the sticky thread on public testing if you want to be involved. The Dev mode slot (available via the FG Settings dialog) contain this version right now.

Remember, this is an alpha release, which means that features are still being developed, and may change radically.

As always, we're a small company so we rely on our community to help sound out each new release. Thanks in advance to all those who pitch in.

Thanks,
JPG

Note: As always, please make a backup of your FG data folder before updating and opening campaigns with a test release.

[Moon Wizard]

Updates


[CoreRPG+] Campaign data can be viewed and managed through the new Journal button, and sidebar buttons customized.
[CoreRPG+] NPC and Encounter records can be shared with players by right click menu, if desired.
Lighting command (/lighting) with empty parameter will black out screen. Empty parameter ignored. Fixed.
Scrollbar buttons for long lists and text fields are hard to grab. Set minimum size for scrollbar buttons. Fixed.
When right clicking while dragging tokens, tokens would remain ghosted sometimes. Fixed.
Clicking on link text in locked or read-only formatted text fields does not activate link. Fixed.
[PFRPG/3.5E] CT attack entry attack and damage rolls not adjusting after manual editing until you change field focus. Fixed.
[PFRPG/3.5E] Skill modifier effect not working for multi-word skills. Fixed.
[DEV] Campaign and registry data saved on reload request.
[DEV] categoryselectioncontrol - Added setTarget function
[DEV] windowlist - Added getChildClass and setChildClass functions; setDatabaseNode parameter updated to accept database paths, in addition to databasenode objects


JPG

[HoloGnome]

Hi MW - Thanks for the bug fixes. Public Testing mode is a good idea. Is there any reason that users can't have a parallel testing install? Based on my earlier install experiments on Windows Server to move the install to a non-admin user context, it looks like the app and data directories can be anywhere. So, the best way to do public testing would seem to be:

1. Install FG
2. Move the app and data directories to a "public test" location
3. Install FG again and use as the main install with the main data directory.
4. Use the 1st install in test mode.

Run 1, run both at the same time to compare - it all should work...I think...(barring licensing conflicts, depending on what you're trying to do)...

Alternately, considering that FG supports public test mode, you could add a secondary data path for public testing and offer the tester the option to use either the main data path or the test data path (solves licensing conflict issue) -- uses test dir by default. That way, no data folder need ever be put at risk, unless the tester wants it that way, and testing would not interfere with other gaming, requiring constant data (or path) swapping.