Bruno Wolff III schrieb: > I have thought of something else that might be nice to do after each > campaign is in its own directory. If references were only allowed within > a campaign or to main line stuff and not cross campaign, we could make sure > that removing a campaign will not break another campaign because of > dependencies. This could enforce the rule that you are supposed to copy > non main line objects rather than make references to them. > Ehm, we are already using this policy. It will be enforced for all new content to add mainline and it is eg needed for the split debian packages. So in this matter it does not make a real difference, since we already do handle things this way. Btw, I do completely agree to restructuring things. One short proposal to work together with the soon to come campaign server changes: Devide data in some "groups" like campaigns_singleplayer and multiplayer where under multiplayer all the factions stuff, mp maps/scenarios and (once they come) mp campaigns reside. The same structure should be used inside the userdata dir to make it in the end easier to see what the installed content is. So a new faction (with all needed for it) would go to userdata/multiplayer/factions/newfaction, where a normal campaign would do to userdata/campaign_singleplayer/newcampaign and so on. I think some structure like this would help users that "only want to get rid of the mp content but keep the usercampaigns" and makes it easier to see what which UMC is meant to be. Cheers, Nils Kneuper aka Ivanovic
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
