Originally Posted by unexpectedly;12205547
What about letting it run multiple instances... maybe popup a warning box saying this is for advanced users only? Is it possible to have its reality based solely out of its working directory?
I'm just thinking there's got to be a way to add the "for the teams" tweak that doesn't mean a big rework.
Well, for multiple instances I am using the built in .NET function so I have 2 choices:
1. Leave it as-is
2. Completely remove multiple instance checks.
#2 can cause MAJOR issues if an inexperienced user tries to launch a second instance in the same directory and has clients set to run on startup. This has a good chance of causing errors in the WUs that are running on the other instance of the Tracker since the second set of clients will share the same working directory.
The problem is that the .NET multiple instances option can only be set at compile time, so the simple solution of providing a config setting doesn't work.
Disabling the Tracker's config system entirely is incredibly simple to do since I can just disable verifying name/team/passkey on client startup. This would allow per-client config, but it would be up to the user to figure out how to do it manually.
Implementing a per-client config into the GUI is somewhat tricky since it can overcomplicate things for new folders. The entire idea behind the Tracker was to avoid the complicated manual setup of FAH clients. I am open to suggestions about how to accomplish this, and I will consider adding per-client config if a reasonable way of implementing it in the GUI is found.