Difference between revisions of "DebuggingCampaigns"
From The Battle for Wesnoth Wiki
m (DebuggingCampains moved to DebuggingCampaigns: Typo fix. Links have been moved) |
m (Categorize) |
||
| Line 26: | Line 26: | ||
*[[BuildingCampaigns]] | *[[BuildingCampaigns]] | ||
*[[BuildingCampaignsDirectoryStructure]] | *[[BuildingCampaignsDirectoryStructure]] | ||
| + | |||
| + | [[Category:Create]] | ||
Revision as of 11:45, 8 March 2008
"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
- Do the id tags match exactly? Does the id in the caller script have the same case (lowercase/uppercase) as the scenario's id?
- Is the ".cfg" extension appended to the script filename?
- Is the script in the right location (usually campaigns/YOUR_MODULE/scenarios)
- 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=???")
- 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)
- Is a downloaded module breaking you version of the game?
- Do you have read permissions on your scripts?