The localization strings are stored in an object. You could simply replace the values stored in the
The localization strings are stored in an object. You could simply replace the values stored in the localization object with different ones.
<@&859063949994360853> The <@&756158119389692007> have been gearing up for PAX Unplugged this weekend but wanted to check in following the release of V9 Testing 2. As per Atropos's announcement to published package developers in the official Foundry Discord, we're aware V9 Stable is *close upon us.* We're excited to have you join us for Updatathon Part 2 on December 18-19th for any stragglers (like me!) still catching their modules up. There's no rush! We're just here to give you the good ol' community push to make sure you're comfortable with your progress and not overwhelmed. Keep posting progress in <#915388333125955645>, <#871072051799134258>, and your questions in any of the appropriate channels. Good luck friends! Milestone for Testing 2: https://gitlab.com/foundrynet/foundryvtt/-/milestones/93 Milestone for Testing 3/Stable 1 candidate: https://gitlab.com/foundrynet/foundryvtt/-/milestones/94 List of breaking changes sorted by date (none for Testing 2, none for Stable 1 so far): https://gitlab.com/foundrynet/foundryvtt/-/issues?scope=all&state=all&label_name[]=Breaking
corporat · 5y ago
<@&859063949994360853> (get this role from <#798023493689147453>) This announcement has just gone out from Atropos on the Mothership's <#596076404618166434> channel (you'll need one of the mothership's developer roles to see this channel) in the <#880204104687845436> thread. > **Deprecations from V8 and prior which will be fully deleted in V9** > ============================================== > Hello folks. We have deleted 1434 lines of code! These were deprecated methods and attributes which support was removed for in v8 and prior. These methods are currently throwing warnings in the console if used, but starting in v9 their continued use will cause unhandled exceptions. > > Please refer to https://gitlab.com/foundrynet/foundryvtt/-/issues/5783 for a complete list of these removals and the new APIs that should be used instead. Please respond to this thread with any questions or concerns that you have. > > These removals will be included starting in the forthcoming v9 prototype 2 build. I've copied this list of methods to the v9 Migration wiki page as well: <https://foundryvtt.wiki/en/migrations/foundry-core-v9> We have a channel for discussing v9: <#871072051799134258> --- Please remember that if you would like your feedback heard about the API changes going into v9 (especially those related to the Canvas and forthcoming Cards), **this feedback is expected to be given during the _current ongoing_ prototype phase.** Prototype phase is the only time when large-scale API changes are considered, speak now or hold your peace.
Calego · 5y ago
**Foundry Core Version 9 prototype 1 is out!** <@&756525261725368460> and in particular <@&758570477798031381> The Prototype phase of development is when Foundry Gaming is most open to API feedback. If you care greatly about PIXI and the Canvas, go try this out with your modules so your voice can be heard! <https://foundryvtt.com/article/versioning/> **Patch Notes:** https://foundryvtt.com/releases/9.220 Milestone: <https://gitlab.com/foundrynet/foundryvtt/-/milestones/84> ⚠️ Issues marked Breaking: ⚠️ <https://gitlab.com/foundrynet/foundryvtt/-/issues?scope=all&state=all&milestone_title=Version%209%20-%20Prototype%201%3A%20Canvas%20Rendering&label_name[]=Breaking> **Announcement:** https://discord.com/channels/170995199584108546/675738274572271656/872581218850447400 Wiki Page for API Findings: <https://foundryvtt.wiki/en/migrations/foundry-core-v9> Channel for further Discussion: <#871072051799134258>
Calego · 5y ago
