Whether or not to use the override configurations
An array of arguments to pass in to the script command NOTE, there are a few special strings when put into this array, will be populated with dynamic data.
See MatchEngine.DynamicDataStrings for what is available and what they do
The command to run that will run a match and send to the standard out any updates and and match conclusion data. This is always executed in the same directory the dimension is created in.
The command telling the engine that the match is done and should now process the remaining lines as results until the process running the match exits.
The result handler to handle results returned by the command provided in the OverrideOptions.
If the result handler returns an object with the key replayFile, Dimensions will recognize the string
in that key as the replay file location.
If a Storage plugin is used, the replay file is uploaded and the local fle is deleted
Number in milliseconds before a match is marked as timing out and thrown out. When set to null, no timeout is used. This is dangerous to set to null, if you are to set it null, ensure your own design has some timing mechanism to ensure matches don't run forever and consume too much memory.
Generated using TypeDoc
The override options interface This is used to provide configurations for a custom Design outside the scope and infrastructure of Dimensions