MWSE has evolved further and added LUA, allowing more modding opportunities for Morrowind. I think it would have been done sooner had OpenMW not existed and people got tired of 'waiting' on OpenMW. That's a reasonable decision and I think LUA is a very good choice as a replacement for mwscript in the scope of MWSE/Morrowind.
OpenMW will be taking another road, one that makes mwscript suck less.
However, I personally think, and as has been already discussed in the forum multiple times, if you can provide a way to properly sandbox and prevent native code execution, then you'll have a real chance of seeing it in OpenMW.
Lua seems to be at the for-front here for three reasons:
1) TES3MP already has it on the server-side and TES3MP _will_ be merged into OpenMW post 1.0
2) It makes sense since MWSE also supports Lua.
3) Lua is easier to sandbox than other scripting languages which helps alleviate security concerns.
Another reason why I think people are concerned and frustrated is that this post-1.0 design document is much talked about and not yet seen in full. This is unfortunate because people fear the unknown and details are sparse. Zini has been working on this for awhile and wanted Scrawl to proof-read it to see if it made sense. It is supposed to be a guide for the way forward, but that isn't as set in stone as people might think.
To quote Field Marshal Helmuth Karl Bernhard Graf von Moltke:
orKein Operationsplan reicht mit einiger Sicherheit über das erste Zusammentreffen mit der feindlichen Hauptmacht hinaus.
No matter how great and well-thought out, a plan will change when dealing with new events and it has to be adjusted accordingly. No one is going to blindly follow orders or be apart of a project that they don't believe in. OpenMW developers understand that. So cut us a little slack please.no plan of operations extends with any certainty beyond the first contact with the main hostile force
I believe there is enough wiggle-room to please modders and move forward.
If someone wants to lead the effort to see Lua go into OpenMW, it likely won't be an overnight affair. Like TES3MP, it will be a long living branch and will require a lot of testing along the way. Actually having something goes a long way to having it included in OpenMW. Any concerns about it can be hammered out and adjusted and I'm sure a compromise can be found.
Just remember, the only 'hard stance' that Zini has is:
Keep this in mind, then we may have something.Zini wrote:This is the one point where I take a hard stance. I do not compromise on security and there is nothing more to discuss.
With that being said, I'm going to split this conversation off from the main since it's another tangent.