

But steam will only put the mod into the correct file, so it will cause the mod to not load properly. When the C drive has no documentation, it will create one by itself, and only recognize mods in this folder. The problem with the location of the game's Documentation was present in Age of Wonders: Planetfall, and that was because the game launcher only recognized the C drive as the documentation location. There may be multiple of this folder, but they will all have a "My Games" folder, so searching for My Games or AOW3 can quickly find them. Find this folder and put the mod files in it. So now that we know the cause, the solution is simple. It's hard to realize that the game itself created an invalid "Documents" folder because it wasn't called "Documents" at all. But the problem is that the name of the folder created by the game itself is a string of garbled characters.

Steam does not put mod files in this place, so there is a model loss.īut if it's just that I think most people can actually spot this problem and fix it themselves, because it's a very common situation and many games have this kind of problem caused by the location of the Docs. It will create a new but invalid "Documents" on the drive where the "Documents" folder is located, and then treat this place as the recognized location of the model assets. The weird thing is that it's not completely unrecognizable, it can read and load mods correctly, apparently because it recognizes the correct Docs location, but it doesn't recognize the new material in it.

The cause of the problem is that the game cannot properly read any new assets added by modders.

I'm just stating my personal guesses about the cause here, and the solutions I'm currently using that are confirmed to work. I'm not a professional, so I don't know what the real problem is. Phantasm Warriors are usually summoned so they typically have a mana upkeep cost.Actually I found this solution some time ago, but I'm lazy so I didn't post it here in the first place. Note: Currently, the cost and upkeep match the Tome of Wonders, which does not necessarily correspond to cost and upkeep from the method of recruitment e.g. The few units that have multiple types are listed under both, with details only listed under the first entry.
