JPG ruleset updates

[Moon Wizard]

I just posted updates for both the d20_JPG and 4E_JPG rulesets over at the FUM web site.

d20_JPG - Group Site (https://www.fouruglymonsters.com/community/community/groups/viewgroup/62-DD+3rd+Edition+FG+Development)
4E_JPG - Group Site (https://www.fouruglymonsters.com/community/community/groups/viewgroup/49-DD+4th+Edition+FG+Development)

I was originally waiting for the FG 2.4.0 release, but I decided to move ahead. There are no known issues with the current RC4 release of FG 2.4.0 relative to FG 2.3.6. (i.e. Any issues are the same in both versions.)

Thanks,
JPG

[grider]

Thank you for your hard work!!

[Leonal]

Seconded!

Thanks a bunch!

[Zoso]

Thirded!!!

[arnon]

Thanks Moon_wizard :)

[nezzir]

Best ruleset ever made. It has an incredible amount of features.

[feldrol]

I like the possibilities offered by the new 3.5 ruleset. I have yet to find exactly how to use everything.

Last tuesday I ran my weekly campaign using the updated rulesets and I found some weird behaviors (bugs?).

After droping an encouter into the combat tracker, an empty line appeared into the combat tracker, then a second one kept appearing and disappearing every 0.5 seconds or so. When I tried to delete the first empty line, the system slowed to a crawl and freezed.
After stopping and restarting the server the phenomenon kept repeating (empty line in CT and second one, blinking).
When I used the new cross to close the CT, FG2 crashed. I tried three times and had three crashes.

I use 2.3.6 version of FG2, with winxp up to date.

I tried to re-create those issues today with no client connected, but everything is normal.

I will try my next group session with the updated ruleset to check if the 2 issues are reproduced.

[Moon Wizard]

There is a known issue with shared windowlists in FG, where a list which is shared between client and host can sometimes get into an infinite loop state. It seems to be triggered in the JPG rulesets primarily when deleting entries from the CT (which is shared with the clients).

The best thing to do is keep up to date on the latest version of the ruleset and FG. I've continued to add better error handling to avoid the situation as best I can, and SmiteWorks is working on some changes to FG which should also reduce/remove the issue.

Once the infinite loop state has started, the only way to stop the issue is to have all the clients disconnect. It may only be one client that is causing the problem, but there is no way to tell which one.

Regards,
JPG

[feldrol]

Ok, now that you mention it, I indeed had deleted an entry in the CT before it happened.
Since it was the very first time I saw that behavior in more than 40 sessions of play I thought it was the ruleset.

Anyway thanks a lot for your rulesets. They are awesome.

[DNH]

Is it true to say then that even if using FG2.3.6 and 4e_JPG 1.5, you will likely encounter this issue when deleting items from the CT?

[Griogre]

Yes, it is true you may find this issue. I don't know it is likely, though - eventually is probably a better way of saying it. Apprently, you have to do things in a certain way and then delete an entry in the combat tracker. What that sequence of events is I think still up in the air. Once you do that sequence you might have problems the whole session. You can always stop the looping by having the players log out and then restarting the server. Once you restart the server and before the players log in you can clear your tracker without problems. Sometimes having all the players log out is enough. It's not just loops in the combat tracker either, that is just the most common one.

Once you recognize it in the combat tracker you will recognize it elsewhere because it is usually a line appearing and disapearing - it looks the same in other places.

The looping happens in the 4E ruleset also, but the release of FG 2.4 may solve the problem in both rulesets because Moon_Wizard has been able to reproduce something and send it in to Smiteworks.