How to configure Move Generator Scope

As I said before, I used Sharper as a benchmark for correctness of my move generator, It is a great engine and supports all the requirement needed to do a comparison between generation of two engines. So the default configuration works for Sharper. The shortest path to test your move generator is to made it compatible with sharper for the needed commands, and use the default configuration. If you prefer using another syntax for your commands, or test with another generator, you possibly need to change something, and this page should explayn how to do it. If not, please feel free to open an issue on the project, or contact me directly.

This is the configuration form screenshot:

conf.png

First the obvious: the working folder is the path in which the engine resides. In some cases could be not necessary at all, but if needed here is the place to specify.

Then we have two main topic to configure: Here we use the Antlr StringTemplate library internally. This library is very useful for emitting strings based on a template. We do a very poor use here, but if you need more help about how to use it, please refer to the link. We have to keep in mind that for each of the following templates the "Return" is not implicit, so if we want to send a new line to the engine, we have to specify $\n$ in our template.
This could be a little tricky, .Net Regular Expressions are used to parse the line and extracting the substring needed in a single capture group.