Gweneph

I believe the timer starts when the server receives the message, or possibly from the timestamp of message creation. So it's expected that the message would already be expired as...

The LuaLS docs mention type narrowing issues in the overload annotation: https://luals.github.io/wiki/annotations/#overload which points to this issue: https://github.com/LuaLS/lua-language-server/issues/1456 So this does sound like an upstream issue, but I'm wondering how...

sorry it took so long to get back to you. We have a launcher that uses Factorio's stdout that we're using as a layer between FMTK and Factorio and apparently...

Ok... so without the launcher in between now the type narrowing seems to be working.... Here's the dump when our launcher is in-between: ``` 2024-06-29 18:39:53.530 [info] Active Factorio version:...

Well, I got the version check to pass, and now the type narrowing seems to work about 30% of the time on my original Factorio Version configuration, but 100% of...

Here's mine: ``` { "folders": [ { "path": "." }, { "path": "../.." } ], "settings": { "Lua.workspace.library": [ "c:\\Program Files\\Factorio\\data" ], "Lua.workspace.userThirdParty": [ "c:\\Users\\...\\AppData\\Roaming\\Code\\User\\workspaceStorage\\a0abab6ef892f43cd580f1486a98ca3d\\justarandomgeek.factoriomod-debug\\sumneko-3rd" ], "Lua.workspace.checkThirdParty": "ApplyInMemory", "factorio.versions": [...