The use of numbers instead of track names seams unreasoned. What will happen when we get 11 tracks in the game?
With commonly used BL1[R] system this problem goes away (atleast we can have 4294967296 tracks instead of just 10 ). The drawback is that it will make the response 619 bytes bigger (but with time, as new tracks get released, the letter-system will actually become smaller, if you have to add another digit for other tracks for the old system).
But the most important gain is that clients wouldn't have to dive into their applications' implementations whenever there is new track out there. This is pretty big.
I got a strange behavior when using my tool mates@track NG. Someone told me that the server list can not be loaded. I tried it manually by using the browser which worked fine. But inside the tool it isn't working anymore. It seems that it stops working after the hacking attack (around end of March 2018 and beginning of April 2018). Are there some significant changes?
I tried v 1.3 and 1.5. The tool wasn't change at all. It just stopped working when trying to receive the hosts list.
What are the codes for RO tracks?
Are those right (copy & paste from config file)
Name=ISSC Long rev.
Name=Historic Short rev.
Name=International Long rev.