Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[LoSboccacc]

Every mod in their forum gets hammered by "updoot now!" for a few pages after a KSP release before moderators come and clean it up.

aaaand? sure it's annoying, but from there to going ballistic there are more reasonable courses of action. beside he likes the spotlight, he didn't even keept it down more than 24 hours.

[BigD145]

Every mod in their forum gets hammered by "updoot now!" for a few pages after a KSP release before moderators come and clean it up.

Yes, but most of them don't go nuclear and delete their own work over it.

Exactly my point.

[forsaken1111]

Every mod in their forum gets hammered by "updoot now!" for a few pages after a KSP release before moderators come and clean it up.

Yes, but most of them don't go nuclear and delete their own work over it.

Exactly my point.

Ah sorry, sounded like you were excusing his behavior.

[BigD145]

Every mod in their forum gets hammered by "updoot now!" for a few pages after a KSP release before moderators come and clean it up.

Yes, but most of them don't go nuclear and delete their own work over it.

Exactly my point.

Ah sorry, sounded like you were excusing his behavior.

Heck no. He's not that special of a flower. Sarbian has been at this a long time and I know he reads the forums.

[Shadowlord]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

[forsaken1111]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

Because new versions bring new code which behaves differently? Honestly why would you expect them not to break?

[LoSboccacc]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

Because new versions bring new code which behaves differently? Honestly why would you expect them not to break?

yeah games usually do shit about modding forward compatibility, even if it has proven times and times again to lead into modders burning out.

[Putnam]

>implying it's not ludicrously difficult to do that

[Putnam]

Especially with KSP which, as far as I can tell, supports DLL injection with its mods. Good luck maintaining forward-compatibility with that.

In fact, most mods use it extensively. You can't add any new features to the game without it. You can add new parts that have similar functionality to existing parts, but that's almost entirely it.

KER, Kopernicus, StageRecovery any lighting changes, transfer window planner, EVA handrails, modularflightintegrator, module manager and KAC all require this. Note that I named all but one of the mods there. That last one should still work, but I wouldn't be surprised if CKAN's a butt about it.

[BigD145]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

CKAN is awful. More trouble than it's worth especially for certain mod authors that nest their work in one folder.

[forsaken1111]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

CKAN is awful. More trouble than it's worth especially for certain mod authors that nest their work in one folder.

Worse, I've seen CKAN mods flagged for versions that they absolutely DO NOT work for, and it will quite happily install them anyway royally fucking your setup. I just install everything manually, just like I do with Skyrim and Fallout 3/4. Trusting a mod manager for anything beyond the most basic tasks will almost always end in tears unless the game is designed with mod compatibility in mind like Rimworld, and even then it can lead to huge problems if you don't know what you're doing.

[BigD145]

Why does every new KSP version seem to break all the mods I have installed? Sigh.

Spoiler (click to show/hide)

CKAN is awful. More trouble than it's worth especially for certain mod authors that nest their work in one folder.

Worse, I've seen CKAN mods flagged for versions that they absolutely DO NOT work for, and it will quite happily install them anyway royally fucking your setup. I just install everything manually, just like I do with Skyrim and Fallout 3/4. Trusting a mod manager for anything beyond the most basic tasks will almost always end in tears unless the game is designed with mod compatibility in mind like Rimworld, and even then it can lead to huge problems if you don't know what you're doing.

As long as you remember how you did it in the first place, yes. Skyrim and Fallout have very specific orders and overwrites for certain mods. Kerbal you always delete the old version, not overwrite.

Mods like the contract one and Strategia require waiting for now. They're too big of an impact in career.

[Putnam]

Nono, mod managers are required where mod installation is complicated. Bethesda's games are an obvious case of this, with load orders n' shit. Kerbal Space Program's mod installation is as such:

1. Download the mod and open the archive. If the folder contained within is "GameData", move on to step 2a, otherwise move to step 2b.
2a. Merge the GameData folder with your KSP install's GameData folder.
2b. Move the folder in the archive to your KSP install's GameData folder.

The only thing you have to worry about on top is dependencies (which are in almost all cases taken care of by the original download) and incompatibilities (which are hideously rare). CKAN tries to take care of both, but the more dependencies, the more likely someone screwed up the metadata or has the wrong version.

[Shadowlord]

To be frank, the main reason I use CKAN is experience with Bethesda games.

[BigD145]

Kerbal modders add AND remove parts OR rename them. Copying over is a terrible idea.