Add XIVOmega Plugin

[shingonati0n]

XIVOmega

A Steam Deck Plugin (for Decky Loader) to mitigate latency on the Critically Acclaimed MMORPG Final Fantasy XIV. This plugin is the evolution of xivomega which in turn is based on XivMitmLatencyMitigator, XivMitmDocker and XivAlexander. Mitigation is done by using containers via Podman, which comes bundled with SteamOS.

Checklist:

Developer Checklist

• 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 Checklist

• 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 alternatively provides more/alternative functionality to a similar plugin already on the store.

Plugin Backend Checklist

• 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.

Testing

• Tested on SteamOS Stable/Beta Update Channel.

• Tested on SteamOS Preview Update Channel.

[shingonati0n]

Hello, is there anything else I need to do to advance this request?? First time submitting a plugin,thanks. @TrainDoctor

[TrainDoctor]

Hello, is there anything else I need to do to advance this request?? First time submitting a plugin,thanks. @TrainDoctor

Nothing that's your fault, apologies. Been busy with work and life and didn't get to many PRs, let alone yours 😅.

[TrainDoctor]

1. Please remove the backend folder and it's contents as you don't appear to be using that functionality.
2. Remove defaults.txt from the defaults folder.
3. Remove decky_plugin.pyi as it is out of date and no longer used.
4. Please update the license file to include your name or username (whichever is preferred).
5. This is my fault, please update your lockfile to the latest (~v 9.0 etc) version. The plugin development side of the wiki was out of date and I only just updated that today.

Once you make these changes the plugin will be good to go to the testing store and once a testing report following the proper format (https://deckbrew.xyz/testing) is completed you'll be good to go to the production store!

[shingonati0n]

Hi @TrainDoctor, changes have been made as requested. Note I also added a small update to main.py to handle an scenario I ran into recently (wlan0 not active at boot time). Please take a look, thanks!

[TrainDoctor]

Hi @ TrainDoctor, changes have been made as requested. Note I also added a small update to main.py to handle an scenario I ran into recently (wlan0 not active at boot time). Please take a look, thanks!

Thanks, and sorry for the delay. Changes look good. Off to testing.

[TrainDoctor]

Closing as untested. If you are able to locate a tester in future we will happily accept a re-submission.

[TrainDoctor]

@shingonati0n, if you are able to update this PR with a version of your plugin (please also make sure to bump your version by at least a patch to ensure no conflicts will occur in CI/CD etc) that you have verified with the latest stable versions of Loader then I can re-open this PR. (Please note the below text only applies if you are able to make the requested update, thanks for your understanding). The more plugins that can come back the higher chance you are able to see a tester for your plugin is my hope.

I am currently experimenting with a concept for testing plugin submissions and plugin updates. I would request that you submit testing reports for at least 2 other plugin submissions/updates (preferably the oldest PRs still active). Then if no other plugin author (as I will be encouraging all others to do the same) or tester submits a testing report I will request that a member of the SDH team tests your plugin update/submission according to the testing guidelines.