#Different versions are hard to find

148 messages · Page 1 of 1 (latest)

opaque coral
#

This is mostly a feedback, regarding 64x Faithful but I think it applies to everything. I wish there was a single page on the website with a simple way to find the versions I want. Usually, the beta releases of older Java edition versions are pointless. I think it would be nice to have a simple table with "JE 1.16.5 - 64xFaithful 1.16.5 (or 1.16.x) (and this links to a download)" and similar for all the older versions of JavaEd - Faithful, since neither of those is being updated, and the betas are just inferior.

I stumbled upon this issue when looking for 1.20.x version of Faithful. https://faithfulpack.net/faithful64x/latest has 2 different links (that download the same files but named differently for whatever reason), while https://faithfulpack.net/downloads, under 64x, has the beta9 as being "latest". And it gets worse; if I for some reason think this beta is too old and click on the github repo link, looking for the latest version, I can download 2 different zips: 1.20.2 and java-latest, and both of these differ from the files downloaded from https://faithfulpack.net/faithful64x/latest. Yes, I could use mod loaders for texture packs, and in fact, prism launcher made it really easy to find the latest one, but c'mon guys, the website needs some cleaning up.

Faithful Resource Pack
Faithful 64x Full Release

Just over three years after its release, Faithful 64x is finally complete!
With the Release 1: Path and Journeys, I thought big and finished what I started....

terse nexus
#

also the website is in the process of being rewritten but at a very slow rate

#

this will involve a redesigning of all the ui

green sparrow
#

the current ui isn't confusing either really

#

the supported minecraft versions are listed right there

#

if theres only one theres only one

opaque coral
#

I just realized I was kinda dumb, the 32x is exactly what I said lmao. I guess I just projected my issue with the latest version onto the older versions because I couldn't find 1.16.5 64x (which doesn't exist)

terse nexus
#

i dont blame you

opaque coral
#

I guess the only issue now is the fact that I managed to download 4 different zips, from 4 different sources, all with different files, while looking for the "latest"

green sparrow
#

f32 has consistent naming – the zip always lists the mc version the pack is for, and the pack description mentions the release date. f64 should be the same, if it's not blame harya

atomic depot
#

the only problem would be any textures from before the autopush process that weren't in the older versions, but most should be supported

terse nexus
#

i dont think thats how the pushing works

atomic depot
terse nexus
#

i think it pushes it to a fresh branch

#

could be wrong tho

atomic depot
green sparrow
#

yeah

terse nexus
#

o

green sparrow
#

i uhh i have no idea why we still keep these branches

terse nexus
#

i muted that channel when i first joined

#

lol

green sparrow
#

@potent fern would anything break if we just got rid of the legacy version branches for f64

#

since support is not planned

opaque coral
#

this is kinda leading into another question of mine. If I install something like, 1.16.5 version of faithful, will it break anything if I use this version into like 1.12 of minecraft?

atomic depot
opaque coral
#

it should only have extra blocks and stuff, but shouldn't be an issue right

atomic depot
#

minecraft loves to change pack formats every update so it might break

green sparrow
#

using anything >1.12 on ≤1.12 especially will always break

#

since 1.13 was the flattening where nearly every texture got renamed and/or relocated

#

or reformatted

opaque coral
opaque coral
#

so I could have one faithful for 1.11 and everything before, and then the latest 1.20 for anything between 1.20 to latest?

atomic depot
#

maybe?

#

be prepared for it to break though

opaque coral
#

yep sure thing, I just wanted to simplify my life with the amount of versions I have to manage

green sparrow
#

latest gui won't work below 1.20.2

atomic depot
#

everything before probably has a few changes to textures that you don't know of

opaque coral
#

but based on the flattening, 1.11 should be the "latest" version for pre-flattening then

green sparrow
#

and there are a few entity textures that have had their format changed

opaque coral
green sparrow
opaque coral
#

my b, i read them the other way around

atomic depot
green sparrow
atomic depot
#

it just wont break as bad as a post 1.12 pack

opaque coral
#

alright, thanks everyone for the help

green sparrow
#

yeah pack formats change way more often and more drastically nowadays than they used to

#

for texture packs you should be mostly fine using a 1.12 pack even in 1.6

#

the largest thing i can think of that they changed was the model format in 1.9

potent fern
green sparrow
#

should we get rid of them then

potent fern
#

probably

green sparrow
#

@raw swallow should we

potent fern
#

@stray carbon should probably do it for cf64 as well

raw swallow
#

what's going on?

atomic depot
#

it doesn't hurt to have

raw swallow
#

ah I see

#

@green sparrow yes

#

delete old versions

#

fuck it

#

I'm not supporting them by any means

green sparrow
#

please do it yourself im not exactly sure where the cutoff is for you

#

just open github desktop right click the branch and delete

stray carbon
#

I definitely agree.

#

Seeing as CF64 isn't maintained at this point

#

Well actually

#

We should have two branches

#

one for the very latest release

#

and one for java-latest

terse nexus
#

wtf does this have to do with cf

raw swallow
#

LMAO

stray carbon
#

CF64's branches besides the latest ones aren't well maintained by me

#

they weren't really to begin with

raw swallow
stray carbon
#

Yeah.

raw swallow
#

What I can do

stray carbon
#

Which is why I'm saying

#

it should have two branches

#

can't just be one

raw swallow
#

is just remove all versions except latest and 1.20s branches

#

so once 1.21 drops

#

no more 1.20 branches

#

and etc

green sparrow
#

oh youre going all the way here

#

ok then

#

i wish you could archive branches

#

hm

stray carbon
#

well 1.20s

#

Just 1.20.2

raw swallow
#

hmmmm

terse nexus
#

i would only delete ones that arent 100% finished

stray carbon
terse nexus
#

if a version is fully done then keep it even if you arent actively maintaining the textures

potent fern
terse nexus
#

its better than nothing

potent fern
#

which basically means ignore their existence

stray carbon
#

So just have the bot skip them over?

potent fern
#

no I mean the bot would push but everyone pretends they don't exist

#

the only way for the bot to skip it is if the bot doesn't find the branch at all

#

you could rename it to like "1.13-wip" or something like that

#

which would ignore it

stray carbon
#

eh

green sparrow
#

oh so do nothing

#

lol

stray carbon
#

But at that point you might as well just do nothing yeah

raw swallow
#

so what do i do?

potent fern
#

delete honestly

green sparrow
#

yeah i guess in the end thatd be the best way to do it

potent fern
#

there's a lot of problems with the existing branches

green sparrow
#

what i would do:

#

delete the ones you never supported

terse nexus
#

what versions are 100% done

potent fern
#

would be better to port them properly later

terse nexus
#

just 1.20?

green sparrow
#

let the ones you did work on go stale

stray carbon
#

Why rename the branches just so the bot doesn't update them when you can at least somewhat have them be updated

green sparrow
#

keep them as archive

stray carbon
#

hm

potent fern
#

but why

#

autopush would handle new changes anyeays

stray carbon
#

In all fairness

#

There are perhaps some major versions we may want to keep

potent fern
#

archived versions are kinda stupid when there's basically 0 maintenance

stray carbon
#

Now that I think about it.

potent fern
#

the only versions that require serious maintenance are the atlases

stray carbon
#

1.20.2, 1.16, and any other version where the default textures change

raw swallow
green sparrow
#

you did support versions like 1.19

stray carbon
#

I would recommend

raw swallow
#

hmm probably

stray carbon
#

supporting versions in which there were texture changes.

#

Examples include 1.16

raw swallow
#

1.14?

stray carbon
#

uh yea prolly

#

idk whichever ones had textures change overtime

#

since Japap ofc.

jolly silo
#

F64x for 1.6.4 doesn't exist yet for some reason

stray carbon
#

Because Harya isn't looking to support old versions rn

jolly silo
#

Ok, understandable

heady apex
#

128x doesn't existtrollface

gilded magnet
terse nexus
#

no one wants to put in the work

green sparrow