New structure of campaign loading

Discussion and development of scenarios and campaigns for the game.

Moderator: Forum Moderators

User avatar
Zaroth
Inactive Developer
Posts: 75
Joined: January 29th, 2011, 4:33 pm

Re: New structure of campaign loading

Post by Zaroth »

So, an update. It turns out that current model of managing configuration data and preprocessor defines/guards didn't quite cut it to the new requirements, so it is going to be reworked. The state machine for the new config loading model is going to have 3 states:
1. Nothing is loaded, a state for when Wesnoth is first started.
2. General configuration (number of experience per kill, cost of recalling units, main menu theme song...) is loaded, as well as headers of all the campaigns and eras.
3. All what was in state 2 + core wesnoth macros + stuff unlocked by defines in chosen [era] + stuff unlocked by defines in chosen [campaign].
Full state diagram can be seen here.

There also is a general diagram, describing how different parts of Wesnoth engine interact and in which state are they supposed to be - it can be found here.

Please do tell if you see that something obvious was missed /done wrong. Any other comments on feasibility/usability of such model are also welcome.
Anonymissimus
Inactive Developer
Posts: 2461
Joined: August 15th, 2008, 8:46 pm
Location: Germany

Re: New structure of campaign loading

Post by Anonymissimus »

1. link:
google wrote:You need permission to access this item.
about the automaton:
Green connections are old (and to be removed) ?
projects (BfW 1.12):
A Simple Campaign: campaign draft for wml startersPlan Your Advancements: mp mod
The Earth's Gut: sp campaignSettlers of Wesnoth: mp scenarioWesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
User avatar
Zaroth
Inactive Developer
Posts: 75
Joined: January 29th, 2011, 4:33 pm

Re: New structure of campaign loading

Post by Zaroth »

Added explanation about arrows to the diagram. Also attached the first diagram to the previous post - for some reason I couldn't set it public the same way I did with the second one, at least now.

Edit: fixed the visibility issue, try to view the first document now.
Post Reply