V10 package compatibility spreadsheet

[dim sandal]

Wildjammer: More Adventures in Space now has a v10 compatible branch available.

[tranquil vine]

日本語化（オンセ工房 Foundry VTT 本体＆Mod）
(Japanese core localization mod)
Is updated for v10 compatibility

[polar heath]

The v10 testing version of dnd5e is now published publicly and is available on https://foundryvtt.com/packages/dnd5e

[tawdry compass]

wfrp4e, wrath-and-glory, and age-of-sigmar-soulbound now all have public v10 testing branches. Additionally all of their premium modules should be compatible

[polar heath]

That's a big accomplishment, nice job and thank you!

[weak birch]

and here i was, just two hours ago, expressing concern that some systems with premium content were not going to be available during the testing phase, meanwhile you're up in here proving me wrong.

[tawdry compass]

Well honestly I didn't change anything, the premium modules just work fine, from what I can tell. The only incompatibility was the module content importer, which is in the systems

Also "compatible" certainly isn't "converted to v10 journals" ... that is a something else entirely

[static bane]

Oh, lol. Somehow I thought that you had converted everything already and I was very confused

[tawdry compass]

Nah, but I think some scripts can help me with that. Take a folder and combine the journal entries into pages inside one entry

[static bane]

Ooh. That's a good idea.

[tawdry compass]

It's likely going to screw up all the links though

[weak birch]

I'll take compatible. Compatible means some of your users can test on the feature testing phase. XD

[weak birch]

--------------All reports above this point have been processed--------------

[timber delta]

@weak birch QuickScale compat in progress; done soon.

[night vine]

Effect Macro is not on the sheet.

[warm hare]

bulk-tasks has a v10 version that's ready on a pre-release

[tawdry fog]

I only yesterday installed v10 again to see if I can work on getting my things compatible. I'll probably only update the package listing instead of announcing things here.

[weak birch]

that's odd. I'll investigate that.

[night vine]

It's recent, that's probably why.

[weak birch]

could be

[weak birch]

perfectly acceptable

just as a note for those wishing to test:

[warm flicker]

Running an Alternate Version of Foundry VTT

During the Feature Testing phase of development, we seek feedback from users excited by the features of Foundry VTT's latest version. However, this often leads to users forgetting to backup their worlds and ending up in a situation where they have not protected their data properly!

The awesome @thick sphinx has assembled a video on how to safely try alternate versions of Foundry VTT, and released it through our partner Encounter Library.

Testing V10

Check out the video guide on how to run additional versions of Foundry VTT.

Don't forget to backup your data!
USE ?backup FOR MORE INFORMATION!

[elfin spindle]

@weak birch All 4 Backstory Cards modules are pretty much updated for v10. Just waiting for the near final release to verify additional work will not be needed.

[fluid cypress]

@weak birch Monk's Hotbar Expansion is fine, no changes needed, Monk's Active Tile Triggers Working on it, will be released shortly. Enhanced Terrain Layer Will need a complete rebuild so it might be some time before that one is ready.

[elfin spindle]

I think Savaged.us Importer is pretty much ready, too.

[weak birch]

swapping focus onto some other tasks, will circle back here to do run more dupates either later or tomorrow.

[crisp walrus]

@weak birch I will be waiting for PF1E and the v10 release to look over my packages.

[plain ether]

@weak birch Oddly (Whisper) Sweet Nothings still reports v10 branch but not yet released when it was released last week.

[weak birch]

corrected

[heady light]

@weak birch ose and ose-content will get their V10 compatible release this week.
tips is a forgotten stepchild. It isn't being looked at but if I'm bored I might check if it needs any work or if it's already V10-ready

[ashen escarp]

@weak birch - Torg Eternity has a build ready to go that is v10 compatible.

[rich ermine]

@weak birch Cyberpunk Red Core is not yet compatible with v10 of Foundry. It is actively being worked on though, should be ready within the next few weeks

[cosmic mason]

@weak birch Special Dice Roller and Quest for the Frozen Flame Tools are not yet compatible with v10, will wait for PF2 v10 release to test locally

[pliant tide]

@weak birch SBC is not compatible to v10, but an update is planned

[mossy aspen]

@weak birch Vaesen and Tales From the Loop systems both have forks that work in v10 I am holding off on a full release until v10 is out of testing just to be sure things actually work at launch

modules:
Tales from the Loop - Core Game not started but should be in free league's hands in a week or so
Tales From the Loop - Starter Set not started but should be in free league's hands in a week or so
Things From the Flood - v10 fork waiting on system to publish

Vaesen - A Wicked Secret not started but should be in free league's hands in a week or so
Vaesen - Mythic Britan and Ireland not started but should be in free league's hands in a week or so
Vaesen - Seaons of Mystery not started but should be in free league's hands in a week or so
Vaesen - Core Rules - Complete and ready to send to Free League

I will send all the premium modules to free league at the same time

[weak birch]

Vaesen and Tales From the Loop systems both have forks that work in v10 I am holding off on a full release until v10 is out of testing just to be sure things actually work at launch
A note on this----if your users can't test the system during the period where users are expected to test, how will you know it will work at launch?

[mossy aspen]

i published the links to the repsoitory for testing and have reached out to individuals to test so far so good

[weak birch]

👌

[static bane]

the-sky-isles-module is compatible with v10

[shut flicker]

@weak birch
Title: Automated Animations

• Broken in V10. Will not be worked on until after V10 release. System support will be updated in A-A as their V10 releases become available

[opaque sage]

@weak birch FlexUI waiting for v10 stable

FantasyUI/SciFiUI/Master Mirror are deprecated and will not be updated

[empty dew]

@weak birch Cypher System has a V10-compatible pre-release. Some more testing needed, but it’s mostly done.

[hidden ruin]

"Wild Magic Surge 5e" V10 ready. Awaiting to be published.

[hallow peak]

"Clé en main" system is roughly compatible with V10. A V10 branch with full V10 data model is ready, awaiting to be published.

[hard timber]

@weak birch Director has the v10 branch that requires Sequencer's branch for v10 support. It will be released in a week as a single release for v9 and v10

[marble stone]

@weak birch
"HeXXen 1733" system - v10 support in progress
"HeXXen 1733 - Buch der Regeln" module - v10 support pending, also updated package information to state v9 compatibility

[warped schooner]

Sandbox system, not compatible. I have no time to do this, and I don't know when it will be possible.

[last ether]

@weak birch
"Lancer Clocks" supports v10 as this update did not change how it functions. Manifest has been updated and I will be updating the package listing soon.

[ancient silo]

@weak birch shadowrun6-eden (now, not in the spreadsheet yet because too new): Broken inV10 (70% works but myriads of data model warnings in log)
Waits for Typescript definitions to start migration

[thorn ocean]

@weak birch Quick Encounters tested with v10; breaking change (bug) in 10.275 which I am going to wait to get fixed rather than workaround. Previously worked in 10 Prototype versions.

Haven't tested Easy Exports

[vagrant fractal]

@weak birch Bunkers & Badasses looks like it'll not work in V10. A v10 version is still in progress for now. I'm like 95% done, trying to tie up loose ends and get a proper manifest.

[elfin spindle]

@weak birch scratch that. Savaged.us Importer is still pending updates from the SWADE system.

[weak birch]

--------------All reports above this point have been processed--------------

[high dune]

@opal stream here

[opal stream]

Ah, thank you.

@weak birch

The Secrets of Cats
Knights of Invasion

The import function won't work in v10 due to changes in various places. I have compatible versions of both of these using Adventure documents, but I've been waiting for the final version of v10 to be released because these are paid modules. The new versions won't be backwards compatible with v9 for simplicity. I'll need to work with Foundry staff to get the new versions uploaded and available for use by customers.

Blood on the Trail
Weird World News

I'm not directly responsible for the development of these modules but I've been briefing the guy who is on what needs to be done with these and we'll intend to get v10 compatible versions ready in the same way.

[hard oasis]

Twodsix has a working v10 branch.

PF2e Workbench is not yet compatible with v10, will wait for PF2 v10 release

[sleek wraith]

"Walls have Ears" maintainer here...
I dont think v10 posess any change for my mod but will wait until v10 stable to update. I just use the Audio subsystem and a basic raycast for detecting walls.

[silver egret]

System "Legend of the Five Rings (5th Edition)" is v10 ready (on dev branch), but waiting for FVTT v10 to be stable to publish the version publicly.

[dusk mauve]

Hello 🙂
Custom System Builder is in the process of v10 compatibility !

[verbal drift]

Still a bit uncertain if I should say something if a module -is- compatible without issue..so ignore if needed 😁
Three modules that have released v10 branches now:
Introduce Me
Combat HP Display
Join Combat

[timber delta]

If they're listed in the package repo as v10-compat, no need to report; they're picked up automatically.

[hard timber]

Alpha HUD is v10 ready
Director with v10 is released (still needs sequencer's brunch)
Merchant Control isn't compatible and Im going to migrate to upcoming release of Item Piles or just discard the module due to support of restocking in Item Piles.

[stray mesa]

Kris's Compendium of Trade Goods is V10 ready and working

[lost summit]

Warp Gate has a v10 ready beta. Not published on the package listing

[lament crystal]

**Crash's Tracking & Training **- Should probably work fine on v10, but I don't have the time to keep up with it anymore. De-list it.

Crash's Automatic Blind Rolls - No longer being maintained, de-list it.

[lost summit]

Ruins of Symbaroum 5E - Core System Module has a v10 compatible alpha release. Not published on package listing

[heavy viper]

@weak birch Pathfinder 1 has a v10 ready branch, but no published release yet.

[weak birch]

offtopic but quick question does pf1e have active effects support?

[heavy viper]

Kind of but not really. AEs are only used for icons/conditions, the actual data handling of "increase value X by Y" is done by the system's "Changes" system.

[flint cave]

@weak birch AGE System (unofficial) age-system has a fully working v10 branch. Public release after Foundry v10 reaches stable.

[desert quarry]

system: Fallout 2d20 has a working v10 branch. Not released to public yet

[weak birch]

I haven't had opportunity to circle back to this in a few days, but will do so soon

[lyric cedar]

@weak birch World Explorer should work in v10 now

[hexed moth]

VGMusic (module) now has a v10-compatible release.

[hard oasis]

PF2e Workbench has a working v10 branch, will release after PF2e supports v10.

[weak birch]

Now going back and cycling through these,

[weak birch]

--------------All reports above this point have been processed--------------

Thanks everyone for keeping things rolling! Sorry it took a bit to process all the updates since last time, last week was a bit hectic. 😄

[static bane]

There's a v10-compatible branch of Tidy5e Sheet here https://github.com/sdenec/tidy5e-sheet/tree/0.6.0

[lost summit]

Note Macro has a v10 compatible branch (no pre-release manifest)

[static bane]

toggle-banner is not v10 (or v9) compatible and should be archived (it won't be updated anymore)

[lilac idol]

@lament cargo here is the place to let Nath know about v10 readiness for systems (check the pinned comments)

[lost summit]

MCDM: The Illrigger has a v10 version awaiting v10 stable.

(unsure if premium modules should be noted here or not)

[lament cargo]

Robert E. Howard's CONAN: Adventures In An Age Undreamed Of has a working v10 branch ready for release. Public release once Foundry v10 stable releases

[thorny vale]

Everywhen (Unofficial) works with version 10 without apparent bugs. It does not have a V10 branch yet (no ETA on that).

[night glen]

Exalted Third, Exalted Essence, and Storypath (Scion) have v10 branches. Waiting for stable release

[rich ermine]

@weak birch Cyberpunk Red Core now functions with some errors on v10 of Foundry, though we are still waiting to release until a stable version of v10 is announced We also have some migration code that needs to be written but otherwise we are nearly there. Not sure if that changes our status on the spreadsheet. Thank you!

[safe aurora]

@weak birch hello! There's a v10 compatible branch of GM Toolkit (WFRP4e) that is mostly compatible with the forthcoming v6 of the system, and Foundry v10. A few areas to review and some more to address but generally works. https://github.com/Jagusti/fvtt-wfrp4e-gmtoolkit/issues/156

[cloud aspen]

‣ lancer-speed-provider – Waiting on v10 compatible lancer system
‣ ffg-pool-party – Waiting on v10 typescript types
‣ lancer-initiative – Waiting on v10 typescript types

[heavy valve]

I've just released a new module so it isn't on the spreadsheet yet: Immersive Render (IR): https://foundryvtt.com/packages/immersive-render
It's v9 compatible for now but I'll work to update it to v10 once a stable version is released.

[static bane]

FYI modules released after the spreadsheet was created in the v10 Development phase are not added to the spreadsheet. It's presumed that if you create a module now, it's v10 compatible.

[heavy valve]

Ah okay. Thank you.

[safe aurora]

GM Toolkit (WFRP4e): the v10 branch on the repo is pretty much done for FVTT 10.278 and WFRP4e 6.0.0 compatibility. I think I'm all clear on errors and deprecation warnings, and have full feature parity with the current version. A formal release will likely follow v10 Testing 5 or Stable. A pre-release will probably rear its head after this weekend.

[terse prairie]

@weak birch I just got around to testing.
Arius Planeswalker's Stylish Journal: To be archived.
Arius Planeswalker's Stylish Journal for Monk's Enhanced Journal: to be archived.
I will create a new APSJ for v10 that works with ProseMirror and the new journal system.

[iron knot]

@weak birch KNAVE is updated for v10

[weak birch]

---------------All reports above this point have been processed-------------

[weak birch]

@livid seal though it will automatically update when you update any manifests or package page listings, here is where you would post for this.

Gonna quote your notice so i can tag it later

Hey all, who do I talk to about the V10 Package Compatibility spreadsheet? "7th Sea Second Edition System (Unofficial)" is highlighted grey which means "Archived."
I'm actively maintaining this system now and I have a v10 branch that's nearly complete.

[tawdry fog]

I feel like there's small communication error whenever this compatibility spreadsheet happens. It seems (to me anyway) like a lot of people think this is mandatory process to report to it.
And the part about using package manager alone being enough seems lost.

[lost summit]

I think its understood that this is an optional thing, however, the module compat checker module does put extra pressure on devs when comments are made about "X is being archived"

[tawdry fog]

Archival is separate process tho (I think, but even then, posting new version compatible with current version in package manager should be enough to undo that).

[weak birch]

@clever helm that should be resolved now, sorry for the confusion

[clever helm]

NP, thank you!

[static bane]

If there's anything that you think can be improved here lmk
I just use Archived - To be archived or no longer available for the explanation currently

[lost summit]

i have no suggestions for the module (havent touched it), just pointing out a situation that I try to correct when i see it, stemming from the list and module.

[clever helm]

Brazilian Portuguese [Core] has a v10 compatible branch and is working without any errors
Brazilian Portuguese for [D&D 5e] is being updated to v10 and already works in v9 (I probably forgot to update the module compatibility in the Foundry site)

[fervent dune]

Tormenta20 there is a v10 ready branch and a test release (not include in foundry admin)

[hidden ruin]

Wild Magic Surge 5e V10 compatible and released
Encounter Stats V10 compatible and released

[loud timber]

Eclipse Phase 2e - v10 compatible & migrated, not yet released though.

[ashen belfry]

Simple Calendar has a v10 branch ready to go. Will be released in a few days after more testing.

[tacit solar]

Wicked Ones V10 compatible and released

[sudden bison]

Fate Worlds Arecibo, Blood on the Trail, and Weird World News - can these modules be marked as Import functions broken, v10 branch in progress?

Letter Tokens - Work in progress on V10 compatibility

[safe aurora]

GM Toolkit (WFRP4e) has a v10.279 compatible version available.

[crimson gull]

Effective Transferral has a v10 release ready which can be found here: https://github.com/GamerFlix/effective-transferral/releases/tag/1.1.!8. While it is intentionally marked as a prerelease I don't anticipate any changes apart from updating the verified system, core and module dependency versions once they release an update.

[upper kayak]

Dungeon Crawl Classics has a mostly working v10 branch, but our premium content still needs a bit of work to get the content importers working.

[grave bridge]

@weak birch I have a unpublished v10 branch ready for DnD5e Drag Ruler Integration, it should work but I can't test it till Drag Ruler itself is updated (that module does not function at all in v10).

[hollow crane]

Something came up in the #dnd5e channel about the system's compatibility with v10. It's showing in the spreadsheet and in the Module Compatibility Checker as green. It's still in the "alpha" releases. Should we manually mark that as "O" (package functions with some errors) until it's done with the alpha releases?

Just to avoid people from thinking the system is ready once v10 goes live before it actually is ready

[weak birch]

Should have been an O

oh

wait

no

the alpha release is available on main stream

so if you're in v10 you can straight install it/update it

[hollow crane]

Yup, can install the alpha releases from the setup screen

Which is fine IMO, helpful for testing dnd5e-related modules so you don't have to clone the repo

[timber delta]

(The point was that it should be an O due to the fact that it isn’t all-feature-stable.)

[hollow crane]

I see, so it was intended to be O but b/c the alpha releases were listed, the automated process that updates the sheet flipped it to compatible

[weak birch]

If it's released and public and functions in v10

it's a G

[weak birch]

process isn't that automated, it's literally me going "ah, released v10 compatible? G now."

XD

[timber delta]

Apparently active effects can’t be edited at all, kinda seems broke but okay 🤣

[weak birch]

That's a core bug

documented and fixed by now

[foggy dune]

@weak birch seems like the spreadsheet has some issues with the new version fields:

you've got an idea what's wrong? is it pulling the information from the admin panel database or the module.json? would entering a compatible version in the admin panel or sth help?

hm I guess I'll try. this is then related to the creator upload tool not reading the compat version

[dusk shuttle]

The spreadsheet is missing the module I released in July, which supports V10.279:
https://foundryvtt.com/packages/inline-linktext

[static bane]

#994385117067890758 message

[weak birch]

Resolved

[fringe ocean]

DDB Importer v10 version released publicly

[cloud aspen]

@weak birch I don't know why it's listed as ready, but v10 support for LANCER is still in development and kind of a long way off.

[dusk shuttle]

Adventures in Middle Earth (https://foundryvtt.com/packages/aime) is marked as only compatible with 0.8.9, but it has version 0.3.3 which is compatible with foundry V9 (it is the first version in the available versions list)
It is appearing as "archived" in the module compatibility checker.

[cloud aspen]

I'd also like to ask that for v11, none of my packages be included in the spreadsheet. It is a source of nothing but anxiety for me.

[static bane]

Why is this? I think the reason why the spreadsheet was originally created was to stop users from asking devs when their packages will be updated

[lost summit]

it seems to have the opposite effect, from the interactions ive had regarding it

[static bane]

Yeah, that's true. The only thing it is helping with is the decision about whether to update to v10, but I guess people are happy to ignore the advice and yell at module devs...

[lost summit]

seems to serve more as a "these modules are updated, why isnt yours" from my experience 😕

[tawdry fog]

Make less popular modules like me and no-one cares :)

[static bane]

Maybe I can add a big warning at the top of MCC to tell people not to ask devs these questions. Might help

[lost summit]

(it wont)

[tawdry fog]

It's still nice reminder that badgering devs isn't going to make it happen faster (usually).

[crimson gull]

Never too many of those, considering recent comments.

[static bane]

I hope we can keep MCC around for v11 because I'm very proud of it. It was definitely not the intention to cause anxiety or frustration, so I'm very sorry to hear this 😥

(the reason that I mention MCC is because it is inherently linked with the spreadsheet at this point and is probably exacerbating the issue by making the data more accessible)

[lost summit]

it very much is 😅

[weak birch]

That's...disappointing to hear.

[weak birch]

I was advised there was a v10 copy that was near ready, but not ready yet, so i tagged it the way i've tagged every case of that.

[lost summit]

of course, it may provide benefits that are invisible to me, which is why i prefaced these comments with them being anecdotal 🙏

[weak birch]

Sorry- what i meant was it's disappointing to hear that the community is taking the spreadsheet as instruction to pester devs to update.

[lost summit]

yea, and i am 100% agreed on that part

[lilac idol]

ae-to-chat : O/Yellow. Start of turn effect list works, notification on effect creation does not

[ashen belfry]

Does the spreadsheet still update (periodically) when we push a valid v10 update or do we need to update here?

[static bane]

I think it does, yes

[opaque sage]

FlexUi is now v10 compatible

[dim sandal]

to clarify, the pin says the script runs every few days...just so people don't expect an immediate update.

[silver egret]

Hi, "Legend of the Five Rings (5th Edition)" is now v10 ready

[static bane]

wst is not compatible with the latest versions of V10 yet, only versions before testing 4

[timber sparrow]

Hackmaster is working under v10, now.

[pseudo basin]

Hi World of Darkness 20th edition has now released a V10 version that is out in public testing.

[ocean bay]

Hey there ddb-game-log is v10 compatible from the last release

[kindred tartan]

Hi Against the Darkmaster has now released v2.00 for FVTTv10 for public testing.

[safe aurora]

GM Toolkit (WFRP4e) is no longer in pre-release. New version 6.0.0 is considered stable and FVTT v10.284 compatible.

[night glen]

Exalted Third, Exalted Essence, and Storypath (Scion) all have V10 versions up.

[quick crystal]

Sequencer and Tagger are both V10 compatible now

[weak birch]

i'll be cycling to run through these today sometime

[dusk mauve]

Hello 🙂
Custom System Builder is now v10 compatible !

[weak birch]

---------------All reports above this point have been processed-------------

[tidal badge]

"WFRP4e – Random Treasure Generator" works on V10 now

[honest bough]

Module Management+ is now v10 compatible

[quick crystal]

Rest Recovery is now v10 compatible

[timber delta]

(Just a general FYI for everyone — when you release a v10-compatible version, that'll automatically get pulled into the spreadsheet when it's updated next; no need to manually call those out 🙂 )

[umbral aurora]

Update for CD10 RPG System:
It will not be updated to V10 at all. Consider this system deprecated. The current version loads and works with a whole lot of warnings in V10, so it will likely remain functional until V13 comes out, but I have no intention of updating it.

It's my first system I ever wrote and it's an ungodly mess. I will instead release a new package for V10 with cleaner code, less chaos and fewer bugs.

[sleek wraith]

Updated Walls-Have-Ears:
CHANGED

• Moved to yarn stable for quicker builds and better dev experience (no zero-install though)

ADDED

• ESLint's configuration from FoundryVTT, I think it should be stricter though
• Compatibility with v10
• Implemented a muffling cache to avoid changing the filter nodes if no muffling is needed (preventing ticks)

[harsh wyvern]

Forien's Quest Log is v10 compatible. Released 6 days ago and not updated in the v10 spreadsheet. Cheers.

[sharp cedar]

Hi, can the package compatibility spreadsheet please be updated for Token Health? It's showing my module as archived (no idea why), when in fact I've already released a couple of updates for V10 and it's fully V10 compatible, tested in 285.

Also, why not pull data for the spreadsheet from the module.json file? If that were done, my module would already have been correctly listed as compatible in the spreadsheet. Seems like maybe we're missing something here. Might be there are other modules where you could ascertain their compatibility just by examining the module.json file.

[weak birch]

<@&596076164104323104> There seems to be some confusion about how this update process is handled---for clarity, it is not a fully automated process.

While we do pull from the data in our repository, the act of updating the spreadsheet is partially manual, in that I go through and update it to align.

At present I aim for twice per week, but sometimes that is once per week. You will have to have some patience with the fact that I can't be on hand to update it every day.

Secondarily, I am not able to entertain suggestions of how this could be improved at this time- any such suggestions would require dev hours we do not have available to commit to this project at this time.

[tawdry fog]

They're pulled from the version provided in the package admin page, which is also what's shown in the package listing on the website, and in the foundry install interface (and yes, if you don't update the releases in package admin, people are installing older versions of your module first).

[weak birch]

@novel hilli've noticed a few of your modules no longer have any release versions at all available---should these be archived?

[novel hill]

They've already been archived, I emailed yesterday and asked that to be done. I submitted a single V10-ready, merged module for listing earlier today

[weak birch]

cheers, sorry i haven't been through the inbox yet today--

[novel hill]

No worries 👍 Figured with the new journal capability and my own plans to expand the module concept there was no sense maintaining multiple modules over one merged one

[weak birch]

This will need to be cut with a new release on the package admin page to resolve- if you need assistance doing so please ask and i'll help in any way i can

---------------All reports above this point have been processed-------------

[livid seal]

@weak birch FYI I have a PR with full v10 compatibility under review right now, 7th Sea 2e (svnsea2e) should be v10 in a day or so.

[sharp cedar]

Thanks for taking the time to reply to me. Clearly, I am confused about what I need to do. I don't think I've visited the package admin page since I first took over managing Token Health. To be honest, I thought the module compatibility was pulled from the module.json file and I didn't need to go back to that page to update anything there. Can you please link that page? Searching for it I don't seem to be able to find it.

[weak birch]

it should be available from https://foundryvtt.com/admin/packages for you---you may need to log in on the main website first

[sharp cedar]

Thanks. It's updated there now.

[weak birch]

You'll want to check the other fields (such as verified and maximum core version) and it would probably be advisable to add a new line and delete your current if you'd like to push a notification to our #package-releases channel that it has updated, updating the existing line just changes the fields and doesn't push a notification out

[sharp cedar]

Rats. Now I'm confused again. The only fields that seemed to need updating were the version (was 0.4.something, now 0.5.8) and the minimum core version (was 0.8.6, now 10). I don't see a field on that page for verified and maximum core version. Presumably I must be on the wrong page...

[weak birch]

you may have to scroll right.

(our admin interface isn't the most aesthetically pleasing. >.>)

[sharp cedar]

Yep. That was it. Is it OK to leave maximum version blank if it's been tested with the latest version?

[weak birch]

sure

[cloud aspen]

lancer-speed-provider is now held pending v10 drag ruler update.

[quick crystal]

token-ease has now entered the v10 fold

[lost summit]

With a heavy heart, I intend to sunset DnD5e Helpers. It's relatively widely used, so once I get back into the country in about a week I will make a notice on the league server in case any brave soul wants to take over.

[thorny vale]

Everywhen game system now has an official V10 release.

[weak birch]

---------------All reports above this point have been processed-------------

[limber flint]

Starfinder has just released a v10 compatible version.

[livid seal]

@weak birch I released v10 support for 7th Sea 2e (svnsea2e)

[kindred tartan]

Veil Rider has just released a v10 compatible version.

[pliant tide]

SBC | StatBlock-Converter for Pathfinder 1E: I just released a v10 compatible version.

[ivory tapir]

Simple Worldbuilding Plus is now v10 compatible (and I've updated the display name in the package listing to remove the hyphen for better consistency).

[quick crystal]

ya know it! Item Piles has joined the v10 fray

[lost summit]

nova now has a v10 beta (multi-track)

[kindred tartan]

Reclaim the Wild has just released a v10 compatible version.

[velvet shale]

I'm not sure if the spreadsheet is still being maintained

[kindred tartan]

You may be right. The module compatibility checker has my veil rider system as not upgraded though. Trying to figure out why.

[weak birch]

I'm hoping to give the spreadsheet a 'final' update next week

things have been

busy.

[static bane]

I think it may be interesting to add the option for users/devs to contribute to the data from directly within the module as well as to access it on a standalone website. I think this would provide more utility for users, the data would be more accurate, devs would have more agency on what is shown for their modules (perhaps the option to opt-out), and it would be less of a burden on staff.

[weak birch]

if you think that would be less of a burden, you have never had to clean up after some internet jerkbag wrote racial slurs across every inch of a shared space.

[harsh wyvern]

contribute to the data from directly within the module as well as to access it on a standalone website

Doesn't mean direct access to editing the spreadsheet. What I believe Arcanist is suggesting is a way for developers to auto-report compatibility through additional UI / interface / separate DB of potential changes in MCC or on a separate website that duplicates the MCC like module listing. At least create a funnel to look at and check up on that is somewhat automated vs the various source collection that is the current process when it happens. Nothing would be public and no direct changes to the spreadsheet. At least that is how I interpreted it.

[weak birch]

we...already read the package listings.

**IMPORTANT NOTE: ** If you have released a v10 version of your package in the admin interface, our script (run once every few days) will automatically handle updating for that, so you don't need to message me if your package is compatible and listed.

[harsh wyvern]

Yeah I was generally aware of that.. Too bad it doesn't also auto-update the spreadsheet. Then perhaps just giving someone that is trusted that data to update the spreadsheet could help. 😄 My understanding at least is that the spreadsheet hasn't been auto-updating.. Could be wrong..

[kindred tartan]

Well, my Veil-Rider system has that and was posted above on 22-09-22 and still shows as incompatible. The v10-compatible version is listed first, so might that be the issue?
My Reclaim-the-Wild system was only posted above for v10 compatibility on 27-10-22 but is not listed in the spreadsheet at all. It was officially listed as a new system for v9 around 28-09-22.

[tawdry fog]

IIRC packages released since the spreadsheet was started aren't listed as they're assumed to be v10 compatible (or not matter for tracking in it, as the dev can be assumed to be active and release v10 version "soon").

[polar heath]

You need to arrange your package versions on the website admin according to the versioning scheme you use. Re-arrange the order and it will work as expecfted.

That being said, I think we haven't updated the spreadsheet for a while, not sure whether we will continue updating this or not. It doesn't seem super valuable now that we are a month+ post V10 release.

[weak birch]

...Since i can't pin that message for some reason, thanks discord---

The purpose of this post is to ask that you inform me directly if:

1. You know your system/module is not functional in v10.
2. You have a functional version for V10 that you are holding back from publishing for any reason (such as wanting to prevent users from trying to install it on v9).

I have not yet roped any of our community helpers or moderators into testing, so I'm asking that you all check your own packages, and @weak birch with the ones that you know don't work.

The details I need from you when mentioning me on this are simple, i just need the title of the module, and whatever comment you need to make on it, such as "Broken, will not have time to work on it for several weeks"

**You can view the spreadsheet here: **
https://docs.google.com/spreadsheets/u/2/d/e/2PACX-1vRrcQL-r09Bi4MsbHUXlmOVx6DP4Ju143zRmk3HiUK2qU6gA3naxuSUcyv3EVhjMThXzJ_455jnyWfK/pubhtml
**IMPORTANT NOTE: **If you have released a v10 version of your package in the admin interface, our script (run once every few days) will automatically handle updating for that, so you don't need to message me if your package is compatible and listed.

Okay go

[dawn pivot]

Chromatic Dungeons won't work with V10.

[tawdry compass]

Nothing is compatible, working on it 🙃

Warhammer 40,000 Roleplay: Wrath & Glory
Warhammer Age of Sigmar : Soulbound
Warhammer Fantasy Roleplay 4th Edition
Dark Heresy 2e
DEGENESIS: Rebirth

Warhammer 40,000 Roleplay: Wrath & Glory - Core
Warhammer 40,000 Roleplay: Wrath & Glory Forsaken System
Warhammer 40,000 Roleplay: Wrath & Glory Litanies of the Lost
Warhammer Age of Sigmar: Soulbound - Core
Warhammer Age of Sigmar: Soulbound - Starter Set
Warhammer Age of Sigmar: Soulbound - Champions of Order
Warhammer Fantasy Roleplay 4e - Altdorf: Crown of the Empire
Warhammer Fantasy Roleplay 4e - Archives of the Empire: Vol 1.
Warhammer Fantasy Roleplay 4e - Core
Warhammer Fantasy Roleplay 4e - Death on the Reik
Warhammer Fantasy Roleplay 4e - Enemy in Shadows
Warhammer Fantasy Roleplay 4e - Middenheim
Warhammer Fantasy Roleplay 4e - Power Behind the Throne
Warhammer Fantasy Roleplay 4e - Rough Nights & Hard Days
Warhammer Fantasy Roleplay 4e - Starter Set
Warhammer Fantasy Roleplay 4e - Ubersreik Adventures I
Warhammer Fantasy Roleplay 4e - Ubersreik Adventures II
Warhammer Fantasy Roleplay 4e - Old World Bundle
Universal Battlemap Importer
Selective Show

[safe aurora]

GM Toolkit (WFRP4e) is Blocked until WFRP4e system is OK.

[iron knot]

KNAVE, broken, v10 update in progress

[civic moon]

Cryptomancer is broken in v10 and won't be ready until updated typescript types are available.

[plain ether]

• Tiny MCE Extended: v10 compatible

• (Whisper) Sweet Nothings: v10 branch ready

• Salvage Yard: v10 branch ready

• Token Mold: Compatible w/ warnings

• Regions: Compatible w/ warnings

• Masks! Unofficial Character Sheet: Not compatible

[ivory tapir]

Systems
Toolkit13 - v10 branch WIP
PbtA - Not started, unsafe in v10, will finish before stable

Modules
Legend Keeper Integration - Not started, likely unsafe, will finish before stable
Simple Worldbuilding Plus - Not started, likely unsafe, will finish before stable.
Combat Enhancements - Not started, will finish before stable

[quick crystal]

Sequencer: Branch ready
Item Piles: Will update post V10 stable release
Rest Recovery: Will update post V10 stable release
Token Ease: Will update post V10 stable release

[limber flint]

Starfinder is currently broken on v10. I know what the issue is and have a vague idea on how to fix it, I just haven’t had time to work on it.

[kindred tartan]

GRPGA - Likely unsafe, will start post stable v10
Against the Darkmaster - Likely unsafe, will start post stable v10
Veil Rider - Likely unsafe, will start post stable v10

[heavy viper]

Pathfinder 1 - broken
Spheres for Pathfinder 1e - blocked by the Pathfinder 1 system

[weak birch]

(note, please ping or reply to me here when commenting, it allows me to keep a log of things i haven't noted on the spreadsheet more easily.)

[limber flint]

@weak birch Starfinder is currently broken on v10. I know what the issue is and have a vague idea on how to fix it, I just haven’t had time to work on it.

There 😉

[weak birch]

XD

Don't worry if you've already commented

i'll just log those before i call it a day so that they're done

Thank you everyone for your responses already

[clever wolf]

Anyone got a link to a procedure describing the simplest dual v9 + v10 dev env setup on Windows (and by simple I mean no VM)?

[weak birch]

sec, matt recently released a video that'll give you the quick and easy steps

[weak birch]

it was for prototypes but it will work the same for non-prototypes:
https://www.youtube.com/watch?v=B74ZAp3xx3o&t=1s

Just do the smart thing and backup your data folder before doing anything, just incase

[bright night]

@weak birch Wasteland Ventures is known broken and I will only start porting it to V10 once the league types at least have the DataModel/DataField changes in. @plain reef is working on that.

[weak birch]

RE: Selective Show----I believe the featureset it offers is becoming core in V10.

[tawdry compass]

Cool! I'll keep that in mind

is it in dev2? I haven't checked

[weak birch]

i think so?

sec

[weak birch]

https://github.com/foundryvtt/foundryvtt/issues/2842
Yeah, dev 2

Based on that should i mark selective show as "will not be updated?"

[tawdry compass]

Just delist it then I suppose

sure

[weak birch]

cool, cheers

[terse narwhal]

Wands & Wizards WANDS Rulebook - not sure when I'll be able to work on this but will asap (may be a month or 2)

[slow imp]

About Face - V10 branch ready
Health Estimate - V10 branch ready
Party Overview - Safe to use.
Polyglot - Waiting on V10 stable because Journal interactions are broken currently.
Tormenta RPG e Império de Jade - Safe to use.

[wispy palm]

DAE, Midi-QoL, Item Collection definitely not compatible.
About-time/times up unknown.

Plan to start migration next week.

[pseudo basin]

World of Darkness 20th edition does not break the world entierly but it has serious problems. Support V10 has not started but is in plan, most likely time estimation will start after summer.

[fossil imp]

Crossblade is not compatible with v10 yet. It's been on my list and I plan to take a look soonish, but I'm not sure how long it will take.

[fringe ocean]

DDB Importer - broken in V10. Private V10 version in development.
Tokenizer - mostly works. A couple of snags need ironing out. Not expecting problems.
Grit & Glory - unknown, requires some dependencies updating .

[empty dew]

Cypher System - Not compatible. Working on it.

Disable Mouse Wheel Control for Sliders - V10 Compatible

[upper kayak]

Dungeon Crawl Classics - Not compatible. Will start on it when I have time, but from watching the chatter v10 seems like a huge undertaking.

[timber sparrow]

Hackmaster, broken, v10 update in progress

[tidal badge]

WFRP4e – Random Treasure Generator is Blocked until WFRP4e system is OK

[woeful cipher]

Symbaroum - Not compatible. V10 in progress

[umbral aurora]

Celenia D10 Roleplaying System - Compatible with V10.

Not updated, however and will require maintenance before V12 .Will throw out a lot of warnings, but no errors.

Planned release of V10 re-code after V10 goes live. It's in progress.

[heavy valve]

@weak birch
SWADE Immersive Macros and SWADE Ultimate Condition Changer:
Not safe for v10, awaiting stable v10 SWADE system version before update.

[civic moon]

Your info on the Wicked Ones system seems outdated. It was updated for v9. Compatible core version in the json file is 9.245. Maybe it wasn't updated correctly somewhere else along the line? @tacit solar / @harsh temple

[tacit solar]

Thanks for noticing. I did an update with some minor 0.9 compatibility fixes after there were some minor issues but I did not update the entry in the spreadsheet (didn't even know it was something to be done after release.

[civic moon]

That was more for @weak birch's sake, you'll have to report on the state of its v10 compatibility here.

[analog light]

@weak birch Token Says v10 branch is ready and awaiting v10 release; Target Recall branch is ready and awaiting v10 release; Danger Zone broken and under development for v10.

[tacit solar]

Still good to get an update on the mismatch. Didn't have the time to do any testing for WO in v10 but that might be something to put on my to-do in the hopes of getting that done soon.

[weak birch]

Looks like the admin interface listing data is incorrect - 9.245 is listed as minimum core, but verified (compatible) is 0.88

could be resolved by @tacit solar with a quick change to "verified core version" on https://foundryvtt.com/admin/packages/package/836/change/

[tacit solar]

Thanks. Updated to that for now. Will need to check for the current build soon and update again

Been out of the loop for quite a bit

[weak birch]

--------------All reports above this point have been processed--------------

[flint cave]

@weak birch AGE System (unofficial) is broken on v10. Working on a v10 branch. It will be published only after v10 has a stable release.

[mighty gorge]

@weak birch Party Resources works in v10. Its v10 branch will be published after v10's stable release.

[little orbit]

FantasyMaps map canvas works with v10 (naming fixed in database now, will update the manifest during the weekend)

[dim sandal]

@weak birch Wildjammer: More Adventures in Space current release is known broken on v10. I have a branch for v10 working and plan to release on or before v10 stable.

[static bane]

Journal Code Editor (jce) doesn't work on v10. I intend to update it eventually, but that may not be before v10 stable.

[clever wolf]

As far as I can tell, I won't have anything to change in system "Castle Falkenstein" for it to be compatible with v10 (accepting the 'data'-related deprecation warnings for now). But I will only be able to mark the system as actually compatible with v10 when Core cards regressions have been fixed (see #956307084931112960 message).

[static bane]

forien-custom-fonts should be archived since custom-fonts replaces it

[polar heath]

@weak birch the dnd5e system is updated for V10 on the v10-dev branch https://github.com/foundryvtt/dnd5e/tree/v10-dev. It is not yet publicly released but can be installed for testing.

I anticipate us publicly releasing a dnd5e version for v10 on Thursday to coincide with Dev3.

[terse narwhal]

Got a moment to test the Wands and Wizards WANDS Rulebook module in V10 and everything is working fine. Will add V10 compatible in next update but works as is.

[static bane]

btw if you change the verified core version on the package admin panel, it will side-grade your users, so there's no need to make an entire release just for this.

[terse narwhal]

Oh that's useful. Thanks.

[dawn pivot]

@weak birch The Chromatic Dungeons system should be good for v10 now, there's a separate v10 branch here: https://github.com/wyrmisis/foundry-chromatic-dungeons/tree/v10-updates

Turns out I was wrong about it being borked; I just had to clean up some deprecation warnings 😅

[desert quarry]

Systems:
**Mutant Year Zero **- Not v10 ready. Waiting for v10 stable to finish the updates.
Fallout 2d20- Not v10 ready. Waiting for v10 stable to finish the updates.
Achtung Cthulhu- Not v10 ready. Waiting for v10 stable to finish the updates.
Talisman - No plans to update to v10 atm.

[clever wolf]

An update on "Castle Falkenstein": to keep the console clean, I'll at the very least release a patch to suppress the datamodel-related deprecation warnings for users with CONFIG.compatibility.mode before v10 hits stable. And I'll also consider having 2 separate branches / versioning tracks for v9 and v10 soon after or maybe even before v10 hits stable.
So I think this mean you can mark "Castle Falkenstein" as "G".

[ivory tapir]

@weak birch I don’t think the sheet picked up the v10 update for the Dungeon World system, but it has a v10 compatible version available through the package listing.

[night vine]

Effect Macro, Requestor, Z's Formulaic Recharge, Concentration Notifier: all compatible (with warnings) already. All getting updated after v10 stable release to remove warnings (updates ready already).

[waxen ledge]

"Share Media" V10 ready. Awaiting to be published.

[fringe ocean]

Tokenizer is now v10 compatible

[ivory tapir]

Combat Enhancements is now v10 compatible

[slow imp]

Polyglot - V10 branch ready

[high dune]

• FXMaster: Fully supports V10
• Dungeonslayers 4: Broken, I will work on V10 support as soon as the TypeScript type definitions are ready
• Per Actor Roll Mode: Fully supports V10
• Keyboard Layout: Fully supports V10
• Foreground Drawings: Broken, I will work on V10 support as soon as the TypeScript type definitions are ready
• Autocomplete Inline Properties: Fully supports V10
• Tickwerk: Broken, I will work on V10 support as soon as the TypeScript type definitions are ready (will actually be quite a bit of work since I was overriding the round and turn properties on the Combat class, which now is not possible anymore since they are now DataModel properties...)
• Darkness Dependent Vision: Broken, I honestly think I won't update this for V10 at all, since I don't use it myself and I think I'll do a completely new take on properly implementing rule based vision for Dungeonslayers 4 (which this was an attempt for), using the new vision modes feature. I think I'll put out a new release that also declares compatibility.maximum to be "9".

[ivory tapir]

• PbtA system is now v10 compatible
• Simple Worldbuilding Plus: This module is now on hold and I'll revisit adding v10 support after Simple Worldbuilding gets a v10 compatible version.

[ashen belfry]

Simple Calendar works with some errors (around notes which are journal entries). Working on updating it for v10.

[analog light]

@weak birch Token Says, Danger Zone and Target Recall are now v10 ready