FG III and Savage Worlds :(

[Doswelk]

One of my players had upgraded to 3.0 before connecting to my game tonight, so of course he could not join us.

So we all upgraded.

Unless you really need to I would suggest you stay on FGII 2.9x right now, too many things are broken by 3.0

I am sure that PW and Ikael will have them fix sooner rather tan later, but tonight we observed:

Damage dice not always exploding.
Combat Tracker targeting not working
My custom Adventure deck not working

I disabled all of IKael's extensions before connecting (assuming they would not work), so not tried those.

[Hector Trelane]

Thanks for the heads up... saves headache on my end.

[Moon Wizard]

The targeting is expected as the targeting system was completely overhauled in v3.0, and there was no way to maintain backward compatibility.

The other items should be addressable once we identify the issues. It may be something I can patch in the main client without changes to the ruleset. (except targeting)

Regards,
JPG

[Moon Wizard]

Just tried to recreate the damage exploding issue, but it appears to be working in my old Zombie Run campaign. More details on which sheet/field you are rolling damage from? Other fields related to the damage (i.e. weapon, power, etc.)?

Thanks,
JPG

[scionofnyarlathotep]

As one of the player's concerned, the problems I encountered were:

- Dice not exploding when power clicked on the PC sheet
- Dice not exploding from short cut which had been created by dragging from PC character sheet
- Wound and fatigue and encumbrance modifiers not being applied on all rolls

I will do some more in depth testing tonight on the various settings I run and provide more feedback then.

[Casamordius]

I also made the mistake to update to 3.0.

Bug: Fantasyground crashes if I clear the owner of a pc

My tests:
- I created a new pc and this worked.
- I took a look at the db.xml and detected a lot (!) of "<holder name="casamordius" owner="true" />" tags littered all over the character (151 holder tags in 1 character) which seem to make no sense at all. I am not sure if this has always been the case. In older chacters I even detected that there are multiple different holder tags inside the same character (I think these are remnants from switching the holder). This also seems to make no sense and looks like a bug.
- I replaced all holder tags inside the file by nothing: after this the pc owner is cleared an can be selected by a player again
- After selecting the pc I tried again to clear the owner and fantasygrounds chrashes again

conclusion:
- seems there is a bug in the adding of holder tags
- the clear owner process seems not to clear all all holder tags of a character

[Trenloe]

Bug: Fantasyground crashes if I clear the owner of a pc
Which ruleset?

[Moon Wizard]

Casamordius,

* Which ruleset are you using? (assuming SW, since this is the forum)
* You should not attempt to clear holder tags manually by editing the campaign XML, which can cause data loss in done incorrectly.
* To unshare all records in the database, type /flushdb in the chat entry box. (This does not clear ownership.)
* To clear the owner of a PC, right click on the PC in the Character Selection window and select the "Clear Owner" menu option.

Also, can you recreate the crash situation every time? If so, can you send me the campaign directory that causes the crash along with the steps to follow?

Thanks,
JPG

[Moon Wizard]

scionofnyarlathotep,

Just took a look at the specific items mentioned. I'm running a vanilla SW ruleset. (v3.4.1 (Build 2))

* Both attack and damage rolls from attacks and powers tab on front of character sheet are applying wound/fatigue modifiers as well as exploding when max die value rolled.
* When dragging attack and damage rolls to hot key bar, they are correctly exploding. However, wound/fatigue is not being applied when rolled from hot key bar.
* I tried it on both the GM and player side.

Hopefully, phantomwhale can add the wound/fatigue from hot key bar. It looks like the modifiers are added when you start dragging, so it will require some ruleset changes to make it occur at a different time.

* Can you recreate the dice not exploding issue on your own machine?

Regards,
JPG

[scionofnyarlathotep]

scionofnyarlathotep,

Just took a look at the specific items mentioned. I'm running a vanilla SW ruleset. (v3.4.1 (Build 2))

* Both attack and damage rolls from attacks and powers tab on front of character sheet are applying wound/fatigue modifiers as well as exploding when max die value rolled.
* When dragging attack and damage rolls to hot key bar, they are correctly exploding. However, wound/fatigue is not being applied when rolled from hot key bar.
* I tried it on both the GM and player side.

Hopefully, phantomwhale can add the wound/fatigue from hot key bar. It looks like the modifiers are added when you start dragging, so it will require some ruleset changes to make it occur at a different time.

* Can you recreate the dice not exploding issue on your own machine?

Regards,
JPG

I've tried to replicate the issues from last night but without success except as noted above re the hot key issue.

My test was using SW with no extensions enabled and I also disabled the adventure deck. We were using 50 Fathoms last night so I am unsure if it was a setting specific issue. As I do not own 50F, I am unable to test it there. Perhaps Doswelk will have some success.

[Irondrake]

Would it be possible to implement GM targeting while the bugs are being fixed? :) With 3.0 the GM can target, but rolls made are not applied toward the targets (Fighting/Shooting or damage, etc.)

[Doswelk]

Would it be possible to implement GM targeting while the bugs are being fixed? :) With 3.0 the GM can target, but rolls made are not applied toward the targets (Fighting/Shooting or damage, etc.)
Personally I'd rather bugs fixed before new stuff added!

[Casamordius]

* Which ruleset are you using? (assuming SW, since this is the forum)

=> of course :-) as you said. this is the forum



* You should not attempt to clear holder tags manually by editing the campaign XML, which can cause data loss in done incorrectly.

=> I had done this quite often to fix broken xml, so I think I know what I am doing.



* To clear the owner of a PC, right click on the PC in the Character Selection window and select the "Clear Owner" menu option.

=> I know that. But this is exactly what is not working since upgrade to FG3.0. When I try this using teh menu, FG crashes.



Also, can you recreate the crash situation every time? If so, can you send me the campaign directory that causes the crash along with the steps to follow?

=> Yes I can recreate every time. You just have to try to clear an owner via menu exactly as you have advised me to do ;)

[Moon Wizard]

You can send me your campaign file to [email protected]. I just tried to recreate with a local test campaign with no luck.

Thanks,
JPG

[Moon Wizard]

Can someone explain to me how the targeting worked in v2.9.4 with the SW ruleset?

Other target list in the CT that displayed which targets that a PC was targeting, I don't see any functionality that used any targeting features.

Thanks,
JPG

[Doswelk]

When a player targeted a token the player portrait was placed next to the selected entry on the combat tracker, made removing the killed NPCs much easier (especially in fights as big as Necropolis can get!)

[Moon Wizard]

Have you tried the new targeting? There would be an arrow(s) from the PC token to the target(s).

Cheers,
JPG

[Doswelk]

That works but nothing is shown on the combat tracker, but it does not help much, in fact it's fairly pointless right now (as it does nothing except draw a line between the two tokens), If I could delete a token from the map and that npc was removed from the tracker it would be fine, but that does not work all that happens is the token is deleted from the map.

I know that these will be fixed (at some point) but right now I am happy that I can roll-back to 2.94

All these problems stem from the fact that SW has been around since FG1 and thus has it its own code base for years and thus always had to play catch up every-time you added nice new features to 3.5/4e, so it's all your fault! :p