Page 1 of 1

Wrye Mash for OpenMW -Need omwgame, omwaddon info.

Posted: 29 Sep 2018, 11:18
by polemos
Hi guys,

I am the the guy behind the "Wrye Mash 2018, Polemos fork".

I am also working on Wrye Mash for OpenMW and eventually TES3mp (as a matter of fact I started working with Wrye Mash so I could create a version for OpenMW, but I got sidestepped with bugfixing and adding things).

I believe I am ready to release my Wrye Mash version for OpenMW but before doing so I would like to check some things.

As a starter, is there somewhere I can read for the differences (all of them) and incompatibilities of omwgame and omwaddon with esm and esp?
I have searched but haven't found anything.

Thanks

Re: Wrye Mash for OpenMW -Need omwgame, omwaddon info.

Posted: 29 Sep 2018, 22:05
by AnyOldName3
Right now, the only difference is that OpenMW's CS doesn't compile any script bytecode, so if you renamed an omwaddon to esp, the only problem you'd have is that if it used scripts, you'd need to open it in the vanilla CS and resave it to get the bytecode. However, in the future, as post-1.0 features are added, omwaddon files will need to start holding extra data to control these extra features, so more differences will appear over time.

Re: Wrye Mash for OpenMW -Need omwgame, omwaddon info.

Posted: 01 Oct 2018, 10:46
by Zini
Here are our plans for post 1.0 development: https://gitlab.com/OpenMW/openmw/blob/m ... -stage1.md

That's only a rough outline and nothing is final yet anyway, so we have little that is actionable for you right now. I guess if you do have spare time and want to get a head start you could prepare for all text changing from legacy encoding to UTF-8. That is probably one of the first things we will change for 1.1. But then, this is still a good while away, so there isn't any hurry.

There is one useful change you could do right now. We added an additional format field to the TES3 record (you can find the source in components/esm/loadtes3.cpp), because the original way the format is specified is garbage.

The sub-record has the ID "FORM" and it contains a single integer (the file format version number). If this version number is 0 (legacy file format, essentially compatible with esm/esp) this field is not written to the file by OpenMW-CS (but when reading a value of 0 would still be valid).

So what you could do now is to check if this field is present (and has a value larger than 0) and if that is the case either show the user a warning or flat out reject the file as "too new"/not supported yet.

Re: Wrye Mash for OpenMW -Need omwgame, omwaddon info.

Posted: 01 Oct 2018, 21:10
by polemos
Nice, thanks guys.