Skip to content
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

Preliminary 3.4.0 Support #123

Merged
merged 10 commits into from
Jul 14, 2022
Merged

Preliminary 3.4.0 Support #123

merged 10 commits into from
Jul 14, 2022

Conversation

CDAGaming
Copy link
Contributor

  • Evidence in datamining has shown _Wrath to be the new suffix, hence it's preliminary implementation.

CF Releases fallback to TBC's Game Type ID, to prevent accidental releases as Retail and since the API is closer based to 9.2.5 and TBC then anything else.

- Evidence in datamining has shown `_Wrath` to be the new suffix, hence it's preliminary implementation.

CF Releases fallback to TBC's Game Type ID, to prevent accidental releases as Retail and since the API is closer based to 9.2.5 and TBC then anything else.
Copy link
Contributor

@Meorawr Meorawr left a comment

Choose a reason for hiding this comment

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

Nitpick: All your added lines are indented with spaces, whereas the rest of the file uses tabs.

I'm not sure defaulting to the TBC game ID for CF without the warning message being printed is a good idea as that could lead to surprises for any addons that need client-specific packages.

@Sharparam
Copy link

If CF doesn't support Wrath yet then shouldn't uploading Wrath packages to CF just be disabled until they support it?

@Meorawr
Copy link
Contributor

Meorawr commented May 13, 2022

If CF doesn't support Wrath yet then shouldn't uploading Wrath packages to CF just be disabled until they support it?

For packages that explicitly only support and target Wrath, yes - to me it'd make no sense to upload such a package to a platform that doesn't support that game version.

For multi-client packages that support versions other than but including Wrath, no - it should just flag it as supporting the other game versions and log a warning stating that the packager was only able to mark compatibility with a subset of the supported game versions.

@CDAGaming
Copy link
Contributor Author

Fixed up the indents and added a clearer message/warning for while CF doesn't support wrath. Presumably, if we just dont want it to upload to CF at all as wrath, then I'd assume the id assignment could just be removed or made invalid. Either way, up to you all 👍

@nebularg
Copy link
Member

Thanks for doing the work to get this ready 😛 Everything looks fine, but I'll probably sit on this for a bit until we actually get some wrath support/servers

@CDAGaming
Copy link
Contributor Author

Happy to help. At most, the only change thatll be needed to thos after merging is adding the curseforge game type once cf implements it, and possibly adding a few aliases for -Wrath depending on how devs end up packaging releases (In a perfect world, theyd all use -Wrath, but looking at the aliases bcc uses, its unlikely)

@Meorawr
Copy link
Contributor

Meorawr commented May 17, 2022

There won't be a need for any TOC suffix aliases; they only exist for Classic Era/TBC because Blizzard changed the original pair of suffixes in a patch after some addons had already started using the older ones.

@Meorawr
Copy link
Contributor

Meorawr commented Jun 24, 2022

Per #126 and some manual digging it seems we got a suffix alias anyway - WOTLKC. I guess this PR should add support it for the few people who'll be using that suffix for whatever reason.

@QartemisT
Copy link
Contributor

There will need to be a fix much like there is [[ "$wago_type" == "bcc" ]] && wago_type="bc", but for wrath -> wotlk, for the Wago support

@CDAGaming
Copy link
Contributor Author

CDAGaming commented Jun 25, 2022

Ill implement both these either later today or tomorrow morning, depending on time. Thanks for letting me know :)

@CDAGaming
Copy link
Contributor Author

Bit late, but I've adjusted the pr for wotlkc suffix support plus support for the argument mentioned in #126

Cheers!

@nebularg
Copy link
Member

No worries, addons aren't enabled yet and only wago supports it :p

@CDAGaming
Copy link
Contributor Author

https://www.wowhead.com/wotlk/news/addons-enabled-on-wrath-classic-beta-questie-weakauras-wowhead-looter-327667?webhook

Addon Support for WOTLK is now Live on the Beta, Let the games begin!

Credits to Qartemis for the find, should hopefulyl allow CF uploads pending any further issues
@QartemisT
Copy link
Contributor

Confirmed tested and working.
:) Amazing PR

@CDAGaming
Copy link
Contributor Author

Ah yeah, forgot to comment:

On behalf of commit bb7e652, CurseForge uploading should now be fully operational.
Pending any further issues, this PR is officially ready for review/approval 👍

@nebularg nebularg merged commit 1004c31 into BigWigsMods:master Jul 14, 2022
@nebularg
Copy link
Member

Thank you for your service, sir

@CDAGaming CDAGaming deleted the patch-1 branch July 14, 2022 20:49
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.

5 participants