Feature request: Deleting a module - Revision history

Sunjammer: /* Deleting a Module from the Toolset */ Clarified that the workaround is just that

2012-02-14T13:06:09Z

‎Deleting a Module from the Toolset: Clarified that the workaround is just that

2012-02-14T13:01:18Z

Removing category

2012-02-14T12:36:49Z

moved Deleting a module to Feature request: Deleting a module: To clarify that this is a feature request.

2011-02-11T14:18:55Z

Add language bar

2010-07-13T18:43:04Z

‎Deleting a Module from the Toolset: alternate SQL to avoid orphans

2010-03-01T20:43:38Z

2010-02-08T23:26:27Z

2010-01-25T09:31:11Z

‎Deleting a Module from the Toolset

2010-01-25T09:30:58Z

2010-01-25T09:30:18Z

@@ Line 8: / Line 8: @@
 Beware, this is by no means a clean and easy solution.
-== Deleting a Module from the Toolset ==
+== Deleting a Module from the Toolset Workarounds ==
-Setup:
+=== Quick and Dirty Approach (Creates Orphans) ===
 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
@@ Line 32: / Line 33: @@
 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.
-=== Alternate SQL to Avoid Orphans ===
+=== 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_Script.sql|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.
 {{languages}}
 [[Category:Feature requests]]

@@ Line 36: / Line 36: @@
 Instead of removing only the entry from the dbo.t_Module table as described above, you can modify the [[Module_Resource_Script.sql|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.
 [[Category:Feature requests]]
 [[Category:Modules]]

@@ Line 31: / Line 31: @@
 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.
 [[Category:Feature requests]]
 [[Category:Modules]]

@@ Line 26: / Line 26: @@
 * Expand bw_dragonage_content
 * Expand Tables
-* Right click and select open on the dbo.Modules table
+* 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.

← Older revision	Revision as of 12:36, 14 February 2012
(No difference)

@@ Line 5: / Line 5: @@
 {{EV|210854|[[User:Allan Smith|Allan Smith]]}}
 Beware, this is by no means a clean and easy solution.
@@ Line 33: / Line 31: @@
 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.

← Older revision		Revision as of 09:31, 25 January 2010
Line 33:		Line 33:

	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.		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.
−
−	~~There is a feature request regarding this functionality: [[Deleting a module]]~~

← Older revision		Revision as of 09:30, 25 January 2010
Line 31:		Line 31:
	* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.		* 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.		* 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.
		+
		+	There is a feature request regarding this functionality: [[Deleting a module]]

@@ Line 2: / Line 2: @@
 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 ([[How-tos#Removing_Modules|see here]]), but it just orphans all the modules resources without removing them from the database.
+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.
 {{EV|210854|[[User:Allan Smith|Allan Smith]]}}
 [[Category:Feature requests]]