bronze onyx
The "Supported Game Systems" section on module package pages is misleading. It always lists the current release of the game system in question, with no regard to the module's actual compatibility as defined in its manifest.
If there's a relationships.system.compatibility property in the manifest, these values should be clearly presented.
bronze onyx
Heyyyy @worthy relic is this one on the actual radar yet? 😅
worthy relic
Heyyyy <@692454090910859335> is this one on the actual radar yet? 😅
Hrm not something I have direct control over but I agree it would be very helpful for the V13 rollover
worthy relic
Heyyyy <@692454090910859335> is this one on the actual radar yet? 😅
I've signal-boosted this in our internal website tracker. I'm not sure how much footgunning it would prevent, but anything that can potentially help The Cause is a good thing
bronze onyx
If this one doesn’t look like it’s going to happen for some reason, maybe just delete the system version string from the display? At least then it wouldn’t be misleading.
hearty heart
Could we please get an update on whether this is being considered?
It has been a recurring problem for a long time, and the amount of user confusion it causes is significant. At this point, it feels like something that really needs attention.
Removing the “latest version” string, as unsoluble noted, seems like an easy and effective solution.
regal bronze
Agreed, this would be a nice qol improvement
flint sail
Aye. I’ll make a bold claim here, but I think it may be true:
Nobody in the history of foundry has ever gone to a module's package page wanting to know what the most recently released version of a system is
Pulling actual compatibility would be nice but I don't expect it, since nothing else on that page is pulled from the manifest, but rather entered manually