What this app changes on your PC, and how to remove it
aotd.exe is the same file as modwith.exe, its first name (same fingerprint).
modwith.ai app 0.1.0 is one program, aotd.exe, with no installer. This is every change its own code makes, as we traced it in the code it was built from (commit e802d21864). Its code adds no Start menu entry, desktop shortcut, service or startup item, and writes nothing to the registry. What we did not trace is at the end.
This version does not update itself: get a newer app from the releases page.
The names below, in this version's window: "the Library" is the screen called Home, and "the Doctor" is Your setup (its "Check and fix" is the Fix button there, after Check my setup).
Its own folder, %LOCALAPPDATA%\ai.modwith.app
- its log (log.txt, and the one before it, log.old.txt);
- downloads in progress (downloads). If you press Install before Plutonium is on your PC, the whole mod (about 1.4 GB) downloads there and is checked, then waits for Plutonium. Once Plutonium is installed, the mod moves into Plutonium's mods folder by itself while the app is open (it looks every 2 seconds, for up to 45 minutes), or with one Install press later. Until then it stays in that folder: Delete the download (in the Library, under More) deletes it, after saying how big it is. An older version still waiting there when a newer one installs gives the newer one the files they share, and is deleted;
- the names, sizes and last-written times of the mod's files as it put them in place, never their contents, and the folder it put them in (installed\aotd.json for Ashes of the Damned, one file per mod), so the Library sees at once when a file is missing or changed and offers Repair, and knows which files in the mod's folder are its own; while a move into place hasn't finished, the same file also holds the fingerprints of the files being put there. Remove deletes it;
- Your files (
Your files\<the mod's name>\<date and time, UTC>): anything in the mod's folder the app did not put there (a script or settings file of yours, a file of the mod's you changed, a file of yours where a new version puts one of its own, a link), which Update, Repair, Check every file, Remove and Your setup's Fix move out of the mod's folder instead of deleting, each press into a folder of its own named by its date and time in UTC, with a list (kept.json) written before and after each thing moves, so a press that stops lists what it had moved and what it was moving when it stopped (marked"moving": true; a folder being copied to another drive can then be part in Your files and part where it was). A later press never writes over anything already there. Before any of those presses moves anything, the Library (or Your setup, for Fix, a second Fix after one that stopped included) names every file it will move, however many (the list scrolls), and asks; when the app has no record of what it put in the folder, it says so and that the press checks every file first. The result says where they went, and Open Your files (in the Library and in Your setup) opens the Your files folder. An unzipped download Check and fix moved is inYour files\Unzipped downloads. On another drive than the mod's, a file is copied under a name nothing else has (.<name>.modwith-part, or.<name> (2).modwith-part…), checked byte for byte, given its name, and only then removed from the mod's folder, and only when that drive has room for it. The app never deletes anything in Your files but its own unfinished copies that a press stopped part way left: a list being written, and the.<name>.modwith-partof a file the run's own list marks as still moving; the next press (never a check) removes those. A file of yours with such a name stays; - the Plutonium folder it last installed into or started (plutonium-seen.json), so if Plutonium is moved or removed it says "Plutonium isn't where it was" instead of starting over;
- a small lock file (busy.lock), made the first time it installs or changes something; it stays there;
- the Plutonium folder you chose, if you ever chose one (plutonium-folder.json);
- the launch line it set for Play (launch-args.json, deleted once the line is put back);
- the window's own data (EBWebView, kept there by WebView2, the part of Windows that draws the window);
- a small lock file (self-update.lock, made at its first start; it stays). At each start the app also deletes a aotd-<version>.new.exe.partial beside it, a download an earlier version's update stopped, if there is one;
- if your PC has the app's older folder, %LOCALAPPDATA%\ai.modwith.aotd: the app moves that folder's log, launch note and folders into this one, and deletes the old folder if that leaves it empty;
- only if you pressed the buttons for them: other mods' files you set aside (set-aside), your Plutonium plugins you moved out (plugins-aside), and offline-only files the Doctor moved out (moved-out), each press in a folder of its own with a list of what was moved (moved.json), never over a file already there. One press, Put back files the app moved aside in Your setup, takes back both the other mods' files and the plugins, what their lists name, each to the place it came from and never over a file that is there now, and leaves anything else in those folders where it is. The offline-only files of ours stay in moved-out: nothing brings them back, and they are the app's own.
In Plutonium's folder, %LOCALAPPDATA%\Plutonium
- The mod. Ashes of the Damned lives in
storage\t6\mods\tm_transit_tessie. Install, Update, Repair and Check every file write there. A file the app put there itself (by its record above, checked again just before) that the new version no longer has is deleted, and if it can't be, the press stops and names it; anything else in that folder (a file of yours, a link, a file of the mod's changed since the app put it there, a file of yours at a place the new version uses) is moved into Your files (above), never deleted. Every log file there (a name ending in .log, or in .log and a number: the game's console_zm.log and its numbered copies, and any other) stays where it is on Install, Update, Repair and Check every file; Remove moves them into Your files with the rest, and names them before it does. A new copy of a file the app was putting in place from another drive (.<name>.modwith-newbeside a file of the mod's) that a stopped press left is the app's own: never named as yours, removed by the next press; a file of yours with such a name beside none of the mod's (or, on Linux, in other letters) is yours like any other. That is the one exception to "the app never deletes a file it did not put there": a file of yours named exactly like the app's own working copy of one of the mod's files is taken for the app's and removed. If the app has no record of that folder, every file it can't tell is its own (byte for byte a file of the version installed) counts as yours; a record from a version before this one tells only the mod's own files at the mod's own places. A file the app replaces is never written through: the new file takes its name, so another name for the old one (a hard link) keeps the old bytes. Remove deletes the app's own files there, moves anything else into Your files, then removes the folder, empty by then, and deletes its record (installed\aotd.json), a folder that was a link included. The app clears a read-only mark only on its own files, to delete them. A link or junction inside the mod's folder is moved as a link when Your files is on the same drive, and what it points to is never read, written or deleted; on another drive the app can't make a link, so the press stops and says to move or delete the link yourself. If the mod's folder is itself a link, the app works in the folder it points to, and Remove takes the link away, never that folder. A file another program holds open is never copied and left behind: the press stops and says to close that program. A developer copy of the mod (one with the dev menu) is never changed. A download waiting for Plutonium moves in by itself only into that folder when it isn't there yet or holds nothing; a folder that already holds files is left as it is, for the Library to show. - One game setting. The line
seta r_skinnedCacheScale "10"instorage\t6\players\plutonium_zm.cfg(your normal Black Ops II Zombies settings) and instorage\t6\players\mods\tm_transit_tessie\plutonium_zm.cfg(the settings used while Ashes is loaded). It gives the game room to draw a big horde; the other lines stay as they are. A file that isn't there yet (Plutonium installed but its game never started, as when the mod moves in by itself) is made holding that one line. - The launch line. When you press Play, it sets Black Ops II Zombies' launch line in Plutonium's
config.json(launchArgs,t6zm) to load Ashes:+set fs_game mods/tm_transit_tessie +set logfile 1, then anything else you had there. The logfile part makes the game keep its console log (console_zm.log) in the mod's folder, which Get my game log saves for you (below). The app puts the line back as it was as soon as the game has started; if something stops it first, it puts it back at its next start, or when you press the Doctor's Check and fix. Each time, it writesconfig.jsonagain as a whole: everything in it is kept, in its order, but its spacing changes (one line). Your Plutonium login is in that file too: the app only checks that one is there, and never shows, logs or copies it. - Never your game folder. The app never writes your Black Ops II folder into Plutonium's settings. When Plutonium doesn't know it yet, the Library shows the folder the app found, and Set your Black Ops II folder (or Open Plutonium in Your setup) puts it on your clipboard, replacing what was there, and opens Plutonium for you to paste it.
- Check and fix. If a download of Ashes was unzipped into the wrong place (a folder in
storage\t6\modsorstorage\t6holdingfiles\mods\tm_transit_tessie), Check and fix moves that folder into Your files (Your files\Unzipped downloads, above), never deletes it, once Ashes itself is installed right. The app puts nothing in the Recycle Bin. - Only if you pressed the buttons for them: other mods' files in
storage\t6\scriptsandstorage\t6\raw(notraw\scriptdata), your plugins inplugins, and offline-only files of ours (from the app's full edition) that the Doctor finds, moved into the app's folder (above). Files set aside and plugins come back with one press, Put back files the app moved aside in Your setup.
Black Ops II's own folder
The app reads it. The one change: offline-only files of ours (from the app's full edition) left at its top level are moved out by the Doctor, only when you press it, into the app's folder (moved-out, above).
Elsewhere
- What it reads to find your game, while Plutonium doesn't know your game folder yet, each time the Library or Your setup looks: Steam's location in the registry (
HKEY_CURRENT_USER\Software\Valve\Steam, the valueSteamPath), Steam's library list (steamapps\libraryfolders.vdf), and whether one of these folders sits at the top of each fixed drive:SteamLibrary,Steam,Games\Steam,Games\SteamLibraryorProgram Files (x86)\Steam. It changes none of them. - plutonium.pw opens in your browser when you press Install before Plutonium is on your PC, and when you press Get Plutonium.
- Get my game log saves one zip (AotD-log-<date and time>.zip) in your Downloads folder, or on the Desktop if there is no Downloads folder, or in the app's own folder if there is neither.
What we did not trace
- what Windows itself keeps about programs you download and run (for example its download mark, its SmartScreen and Defender records, and its lists of recent programs);
- WebView2 itself beyond the folder above: Windows installs and updates it;
- what Black Ops II and Plutonium write themselves while the game runs;
- the code libraries the app is built with, beyond what its own code asks them to do.
How to remove it
- In the app, press Remove on Ashes of the Damned. That deletes the mod's own files and any unfinished download, moves anything else in its folder into Your files, and puts the launch line back if one was left. The game setting above stays.
- If you ever set files aside or moved plugins out, put them back first: in Your setup, press Put back files the app moved aside. That one press brings back both the files you set aside and the plugins you moved out. Otherwise they stay in the app's folder (step 4 would delete them). The offline-only files of ours it moved out are the app's own: step 4 deletes them. Anything of yours the app moved out of the mod's folder is in Your files (Open Your files in the Library, or the
Your filesfolder in the app's folder): copy what you want to keep before step 4. - Close the app and delete aotd.exe.
- Delete the folder
%LOCALAPPDATA%\ai.modwith.app(type that into File Explorer's address bar to open it), and%LOCALAPPDATA%\ai.modwith.aotdif it is still there. - If you like, delete the line
seta r_skinnedCacheScale "10"from the two settings files above. It does no harm if it stays (Plutonium's own default is 1). - Any game log zips are in your Downloads folder (AotD-log-...zip), if you want those gone too.