Silentwings wrote: ↑31 Jan 2019, 20:45
I'm afraid the real point here is that its not just about you or players of game xyz, who might well (at least, in the short term, before hardware progression catches up with you) subsist on with zero work / changes.
The point is that engine devs usually provide the hardest work and ask for nothing back, but this time they do need something back, and they are confident that it directly affects the survival of the whole project.
It's always about the players. We do not live in communism so the market decides. Btw, now that there has been a year since this very important change for engine dev, where is the new version? I can just see the last version is from 2016. Wasn't this change supposed to help development?
103 breaks compatibility with bos scripts and fixing it would require us to manually compile 750 scripts
Since both BA & TechA rely on bos scripts, and have certainly not manually edited and recompiled each individual script, I don't believe this. If there is a degree of truth inside it somewhere, please explain - presumably BA/TechA/others already found a way to do whatever you're concerned about.
103 changes the parameters of the killed function, which need a fix and a subsequent recompilation to be made. I don't see how this could be automated. That's why nobody has done any work on xta for some years.
absence of desyncs, because the path cache
Lobbys with multi-engine support are required since years ago, no issue here.
Not multi-engine. Multi-game. Game has also a cache, and this is not engine-specific. It has been put that this could cause desyncs.