[128x - 32x] InfiTech 2 & 3 [MC1.7 & 1.12]

[Loonessia]

...

Added to OP. Thanks.

If you think you're going to do further updates, and will commit to keeping the first post tidy, I can change thread ownership to you.

If my post is anything decent, I can do that. Thanks.

[HanFox]

...

Added to OP. Thanks.

If you think you're going to do further updates, and will commit to keeping the first post tidy, I can change thread ownership to you.

If my post is anything decent, I can do that. Thanks.

Okiepokes. You're the owner of the first post now.

Not really much you need to do besides updating the changelog as you make changes to your patches and keeping the Credits up-to-date

[HanFox]

The way you're versioning your patches is likely to cause confusion. If you say your patch is v1.0.8.2.1 people are going to expect the modpack to also have that version, but it doesn't.

I would suggest if you're updating the patch for the same modpack version just to keep calling it v1.0.8. The changelog will show changes if people are interested, you can also reply in the thread to say you updated it to draw attention. That also means if you keep the zips with the same name people can just copy/paste over the old one and load up without having to wait 15 minutes for the old patch to load before then having to wait another 15 minutes when they swap it over

With my mod patches I usually rename the old patch to the version it matches, and the new patch would be versionless.

If you are particularly keen to keep the patch version, too, however the generally accepted "standard" is usually to append a dashed number to the end (i.e. v1.0.8-2).

Lastly your 128x patch had the same link as the 64x patch, so I removed it for now.

[Loonessia]

The way you're versioning your patches is likely to cause confusion. If you say your patch is v1.0.8.2.1 people are going to expect the modpack to also have that version, but it doesn't.

I would suggest if you're updating the patch for the same modpack version just to keep calling it v1.0.8. The changelog will show changes if people are interested, you can also reply in the thread to say you updated it to draw attention. That also means if you keep the zips with the same name people can just copy/paste over the old one and load up without having to wait 15 minutes for the old patch to load before then having to wait another 15 minutes when they swap it over

With my mod patches I usually rename the old patch to the version it matches, and the new patch would be versionless.

If you are particularly keen to keep the patch version, too, however the generally accepted "standard" is usually to append a dashed number to the end (i.e. v1.0.8-2).

Lastly your 128x patch had the same link as the 64x patch, so I removed it for now.

The versioning:
That was my way of being clean about compiling my modpatch versions together. I can just fix that up in Google Drive I suppose. If I understand correctly, if I just keep the patches versionless, but update the mcmodmeta.info, minecraft will load it up automatically given that the old resourcepack file was replaced?

128x: My computer has a weird way of not wanting to copy links sometimes. It's weird.
Furthermore, since I am kinda new to forum posting, please tell me what you're doing to my post in a PM after you edit it. Thank you.

[AtroCty]

Go ahead and get dem ownership.

[Loonessia]

Novamanga just PM'd me basically telling me he's added some patches I've missed. I'm going to converse with him to see what he's added so I can keep the post clean, and add it to my Google Sheet, but for now I'll just addendum what he made for me.