Feedback Thread - FGU v4.6.0

[Moon Wizard]

@humby,
Carl just provided fixes for the majority of the items you reported; and the latest version is available in the Test channel for update. Resetting image to Play mode when switching image window states (floating to background) is expected.

@SilentRuin,
Carl is continuing to look at additional items that you brought up; but are more complex to resolve.

Regards,
JPG

[fabiocm]

Hello. Folders on the image layers are not working. When we put something into a folder, the layer becomes invisible and the folcer can't be expanded.

[fabiocm]

Is multi-line support on roadmap? A soft break, similar to what's found in software like Wonderdraft, Inkscape, Gimp, and Inkarnate, would be ideal. While a pop-up box would be great, simply enabling line wrapping would be sufficient.

[pindercarl]

Hello. Folders on the image layers are not working. When we put something into a folder, the layer becomes invisible and the folcer can't be expanded.

Thanks for the report, I'll be looking at folders today. I've taken a look at supporting multiline text, it's unlikely to be in the 4.6.0 release, but I will add it to the short-term list.

[Vass_Dts]

When tokens are locked, holding ALT as the DM to move them in a manner that designates their path and distance counter, no longer works. Have not tested client side to see if that is an issue that also affects players for token locked movement.

[Vass_Dts]

Radial menu: Exit Program and Quit to Launcher have the same icon. I don't think that was intentional.

EDIT: Hmm.. on the very next campaign I loaded, the icons were correct. O_o

[deer_buster]

I wonder if it would be worth it to add some kind of validated level to extensions, modules, and rulesets (for that matter). And when one of those is loaded, it checks and says "yep, I am validated for that version of the ruleset" and places a "VALIDATED" (or "UNVALIDATED", as applicable) next to the announcement of whatever was loaded.


Example:


Extension XYZ's extension.xml properties includes
<ruleset>
<name>5E</name>
<version>2024-03-19</version>
</ruleset>


Ruleset 5E's base.xml would have
<version>2024-03-19</version>
<importruleset source="CoreRPG" version="2024-03-19" />




For example, when CoreRPG gets updated, but 5E doesn't, "UNVALIDATED" gets appended to the ruleset announcement text to warn users that "hey, there may be some issues, so be on the lookout".


Same with the extension if 5E gets updated, but the extension doesn't have the ruleset version updated. Potentially, with extensions, provide a popup that warns and gives the option to not load the extension on startup of the campaign. Keeps the extension in the list, but disables for that session.

[SilentRuin]

I wonder if it would be worth it to add some kind of validated level to extensions, modules, and rulesets (for that matter). And when one of those is loaded, it checks and says "yep, I am validated for that version of the ruleset" and places a "VALIDATED" (or "UNVALIDATED", as applicable) next to the announcement of whatever was loaded.


Example:


Extension XYZ's extension.xml properties includes
<ruleset>
<name>5E</name>
<version>2024-03-19</version>
</ruleset>


Ruleset 5E's base.xml would have
<version>2024-03-19</version>
<importruleset source="CoreRPG" version="2024-03-19" />




For example, when CoreRPG gets updated, but 5E doesn't, "UNVALIDATED" gets appended to the ruleset announcement text to warn users that "hey, there may be some issues, so be on the lookout".


Same with the extension if 5E gets updated, but the extension doesn't have the ruleset version updated. Potentially, with extensions, provide a popup that warns and gives the option to not load the extension on startup of the campaign. Keeps the extension in the list, but disables for that session.

What a horror that would be if nothing needed to be updated. My dream is my extensions just work on every update with me doing nothing - as in no extra work.

AT ALL. Including what your suggesting.

[Farratto]

I wonder if it would be worth it to add some kind of validated level to extensions, modules, and rulesets (for that matter). And when one of those is loaded, it checks and says "yep, I am validated for that version of the ruleset" and places a "VALIDATED" (or "UNVALIDATED", as applicable) next to the announcement of whatever was loaded.


Example:


Extension XYZ's extension.xml properties includes
<ruleset>
<name>5E</name>
<version>2024-03-19</version>
</ruleset>


Ruleset 5E's base.xml would have
<version>2024-03-19</version>
<importruleset source="CoreRPG" version="2024-03-19" />




For example, when CoreRPG gets updated, but 5E doesn't, "UNVALIDATED" gets appended to the ruleset announcement text to warn users that "hey, there may be some issues, so be on the lookout".


Same with the extension if 5E gets updated, but the extension doesn't have the ruleset version updated. Potentially, with extensions, provide a popup that warns and gives the option to not load the extension on startup of the campaign. Keeps the extension in the list, but disables for that session.

I like the idea. Seems to work well for WoW extensions.

[deer_buster]

I like the idea. Seems to work well for WoW extensions.

I will say that I love the way Factorio handles mods