openmw.org

You _can't_ practically sandbox python so that's a no go for OpenMW but not for OpenMW-CS where it can be used.

Actually, scripting support would be helpful in OpenMW-CS - as in, automating actions in the CS itself, not writing game scripts. And you cannot expect modders to learn an entirely new programming language just to do menial automation of the editor, so it has to be the same language as used for scripting the game. And I don't see oldscript or even oldscript+ being particularly useful for scripting the editor.

Python is the standard scripting language for desktop applications.
Using something else for the cs is imho the wrong move.
(sorry for beeing off topic)

Eli2 wrote: ↑16 Jun 2018, 20:39 Python is the standard scripting language for desktop applications.

We do not choose a language for desktop application, we choose an embeddable scripting language for game engine to provide flexible modding tools, dehardcode game mechanics, AI, automate editor, provide event-based hooks, etc.
Lua is faster than Python, especially when reading data structures from native code (Lua was designed as embeddable extension language).
As was mentioned above, Lua is easily to sandbox than Python.
Lua is widely used for game scripting, so there are a lot of examples and documentation in Web.

Maybe i was not clear, i was talking about OpenMW-CS, that is why apologized for beeing off topic.

Zini has been very clear that the plan is to allow the CS to be automated through Python scripts. Everything is fine on that front.

werdanith wrote: ↑15 Jun 2018, 10:05 Even if oldscript+ is engineered to be a technically sound, featureful and the Right Tool For The Job™, it's still a new tool for people to learn and documentation to be written for. A new potential wedge to separate the target audience. Quite a deterrent, that could lead to a chicken and egg problem with regards to adoption.

It's not a "new tool", it's an improvement for the already existing language. The thing people need "to learn and documentation to be written for" is, in fact, newscript. There is documentation for how to hook Lua into engine, but there is no documentation for API yet, because, well, there is no API.

Injazz wrote: ↑17 Jun 2018, 23:19

werdanith wrote: ↑15 Jun 2018, 10:05 Even if oldscript+ is engineered to be a technically sound, featureful and the Right Tool For The Job™, it's still a new tool for people to learn and documentation to be written for. A new potential wedge to separate the target audience. Quite a deterrent, that could lead to a chicken and egg problem with regards to adoption.

It's not a "new tool", it's an improvement for the already existing language. The thing people need "to learn and documentation to be written for" is, in fact, newscript. There is documentation for how to hook Lua into engine, but there is no documentation for API yet, because, well, there is no API.

On the other hand, there is plenty of documentation on using Lua's advanced features, or best coding practices, etc, while they would have to be written for oldscript+.

What I meant to say is, it would be a shame if I'd have to learn two completely different languages in order to script the game and in order to do some automation in the editor for said game.

That is, assuming modders are the target audience for the scripting feature. If it's just a framework to simplify things for OpenMW developers, then having two different languages is probably okay.

Ideally, you pick one and go with it. Either old syntax or new syntax, you don't use both or have to learn both.

I think he was meaning having to learn OldScript+/NewScript for the engine and Python for the editor.