I understand the problem: it's really a patch to an existing mod. I thought there was a chance that you need internal names only and not the very mod's name (at the risk of unwanted effects in case the player doesn't load the expected-but-not-explicitly-required mod). Let's cheer this patch for the main branch, then. Thank you very much for all of its users.

I think it would be possible to play with the newer version, but I'm not sure. Any updates to the main branch version should not be a problem, unless the name of the mod is internally changed in the package manager.

The main reason these requirements are there, is because AoW3 won't let you mod an imported project, you can only link to that project's resources. Without that link, this mod would overwrite any stats changes. It's really annoying, I know, but seems to be the only way to make patches to other mods.

I mean that you could assume that all the knowledge you've collected so far (in-game references?) is enough for your patch to run safely with any newer version of the mod. Is this reasonable to think so?

Hello, good new!
I quickly tested with T1 Orcish units and the expected improvements are here.

Although making explicit mod requirements is safer and the normal way to go, in case of PBEM & SP balance mod, I wonder if you could be less strict about those requirements. Racial Patch is now integrated into the mod, and this mod's component won't change until the stand alone patch is changed itself. However, PBEM & SP balance mod is due to change several times more, and you'll have to update your mod each time a new main branch is out (am I correct?). This is without saying that your mod is curently unplayable with the beta version.
Would it be then possible to just indicate in the changelog which version of PBEM & SP balance mod your patch is optimized (tested) for? And let the players use it with any newer versions of PBEM & SP balance mod?