ViaFabricPlus integration to temporarily add back removed hacks

[expected-ingot]

Pre-suggestion checklist

• I have searched existing issues and didn't find any previous issues with the same suggestion.
• This is only one suggestion. I understand that GitHub issues don't work well with lists.
• This feature doesn't already exist in the latest version of Wurst. I've made sure my installation is up to date.
• I have looked at the code and am reasonably confident that this suggestion is possible to implement.

What type of improvement are you suggesting?

Other (please explain in description)

What type of player would find this improvement useful?

Griefers

Description

Wurst could detect if ViaFabricPlus is installed. If it is, it could check which version ViaFabricPlus is connecting as, and from there, check which removed hacks worked in the version you connected as.

For example, you could be playing on 1.21 and connect to a 1.17 server with ViaFabricPlus, and then the NocomCrash hack could appear. But if you connect to a 1.20 server, NocomCrash will disappear as it doesn't work for >1.18.2. Same for OP-Sign. When joining a 1.8 server on 1.21, OP-Sign could become available, but would then disappear on 1.12.2 servers.

[github-actions]

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

• They are duplicates of other issues
• There is not enough demand
• They are no longer relevant
• There are not enough details

[expected-ingot]

.

…

On Thu, 19 Dec 2024, 03:42 github-actions[bot], ***@***.***> wrote: This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks. Issues should be closed if: - They are duplicates of other issues - There is not enough demand - They are no longer relevant - There are not enough details — Reply to this email directly, view it on GitHub <#1078 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOHGBO2GQ2LHVBXUFUBFM32GIXBDAVCNFSM6AAAAABQH3FFEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGY2TONJUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>