DebuggingCampaigns - Revision history

Toranks: /* Things to check when your scenario doesn't load */

2023-03-23T03:30:51Z

‎Things to check when your scenario doesn't load

2018-06-17T19:14:21Z

User-level guide for purging the cache

2015-01-05T00:14:37Z

‎Tips

2015-01-05T00:13:37Z

F5 key binding

2015-01-05T00:10:28Z

Always backup your work

2014-03-18T07:00:35Z

‎Things to check when your scenario doesn't load

2014-03-18T06:59:56Z

2014-03-06T08:57:10Z

‎See Also:

2012-01-31T01:29:40Z

2008-03-08T11:45:44Z

Categorize

@@ Line 21: / Line 21: @@
 *Is the script in the right location (usually ~add-ons/YOUR_ADDON/scenarios)
-*Is it really a scenario load problem? Maybe the main.cfg file isn't being loaded correctly.
+*Is it really a scenario load problem? Maybe the _main.cfg file isn't being loaded correctly.
 *Are all the linking tags spelled correctly? (<b>first_scenario=???</b>, <b>next_scenario=???</b>, <b>id=???</b>)

@@ Line 1: / Line 1: @@
-"Debugging" means to fix by removing errors. Here are some ideas to help you when you are building a campaign and need to fix it.
+"Debugging" means to fix by removing errors. Here are some ideas to help you when you are building a campaign (or other add-on) and need to fix it.
 == Tips ==
@@ Line 5: / Line 11: @@
 Use F5 in main game menu to reload WML code and invalidate cache. By this way you save time on rebooting game each time you change map or WML code.
-Always backup your work. Use DVCS so be able to revert any deleted piece and check difference. You can comment out part of WML code by "#" prefix and later back it.
+Always backup your work. Use a DVCS (for example Git), so that you can revert any added or deleted code, and to check the differences between versions. Even without a DVCS, you can comment out part of the WML code by prefixing it with "#", and later uncomment it again.
 == Things to check when your scenario doesn't load ==

@@ Line 3: / Line 3: @@
 == Tips ==
-Use F5 in main game menu to reload WML code and invalidate cache. By this way you save time on rebooting game each type you change code.
+Use F5 in main game menu to reload WML code and invalidate cache. By this way you save time on rebooting game each time you change map or WML code.
 Always backup your work. Use DVCS so be able to revert any deleted piece and check difference. You can comment out part of WML code by "#" prefix and later back it.

@@ Line 1: / Line 1: @@
 "Debugging" means to fix by removing errors. Here are some ideas to help you when you are building a campaign and need to fix it.
 == Things to check when your scenario doesn't load ==
@@ Line 22: / Line 28: @@
 A recommended approach by zookeeper is to remove half your code, and try to load your add-on. If the error is gone, you know it's in the half you removed. Take whichever half has the error, and keep removing half of what remains until you isolate the error.
 == See Also: ==

@@ Line 23: / Line 23: @@
 A recommended approach by zookeeper is to remove half your code, and try to load your add-on. If the error is gone, you know it's in the half you removed. Take whichever half has the error, and keep removing half of what remains until you isolate the error.
+Always backup your work. Use DVCS so be able to revert any deleted piece and check difference. You can comment out part of WML code by "#" prefix and later back it.
 == See Also: ==

@@ Line 11: / Line 11: @@
 *Is it really a scenario load problem? Maybe the main.cfg file isn't being loaded correctly.
-*Are all the linking tags spelled correctly? ("first_scenario=???", "next_scenario=???", "id=???")
+*Are all the linking tags spelled correctly? (<b>first_scenario=???</b>, <b>next_scenario=???</b>, <b>id=???</b>)
 *If you're using the template, did you remember to change all include and file paths to match your setup?

@@ Line 1: / Line 1: @@
 "Debugging" means to fix by removing errors. Here are some ideas to help you when you are building a campaign and need to fix it.
 == Things to check when your scenario doesn't load ==
@@ Line 8: / Line 7: @@
 *Is the ".cfg" extension appended to the script filename?
-*Is the script in the right location (usually campaigns/YOUR_MODULE/scenarios)
+*Is the script in the right location (usually ~add-ons/YOUR_ADDON/scenarios)
 *Is it really a scenario load problem? Maybe the main.cfg file isn't being loaded correctly.
@@ Line 14: / Line 13: @@
 *Are all the linking tags spelled correctly? ("first_scenario=???", "next_scenario=???", "id=???")
-*If you're using the template, did you remember to change the script in the utils directory to load your module? Otherwise you might get a recursion error that may prevent your scenarios from loading (remember, scenarios are loaded last)
+*If you're using the template, did you remember to change all include and file paths to match your setup?
-*Is a downloaded module breaking your version of the game?
+*Is another downloaded add-on breaking your version of the game or conflicting with your content?
 *Do you have read permissions on your scripts?

@@ Line 25: / Line 25: @@
 *[[BuildingCampaigns]]
-*[[BuildingCampaignsDirectoryStructure]]
+*[[AddonStructure]]
 [[Category:Create]]

← Older revision		Revision as of 11:45, 8 March 2008
Line 26:		Line 26:
	*[[BuildingCampaigns]]		*[[BuildingCampaigns]]
	*[[BuildingCampaignsDirectoryStructure]]		*[[BuildingCampaignsDirectoryStructure]]
		+
		+	[[Category:Create]]