Jump to content

nightingale

Members
  • Posts

    4,137
  • Joined

  • Last visited

Everything posted by nightingale

  1. I figured as much - what I should've said is that this thread only links to 1.1.17, whereas KSP-AVC reports 1.1.18 is out there, but with a broken download link to this thread (because of how the forum software started handling shortened links a while back). So most users won't be able to find 1.1.18, and KSP-AVC users will get extra confused.
  2. Hey @sarbian, I'm going to be doing a Strategia release in the next couple days, and it looks like there's a 1.1.18 of CBK hiding in Jenkins. Is this just a case of the thread being out of date, or is there more testing you wanted to do for this?
  3. My alarm just triggered, and it looks like @ObsessedWithKSP re-entered KSP's sphere of influence after two year long trajectory....
  4. Should be based on the RecoveryValue (CelestialBody.scienceValues.RecoveryValue in code, I think it's in Properties/ScienceValues in Kopernicus). If you want to interact with it in CC contracts it's body.Multiplier() (for historical reasons).
  5. No problem! I'm going to do a Strategia release next (there may be nothing needed other than updating version files), then I have one outstanding issue that I owe you (around launch sites). If there's anything else you want as a priority on the GitHub tracker, just post on it to notify me that it's something you're actually still looking for (as it's hard to tell with many of the enhancements that were raised 6+ months ago if anybody is still waiting).
  6. Awww, that makes me sad. I almost took this one over before @Z-Key Aerospace stepped in. Not something that would be in the cards these days (I hardly update my own mods...), but hope someone will come along.
  7. A wild release appeared! @nightingale used GitHub.... it's super effective! Contract Configurator 1.26.0 Recompile for KSP 1.5.1 Updated to work with RemoteTech 1.8.13+ (thanks PiezPiedPy). Added trig functions to expression language (thanks VaPal). Invalid Celestial Bodies constants no longer throw an error on parsing (improves overall support for planet packs that remove/rename planets). Fixed a bug that prevented casting from string to ExperienceTrait. Fixed an issue affecting CollectScience and biomes with spaces (thanks mpharoah).
  8. That's Anomaly Surveyor. Look for updated releases for all that stuff in the next week or so. EDIT for stuff I didn't see: Jeez... sometimes it feels like I've forgotten so much... yes, it's Field Research that has those contracts, not Anomaly Surveyor. Working on it as we speak.
  9. All - I'm going to work on a quick update for 1.5.1 over the next few days. It's not going to be much - grabbing and reviewing a few pull requests, recompiling to 1.5.1, doing some quick testing and seeing if there are any "easy" outstanding issues that I can do a quick fix for in the GitHub list. Sorry that I haven't been updating this recently... other things have been a higher priority than KSP of late, so it's fallen down in priority. If there is anyone who is capable and interested in taking over, do send me a PM.
  10. Github wasn't behaving, so I just did a new release. Waypoint Manager 2.7.4 is now available.
  11. Time to update the mods... Waypoint Manager 2.7.3 Recompile for KSP 1.5.0.
  12. Not easily, you'd have to edit the hotel into the validHotels list, and there's some data that's not easy to get in there. You'd be better off getting the hotel contract again and just using hyperedit or other cheats to get it into orbit.
  13. Hard to say without more info - what does the requirements on the "Bring tourists to a hotel or casino" contract look like?
  14. @VaPaL - Still valid. Your way would work, but it limits the players options (they can't do it in 3 launches if they want). It's also a bit more tutorial-ish (although that may be what you want).
  15. @eddiew - I did fix something a while back around strategy levels that might be the problem. Let me do a release as is and see if that fixes it. If not, will get to it as soon as possible (which may be a bit as I'm travelling for work next week and on vacation the week after). Also - what do you even have going on? It looks like some sort of Strategia+ or something... custom icons, tweaked strategies... --- And here we go, new release. Strategia 1.7.2 Fixed logic for determining strategy level - this was causing some strategies to be the same for all levels (thanks ibanix). Fixed Astronaut Training Strategies not actually costing extra (thanks Jukelo).
  16. Something about it broke a long time ago (probably because of a stock update?). To be honest it hasn't been a priority to fix, but will try to look at it when I'm able to spend time on Contract Configurator. Next week I'm in Mexico City (sorry - not KSP related), and the week after that I'm on vacation. So it may be a bit before I'm able to get into the swing of things.
  17. I get why Arsonide added that from a gameplay perspective to prevent people from farming certain contracts, but I personally don't like it. The "Launch New Vessel" parameter was added into Contract Configurator as a request from a contract author (I forget who). Personally I'd rather have something where there needs to be an "initial" state of on the launch pad and use vessel parameters, but that's really a case by case basis. You might have better luck asking specific contract authors to remove them. Or you should hypothetically be able to write a module manager script to remove them all automatically in your own game.
  18. The intention had been to enhance the Orbit class with methods to generate various orbits and allow that to be an input to the OrbitGenerator (or allow it to be used instead). Unfortunately, that's probably not likely to happen with the amount of time I have for the mod. Right now your best bet is to figure out the various parameters yourself (you can use expressions to provide some randomization there if you want). Why? Only the first page and most recent couple pages are relevant - a new thread wouldn't really change that. And naming it 2018 means I'd have to create another new thread next year.
  19. You'd need to have completeInSequence on every parameter than needs to wait for a previous parameter to complete. If I recall correctly from RP-0, you can also have the duration parameter as a child parameter, and the countdown won't start until the parent is ready to complete.
  20. I assume you mean strategies. Something is likely screwed up - when one fails to load I think it breaks the whole system. I'd need to see KSP.log to comment further though.
  21. None. I think I'd have to see a KSP.log to be able to comment on what's going on here.
  22. This is a known bug - I need to do a release soon to get that fix out, but have been busy for the last little while. I'm out of town this week, so look for something next week.
×
×
  • Create New...