module developer question

I have been doing some light work on map/tile packs going back a good bit and since then new features have been added for lighting and different LoS functions. Also, as to be expected I have gotten better at formatting, naming and labels.

My concern is that by updating, it could impact anyone currently using the module and I don't want anyone to have a negative impact because of internal housekeeping. (thinking about the dreaded Red X Box from missing image asset on a fully built map) I know it is recommended to never update right before a game and maybe this would be a good feature request, but is there a way to notify an end-user that a module has updated and by updating it could have adverse effects?

The only method is to make it clear when you update (assuming that it gets updated in the usual Tuesday update method) that the user may have to revert changes on the module if it's being used in a campaign.

Is the product in question in the Forge or a FG DLC from the store?

Thanks for the info, how would I do that? I was looking over the guide and couldn't find anything about updating as a process. (this is for a store module if that helps)

When you update (and I don't know what your update process is) but generally you need to notify James in some way? Include in the notification details of what has changed and make sure James knows to include any information you give him about reverting changes because stuff has changed in such a way that users may get errors. Like this https://www.fantasygrounds.com/forum...l=1#post663687

Perfect! Thanks so much!