-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shouldn't be a farewell tour #292
Comments
As you can see by looking at the recent commits there is work being done to update this to 7.0/APIX so I wouldn't worry too much. It is just going to take some time. |
what a crazy rude issue to open |
Offering to help someone that stated they needed it is crazy rude? What
the hell are you talking about? I offered to financially help someone to
get a plugin fixed. Wow, maybe I’m satan for bartering my money for his
coding skills. That’s not the way business is done around here at all am I
right?
…On Fri, Jul 5, 2024 at 5:28 PM Harison Punian ***@***.***> wrote:
what a crazy rude issue to open
—
Reply to this email directly, view it on GitHub
<#292 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASY5UAQ4RAOC7WFEEBEWB2DZK4FYTAVCNFSM6AAAAABKNW5L6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGQZTGMRXHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
There's a lot of things wrong with this statement... I'm not defending attickdoor, so take this as an explanation of etiquette:
This is "the way business is done" around here. |
Most of the classes haven't received changes that would alleviate the need for xivcombo
The text was updated successfully, but these errors were encountered: