Post

Slikey
Slikey@slikey·
Either way, we are upgrading the priority on making mod & game versioning more straight forward. Especially with hotfixes causing the same warning it is more annoying than we expected. I'll see when we can talk about the tech we have planned at a later date, but rest assured that we are painfully aware of the implications of the "one client" policy and we aim to bring a solution that seems more like magic to ensure compatibility and keep mods breaking to be rare event rather than the norm.
Slikey@slikey

I've repeatedly said this in the past: We aim to have a proper deprecation policy in place to prevent this but right now the logistics of imposing that on the team while keeping updates up is not feasible. I gave us 3 months of "breaking mods" post release to develop this deprecation policy and we aim to implement it by the end of the 3 months. Right now the best you can do is to prepare you mods on the final build of pre-release to ensure compatibility when release drops. I know it is a pain but in order for the game to thrive, we need to make significant progress on the game and technological foundations. It sucks and sadly this is something we'll have to suffer through for a little longer. It's the cost of rapid progress that keeps the player base alive. Sorry 😥

English
9
13
278
13.9K
vemorph
vemorph@vemorph·
@slikey I personally think you are more than okay with the current strategy. Before EA you said repeatedly that Mod API will change a lot. I totally get the value for the modders but you have plenty options for them, so there’s nothing to complain. We all love core game progress!
English
1
0
0
279
vemorph
vemorph@vemorph·
@slikey And in all honesty, it‘s not meant to critically let alone the modding community; We need to appreciate what your game did and will do for modding, but there‘s nothing to sorry about. You do great and we all get that you want to proceed fast, so the should have all our back. 🤟🏻
English
0
0
0
13
Paylaş