Dependensee - Google, what Fabric is version for 26.1?!!

[thorn belfry]

Disclaimer: This is more of a tool than a mod. If that makes it too irrelevant for this channel, I'll be sure to remove this post!

I'm pretty new to mod dev, so this might be a skill issue, but I quickly noticed a bottleneck of mine for porting was finding the right version for every dependency. So I made this tool!

I can't imagine a tool like this doesn't already exist, but it was good practice, and I hope someone can get some use out of it. Contributions are welcome! The dependency system is simple and modular, so it's hopefully easy to add support for more mod loaders and common dependencies.

Thanks for reading!

https://palmmc.github.io/Dependensee/

[tidal grotto]

What do you use to make these hand drawn style sites?
Sorry, irrelevant questions but I’m curious 😅

[thorn belfry]

A lot of it is just css styling. The header was me with a mouse in a mspaint-like program 🤣

The site itself uses Jekyll to build

[tidal grotto]

Oo cool
Ty

[faint adder]

I have not heard of such a tool before, it seems pretty useful

One additional feature that might be nice is automatically adding dependencies from modrinth, since the modrinth maven is not transitive
e.g. any of the rpg series mods have a big dependency tree

[brittle onyx]

wowza !!!

big fan of this thing

[raven axle]

Awesome!
I always wanted to make such a tool, but never came around to actually do it (and it probably would have required me to do javascript, which I like to avoid).
one feature I'd really want would be to generate a permanent link to that configuration, for easy updates

also it seems like the mod dependencies aren't loader aware, it would be nice if it could look them up for the loader used, and maybe even for all selected loaders (if there are multiple selected)

[thorn belfry]

That is a good idea, definitely will add that when I get the chance!

[thorn belfry]

I can do this as well I think, seems easy enough!

[strong nimbus]

ah
so no april fools

last time i tried the only acceptable configuration was

loader_version=0.7.8+build.184
fabric_api_version=0.5.7+build.2-20w14infinite

but thats probably not feasible to implement

looks really nice tho 🩷

[thorn belfry]

Yeah; it's not even going to work perfectly for normal versions. It's not so much a replacement as just a "saves a bit of time, sometimes".

[boreal dagger]

suggestion: when adding mod implementations, the variable name should be inferred from the project slug unless you give it a custom value, aka the variable name in this example should automatically be sodium_version

[hidden girder]

suggestion: libs.versions.toml version for those of us who follow best practice

[thorn belfry]

Speaking again as someone with very little modding experience, saying your way of doing things is best practice seems subjective. I've never seen anyone do it that way before.

But you're of course welcome to make a fork or PR

[thorn belfry]

This wouldn't be hard to implement, I can definitely do that!

[strong nimbus]

not for mods but just for gradle projects version catalogue is really nice

i have zero clue why its not popular in mods (and i haven't tried myself)

[thorn belfry]

Oh, that is weird. ☹️

Maybe one of those things where people get stuck in their ways; all of the templates I've used for my projects use gradle.properties, I guess it's how they're used to doing it.

Unfortunately though, since I don't have any experience with it, I don't think I can really implement that. I'd still need someone else to make a PR.

[hidden girder]

No, it's the recommended best practice

Fabric's official docs recommend bad Gradle practice far too often

[thorn belfry]

Recommended by who?

[hidden girder]

Gradle

[thorn belfry]

Oh, then you're right. They'd be the expert.

😂

[strong nimbus]

Wow yeah gradle props are so bad and never work lets nuke them

especially if i use 2 libraries

Catalog is the only way

[hidden girder]

Are you being sarcastic?

https://docs.gradle.org/current/userguide/version_catalogs.html

Fabric developers' aversion to best practices always amazes me

[pliant shard]

best practices are whatever I do. anything else is stupid and wrong

[strong nimbus]

Yes absolutely

you dont have to follow every single "best" practice there is

All of them are optional

Are version catalogs good? Absolutely
Are they very necessary if you use one library? No

you just do whatever you want and no one cares

[pliant shard]

actually that person seems to care

[strong nimbus]

Also both fabric docs and fabric mod template generator seems to be super beginner oriented

[hidden girder]

I never said this

[hidden girder]

           DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
  TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

 0. You just DO WHAT THE FUCK YOU WANT TO.

[pliant shard]

I did

[thorn belfry]

Jesus? 😨

I had no idea you were in this space

[pliant shard]

I get around

[strong nimbus]

i agree

i should look at your code and get some inspiration on bestest practices

/j

[hidden girder]

Jesus Christ

hah

[hidden girder]

Yes you should
-# /j

[strong nimbus]

i always follow best practices 😌

-# *only some of them

-# *sometimes

[hidden girder]

do not look at my recent modfest submission for best practices you'll regret it

it went through multiple modfest panics, including adding three features hours and minutes before the deadline

[strong nimbus]

public mixin

[strong nimbus]

erm

to be fair sun's guide is like 27 years old but e.g. checkstyle still follows it and
https://checkstyle.org/styleguides/sun-code-conventions-19990420/CodeConventions.doc2.html#a1852
statics come first, instance next, the order of those is from most public to most private

and tbh i hope i showed how absurd best practices can be

actually a better screenshot
statics are in the middle of them

[hidden girder]

this is just about the worst mod you could ever use for good practices

[strong nimbus]

rip