Beta 0.4.5 Update Key (Patreon)

 Greetings Patreon supporters and Beta testing community - I'm happy to release a the stable version update for Foundry Virtual Tabletop - Beta 0.4.5. This is an "odd-numbered" release, which means it implements bug fixes and stability improvements for all the new features that were added in Beta 0.4.4. If you haven't yet gotten a chance to take a look at the release notes for that update, please do check them out: https://www.patreon.com/posts/33025153 

You can read the full update notes for this new version here:  https://www.patreon.com/posts/33246213 

D&D5e System Update

There is an update to the D&D5E System you will need to install which accompanies this core update if you are updating from 0.4.3 or prior. After updating the core software, be sure to also update your system version!

Full Download Links

Windows: https://foundryvtt.s3-us-west-2.amazonaws.com/releases/045-x6cv1bb339j7/FoundryVTT-0.4.5-Setup.exe

Linux: https://foundryvtt.s3-us-west-2.amazonaws.com/releases/045-x6cv1bb339j7/foundryvtt-0.4.5.zip

MacOS: https://foundryvtt.s3-us-west-2.amazonaws.com/releases/045-x6cv1bb339j7/FoundryVTT-0.4.5.dmg

Direct Update Key (from 0.4.x ONLY)

If (and only if) you were previously using version 0.4.0 or  later, you may update directly using the following update key: 045-x6cv1bb339j7

Providing Feedback

The feedback cycle for these releases are very important. There are many large changes where I will be keenly paying attention to feedback to continue building upon this new framework. There are three ways to provide feedback which I have ordered according to my preference. 

1. Discord Channel. My preferred method to collect feedback is through our Discord server where I have created a dedicated channel for Beta 0.4.2 feedback. If you are able to join our Discord community it's the best way to engage with me directly for feedback.

2. GitLab Tracker. You are welcome to create issue reports directly in the GitLab tracker here ( https://gitlab.com/foundrynet/foundryvtt/issues ). If you choose to create issues in GitLab please take extra caution to check that your problem has not already been reported by checking other recently reported issues before creating a new report.

3. Direct Email. If the prior methods do not work for you, please feel free to email me directly with your feedback (admin@foundryvtt.com).

Thank you all so much for your support!Andrew