Help us plan OpenMW's future

Feel free to discuss here about news on our blog
User avatar
Thunderforge
Posts: 489
Joined: 06 Jun 2017, 05:57
Github profile: https://github.com/Thunderforge

Help us plan OpenMW's future

Post by Thunderforge » 27 Jun 2018, 15:20

It's hard to believe that OpenMW 0.1.0 was released just over 10 years ago! What began as a barely functional ESM viewer is now a complete replacement for vanilla Morrowind and a complete engine for creating original games. There are still a few features that need to be polished, like shadows and AI recastnavigation, but the project is almost ready to become version 1.0, signalling to the world that OpenMW has full parity with the original Morrowind engine.

But that doesn't mean that our work is complete. OpenMW's project leader Zini, with feedback from the project's most active contributors, has produced the first draft of an enormous design document detailing the next steps that they think the project should take. The major focus is on improving modding capabilities (including "newscript" support, most likely Lua) and beginning the process of de-hardcoding game mechanics to allow mods to drastically alter gameplay.

Now we need your help. We'd like for as many people as possible to review this post-1.0 design document and provide their feedback. Have a change that you'd like to make? Submit either a Merge Request on GitLab or a Pull Request on GitHub. Want to talk about it with other contributors? Discuss it on our forum. This document is far from set in stone and will change as the project evolves.

Let's work together to plan how OpenMW will enter into its next ten years!

User avatar
Thunderforge
Posts: 489
Joined: 06 Jun 2017, 05:57
Github profile: https://github.com/Thunderforge

Re: Help us plan OpenMW's future

Post by Thunderforge » 27 Jun 2018, 15:23

If you'd like to comment on something specifically within the post-1.0 design document, I recommend that you create a new topic for whatever your concern is in the Organization and Planning subforum. The document is over 25,000 words and this topic is going to become overwhelming if people are talking about scripting, image formats, de-hardcoding, new features, and everything else.

sg1efc
Posts: 72
Joined: 16 Nov 2012, 02:35

Re: Help us plan OpenMW's future

Post by sg1efc » 27 Jun 2018, 23:22

Cool 8-)

claudekennilol
Posts: 56
Joined: 01 Aug 2012, 20:48

Re: Help us plan OpenMW's future

Post by claudekennilol » 02 Jul 2018, 13:55

> signalling to the world that OpenMW has full parity with the original Morrowind engine

What about mods that have scripts with flaws in them that work with vanilla? Do all "vanilla" mods work with Open MW now?

User avatar
wareya
Posts: 221
Joined: 09 May 2015, 13:07

Re: Help us plan OpenMW's future

Post by wareya » 02 Jul 2018, 14:00

OpenMW still has tons of minor mechanics/gameplay bugs, and some major ones.
paying attention to #1751/#1816 #2473 #3609 #3862/#3929 #3807 #4297

User avatar
psi29a
Posts: 4202
Joined: 29 Sep 2011, 10:13
Github profile: https://github.com/psi29a/
Contact:

Re: Help us plan OpenMW's future

Post by psi29a » 02 Jul 2018, 14:30

claudekennilol wrote:
02 Jul 2018, 13:55
> signalling to the world that OpenMW has full parity with the original Morrowind engine

What about mods that have scripts with flaws in them that work with vanilla? Do all "vanilla" mods work with Open MW now?
Broken scripts are broken, OpenMW-CS can help detect these broken scripts.

OpenMW 1.0 is not yet released, so no, not all "vanilla" mods work with OpenMW currently, but a majority already do.

We want to eventually have a 2 week long mod-hack-a-thon where we focus exclusively on Morrowind mods. Users, modders and developers helping to make that final push to cover as much ground as possible. It would be an event managed here, reddit, irc and discord but we hope to promote it across other platforms.

So we would love to see the community rally around OpenMW, at all levels, to help give it that extra polish for a vanilla drop-in replacement.

User avatar
Zini
Posts: 5504
Joined: 06 Aug 2011, 15:16

Re: Help us plan OpenMW's future

Post by Zini » 02 Jul 2018, 14:34

claudekennilol wrote:
02 Jul 2018, 13:55
> signalling to the world that OpenMW has full parity with the original Morrowind engine

What about mods that have scripts with flaws in them that work with vanilla? Do all "vanilla" mods work with Open MW now?
Let me make this clear once again. There is a class of scripts that aren't just scripts with flaws in them, but that are flat out broken. Both in Morrowind and OpenMW. But how these two engine handling these defects is different. Morrowind is basically just winging it by ignoring all problems, which may result in a behaviour that is either obviously broken or subtly broken or by accident works as expected. OpenMW on the other hand will always yell at you and stop the problematic script.

We provided a few workarounds for cases where the original meaning of the script is obvious and we may be able to add some more of these workarounds. But it is unrealistic to expect us to make OpenMW fail exactly in the same way as Morrowind in every single case. Besides, these scripts are defective. They need to be looked at and fixed; even if they seem to work in Morrowind. Ignoring these defects is what got us in this mess in the first place. In the long run everyone will be better off with not ignoring almost every single kind of script defect.

User avatar
AnyOldName3
Posts: 1092
Joined: 26 Nov 2015, 03:25

Re: Help us plan OpenMW's future

Post by AnyOldName3 » 02 Jul 2018, 15:45

When we have working NewScript and a working OldScript to NewScript converter, it might be a good idea to also have an OldBytecode to NewScript converter, too, even if it's implemented as a third-party CS plugin rather than a first-class feature. That would allow people to get their subtly broken behaviour back without polluting our clean implementation of everything else.
AnyOldName3, Master of Shadows

User avatar
Zini
Posts: 5504
Joined: 06 Aug 2011, 15:16

Re: Help us plan OpenMW's future

Post by Zini » 02 Jul 2018, 16:10

Wouldn't do us any good, since we also need to compile/translate the code in OpenMW. And if people need to take a mod through OpenMW-CS to translate it, they can as well go ahead and fix it. I doubt that the slightly broken behaviour (as you describe it) is desirable; at least not if you can have non-broken behaviour.

Chris
Posts: 1499
Joined: 04 Sep 2011, 08:33

Re: Help us plan OpenMW's future

Post by Chris » 02 Jul 2018, 23:44

In some cases though, the broken behavior is entirely a result of the CS' compiler's lax validation of scripts. That is, in such cases the bytecode itself came out fine, it's just a mess when trying to interpret the source text.

Post Reply

Who is online

Users browsing this forum: Ravenwing and 1 guest