14
« on: November 03, 2024, 04:30:21 pm »
Eh, after much deliberation, I've come to the point where I've given up on backwards compatibility with OXCE. Before version 1.3.8, almost all exclusive features were hidden behind the `ftaGame: true` mod property. By turning it off, you could play an OXCE mod (and vanilla) and expect generally similar behavior to OXCE except for just a couple of things. However, some interesting features are available with the property turned off, as they are minimally invasive and in general could even be part of OXCE. Turning the property on opens Pandora's box, normal mods won't work without adaptation. Of course, the FtA mod itself has this property enabled.
However, supporting backwards compatibility costs a lot from an engine development perspective - some simple features become much more complicated if I need to maintain the original logic. I've never positioned my engine as a universal platform (like OXCE or BOXCE), as my priority is to develop my game. Considering that over the years of development my fork has not received any interest from the modding community (most likely - quite deservedly so), I decided to completely abandon backwards compatibility. This way, the FtA engine will work correctly with FtA mods and potencial FtA-oriented sub-mods. I don't think anyone will have a problem with this. However, if you have a different opinion - I will be as always glad to get feedback. I'm especially interested in the opinion of representatives of OXC and its forks development community and your point of view on my solution, taking into account your background.