MSG files "patch" system

[phobos2077]

1. Load additional MSG "patch" files for vanilla MSG files (dialog/ and game/) by mask: perks_patch_*.msg. Apply them on top of normal entries, overwriting data.

So for example, let's say we have dialogs/mcwhtevr.msg:

{100}{}{You see a dude.}
{101}{}{This is the dudiest dude ever seen.}

If we add dialogs/mcwhtevr.msg:

{101}{}{This dude is a wimp.}

Then in runtime the game will see this:

{100}{}{You see a dude.}
{101}{}{This dude is a wimp.}

2. Add metarule sfall_func2("set_message_item", int listId, int itemId, string text, string audio); :

• uses the same logic as "message_str_game" to find message list to edit
• on top of that, can also edit script message lists (maybe different metarule or with some kind of flag in listId)
• use 0x484D68 message_add_ to add/replaces messages

[phobos2077]

For (1) load order will not change which mod gets "priority" for it's msg patches, this might break normal expectation when from DAT patches lower in load order gets priority. Instead, the priority will be determined by patch name, in the same way as hook scripts work. This might be an issue and maybe require a generic solution:

Add a special function for searching files in DB by mask (how global scripts work), but that could additionally order these files by reverse order of databases they are found in.
For example:

• Mod1.dat
  • perks_patch_1.msg
• Mod2.dat
  • perks_patch_2.msg

Given mods_order:

mod2.dat
mod1.dat

In the engine it looks something like this: master_patches->mod1->mod2->master.dat.

As result, we'll get files loaded in this order:

perks_patch_2.msg
perks_patch_1.msg

So "patch_1" gets applied last, thus having a priority above "patch_2", as you would expect.

This same technique can also be applied for sfall global scripts as well.