Skip to content

Conversation

@A1mDev
Copy link
Contributor

@A1mDev A1mDev commented Oct 2, 2025

  • Added stricter processing of game configuration data.
  • Previously, the extension often returned no errors, even if some sections were
    incorrect, giving a false sense of successful patch application.
  • Now, malformed sections or invalid entries trigger warnings or errors,
    making it clear when something is wrong.
  • This helps prevent silent failures and speeds up development and testing
    by alerting users to typos or misconfigurations in the patch data.
  • Fixed some type cast warnings.
  • Ensured proper initialization of MemoryPatchInfo fields, avoiding uninitialized offset values.

- Added stricter processing of game configuration data.
- Previously, the extension often returned no errors, even if some sections were
  incorrect, giving a false sense of successful patch application.
- Now, malformed sections or invalid entries trigger warnings or errors,
  making it clear when something is wrong.
- This helps prevent silent failures and speeds up development and testing
  by alerting users to typos or misconfigurations in the patch data.
- Fixed some type cast warnings.
-Ensured proper initialization of MemoryPatchInfo fields, avoiding uninitialized offset values.
@nosoop
Copy link
Owner

nosoop commented Oct 2, 2025

Thanks for the PR; looks fine enough to me.

@nosoop nosoop merged commit 815d2ff into nosoop:master Oct 2, 2025
2 of 3 checks passed
@A1mDev A1mDev deleted the error_handling branch October 3, 2025 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants