|
Joel Billings -> RE: Patches on Modded Scenarios (7/30/2021 4:12:09 PM)
|
quote:
ORIGINAL: Naughteous Maximus
I was wondering, when your whole mod is an alternate scenario based off a vanilla scenario, will the patches work on that modded scenario? [&:]
The answer is, it depends on what you mean and what you have changed in your modded scenario.
Some data in all scenarios comes in from the generic data files. An example of this is the leaders that are available. When the scenario is loaded for play, the generic data is loaded in from the data files on the computer that is setting up the scenario. When we change a leader in the generic file in a new update, and the player has updated to the new generic file, if he starts a new game, that change will be loaded in for any scenario. So at the moment you cannot create a new leader just for one scenario. However, units and game events are not generic, they are scenario specific. So if you create a new scenario and change a unit or change an event, those changes will stick and be in the scenario even after we update the game. When we release an update, if we want to make a change/correction to an event, we are making it in each applicable scenario file. So if you have a modded scenario that has that change, you'll have to make it yourself in your modded scenario.
Now in WitW, we had a way to "lock" the generic data files in a modded scenario. This meant that you could change more things (for example make a change in the stats of a ground element), and those changes would stick for that scenario. However this also meant that you would not benefit from any changes/corrections we made in the future to the generic data files that you locked, so in this case the ground.dat file. In WitE2 we had to disable this ability to lock generic data files. We hope to be able to bring back that capability, but there have been more pressing issues and we haven't yet been able to do that. It was complicated by the fact that we now have 3 files (hexes, cities, weather) that are semi-generic). That means that parts of the data in these files are generic and are loaded in for all scenarios, and parts of those files are kept in each scenario file. Pavel needs time to figure out how to deal with these in the editor when it comes to locking the generic files.
In fact Pavel has many ideas for how he'd like to improve the editor, but between bug fixes and adding the in-game scaling (which was determined to be the main priority item due to the increasing number of 4k monitors), he hasn't had the time to work on the editor aside from a few quick bug fixes. We do hope later this year to reach a point where he can work on the editor. The editor is very powerful, but we also realize putting together a scenario is a big job, and there are many traps in the editor that users can fall into (especially given the lack of documentation). Especially with the event editor, there is now an ability to make more interesting smaller scenarios, but we find that most players of WitE/WitW/WitE2 gravitate toward the campaigns. It is much easier for modders that just want to make a few changes to an existing scenario. But in this case, even when we have allowed locking of the generic data, they face the issue that if they lock some data in order to make a change that will stick, they will not benefit from future official changes in that data. We see the data in WitE2 as something that improves over time as more information becomes available. We're both fixing mistakes in the data, and also making adjustments as more information is brought forward. We try to provide info on the changes we're making in updates, but with so many contributors and so many changes, we don't claim that we are providing full detailed info on every change made. We appreciate that some modders want to lock the data and will accept they won't get future changes unless they make them themselves, and we do plan on adding locking of generic data in the future.
I hope this helps explain the situation.
|
|
|
|
