Test release v3.0.8

[Trenloe]

What extra information do you need to fix this?

Which ruleset?
Is it for a player rolling critical damage? A GM rolling NPC critical damage? A GM rolling PC critical damage?

[Moon Wizard]

Irondrake,

I'm not seeing that on my side, can you check the XML in your module?

JPG

[Moon Wizard]

Updates

• [CoreRPG+] Item transfer to PC fails if inventory tab not opened yet. Fixed.
• [5E] Script errors when opening rollable table record. Fixed.
• [5E] Script errors when performing critical damage rolls. Fixed.

JPG

[El Condoro]

Which ruleset?
Is it for a player rolling critical damage? A GM rolling NPC critical damage? A GM rolling PC critical damage?

Looks like this has been fixed but it was a player targeting an NPC. 3.0.8 (latest ruleset in Test mode)

[Irondrake]

I will check it out to be sure, Moon.

[Irondrake]

I had to put a title (Number of Actions. Description....) to keep it from using the previous action name before the legendary action number description.

[El Condoro]

Minor point (and I'm not even sure if I should be posting on this thread) but when using the Wizards theme the close X and the lock/unlock symbol on sheets such as Encounters et al are very close (on top of each other) making it difficult to use either function.

Edit: also obscures the ID/non-ID symbol for items.

[Zeus]

When looking at rollable tables, I am getting a window that pops up that says:

Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)
Ruleset Error: window: No vertical anchor defined for control (rightanchor) in windowclass (table_header)

I am using the new Wizards desktop, looks great btw! It doesn't appear to affect the performance of the table rolling.

Cheers. Make sure you have re-parsed your modules with the latest version of the PAR5E tool as I'm not seeing this error. Also make sure you don't have any expanded (folder) versions of the CoreRPG and 5E .pak rulesets in FG app data/rulesets folder.

Creature Legendary actions appear to be taking the title of the last Action as a header in the Legendary Action description (telling how many legendary points they have). I've looked at two different creatures and both have the same issue. May just be a parsing issue, or maybe I need to define a header for this information?

Here's a picture.

Attachment 7386

This is down to the syntax of the stat block you used for PAR5E. The outcome will occur if you don't precede the descriptive Legendary Actions text with a named tag. PAR5E expects and alpha-numeric string followed by a period followed by the descriptive text for actions/legendary actions. I used the keyword Option. in my modules, see below for an example.

...
Legendary Actions
Option. The aboleth can take 3 legendary actions, choosing from the options below....
Detect. The aboleth makes a ...
Tail Swipe. The aboleth makes one ...
Psychic Drain (Costs 2 Actions). One ...

[Trenloe]

Looks like this has been fixed but it was a player targeting an NPC. 3.0.8 (latest ruleset in Test mode)

Cool, JPG works fast. :-)

Just as a future FYI, "ruleset" in FG parlance is the game system (the one you select when creating a new FG campaign), e.g. CoreRPG, 5E, 4E, 3.5E, PFRPG, Savage Worlds, Castles & Crusades, etc.. It's usually a good idea to mention which ruleset you're using when reporting an issue, otherwise the usual first question back at you will be "which ruleset?". :-)

[El Condoro]

Thanks. I just assumed the title of the thread implied the ruleset.