⚡ Optimize Citra Per-Game Config with Single File I/O

[Ven0m0]

💡 What:
Refactored Citra-per-game.ahk to read the configuration file into a memory variable once, perform all text replacements on this variable using TF library functions, and save the file only once at the end of the script.

🎯 Why:
The previous implementation performed a file read, modification, and write operation for every single configuration setting changed. A typical game profile application involves 5-6 such operations.
This led to:

• Redundant disk I/O (O(N) vs O(1)).
• Increased latency, especially if the config file is on a network drive or synchronized folder (e.g., OneDrive, as seen in the path).
• Potential race conditions or file lock issues if executed rapidly or concurrently.

📊 Measured Improvement:

• Baseline: ~5-6 File Open/Read/Write/Close cycles per execution.
• Optimized: 1 File Read + 1 File Write per execution.
• While exact timing benchmarks were not run (due to environment constraints), the complexity reduction from O(N) I/O to O(1) I/O guarantees a performance improvement and reduced system stress.

Changes:

• Helper functions (SetRes, SetFilter, etc.) now update a global ConfigText variable instead of calling TF_Replace on the file path.
• Added FileRead, ConfigText, %CitraConfigFile% at the start of the main logic.
• Added TF_Save(ConfigText, CitraConfigFile) at the end of the main logic.
• Preserved all existing logic and conditional branches.

---

PR created automatically by Jules for task 75104337869570791 started by @Ven0m0

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[Copilot]

Pull request overview

Refactors the legacy (v1) Citra per-game config applicator to avoid repeated disk I/O by loading qt-config.ini into memory once, performing all TF-based edits in-memory, and writing the result once at the end.

Changes:

• Introduced a global ConfigText buffer and updated helper functions (SetRes, SetFilter, etc.) to operate on it instead of editing the file on each call.
• Added a single FileRead before applying game-specific settings.
• Added a single TF_Save after applying settings to persist changes once.