MISTEST - Revision history

ATHSE at 12:33, 13 April 2025

2025-04-13T12:33:19Z

← Older revision		Revision as of 14:33, 13 April 2025
Line 9:		Line 9:
	To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>		To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>

	MISTEST doesn't do any error checking of the game/mod INIs, and is only using them for reference to understand what is or isn't valid within the map. For error checking the INIs you'll want to use [[AICHECK]]. MISTEST also does not check the terrain or [[~~Overlays~~]] in any way, that's left to the map editors.<br><br>		MISTEST doesn't do any error checking of the game/mod INIs, and is only using them for reference to understand what is or isn't valid within the map. For error checking the INIs you'll want to use [[AICHECK]]. MISTEST also does not check the terrain or [[OverlayTypes]] in any way, that's left to the map editors.<br><br>

	==Links==		==Links==

ATHSE at 12:32, 13 April 2025

2025-04-13T12:32:11Z

← Older revision		Revision as of 14:32, 13 April 2025
Line 5:		Line 5:
	MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>		MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>

	Before using MISTEST, all specified ~~inis~~, have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>		Before using MISTEST, all specified INIs, have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>

	To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>		To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>

	MISTEST doesn't do any error checking of the game/mod ~~inis~~, and is only using them for reference to understand what is or isn't valid within the map. For error checking the ~~inis~~ you'll want to use [[AICHECK]]. MISTEST also does not check the terrain or [[Overlays]] in any way, that's left to the map editors.<br><br>		MISTEST doesn't do any error checking of the game/mod INIs, and is only using them for reference to understand what is or isn't valid within the map. For error checking the INIs you'll want to use [[AICHECK]]. MISTEST also does not check the terrain or [[Overlays]] in any way, that's left to the map editors.<br><br>

	==Links==		==Links==

ATHSE: leftovers

2025-04-06T17:23:07Z

leftovers

← Older revision		Revision as of 19:23, 6 April 2025
Line 5:		Line 5:
	MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>		MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>

	Before using MISTEST, all ~~three~~ specified inis, ~~and ideally the audio.idx~~ have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>		Before using MISTEST, all specified inis, have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>

	To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>		To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>

ATHSE: typo

2025-04-06T17:17:09Z

typo

← Older revision		Revision as of 19:17, 6 April 2025
Line 5:		Line 5:
	MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>		MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>

	Before using MISTEST , all three specified inis, and ideally the audio.idx have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>		Before using MISTEST, all three specified inis, and ideally the audio.idx have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>

	To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>		To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>

ATHSE: moar

2025-04-06T17:16:01Z

moar

← Older revision		Revision as of 19:16, 6 April 2025
Line 3:		Line 3:
	\|yr=yes		\|yr=yes
	}}		}}
	MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, multiplayer maps ~~using ambient~~ effects often have errors it ~~will~~ find, as well as more basic things like invalid ~~buildings~~, or ~~trees~~ outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>		MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, it is equally useful to test multiplayer maps. Ambient effects often have minor errors it can find like a missing value, as well as more basic things like invalid pre-placed [[TechnoTypes]], or objects outside the usable map area. It examines {{ini\|rules}}, {{ini\|art}}, {{ini\|ai}}, and {{ini\|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor.<br><br>

	Before using MISTEST , all three specified inis, and ideally the audio.idx have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>		Before using MISTEST , all three specified inis, and ideally the audio.idx have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below.<br><br>
Line 9:		Line 9:
	To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>		To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log.<br><br>

	MISTEST doesn't do any error checking of the game/mod inis, and is only using them for reference to understand what is or isn't valid within the map. For error checking the inis you'll want to use [[AICHECK]].<br><br>		MISTEST doesn't do any error checking of the game/mod inis, and is only using them for reference to understand what is or isn't valid within the map. For error checking the inis you'll want to use [[AICHECK]]. MISTEST also does not check the terrain or [[Overlays]] in any way, that's left to the map editors.<br><br>

	==Links==		==Links==

ATHSE: Created page with "{{Guideheader |ra2=yes |yr=yes }} MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, multiplayer maps using ambient effects often have errors it will find, as well as more basic things like invalid buildings, or trees outside the usable map area. It examines {{ini|rules}}, {{ini|art}}, {{ini|ai}}, and {{ini|sound}}, along with the map itself. It is run vi..."

2025-04-06T17:11:41Z

Created page with "{{Guideheader |ra2=yes |yr=yes }} MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, multiplayer maps using ambient effects often have errors it will find, as well as more basic things like invalid buildings, or trees outside the usable map area. It examines {{ini|rules}}, {{ini|art}}, {{ini|ai}}, and {{ini|sound}}, along with the map itself. It is run vi..."

New page

{{Guideheader
|ra2=yes
|yr=yes
}}
MISTEST (aka Mission Tester) is a script for checking objects and scripting within maps made for {{ra2}} and {{yr}}. Although the name implies it tests 'missions' only, multiplayer maps using ambient effects often have errors it will find, as well as more basic things like invalid buildings, or trees outside the usable map area. It examines {{ini|rules}}, {{ini|art}}, {{ini|ai}}, and {{ini|sound}}, along with the map itself. It is run via dragging-and-dropping a map onto the included batchfile on Windows, and creates a mission.log file with the results. Make sure to associate log files with your preferred text editor. 

Before using MISTEST , all three specified inis, and ideally the audio.idx have to be extracted to the game directory, where MISTEST should also be extracted, with the correct read/write permissions. A copy of the TCL runtimes (version 8.3+) have to be installed, available through Activestate, link below. 

To configure MISTEST to run correctly, and read the right files, the mistest.tcl will have to be edited to manually set the path for the game, the specific filenames used by the mod, and possibly toggle the optional warnings. Pay close attention to the 'ra2dir' example path, TCL doesn't support backslash for path navigation, it uses the UNIX system of forwardslash. On a side note, the logging can be set to append rather than overwrite, allowing a user to drag-and-drop a sequence of maps to check (one at a time) and all their results will be added with identifiers to the log. 

MISTEST doesn't do any error checking of the game/mod inis, and is only using them for reference to understand what is or isn't valid within the map. For error checking the inis you'll want to use [[AICHECK]]. 

==Links==
* [https://www.ppmforums.com/topic-68090/mistest-a-script-to-test-mission-map-code-and-check-map-objects-for-errors/ Latest download at PPM]
* [https://platform.activestate.com/ActiveState/ActiveTcl-8.6/ ActiveTCL Runtime downloads (free registration)]

[[Category:Tools]]