openmw.org

Does the newscript have a name? (Looks over at TES3MP...)

Well, it looks like everyone has agreed on Lua.

So now it's a bit of chicken and egg... where to begin?

"If you build it, they will come"?

We will see ...

Zini wrote: ↑19 Jun 2018, 14:26 Well, it looks like everyone has agreed on Lua.

That almost sounds dejected.

Well, I am not happy with this turn of events. I elaborated extensively why I think it is a bad idea. But trying to force my own opinion though is unlikely to result in anything good in this situation, so newscript and most likely Lua it is.

Would the dehardcoding be done in oldscript+ or newscript .?

oldscript+-based dehardcoding was the plan, but now Zini may have to rewrite the whole post-1.0 design document.
though not really

There are bits of it that don't really make sense if we have access to a real language as there'll be something similar built into it already.

The script support for de-hardcoding features will be implemented in newscript. I don't intend to rewrite the design document. The scripting section is only 14 pages long anyway (of 81) and most of the functionality in it is relevant for newscript too. That's why we are not moving forward yet with newscript. I want to have the design document ready (we are currently reviewing internally), so that the group of people working on newscript can see it.