Is your feature request related to a problem? Please describe.
The localization solution is great and very helpful, but I would like to have a file outside of the /data/modules , one that allows more contextually relevant information.
Describe the solution you'd like
allow a directory in the worlds' directory, if a /tips is present, stitch the *.jsons within for such.
So that the module references to include as additional tips that are campaign/game specific.
Ideally there would also allow "support" for other modules/systems to include a /tips directory or tip.json in their package so that if the module is loaded it includes those tips into the possible offerings. (this would likely also require settings for enabling/disabling of those tips)
Describe alternatives you've considered
Considered doing a single file for worlds , but was looking at how to expand the module's offering to help with other projects in their use to help bring people into foundry as a platform easier, or into their game, into using their module (functionality) or their adventure/world, or even game system.
(ie someone wants to make a tutorial / session zero module to help, but not force those elements into ALL their other worlds - or wanted to include additional/optional help that will be stitched into the main offerings)
Is your feature request related to a problem? Please describe.
The localization solution is great and very helpful, but I would like to have a file outside of the
/data/modules, one that allows more contextually relevant information.Describe the solution you'd like
allow a directory in the worlds' directory, if a
/tipsis present, stitch the *.jsons within for such.So that the module references to include as additional tips that are campaign/game specific.
Ideally there would also allow "support" for other modules/systems to include a /tips directory or tip.json in their package so that if the module is loaded it includes those tips into the possible offerings. (this would likely also require settings for enabling/disabling of those tips)
Describe alternatives you've considered
Considered doing a single file for worlds , but was looking at how to expand the module's offering to help with other projects in their use to help bring people into foundry as a platform easier, or into their game, into using their module (functionality) or their adventure/world, or even game system.
(ie someone wants to make a tutorial / session zero module to help, but not force those elements into ALL their other worlds - or wanted to include additional/optional help that will be stitched into the main offerings)