Ippo

This is not really a small patch as the .1 would suggest: the big stuff is that it is now FAR-compatible! Or at least it didn't cause any problems when *I* tested it. To install the FAR patch, just copy the new ZZZ_DangIt_FAR folder in your GameData. DO NOT RENAME THIS FOLDER*, otherwise it will not work. If you don't use FAR, you can either remove this folder or just leave it there, it won't cause any problems. The cost of command pods has been fixed, and also the issue with rapier engines. * or if you really must, just make sure it comes after "FerramAerospaceResearch": it needs to be loaded after FAR, and the AddonLoader goes in alphabetical order.

I think we might have a problem, guys.

Joined 3 months ago, only posted twice (and one of them was deleted) and the only post we can read of you, what a coincidence, is bashing the main community project against curse. Not suspicious at all.

Regarding the single, unified update check mod, there is already KSP AVC that does basically that. It would be a good way to start.

No, I've been busy in RL. I'll have some time this weekend. P.S: By the way, I found out what is causing the issue with the rapiers. I added a safety measure in the code to prevent unexpected stuff, but then I found out that the rapiers don't respect my assumption. I'll get to it as soon as I can

Aerodynamics is (and has always been) on the what not to suggest list.

Know bug, I already notified the author. Unfortunately I haven't been able to find the cause / fix, so we'll have to wait for him to have some free time again

Actually, if you check the thread I've been a proponent of opt-in since the very beginning.

I'll just drop this here, and never come back. I just want to let everybody know that there are two separate merge requests to improve the code in order to address the issue. We will know what Majiir thinks of the issue when he comes back online to discuss those merge requests. Timezones are problematic, but I imagine we'll have his opinion on them in 24 hours.

Hint: the forum doesn't provide hosting. This is community hosting.

That *was* the polite version.

Let's be clear: BetterThanSpyware and StillBetterThanSpyware are not alternative implementations of an API. They are software that hijacks another program. Also, considering that I've been pushing for the opt in since this was first posted AND SO FAR I'M THE ONLY ONE WHO CARED TO DO SOMETHING ABOUT IT, shut up.

No, what I'm saying is that if the plugin A is so similar to plugin B that plugin B recognizes it as a version of itself, then I can see why there are licensing issues. I'm very glad I don't have to sort this out, though I just hope that Majiirs wakes up early and sees the pull request I made so we can end this nonsense.

Yeah sure, I was just giving my opinion. I still don't understand why you can't just distribute a config file with "disabled = true", though. No legal problems at all, saves the same purpose.

I believe that the problem lies in the fact that your mod is recognized by ModStatistics as a ModStatistics implementation. Fork or not, as long as your plugin is mistaken by the original plugin as a new version, I can see why it counts as a derivative work. Even if you didn't modify the source code, you are still compatible enough that the mod believes it has found another version of itself: so yes, I can see why it counts as a derivative work, and the license does not allow you to distribute it.

You really don't understand how these things work. Showing the source is a requisite because of the forum's policy, but you have to choose a license for your work and the license he chose is "you can't do anything with it". A software is not free software just because the source is posted online: you always have to comply to the license the author has chosen, failure to do so is simply illegal. Fair enough: Majiir needs to fix this.

Well, in this case I have no idea about how legal this is. The previous time it was obvious, this time I honestly don't know and we'll see. Anyway, I think you are doing the wrong thing. More than Majiir.

Agreed. What a stupid waste. 1) You have the right to write a mod that disrupts ModStatistics, but it's not legal to do it by modifying his code; 2) If you have the coding skills to write a plugin, why don't you just go ahead and submit a pull request with the changes you want instead? No, he's enforcing his rights, which forfeit violated. Can you back this accusation, or is it just random talk? So let's start the compromises there.

1) Wrong thread 2) No 3) WRONG THREAD.

Thanks, I'll look into that.

Actually in 1.0.3 that popup only asks you if you want to auto-update, but it doesn't let you opt-out. And it relly should, so we could get this over with.

Very unlikely, since Squad doesn't endorse or distribute this mod in any way.

Actually this gives you permission to fork it, but Majiir has decided to hold all the rights and explicitly states that you are not allowed to distribute a modified version of his mod.

Yes, but this is (imho) violating ModStatistic's license and you are not allowed to do it.

Isn't it easier to just provide a cfg with the opt-out option set, instead of a full-blown plugin? EDIT: Also, I think you should clear this with Majiir. I'm not sure if this is compliant with ModStatistic's license: "License: You may redistribute unmodified versions of ModStatistics. All other rights are reserved." It's basically an empty plugin, true, but since you forked the repo and deleted code... not sure if it's kosher.