[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

Update of bug #22974 (project wesnoth): Status:None => Fixed Assigned to:None => gfgtdf Open/Closed:Open => Closed __

[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

Follow-up Comment #4, bug #22974 (project wesnoth): possible patch here: https://github.com/wesnoth/wesnoth/pull/401 ___ Reply to this item at: ___ Nachricht ge

[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

Follow-up Comment #3, bug #22974 (project wesnoth): we already allow force_modification= for [multiplayer] (at least accoring to the wiki, i didn't test it). It is intended to add the code that checks for compability with [modification], [era] and [multiplayer] for [campaign] too and then force_mo

[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

Follow-up Comment #2, bug #22974 (project wesnoth): it would be also very hepfull if such [modification] could have [variables] tag. Currently my {MY_COOL_LIBRARY} takes more space than {MY_COOL_EVENTS} and it is also multiplied by 3 space it consumes.

[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

Follow-up Comment #1, bug #22974 (project wesnoth): I have realized a hidden forced modification would be really usefull to not bloat BfW with complex campaigns. I am currently developing a campaign with 5 scenarios that have lot of alternative maps for each scenario. Writing {MY_COOL_EVENTS} in e

[Wesnoth-bugs] [bug #22974] hidden modifications and force_modification for campaigns

URL: Summary: hidden modifications and force_modification for campaigns Project: Battle for Wesnoth Submitted by: None Submitted on: Fr 21 Nov 2014 18:07:04 UTC Category: Feature Request