Jump to content

HebaruSan

Members
  • Posts

    4,995
  • Joined

  • Last visited

Status Replies posted by HebaruSan

  1. On SpaceDock, for some reason, I can't seem to add more collaborators/authors. Can you look into this?

    1. HebaruSan

      HebaruSan

      Hmm, it also says their account's email isn't confirmed, which I think is needed before they can make it public. They should have received an email when they created their account with a confirmation link that they can click to do that. It may have gone into a spam folder. If they can't find it, have them let us know on Discord and we can skip that step for them.

    2. (See 3 other replies to this status update)

  2. On SpaceDock, for some reason, I can't seem to add more collaborators/authors. Can you look into this?

    1. HebaruSan

      HebaruSan

      That user's profile isn't public, which is required to co-author mods. Tell them to go here and click "Make Public":

      https://spacedock.info/profile/KnightofStJohn

      (The blank error message is a known issue already being fixed in https://github.com/KSP-SpaceDock/SpaceDock/pull/425.)

    2. (See 3 other replies to this status update)

  3. On SpaceDock, for some reason, I can't seem to add more collaborators/authors. Can you look into this?

    1. HebaruSan

      HebaruSan

      No, I can't look into it, because you haven't described the problem you're having. I would have no idea what to look for or investigate.

    2. (See 3 other replies to this status update)

  4. Preparing a release of ShipManifest.  Anything I will need to do for CKAN beyond the version file, and the git release?

    1. HebaruSan

      HebaruSan

      Hi!

      Right now CKAN is set up to pull this mod from https://github.com/mwerle/ShipManifest (see https://github.com/KSP-CKAN/NetKAN/pull/7756), so we'll have to switch it back to your repo if you're planning to post a new release there. I see on the forum thread that you already talked to @micha about this, so I've started a pull request to take care of that:

      We can merge it once the new release is posted.

    2. (See 1 other reply to this status update)

  5. (don't read)

    1. HebaruSan

      HebaruSan

      I don't think he wants to be bothered about this by random people, since he requested both of the forum threads for those mods to be closed in March 2019.

    2. (See 2 other replies to this status update)

  6. HI all, first off thanks to all those who've inquired after my welfare, as to the reasons I'm no longer active on the forum or releasing mods, they are many and numerous, primarily it's health issues, I've been fighting a mystery virus for several years,  and as I've become older the effects of that have become more difficult to live with, tbh it's really difficult to be creative ( or sociable) when you feel like crap. Along with that, the frequent KSP updates combined with the size of my mod catalog meant that just keeping them all updated or even working became a chore, much more like unpaid slavery than fun, and guys it needs to be fun.  There are of course other reasons, some to do with the forum in general and some  to do with mods that have been a cornerstone of SM mods since the very beginning but we'll leave that there.  
    Regarding the closed threads and broken links, when i decided that enough was enough I was not in the best frame of mind, and certainly was not in the mood for explanations,  so perhaps a final message was in order, but honestly forum interaction had dropped to a point that it hardly seemed worth the effort.  Shortly after closing the threads i became aware that certain parties had without my permission, or even asking for it, taken  parts of various mods, the simple solution at the time, and to prevent further unauthorised use of assets,  was to simply pull the mods from the various locations, and while it was perhaps a bit heavy handed, I do have a serious amount of time invested  in that lot, as any of the guys on the team would tell you, and somehow i don't feel like just giving it all away.


    Which brings me nicely to the current SpaceDock situation I'm aware that SM Armory and SMAFV's are back up on SpaceDock, this is completely unauthorised, they are not supported . I've not been contacted by the user RecoverMod regarding them, and such publication is in breach of the license. I and others are taking steps to have them removed, something I shouldn't have to do.


    As to the future,  difficult to say, but after playing KSP since 2012 and making KSP mods since 2014, I think a break is in order, but the sad thing is we, the team and i, know pretty much where KSP outer limits are, we know what can be done and where, and while the game remains unity based they are very unlikely to change in any great way, so where's the new challenge? the idea of doing the same thing over and over just in different ways is not something that appeals

    Thanks again to all those who supported the SM mods in any way, particularly those who got my gears spinning.
    Happy travels guys

    1. HebaruSan

      HebaruSan

      Thanks very much for explaining all that. That RecoverMod guy had the gall to request CKAN indexing for his unauthorized uploads, which we declined, but it's nice to know the situation for sure.

    2. (See 6 other replies to this status update)

  7. I think your avatar pic is absolutely hilarious.

    1. HebaruSan

      HebaruSan

      Thanks! Unfortunately I found it via image search rather than creating it, so I've been meaning to change it for a long time.

  8. Have you found the time to update your mod? I would love to try it.

    1. HebaruSan

      HebaruSan

      It should already be working on KSP 1.4. I haven't looked at it on 1.5 yet.

    2. (See 3 other replies to this status update)

  9. Have you found the time to update your mod? I would love to try it.

  10. I saw you liked my Thank You post on the CKAN thread.  Was it you who did the work?  How does CKAN import/incorporate stuff from Spacedock when you click the little box to add it to CKAN?

    1. HebaruSan

      HebaruSan

      Hi! Yep, I took care of that. When you click that box, SpaceDock auto-generates a pull request with a .netkan file on the NetKAN repository; in your mod's case, this one:

      https://github.com/KSP-CKAN/NetKAN/pull/6054

      Then somebody from the CKAN team takes a look at it (there are queues/feeds/notifications) and can accept it as-is, reject it completely, or make tweaks. We usually try to check for dependencies, weird installation requirements, etc., and there are some validation checks that run as well to catch common problems.

      In this case, I actually deleted SpaceDock's new file because we already had one for your mod from 1.2.2, which I updated instead based on what was in the new zip file and your forum thread. I felt a bit bad about messing up a different request earlier (I merged #6052 without its dependencies, so the mod author had to submit #6053 to add them), so I tried to learn from that and cover all the bases on yours.

      Thanks for your kind words on the thread, and you're welcome!

×
×
  • Create New...