Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    @MaverickNoob & @Tokamak - Something very odd going on. If you look in the WEIGHTS section for the ContractSystem you can see the stock contracts are all there twice (the excerpt is from MaverickNoob's save, but Tokamak has the same thing): Deleting the duplicated stuff should make it work. Also, note that only the error in my previous post is relevant - the rest is side effects from the ContractSystem lying dead on the road after failing to load. I still have no idea what caused it - you both have Contract Configurator & DMOS in common, so it could be either of those (or a stock problem). I'll continue to investigate.
  2. nightingale
    Here's your error: [EXC 15:43:07.890] ArgumentException: An element with the same key already exists in the dictionary. System.Collections.Generic.Dictionary`2[System.Type,System.Int32].Add (System.Type key, Int32 value) Contracts.ContractSystem.LoadContractWeights (.ConfigNode gameNode) Contracts.ContractSystem+<OnLoadRoutine>c__Iterator80.MoveNext () I'm not sure exactly what is causing this (it's a completely stock error). Can you post up a save file and I'll take a closer look?
  3. nightingale
    That's pretty much what most of them are already.
  4. nightingale
    It's come up before, and for the most part they are spoiler free. For the pyramids, the argument was that it would be hard for the Kerbals to miss them, but I think I'll revisit that for the big update that is currently underway.
  5. nightingale
    Yup, I doubled checked and my original post was incorrect - you don't lose rep for any vessel destruction, regardless of the type of vessel (debris, probe, etc.).
  6. nightingale
    I just released an update, so get that instead. Uninstalling shouldn't have caused lost progress anyway.
  7. nightingale
    Just a quick recompile because it's completely broken in 1.1.3 without this. Bigger update still coming later this week. Download here. ContractPack-AnomalySurveyor 1.4.4 Recompile for KSP 1.1.3
  8. nightingale
    Ah, looks like Anomaly Surveyor is broken! I was going to update it this week for the easter egg changes in 1.1.3 anyway. Until I can get a fix in, I'd either suggest uninstalling it, or at the very least not accepting the Jool monoltih contract.
  9. nightingale
    I think anytime the rep changes there's an entry in the log. That won't help you if it happened in a previous post session though. If the top of my head, the following can give negative rep: vessel destruction, kerbal death, contact failures (specific ones), contact decline, building destruction, strategies. Mods are also able to affect it, but don't have a specific example that isn't already included in the above list.
  10. nightingale
    OMG, I can't believe I've been doing mouse gymnastics instead of this. Now if this works on mobile too...
  11. nightingale
    Can I get a KSP.log file?
  12. nightingale
    If it's what it takes to get 'er done, then I too would like to say I support the above pull request.
  13. nightingale
    @ebigunso - Just to clarify on that, the RP-0 team has the position that it doesn't work with other contract packs due for balance reasons. Contracts packs that have been built without references to specific planets or parts should work in RO (which is the majority of contract packs). So with RO you can get a choice between RP-0 and a bunch of contract packs (which may or may not result in a playable/enjoyable career).
  14. nightingale
    I've been staying pretty quiet in this thread, but I've been actively reading. I won't rehash anything others have said, but I'll make my position clear, which is: CKAN needs to be respectful of authors, regardless of what rights the chosen licenses gives CKAN That is the key issue here. And with this I'm pretty close to de-indexing as well, as this will cause some pretty heavy dependency issues on my end.
  15. nightingale
    Very soon on my to do list is too properly update Anomaly Surveyor for 1.1.3. It'll technically work for 1.1.3 right now, but there's two major issues: 1. Some of the text in contracts and pop ups have tongue in cheek references to broken Easter eggs (like monoliths floating in the air). 2. Some of the ones that were completely broken before don't even have contracts. So look for an update in the next week or so.
  16. nightingale
    +1 on the external HTML if you're trying to make something complex (I just finished redoing my signature using that method last night). The forum stylesheets will make it look a little bit different than what you see if you just make an HTML and open it manually, so I'd suggest heading over to the great forum test thread and copy+pasting it in there to make sure you're happy with it before you update your sig.
  17. nightingale
    8/10 - love the ROFL-copter, but I think it's time for the old forum rep stuff to die. Just finished up new sig, so would be interested in opinions.
  18. nightingale
    I use KSP to make contracts, and I Am Canadian.
  19. nightingale
    Have a look at the RemoteTech and Field Research contract packs, they have a lot of carefully tweaked expressions for Celestial Body selection (including handling for stuff like New Horizons where Kerbin is a moon of a gas giant. In short, rather than trying to base everything off the homeworld and order of bodies, you should use something like this (example is to get a random gas giant): AllBodies().Where(cb => cb.IsPlanet() && !cb.HasSurface()).Random() Also, various planet packs can change so much, so I'd avoid the following assumptions: The HomeWorld is called Kerbin There is a planet called Kerbin (or Duna, or...) The HomeWorld is a planet There is only one gas giant There are gas giants All bodies orbit the Sun The HomeWorld has two moons (or one moon or any moons) I'm sure there's plenty more (and I'm sure I've violated some of the above). The point is that with Kopernicus in the mix, anything is possible, and if something that breaks your contracts doesn't exist today, it probably will exist some day.
  20. nightingale
    AFAIK RP-0 is updated for 1.1.3 - so if there's errors you should report them there (although it's always possible you've uncovered a Contract Configurator bug, too).
  21. nightingale
    No, you need to use the versions of mods built for 1.1.2 if you want to remain on that version. If you're ready to go to 1.1.3, then you need the latest versions of whatever mods you're running.
  22. nightingale
    Everything seems to still be good in 1.1.3
  23. nightingale
    New release here! Strategia 1.2.4 No longer lose reputation bonuses when upgrading/downgrading within the Free Ice Cream I/II/III strategies (thanks ibanix). Bonuses/maluses are preserved when upgrading or downgrading Free Ice Cream. Don't change active contracts when activating Free Ice Cream for the first time (thanks ZachPruckowski). Increased Moho rewards for various strategies (thanks ibanix). Fixed mission requirement in moon probe strategies (thanks ibanix).
  24. nightingale
    Check again - the doco and warning are correct - partModuleType is not supported in the PartValidation parameter. Raise an enhancement and I'll add support for it.
  25. nightingale
    Already fixed that one, it's just in the queue for release. One or two things to check on this one and I'll have a release out (probably tonight). Everything should be fine in 1.1.3 on the current version, regardless.
×
×
  • Create New...