How do I know if two mods are compatible?

[sweet cobalt]

Ive got one mod for extra parts, and I wanna install shaders, but idk if theyre compatible. How do U know that?

[elder coral]

Are you using CKAN?

[sweet cobalt]

Idk whats that, I'm kinda new

The mod suggested not to use that tho

( btw the mod I have is this one https://forum.kerbalspaceprogram.com/index.php?/topic/79433-18x-112x-soviet-probes-soviet-rockets-r7n1soyuzprotonzenitdneprkosmostsiklon-7-24-21/ )

[elder coral]

Well it’s really hard to check compatibility without CKAN. Go to #ksp-faq and read about how to install and use it.

[feral latch]

He asked in the KSP 1 chat too. Use CKAN.

[sweet cobalt]

Im looking CKAN rn

Lets see how it works

Thank u both

[elder coral]

Yeah once you get that working, as long as CKAN doesn’t show a red highlight on the mod then it’s compatible

[heavy sentinel]

still ckan hasn't fixed simpleadjustablefairing is a dependency for benjee mod

so sad

[frail leaf]

Graphics mods and part mods almost never interfere with each other, you should be fine installing both on the same game.

[wheat wing]

That's not for ckan to fix, that's for the mod author to fix.

[heavy sentinel]

that's ckan metadata side, it is often ckan maintainer has final say lol

[tight dove]

You know they’re not compatible when the game stops working with both of them installed

[wheat wing]

ckan maintainer has no 'final say', the bot indexes it according to what you've set. They haven't set it as a dependency

[heavy sentinel]

what you've set, but where you set it?

[wheat wing]

You define it along with everything else when you're either putting a PR directly into netKAN or uploading to spacedock with the box checked.

[heavy sentinel]

that's it, but most modders doesn't do it themselves. It is usually ckan mantainer or the bot does it

[wheat wing]

and that guy hasn't set it as a dependency on spacedock or sent in a PR so it's not ckan's fault

ckan cannot be expected to handhold for modders who don't know their own mods

[heavy sentinel]

most modders don't want to deal with ckan metadata

it is usually ckan maintainer does it

otherwise we won't have nertea mod on ckan at all lol

[wheat wing]

as the ckan implementation says, they'll review it before throwing it to the bot but they're just going to read the list of dependencies/conflicts/etc off what you put

and if you don't put it, that's your fault

[heavy sentinel]

but where you put these "list of dependencies/conflicts/etc"?

[wheat wing]

.

[heavy sentinel]

again
most modders don't want to deal with ckan metadata

[wheat wing]

again, he has refused to state "my mod requires this other mod". There is no metadata involved. He simply refuses to state it

His fault.

[heavy sentinel]

the original mod bundled with it

[wheat wing]

it is not ckan's responsibility to datamine previous versions of your mod to figure out what stupid shit you've been doing

[heavy sentinel]

the ckan somehow doesn't read oh that mod has that bundled, and didn't list it as dependency

but somehow able to manage to read off like other dependency

and yes the thread listed it has that bundled

[wheat wing]

everyone else manages to type out this simple sentence:
"My mod requires [other mod]"

failure to do that is on you

[heavy sentinel]

They have done that in the thread lmao

[wheat wing]

that's the exact info provided to ckan when uploading.

if you fail to provide it, guess what

[heavy sentinel]

where you provide it?

[wheat wing]

.

[heavy sentinel]

why you would think think ppl know how to tick the tickbox to add it ckan 100% know to edit dependency, you report it to there?

[wheat wing]

if they can't type out "My mod requires [other mod]" when checking the box that's their fault

[heavy sentinel]

There is none

[wheat wing]

it is not up to ckan to handhold modders who don't know their own mod

[heavy sentinel]

tell me where you can type out "My mod requires [other mod]"

[wheat wing]

dude have you even used spacedock

[heavy sentinel]

just screenshot it lmao

[heavy sentinel]

?

[wheat wing]

hey look they managed to type it out!

weird how other people list dependencies just fine.

[heavy sentinel]

what

nertea mod does not typed dependency here and ckan still manage to know what dependency are

[wheat wing]

that would be because nertea used an alternative method of ckan indexing or otherwise made sure the info they sent to ckan was correct

which the mod author you're crying about failed to do

if they refuse to provide all the needed information, that's their own fault

it is not ckan's fault

[heavy sentinel]

no one say it is ckan fault lol

[wheat wing]

.

[heavy sentinel]

doesn't mean it is ckan fault lmao

[wheat wing]

.

backtrack more

[heavy sentinel]

final say doesn't mean they have all responablity

[wheat wing]

then go talk about how benjee doesn't know how to type out simple sentences and never mention ckan again, thanks.

[heavy sentinel]

benjee has listed dependency in the mod description

[wheat wing]

they have not.

[heavy sentinel]

they have, but they missed that particular mod lol

[wheat wing]

Nobody missed that particular mod, the mod author did not list the dependencies. You can go look at the commit history on netkan

[heavy sentinel]

where? I checked the commit history, and didn't found what you say

on the other hand, the mod description listed deployable engine as dependency, but the file doesn't have it. The main point is we still haven't clear on how to list/include the dependencies, is it on spacedock, or github, or both, and on which specific part? Is listing in description alone is ok?

I think the missing simpleadjustfairing dependency is just slight/"fake" mistake on ckan part, rather than real mistake, since it is optional for kwrocketry even it is bundled, so if they scan folder for dependency they might set to "skip it". After all, missing simple adjust fairing wasn't a big problem until b9 part switch come among and spam everyone about error. But we're not sure how they list out dependency and other inner-working honestly so we all just guessing heavily lol

[wheat wing]

See, I know you didn't because you don't even know how spacedock works

there is no way you actually navigated github. The fact you waited a few minutes and then just blindly said "nuh uh" demonstrates that perfectly.

[wheat wing]

you have been repeatedly told how it works and their own tutorial tells you how to do it. If you refuse to read it, that's on you

[heavy sentinel]

you told bot read it or/and pull request did it. You explained how bot did it by screenshoting of a mod listing it's dependency in a description. That what we goes for.

[heavy sentinel]

If you think I don't know what I did then explain the procedure, rather than let other person guessing what you meant and say you're wrong cuz I say so

[wheat wing]

read

the

tutorial

if you don't know anything about how mods are added to ckan, stop talking about it. It's quite clear you don't, so literally: Stop talking about it. You are doing nothing but spouting misinformation that is disproven with 5 seconds of googling.

[heavy sentinel]

I know, but you said read the tutorial after the fact. I want to talk about our misunderstanding before we continue.

[wheat wing]

if you don't know anything about how mods are added to ckan, stop talking about it. It's quite clear you don't, so literally: Stop talking about it. You are doing nothing but spouting misinformation that is disproven with 5 seconds of googling.

[heavy sentinel]

Nope, my google front page fill with how to install mod and mod development.

[wheat wing]

and my google front page is filled with images of spaghetti when I'm being intentionally obtuse 🙄

[heavy sentinel]

I found the github page (somehow though other proxy rather than original page) in 2nd page. They explain the tickbox send a request to ckan team to add to ckan. But I think they have bot since the ckan file is added by a bot, so it is not related/not to that case

[wheat wing]

"I found the github page by looking everywhere except github"

no wonder why you have issues

[heavy sentinel]

?

you asked to google it, I found a result/"tutorial" related to it, but it is behind indexed page. It might due to page not available when google attempt to index it.

(and yes, my google result only has 3 pages of result, might be google botched the pages indexing)

[wheat wing]

the old "I'm not being obtuse, google must not have archived this widely popular page linked to on a wildly popular github repository!!!"

[heavy sentinel]

tell me what keyword you entered to search it rather than acting smart

[wheat wing]

and you know what I can admit I was wrong earlier
not only do they have a handhold for you for uploading to spacedock or PR'ing it yourself, they have a tool so you can automatically generate valid metadata yourself: https://ksp-ckan.github.io/metadata-webtool/

so it is literally that easy to do it

[heavy sentinel]

And it might not be that popular, since it is hidden behind ckan repo rather than spacedock repo. And spacedock doesn't mention it, at least in obvious way when you trying to upload it

[wheat wing]

"spacedock doesn't mention it"
also spacedock:

gee I wonder what this expandable question mark and link to CKAN is

[heavy sentinel]

it doesn't directly linking to it lol

[heavy sentinel]

cool it has metadata tool, but as same as other ksp tutorial: people have to find it first

[wheat wing]

oh no the immense burden of a modder having to read 6 lines of documentation before blindly being a pro

[heavy sentinel]

Tell me where you found it

[wheat wing]

go to ckan's repo and press the big ass wiki button. or just type it into google

[heavy sentinel]

yes but there are some multiple page which may have overlaying info implied in the title. Modders might skip to read it

and often, word are hyperlinked inside a bunch of info, modders might miss it even they try to read it

and yes, ckan team shouldn't have much responsibility on dealing with mod compatibility, but they rather to take the responsibility even they shouldn't be to encourage people to upload mod without dealing potential problem. However, it must be noticed Modders/users should tell them to fix it as their part of responsibility (and yes, I told das but he said it is quite low-priority).
What I meant final say or "they should fix it" is based on that that ckan team have the power of approving pull request, not meaning that ckan team should take full responsibility (and original reply is kinda a joke)

[brittle violet]

If you have an issue with a mod you can just report it instead of publicly insulting people. Thanks

[heavy sentinel]

maybe das just forgot about that since I didn't officially make a issue on github lol, partially my fault honestly

[wheat wing]

Excuse me, I did misspeak in that regard because from their phrasing it kept sounding like they were in fact you. I am not aware of any trouble with any of your mods, and if you have any with CKAN I'd be happy to help in PMs.