Feature request: Deleting a module

The current toolset does not allow for the deletion of a module that has been created. Users typically initially create a bunch of test modules that cannot be removed, and forever after clutter up the list of modules.

There is a hacky workaround of deleting the module name manually from the database, but it just orphans all the modules resources without removing them from the database.

This issue has been recorded in BioWare's internal tracking system. Reference number: 210854 -Allan Smith

Beware, this is by no means a clean and easy solution.

Deleting a Module from the Toolset Workarounds

Quick and Dirty Approach (Creates Orphans)

Scenario: I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

• Navigate to My Documents\Bioware\AddIns
• Delete the folder called rcfMeep
• Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

• Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
• Connect to the BWDATOOLSET server, assuming that you kept the default options.
• Expand Databases
• Expand bw_dragonage_content
• Expand Tables
• Right click and select open table on the dbo.Module table
• This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
• Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you delete out the resources within the toolset before you remove the module reference you should avoid this.

Thorough Approach (Advanced, Avoid Orphans)

Instead of removing only the entry from the dbo.t_Module table as described above, you can modify the module resource SQL script to delete instead of select. This should clean up all of your module resources cleanly, but is a higher risk approach since you could accidentally delete more than you intended.

Language:	English  • русский