File type permitted not being accepted (webp)

[gtw2017]

Hi FGU,

First-time user. I attempted to upload an webp. file that contains the Line-of-Sight data marking the 10 entrances/exits of Meanders RPG Battlemaps - as this is an unchanging layout and simply by changing the map file name to match the template name, it provides LoS to any Meander. Mostly useful for indoor maps but DM's can lock or unlock the entrances as required.

The Direct Build Upload says it accepts webp files.
However, upon trying to load it into the Forge, I got this error message (right-hand in red) that does not include webp.

65325

Am I doing something wrong? How do I fix this, please? I'd like to provide the LoS as a free download for Meander users.

Kind Regards,
Kris (The Maphatter)

[Trenloe]

Are you uploading a Fantasy Grounds file type containing webp files? Or are you trying to upload webp files direct?

You can only upload .mod, .ext, .pak, .ppk, .tpk or .ipk files; which may only contain the listed file types. I'm not sure how to work around this just to provide LoS XML files. Hopefully someone else may have an idea.

[gtw2017]

65326

Hi Trenloe, yes, it's a FGU exported .webp that I made inside FGU and am now trying to upload direct. Here is the meander inside FGU, and the LoS file. I exported both. The LoS is its own .webp and I'd hoped to upload it to the Forge so others can add LoS to any Meander. The Forge says it accepts .webp in one section but rejects it in another.

Is it possible to change the file type to .mod and have the end-user change it back to .webp?

[Trenloe]

The Forge says it accepts .webp in one section but rejects it in another.
The wording is (highlight mine): "Builds must be a valid Fantasy Grounds package (.mod, .ext, .pak, .ppk, .tpk, .ipk) and may contain allowed file types..."

Whereas you're using an allowed file type of webp, it must be within a valid FG package - which is a ZIP file renamed.


Is it possible to change the file type to .mod and have the end-user change it back to .webp?
As all FG packages are just ZIP files (using the ZIP compression) renamed, you could probably package the webp and XML file within a .mod file (ZIP the webp and XML files into one ZIP file and then renamed the ZIP file).

[gtw2017]

Thanks Trenloe. After the mod file is zipped what is the best file type to rename it as?

[Trenloe]

There's probably no ideal option. You could use .mod, but then users may assume that is a module and install the module and wonder why they can't see it in FG. But that's probably the best option to go with.

[gtw2017]

OK - I'll be sure to add the disclaimer so they know what's going on ;)

Thanks a lot. That should solve it.

[superteddy57]

I would check out the wiki:
https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/996644379/Module+-+Token+Pack+Creation

This is for tokens, but works for a map packs if you place the maps in an images folder instead of a token folder.

[Trenloe]

I would check out the wiki:
https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/996644379/Module+-+Token+Pack+Creation

This is for tokens, but works for a map packs if you place the maps in an images folder instead of a token folder.
I believe Kris doesn't want to provide static maps in FG, but a LoS XML file that can be renamed to match other map files, and then use as part of an image import to apply standard LoS definitions.

[LordEntrails]

What about a script that would just add the xml to all of your existing Meanders? It would really be about updating the existing mod files via script and would require the xml to be duplicated to match all the existing names.

If I have the idea right, then it would be transparent to the users and next time they open a meander map it would already have all the LOS for it. I'm not very good with scripts, but if no one else volunteers, I could see what I could come up with.

[gtw2017]

There's probably no ideal option. You could use .mod, but then users may assume that is a module and install the module and wonder why they can't see it in FG. But that's probably the best option to go with.

Not a bad idea - I have already signed on to the idea of updating existing modules with individual LoS whilst making new ones as well - bringing all Meanders on FGU into Meanders Plus with Los and Lighting over time.

Having the file as optional is probably best since there are thousands of Meanders that don't require the wall and door xml (like deserts, forests, ocean) and it might be problematic later on if they already have this built-in and applied. It might also be annoying for others who may have already added LoS. I don't really know the parameters of making such a blanket choice but I think I would probably be best to just offer this framework this way for now, but thanks a lot for being ready to write a script my man.

[LordEntrails]

Forge items have a link to a support thread. What about just linking the xml file and including instruction on that thread?