nightingale

Members
  • Content Count

    4,064
  • Joined

  • Last visited

Community Reputation

3,250 Excellent

About nightingale

  • Rank
    Configurer of Contracts

Profile Information

  • Location Array

Recent Profile Visitors

12,207 profile views
  1. Can you provide a save? From looking at the code, this could only be an experience trait that is not set up correctly. Which either means something changed in stock, or you had a mod that added experience traits and then removed it.
  2. Probably a miss from an overall design point of view. Something to think about if/when I do a balance pass.
  3. KSP 1.8 support is out now. Next time I take a serious look at this mod I'll probably be doing a balance pass - I see a lot of good feedback related to that. Strategia 1.8.0 Rebuild for KSP 1.8.0 Minor typo correction (thanks Galenmacil).
  4. Quick release to fix the incorrect assembly version (download). Waypoint Manager 2.8.1 Correctly increment assembly version.
  5. I can't see the tourist in the picture, but I'll assume he's there. Can you submit a KSP.log file?
  6. Yeah, I realized last night that I messed up and forgot to change the version in the assembly... I may do a new release just to fix that.
  7. Because of the automated system I have in place for CKAN it's hard to go back and fix the compatibility on an old version - unfortunately 2.7.5 is stuck in a state of claiming to not work on 1.7.3 (even though I know people have reported that it works). 2.8.0 *may* work on 1.7.3, but it's not tested/supported - so I'm not going to change it that way either. It's a mess - but time will fix it as people slowly move off of 1.7.3.
  8. New release available here! Just want to give a huge shout out to the KSP devs (especially @JPLRepo and @TriggerAu) - I pretty much only had to make changes related to the Unity upgrade. It used to be that there'd be a whole host of broken things in CC on KSP updates, but there's clearly been a lot of effort in maintaining backwards compatibility (as much as is possible when you have mods that rely on every single little behaviour of KSP). Contract Configurator 1.28.0 Support for KSP 1.8
  9. I don't understand what you mean - Waypoint Manager has no dependencies. Everything in CKAN looks good to me.
  10. First mod update from me in a long time, please enjoy! Waypoint Manager 2.8.0 Recompile for KSP 1.8.0 Fixed NRE when changing scenes (thanks DomiKamu). Workaround for minor stock bug - the Dessert Airfield has the wrong icon (thanks Jacke4913).
  11. KSP 1.8 Update Plans I haven't been around these days, but I'm going to be taking some time to update things for KSP 1.8. No promises on timelines, but here's my list in order of priority. Note that I'm only looking at minor bugfixes and KSP 1.8 compatibility at this time. Waypoint Manager (done) Contract Configurator Contract Pack: Tourism Contract Pack: Field Research Contract Pack: Anomaly Surveyor Contract Pack: RemoteTech Strategia Kerbal Sports Note that Contract Configurator depends on Module Manager, and Strategia depends on Custom Barn Kit. So don't expect any updates on those ones before their dependencies are ready.
  12. I don't spend much time with KSP modding these days, and there's a fair bit of work to be done. It's high on the list of things that I'd like to do if I'm am spending time modding. That being said, I'll be doing a full recompile/bug-fix pass with KSP 1.8 - so maybe after that's done I'll see where I'm at.
  13. New release, get it here! Waypoint Manager 2.7.5 Recompile for KSP 1.6.1 Group auto-generated site waypoints separately from custom waypoints. Make waypoint data visible in IVA (thanks @taniwha). Workaround stock bug that causes the launch site waypoints to be added in duplicate on each scene change (thanks @catonthekbd & @Steven Mading).
  14. Oh yeah, I just checked - it figures out lat/lon based on world position, which is centered on the player (Krakensbane stuff). Out at Ike you're more or less on the same plane, which is why it's only affecting the longitude. I think I'll just bring the tolerance way up to one km or so, and only do the check if the waypoint name matches something in the list of site names. That plus the existing no contract check should hopefully limit it enough.