Oh, diving into AMP’s database—dangerous, yet thrilling! Let’s do this the safest way possible.
Here’s the step-by-gloriously-detailed-step guide:
-
Locate AMP’s database file. By default, it should be called
AMPConfig.dband lives under your primary datastore directory:
D:\AMPDatastore\Instances\ADS01\Data -
MAKE A BACKUP. Before doing anything else, copy that
AMPConfig.dbfile to a safe spot in case AMP decides to throw a tantrum post-changes. -
Open the database. AMP uses SQLite for its back-end. You’ll need an SQLite Editor/Browser like DB Browser for SQLite (free and simple to use).
-
Look for the
Datastorestable or something similar:- In the SQLite browser, open the
AMPConfig.dbdatabase file. - You’ll want to navigate through the tables until you find one that lists the entries for your datastores.
- In the SQLite browser, open the
-
Identify the ghost entries. You may see rows for those phantom datastores. They should align with the paths you deleted (
C:\...\Instances). Double-check you’ve got the right rows. -
Time to clean house:
- Simply delete the rows corresponding to the deleted datastore paths.
- DO NOT touch anything else unless you’re into “break AMP speedrun challenges.”
-
Save and close the database, then restart your AMP service.
Boom! The ghost datastores should finally disappear. Let me know how this daring operation goes—or if SQLite decides to be overdramatic.