Skip to content

Conversation

@shingonati0n
Copy link
Contributor

@shingonati0n shingonati0n commented Dec 17, 2025

Update XIVOmega to v1.0.3

  • Updates to container for FFXIV 7.4
    • New mitigation script with changes from Soreepeong mitm.py
    • Using updated ffxiv_dx11.exe file
    • Quay Container updated to v0.4.0

Task Checklist

Developer

  • I am the original author or an authorized maintainer of this plugin.
  • I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin

  • I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
  • I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

  • No: I am using a custom backend other than Python.
  • No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
  • No: I am using a custom binary that has all of it's dependencies statically linked.

Community

  • I have tested and left feedback on two other pull requests for new or updating plugins.
  • I have commented links to my testing report in this PR.

Testing

  • Tested by a third party on SteamOS Stable or Beta update channel.

@shingonati0n shingonati0n requested a review from a team as a code owner December 17, 2025 04:28
@github-actions github-actions bot added the plugin-update Updating a plugin on the Plugin Store label Dec 17, 2025
@github-actions
Copy link

Issues Found

  • Both testing boxes are present in your description. Please remove one of them per the Markdown comment above the testing section.

Next Steps

  1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
  2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
  3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

@shingonati0n
Copy link
Contributor Author

Hi, I've removed the checklist for preview as per the comment. Please take a look, thanks

@beebls
Copy link
Contributor

beebls commented Dec 17, 2025

From looking at the diff, it looks like the only change is the quayver property, does this change include the things you mentioned

  • New mitigation script with changes from Soreepeong mitm.py
  • Using updated ffxiv_dx11.exe file
    Or was there some other code change that was also meant to be included here?

@shingonati0n
Copy link
Contributor Author

Hi @beebls, the changes listed were done on the container that runs the mitigation code, hence why the diff is not visible. Please refer to this commit shingonati0n/xivomega@277e891 to see the code changes of mitm.py - this is from the precursor of this plugin, which I maintain for Linux users. Both use the exact same podman container from quay.io. I keep the files that are part of the container in xivomega repo for visibility and transparency. Let me know if you have any further questions.

Copy link
Member

@EMERALD0874 EMERALD0874 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for testing

@github-actions
Copy link

This pull request is stale as no updates or testing reports have been posted within the last 7 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

@github-actions github-actions bot added the stale label Dec 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugin-update Updating a plugin on the Plugin Store stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants