Proposal: Add 1.7.10 support

[billy948787]

Hi I have made this mod available on 1.7.10
Here is my repo url: https://github.com/billy948787/modflared/tree/forge/1.7.10

I've tested on:

• GTNH modpack (platform: mac, Java25)
• Clean Forge instance created on Curseforge(need install UniMixins) (platform: mac, Java8)
• Other Platform

Feature :

• Let modflared run on 1.7.10 and replace minecraft api into 1.7.10 version and Java Std usage into Java8
• Workflow
• Others

Here is the implement detail:
I use the GTNH teams's forge 1.7.10 MDK to develop this project
Here is it's repo https://github.com/GTNewHorizons/ExampleMod1.7.10
They upgrade the gradle version into modern version. And keep the mixin available.
Also they use the Jabel https://github.com/bsideup/jabel
To let Java9+ feature can be compiled into Java8 bytecodes.

What I've done:
Basically just copy all of the original code from branch Neoforge/1.21.1.
Then refactor the code into 1.7.10 compatible.

Looking forward to your feedback. Danke!

Here is some screenshots.

On Clean forge:

On GTNH modpack:
top: No cloudflare tunnel
bottom: Cloudflare tunnel enabled

[HttpRafa]

I like and appreciate your work! However, I think the best course of action is to create two separate mods: one for version 1.21.1 and one for 1.7.10.
​Are you willing to do that? You could name the second one something like 'Modflared Legacy.' If you send me the link, I can add it to the official site so people can find it easily. I highly recommend this approach because Modflared for 1.7.10 and 1.21.1 are very different in terms of the toolchain and architecture. This also let's me concentrate on the newer Minecraft versions.

[billy948787]

Hello I've created the "Modflared Legacy" application in Curseforge. For now it seems like it need to wait the moderator to approve my application.

Also I'm working on CI/CD. To make it same as this "non-legacy" project.

Thanks for your reply and feedback!

[billy948787]

Hello. Recently the curseforge's moderator has disapproved the Modflared Legacy.

It says "Please remove the auto download of the CloudFlare and instead provide a link so the user will have to download it manually."

I wonder whether you had faced this situation before or not?

But it seems like If the user could reach the project with links. They are still able to download the mod though.

Sadly the project itself is only available on lagacy.curseforge. And It can't download the mod.

[HttpRafa]

Hello. Recently the curseforge's moderator has disapproved the Modflared Legacy.

It says "Please remove the auto download of the CloudFlare and instead provide a link so the user will have to download it manually."

I wonder whether you had faced this situation before or not?

But it seems like If the user could reach the project with links. They are still able to download the mod though.

Sadly the project itself is only available on lagacy.curseforge. And It can't download the mod.

I'm sorry you have to deal with this. That's the whole point of this mod! If the user needs to download cloudflared manually, then there is no point in using this mod at all. It's made to make the setup process for the user as easy as possible.

If I remember correctly, I got the same message when I first published the original mod on CurseForge. Is there still a way to chat with the moderator? If so, tell them that handling the download is the main feature. I’d also recommend trying to publish on Modrinth because they are a lot friendlier. If you need proof that I’ve given you permission to republish, just let me know.