Update: With help from Marco from the comments of this post, I have managed to make some changes to the exe and now it should not appear as a threat for antiviruses anymore. But I need people who had this problem to confirm if the fix worked, so please, if you had security problems with the mod's exe, update, check again and report here.
For the past month I have been working on one, if not THE biggest update the mod ever had.
I have a total of 18 new maps, focused around Africa and Oceania, some incredibly awesome stuff and I am really excited to finish everything and release it.
But for all the excitement and pride that I have working on this project, there is also a lot of sadness and helplessness.
As some of you might know, for years AoE3 modding has been very restrictive and many times when someone suggested something radical or even somewhat simple looking, many times the answer was the same: "AoE3 modding is very limited and we can only do so much with what we have".
But a while ago this changed. Two very awesome guys joined forces and released the Unhardcoded Patch, a tool which allows us to do things which were impossible before, like adding completely new civs without replacing any existing civs, including population increase and so much more.
But this awesome patch has a nasty side effect, being applied on the game's exe, it makes the exe lose its official digital signature from Microsoft and this makes it show up as a threat for antiviruses.
I don't know how to fix this, and what I found on the internet, it all costs money, money I cannot pay and even if I did buy a new digital signature I have no idea how to implement it.
I don't want to deal with all this mess, I just want to mod and make awesome content.
I need help, or else the mod will suffer for absolutely no reason.
If anyone has any idea how to work around this or any other info, I'm all ears.
You can check the mod's exe HERE, and if you click on File Detail you can clearly see the problem, which is:
Signature verification The digital signature of the object did not verify.
There's more to this though, the mod's Patcher also used to show up as a threat, and still does for some, for the same reason.
Shyke, the Patcher's creator did all he could to improve the Patcher so that wouldn't happen anymore, but...
We need help.