00:00 <ckanbot> [CKAN] netkan-bot commented on issue #2123: Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automaically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it! https://git.io/vdagI

01:49 <politas> !tell HebaruSan Yes, the netkan filename should match the identifier. Travis checks for it on PRs

01:49 <Qboid> politas: I'll redirect this as soon as they are around.

01:49 <HebaruSan> Thanks! I thought so but didn't know where to look to prove it.

01:49 <Qboid> HebaruSan: politas left a message for you in #ckan [10.10.2017 01:49:06]: "Yes, the netkan filename should match the identifier. Travis checks for it on PRs"

01:50 <politas> Jenkins, I mean, not Travis. Travis is for the codebase.

04:43 <ckanbot> [CKAN] ashein commented on issue #1940: Just got it yesterday when updating `EVA Enhancements Continued`, a day before auto-updating existing mods worked fine, nothing changed as far as I remember. Tried the usual "remove the mod + reinstall the mod", but apparently the "path is already absolute" triggered on mod removal before update, not on the update itself. That was on Win10. Manually correcting `KSPInstancePath_0` in the registry helped me. ht

22:23 <Cell> Hey all, returning to modded KSP after a break. My game crashes when it reaches the menu screen and I believe this to be because my mods current version are spread from 1.3 to 1.31. is there a way to rollback those mods that are currently installed at 1.31 to 1.3 version? I cant figure it out ty!