Author: Calego (Elf Friend)

Dear Foundry Community, First of all thanks for all the support you show to the community of volunteer developers which work to make our favorite VTT even better with a host of systems, modules, content packs, and more. The League of Extraordinary Foundry VTT Developers has a gentle reminder for you: Developers are People Too We are tinkers, artificers, wizards, and we do this code-craft as a hobby. Our hobbies consume our free time, and we offer the fruits of our free time up to the world for free (some of us have ways in which you can support our efforts monetarily, but the vast majority of us do not). Our free time is as limited as your own, and as 0.8 enters Beta I want to remind you that many Systems and Modules will require some work to be compatible with this major core update. There will be issues, some small, some large, with the systems you rely on and the modules you love. Do not update your game and expect things to work. Do not rush to the repository of the Open Source System or Module to create a hasty and unhelpful “This is broken in 0.8.2” report. Do not be demanding of the free time we voluntarily pump into this hobby. Be patient. Be helpful. I can assure you that there isn’t a package dev out there who isn’t worried about what 0.8 will break in their beloved works of art. Some may have already tested and fixed things, but many haven’t. I can confidently say most of us are excited about the new APIs and possibilities that 0.8 brings, but it will take time and effort to update our packages. How can you help? If you are adventurous, make a backup of your world and update in such a way that you can revert for your normal game. Then test your systems or modules in a methodical way, one at a time, and make note of any broken features. Below are the hallmarks of a useful bug report, if you can open an issue for any un-reported problems with the system or modules you test, this will truly be a help. Ensure the issue isn’t already reported on the repository. If it is, simply reacting to it with a 👍 is enough to tell the dev that you’ve encountered the issue as well. Provide specific steps you can consistently reproduce the issue with. Show any screenshots that help explain the problem, or videos if you have that ability. Provide any relevant settings for the module, system, or core that seem related to the issue you’re encountering. Check the Developer Console (try F12) for any big red errors, if there are some, include a screenshot of them in your report. These reports help the developer know what is broken and offering to help test fixes goes a long way. Sincerely,Calego “ElfFriend” on behalf of all Module and System developers. P.S. If you’re a system or module developer and you aren’t already part of the League, by all means join us on discord. We’re all in this together, and by our powers combined we can help the work go smoother.