Ok, just cleaned up the files as well as some other issues with file linking that the developer had. Can you please run a new Check for Updates, and see if that resolves your issues with the module?
Thanks,
JPG
Printable View
Ok, just cleaned up the files as well as some other issues with file linking that the developer had. Can you please run a new Check for Updates, and see if that resolves your issues with the module?
Thanks,
JPG
Hah! So my apostrophe clue was relevant!
Yeah, unfortunately, issues like that are OS-dependent (works in some cases; not in others); which is why we recommend developers not do that.
And mostly em-dash issues, but there were definitely a few right-apostrophes too.
Regards,
JPG
No, mainly windows. But when you test things locally things can work. It's only once it's downloaded from the servers that you can get issues like this. I've seen several instances where things have worked on my local machine when developing but don't once they are downloaded by other users, because a single incorrect apostrophe or em dash had sneaked into something.
I took the time to review the ToV Monster Vault 2 PDF more thoroughly, and the problem is that the FG module has forgotten to include the creatures from the APPENDIX: ANIMALS (page 322) and the APPENDIX: NPCS (page 330).
In the previous list, I forgot to include 2 creatures, making it a total of 34 creatures missing from the Monster Vault 2 module:
APPENDIX: ANIMALS
- Axolotl, Giant
- Cavalry Camel
- Feymount Raccoon
- Hammberbill Goose
- Hedgehog, Giant
- Honey Bee, Giant
- Honey Bee, Swarm of Bees
- Millipede, Giant
- Nightwing
- Oliphaunt Warbeast
- Opossum
- Opossum, Giant
- Skunk
- Skunk, Giant
- Tress Lizzard
- War Pig
- Wooly Hippopotamus
APPENDIX: NPCS
- Arcane Grenadier
- Bard Maestro
- Cultist, Necrograft
- Diviner
- First Servant
- High Mechanist
- Huntmaster
- Mage Knight
- Master Assassin
- Merchant
- Merchant Captain
- Monarch
- Monster Hunter
- Scavenger
- Thief Lord
- Venture Priest
- Wrestler
All of these creatures function like any other and have their complete stats. Could you fix this and include them?
Might be good to add some code to detect these things somewhere before they go to the store.
I know there's an extension called conversion checker devs are encouraged to use.
Or maybe if there are characters that you consider illegal for distribution, have FG sanitize the strings where it can and for filenames throw an exception and just refuse to load the resource while the dev extension is loaded?
Some ideas. I'm sure you have more being actually familiar with the codebase.
@ferrnando,
We'll pass along to the developer.
@drempel,
I'll pass along to James who manages the pipeline for content to see if that is something that can be added. It's not as automated as you might think, due to the variety of developers we work with and the variety of tools they work with.
Regards,
JPG