Authoring tools - Revision history

Octalot: /* trackplacer */ Remove the tool's documentation, leaving the file format

2026-01-09T09:05:42Z

‎trackplacer: Remove the tool's documentation, leaving the file format

Octalot: /* CampSynt */ Removed all documentation about this obsolete tool

2026-01-09T08:53:51Z

‎CampSynt: Removed all documentation about this obsolete tool

Bssarkar: /* Wesnoth Map Tracker */ fixup

2026-01-09T01:46:55Z

‎Wesnoth Map Tracker: fixup

Bssarkar: /* Wesnoth Map Tracker */ use syntaxhighlight

2026-01-09T01:46:22Z

‎Wesnoth Map Tracker: use syntaxhighlight

Bssarkar: Add WesnothMapTracker tool

2026-01-09T01:41:40Z

Add WesnothMapTracker tool

Octalot: /* trackviewer */ Add documentation for this tool

2019-11-21T18:14:06Z

‎trackviewer: Add documentation for this tool

Octalot: Add docs for tmx_trackplacer

2019-11-14T13:28:10Z

Add docs for tmx_trackplacer

Sapient: trackplacer bugs

2018-07-18T19:22:38Z

trackplacer bugs

Iceiceice at 11:03, 7 April 2014

2014-04-07T11:03:48Z

Mercurius999: /* CampSynt */

2011-04-15T10:44:23Z

‎CampSynt

@@ Line 110: / Line 110: @@
 * Space pauses/unpauses
-== trackplacer ==
+== trackplacer's bigmap.cfg files ==
-'''UPDATE: per Elvish_Hunter in [https://forums.wesnoth.org/viewtopic.php?f=21&t=48478&p=631121#p631121 this thread]:
+'''trackplacer''' was the original tool for creating the journey tracks, the sequences of dots, crossed-sword, and flag symbols (track markers) that march across the story screens at the beginning of many Wesnoth scenarios. The tool itself has been replaced by the others on this page, this section remains to document the file format used in bigmap.cfg files (the filename itself isn't important, but in mainline has standardised on that name).
-'''trackplacer''' is a tool for visually editing journey tracks.  Journey tracks are the sequences of dots, crossed-sword, and flag symbols (track markers) that march across the story screens at the beginning of many Wesnoth scenarios.
+To understand what your 'bigmap.cfg' does, you need to know that journey-track markers can be put on your story screens by two different sets of macros.  One, used for 'new' marks, is displayed in color with quarter-second delays; the other, 'old' set displays marks in white with no delay.  Your journey track is divided into stages by battle and rest markers; conventionally, you want to display the latest (most recent) stage with the new macros and all previous stages with the old ones.
 Your track will be saved in .cfg format as a sequence of macro definitions with names like '''JOURNEY_STAGE_1''', '''JOURNEY_STAGE_2''' and so on.  '''JOURNEY_STAGE_1''' will draw the first stage in the 'new' color parts.  '''JOURNEY_STAGE_2''' will draw the first stage in the 'old' color and the second stage in the 'new' one; '''JOURNEY_STAGE_3''' will draw the first and second stages in the 'old' color parts and the third stage in the 'new' one; and so on.
@@ Line 148: / Line 120: @@
 There will be a final macro '''JOURNEY_COMPLETE''' that displays the entire track in the 'old' color. This will be useful when you are piecing together multiple tracks, say for a campaign with branches.
-The track information in your journey.cfg will be enclosed in special comments
+The track information in your bigmap.cfg will be enclosed in special comments
 that look like this:
@@ Line 154: / Line 126: @@
      # trackplacer: tracks end
-'''trackplacer''' will not alter anything it finds outside these comments, and will always enclose everything it writes in them.
+'''trackplacer_tmx''' will not alter anything it finds outside these comments, and will always enclose everything it writes in them.
 Special comments may appear in your ''journey.cfg'', looking like this:
@@ Line 160: / Line 132: @@
       <tt># trackplacer: &lt;property&gt;=&lt;value&gt;</tt>
-These set properties that '''trackplacer''' may use.  At present there is only one such property: <tt>map</tt>, which records the name of the mapfile on which your track is laid.  Don't remove this comment, '''trackplacer''' needs it.
+These set properties that '''trackplacer_tmx''' may use.  At present there is only one such property: <tt>map</tt>, which records the name of the mapfile on which your track is laid.  Don't remove this comment, '''trackplacer_tmx''' needs it.
 == Wesnoth Map Tracker ==

← Older revision		Revision as of 08:53, 9 January 2026
Line 163:		Line 163:

	'''trackplacer''' has one known bug: you can confuse it (or possibly the underlying toolkit, or X) by dragging markers rapidly across other markers. If this happens to you, click '''Animate''' to refresh and slow down.		'''trackplacer''' has one known bug: you can confuse it (or possibly the underlying toolkit, or X) by dragging markers rapidly across other markers. If this happens to you, click '''Animate''' to refresh and slow down.
−
−	~~== CampSynt==~~
−
−	~~'''CampSynt''' is a tool to create a not so skeletal campaign as you can view in the help:~~
−
−	~~camp-synt -c -n -s [-s] -h [-h] -u [-u] -f -w~~
−
−	~~Warning: put underscores instead of spaces or include in double quotes (eg: a_string or "a string")~~
−	~~Warning: you can use long or short notations for options:~~
−	~~-c A_str is the same of -c "A str" and of --campaign=A_str and --campaign="A str"~~
−
−
−	~~OPTIONS:~~
−	~~-c Name_with_underscores or "Name in quotes". This option is mandatory.~~
−	~~-n Number of scenarios if not provided scenario's names via -s option~~
−	~~-s First_scenario [-s Second_scenario -s Third_scenario -s End]~~
−	~~one or more scenario names provided in sequential order~~
−	~~-h Hero_Name [-h Best_Friend -h My_Dog.Wolf]~~
−	~~one or more hero names to create and use in the story.~~
−	~~If the name contains a '.' (dot sign) everything following it is considerd as the type of that unit.~~
−	~~-u new_Unit [-u Another_one -u Last]~~
−	~~one or more new unit types to be included in the private units folder.~~
−	~~If the name contains two dot signs it will be splitted this way: new_unit_name, race, copied_from~~
−	~~like in: Farm_rebel.humans.Peasant~~
−	~~This need -w option properly set.~~
−	~~-f Force the rewrite of an existing file.~~
−	~~-w Wesnoth path (in double quotes if containing spaces) to access original units.~~
−	~~If this option is set and the path match 1.6 then the directory 'campaigns' is used instead of 'add-ons'.~~
−
−	~~EXAMPLES:~~
−	~~-c Camp_Name -n 3~~
−	~~-c Camp_Name -n 3 -f~~
−	~~-c Camp_Name -s Scenario_One -s Scenario_Two~~
−	~~-c Camp_Name -s Scenario_One -s Scenario_Two -h Hero_Name -u New_unit~~
−	~~-c Camp_Name -s One -s Two -h Hero_Name -h His_Friend -u New_unit -u New_Bowman~~
−	~~-c Camp_Name -s One -s Two -h Hero -h Friend.New_Bowman -u New_Bowman~~
−	~~-c Camp_Name -s One -s Two -h Hero.New_Bowman -u New_Bowman.humans.Peasant~~
−
−
−	campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010

	== Wesnoth Map Tracker ==		== Wesnoth Map Tracker ==

@@ Line 208: / Line 208: @@
 It allows you to open an image file (say the Wesnoth Map) and place markers upon it, and the corresponding macro code is generated like this:
 <syntaxhighlight lang=wml>
    {NEW_JOURNEY 455 300}

@@ Line 208: / Line 208: @@
 It allows you to open an image file (say the Wesnoth Map) and place markers upon it, and the corresponding macro code is generated like this:
-<code>
+of a user interface would be :
    {NEW_JOURNEY 455 300}
    {NEW_REST 500 300}
-</code>
+</syntaxhighlight>
 [[Category:Tools]]

← Older revision		Revision as of 01:41, 9 January 2026
Line 203:		Line 203:

	campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010		campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010
		+
		+	== Wesnoth Map Tracker ==
		+	A standalone free and open source GUI tool that is available from here: https://github.com/babaissarkar/WesnothMapTracker
		+
		+	It allows you to open an image file (say the Wesnoth Map) and place markers upon it, and the corresponding macro code is generated like this:
		+	<code>
		+	{NEW_JOURNEY 455 300}
		+	{NEW_REST 500 300}
		+	</code>
		+
		+	For detailed instructions please visit the link above.
		+

	[[Category:Tools]]		[[Category:Tools]]

← Older revision		Revision as of 18:14, 21 November 2019
Line 98:		Line 98:

	Yes it could. Implementing it as a file converter was the easier option for development, and the code is (hopefully) modular enough for reuse.		Yes it could. Implementing it as a file converter was the easier option for development, and the code is (hopefully) modular enough for reuse.
		+
		+	== trackviewer ==
		+
		+	{{DevFeature1.15\|3}} Map journey track animation preview tool, shows the journey without needing to start Wesnoth and refresh the cache. It’s a support program which assumes you’re either editing the .cfg file with a text editor or using Tiled with [[Authoring_tools#tmx_trackplacer\|tmx_trackplacer]]; in other words, it's the part of the [[Authoring_tools#trackplacer\|old trackplacer]] that wasn't covered by tmx_trackplacer.
		+
		+	At least on Linux you can have both Tiled and this open on the same file. Save the file in Tiled, alt+tab to this, and press enter to reload the file.
		+
		+	Keys:
		+	* Escape quits
		+	* Return or Enter reloads the .cfg or .tmx file, and restarts the animation
		+	* Space pauses/unpauses

	== trackplacer ==		== trackplacer ==

@@ Line 1: / Line 1: @@
-This page collects information about tools in the Wesnoth source tree that are intended to help you write campaign WML.  At present there is only one such tool: <tt>trackplacer</tt>.
+This page collects information about tools in the Wesnoth source tree that are intended to help you write campaign WML.
 == trackplacer ==
 '''UPDATE: per Elvish_Hunter in [https://forums.wesnoth.org/viewtopic.php?f=21&t=48478&p=631121#p631121 this thread]:
-'''<nowiki>"trackplacer is outdated (it requires the obsolete PyGTK toolkit, which doesn't run on Python 3) and terribly bugged (it doesn't run at all on Windows, for example)."</nowiki> Until it is fixed, you should use image editing software to find the X and Y coordinates to create each dot or cross manually.
+'''<nowiki>"trackplacer is outdated (it requires the obsolete PyGTK toolkit, which doesn't run on Python 3) and terribly bugged (it doesn't run at all on Windows, for example)."</nowiki> You should either use [[Authoring tools#tmx_trackplacer|tmx_trackplacer]], or use image editing software to find the X and Y coordinates to create each dot or cross manually.
 -------------

@@ Line 2: / Line 2: @@
 == trackplacer ==
 '''trackplacer''' is a tool for visually editing journey tracks.  Journey tracks are the sequences of dots, crossed-sword, and flag symbols (track markers) that march across the story screens at the beginning of many Wesnoth scenarios.
@@ Line 50: / Line 54: @@
 '''trackplacer''' has one known bug: you can confuse it (or possibly the underlying toolkit, or X) by dragging markers rapidly across other markers. If this happens to you, click '''Animate''' to refresh and slow down.
 == CampSynt==

← Older revision		Revision as of 11:03, 7 April 2014
Line 91:		Line 91:

	campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010		campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010
		+
		+	[[Category:Tools]]

← Older revision		Revision as of 10:44, 15 April 2011
Line 50:		Line 50:

	'''trackplacer''' has one known bug: you can confuse it (or possibly the underlying toolkit, or X) by dragging markers rapidly across other markers. If this happens to you, click '''Animate''' to refresh and slow down.		'''trackplacer''' has one known bug: you can confuse it (or possibly the underlying toolkit, or X) by dragging markers rapidly across other markers. If this happens to you, click '''Animate''' to refresh and slow down.
		+
		+
		+	== CampSynt==
		+
		+	'''CampSynt''' is a tool to create a not so skeletal campaign as you can view in the help:
		+
		+	camp-synt -c -n -s [-s] -h [-h] -u [-u] -f -w
		+
		+	Warning: put underscores instead of spaces or include in double quotes (eg: a_string or "a string")
		+	Warning: you can use long or short notations for options:
		+	-c A_str is the same of -c "A str" and of --campaign=A_str and --campaign="A str"
		+
		+
		+	OPTIONS:
		+	-c Name_with_underscores or "Name in quotes". This option is mandatory.
		+	-n Number of scenarios if not provided scenario's names via -s option
		+	-s First_scenario [-s Second_scenario -s Third_scenario -s End]
		+	one or more scenario names provided in sequential order
		+	-h Hero_Name [-h Best_Friend -h My_Dog.Wolf]
		+	one or more hero names to create and use in the story.
		+	If the name contains a '.' (dot sign) everything following it is considerd as the type of that unit.
		+	-u new_Unit [-u Another_one -u Last]
		+	one or more new unit types to be included in the private units folder.
		+	If the name contains two dot signs it will be splitted this way: new_unit_name, race, copied_from
		+	like in: Farm_rebel.humans.Peasant
		+	This need -w option properly set.
		+	-f Force the rewrite of an existing file.
		+	-w Wesnoth path (in double quotes if containing spaces) to access original units.
		+	If this option is set and the path match 1.6 then the directory 'campaigns' is used instead of 'add-ons'.
		+
		+	EXAMPLES:
		+	-c Camp_Name -n 3
		+	-c Camp_Name -n 3 -f
		+	-c Camp_Name -s Scenario_One -s Scenario_Two
		+	-c Camp_Name -s Scenario_One -s Scenario_Two -h Hero_Name -u New_unit
		+	-c Camp_Name -s One -s Two -h Hero_Name -h His_Friend -u New_unit -u New_Bowman
		+	-c Camp_Name -s One -s Two -h Hero -h Friend.New_Bowman -u New_Bowman
		+	-c Camp_Name -s One -s Two -h Hero.New_Bowman -u New_Bowman.humans.Peasant
		+
		+
		+	campsynth is a perl script (with core modules usage only, suitable for most Linux systems and packed as exe for the enjoy of some other OS users). It was written based on 1.8.5 version of the game but can be also used with 1.6.x versions and was successfully tested with 1.9.5 (12 apr 2011). campsynth is located at the forum http://forum.wesnoth.org/viewtopic.php?f=8&t=29010