<p>@airtex2019 Unfortunately this wasn’t made clear enough. I’m the author and first shared the source code on the UOAF discord (<a href=“https://discord.gg/U7UykYX” target=“_blank”>invite</a> and <a href=“https://discord.com/channels/582602200619024406/615631373968998435/908706086377357352” target=“_blank”>specific message</a> link), where I first noticed discussion around the issue. Later I compiled the same code into the .exe that was distributed to everyone. I also attached the source code in <a href=“https://forum.falcon-bms.com/post/334192” target=“_blank”>this reply</a> of mine in this very thread, though I admit I probably should have asked depapier to link it in his first post for best visibility.<br />In any case, as @airtex2019 correctly pointed out, my code just grabs the BMS path from the registry, finds the FALCON4_RCD.XML within every theater and only edits the 3 seeker entries mentioned by the hotfix notice. I didn’t make the script pause because it is usually bad practice when coding CLI applications, but if you open a CMD shell and run the .exe or .py from there you’ll see how it lists every file that it modified.<br />Python is one of the best languages available to quickly write short but powerful code like this, batch files are pretty limited when more complex logic is required. The python interpreter is also trivial to install and only going to become more useful in the future, even on non-coder PCs. For those who trust my word, there’s always the .exe.<br />Next time I’ll make sure to publish both exe and source code together in a more comprehensive way, along with an exe hash for good measure, cheers!</p>