Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I took a look and with the mod folder being in mods, I was able to run the exe from withing the zip, extracted and moved to the desktop, and it found the AoM installtion each time.
I assume you use a steam version of AoM?
Do you use multiple hard drives for your Steam Library? The tool was developed without that possibility in mind, so if AoM is not on your main/first connected drive that might be an issue (not tested).
If you get the message that AoM can't be found, the tool tried to find this folder in your Steam installation folder: "SteamApps\Common\Age of Mythology"
The steam installtion folder is looked up in your registry here:
(go to your windows search and type regedit and look up)
(for me on Win10, in SOFTWARE, it automatically uses the subfolder WOW6432Node first instead of going to Valve directly.
There you will find the Key InstallPath.
If the combination of that install path value and \SteamApps\Common\Age of Mythology is not the correct installation path of AoM, there is not much you can do besides making sure AoM is in that location as the tool does not allow you to pass any other path.
If this is no solution for you, I can take a look to make the tool able to work with a split up Steam library, I can't promise an exact time frame though.
Sorry for only answering now.
If you still want to try and have this issue, can you try to unsubscribe and resubscribe?
For me I get the correct "Ozharas XML-File Mod-Merger" folder in mods, that contains a zip file, that contains the programm exe.
Saying that the tool cant work without an AoM installation, despite the game being installed and playable. How can i get the tool to recognize my installation?
There went something wrong while merging the files you had selected. ;)
To analyse it better, I need those files you tried to merge.
You can send them to me at aoe-modmanager@web.de
That said - I cant remember having merge errors back when I first released the tool. Now while reworking it, there were errors trying to merge proto xml files.
Errors I can't just fix, because for the actual merging I'm using a class from microsoft that is supposed to be able to do this. I don't have access to that class and it doesn't give me good errors so I would know what exactly it can't handle.
The error from your message is the same I got with the proto files - they just mean, that the merger is trying to access an object that is supposed to exist but doesn't - pretty generic.
The only real solution here would be to develop the whole merging logic myself - and that's nothing I'm really looking forward to doing being honest.
I sort of also came back because of AoE2:DE but yeah...
2.7 kinda broke a lot of shit sadly.
I honestly don't want to activly abandon my mods, but I still can't tell any time frame.
With me being back and hopefully more active right now, I will try to make this one of the first mods I take care of though.
For my own taste this is much too uncertain but I won't promise anything I don't know I can stick to.
I didn't buy the expansion for now - thought to wait until I knew it's not bugged/unbalanced too much. Seems I have to wait a little longer...
In theory the different protox versions should be no problem unless their structure got changed for the dll literally just scans all nodes and everything not present in the 'main' file gets importet from all other files you want to merge. In case the same nodes exist but with different values, the values of the file with the highest priority get used.
If there are structual changes made to a file and you try to merge versions with different structures, this approach will mess the merged file up though.
It then really depends on the actuacl structure changes if that merged file will work or not.
For the formatting - yes, the dll I'm using for the merging right now doesn't return that in a formatted way and since xml file modding wasn't officially supported for a long time (didn't check if this changed in the meantime) - resulting in less use for this tool, I descided to further use that dll instead of writing my own merging routines or searching for a way to apply formatting afterwards until xml file modding became better supported.
Did you try the solution mentioned in the error message? To resave your mod-status.txt?
yes - files can become corrupt for various reasons just from patches or even just playing sometimes - so forcing steam to verify each file is ok and reload them if necessary should always be step #1 - makes every further investigation much easier - or fixes the problem by itself.
Never encountered something like that for now - but it's some time since I last worked on the tool - and maybe the last expansion or a patch changed something...
Did you try to verify your game cache?
Thanks for the hint.I'll take a look at that at some point (AoM isn't my main priotity right now to be honest - I still have a huge bunch of mods for AoE that need to be updated for AK)
In that case you need to do what the message tells you - open the file and save it in the correct text format using the 'save as' option.
Without doing this, my tool won't work.
Seems this information 'vanished' from my description at some point.
I got the files and took a look. Sadly the error occurs in a third party dll I'm using for some stuff and for now I can only say that when the two files are merged for some reasons I still need to discover, there are a few xml-nodes missing to rebuild everything correctly.
Therefore the merging process quits at this point.
So I will need some more time to find the real cause of this issue... :(
It also seems to be something I never encountered while testing, for as you can see the error is not covered by my tool but shows a system error message instead.
Can you send me the two files at aoe-modmanager@web.de, so I can take a look at what's going on myself?