Diagnostics break when adding FMTK configuration

[yaSebastian]

Before adding FMTK configuration, all my workspace files are diagnosed correctly and completely. (With lots of additional issues due to the Factorio types not being known, as it should be.)

When picking a Factorio version and adding the configuration to my settings.json (see below), suddenly, my workspace files are only fully diagnosed when I open them. Some rare issues are being shown without opening the files, e.g. the following one:

This function expects a maximum of 3 argument(s) but instead it is receiving 4. Lua Diagnostics. (redundant-parameter)

Most issues only show up when opening the files, though, which complicates things.

I've tried playing with different combinations of settings a lot, but I can't get it to work successfully, generally ending up with either only open files being diagnosed or the extension's type definitions not being used by the Lua Language Server.

This is what the configuration looks like when I start from a clean and empty slate:

{
    "factorio.versions": [
        {
            "name": "Steam",
            "factorioPath": "~/Library/Application Support/Steam/steamapps/common/Factorio/factorio.app/Contents/MacOS/factorio",
            "active": true
        }
    ],
    "Lua.workspace.userThirdParty": [
        "/Users/yasebastian/Library/Application Support/Code/User/workspaceStorage/e30b50b06d79259b691cf107f83028ac/justarandomgeek.factoriomod-debug/sumneko-3rd"
    ],
    "Lua.workspace.checkThirdParty": "ApplyInMemory",
    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/CVS": true,
        "**/.DS_Store": true,
        "**/Thumbs.db": true
    }
}

Any help would be greatly appreciated.

[kuxynator]

I don't understand why no one has replied here for over 2 months.
is the project dead?

"Lua.workspace.checkThirdParty": false,
false enables all the diagnostics again, but seems to disables complete Factorio support from this extension