mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 00:05:58 +03:00
[PR #3299] [MERGED] Core: Only update configs when using a different build. #3367
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#3367
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/shadps4-emu/shadPS4/pull/3299
Author: @StevenMiller123
Created: 7/23/2025
Status: ✅ Merged
Merged: 7/23/2025
Merged by: @georgemoralis
Base:
main← Head:update-config-logic📝 Commits (2)
0d0fcd5Use a config version constant to check for config updatesf80e7b8Use git revision hash instead of constant📊 Changes
1 file changed (+6 additions, -21 deletions)
View changed files
📝
src/common/config.cpp(+6 -21)📄 Description
This PR adds the currently used emulator revision to the config file, and if there's a mismatch between the current revision and the stored revision, a config update will be triggered.
Using this logic addresses the issue where configs with additional entries would trigger a config update on each emulator boot, and removes the requirement for PR authors to increment a constant every time they add a new config entry.
Outside of rewriting config logic to check for the existance of each individual option, I don't see a better solution at this time. I'm also still opting not to clear old/unused config entries, since doing so could interfere with some people's PR/fork testing, though it comes with the downside of cluttering the config file.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.