EditingWesnoth
bitches
SUCK MY DICK !!!
User Data
The user data directory can do a lot of things. The game looks here for several things:
- userdata/data/campaigns - campaign configuration files and subdirectories
- userdata/data/editor/maps - multiplayer standalone maps (map data only)
- userdata/data/units - drop your custom units here, and they will be visible to the game
- userdata/data/images - drop your custom images here, and they will be visible to the game
The userdata/data/campaigns directory is particularly useful. A single configuration file here can selectively point to an entire subdirectory tree of units, images, sounds, scenarios, and macros. This allows you to wall off parts. Content included in the userdata units or images directories will be available globally whether you want it or not. Content included in the campaigns directory won't be loaded unless the game is told to do it.
For example, assume you have a campaign called MyCampaign. This is what the userdata/data/campaigns directory looks like:
- userdata/data/campaigns/MyCampaign.cfg - a text file
- userdata/data/campaigns/MyCampaign/ - a subdirectory
- userdata/data/campaigns/MyCampaign/scenarios
- userdata/data/campaigns/MyCampaign/units
- userdata/data/campaigns/MyCampaign/images
- userdata/data/campaigns/MyCampaign/music
- userdata/data/campaigns/MyCampaign/sounds
- userdata/data/campaigns/MyCampaign/utils
MyCampaign.cfg will have something called the "campaign ifdef", which is a syntax structure that instructs the game to search userdata/data/campaigns/MyCampaign/ for data. More about this is found in BuildingCampaigns. However, it is important to understand the different capabilites of the user data directory.