An interesting poll result, yeah.
It could be made togglable but not cleanly or easily and I don't believe that's the best option here.
Well, since this idea came about as an alternative solution, what better than an alternative solution!
Since people already think the fields go away too quickly, I'll add about a day to the current ones and keep those showing up on radar.
Then I will change the decay behaviour so that any decaying debris field randomly destroys about half the loot, adding the other half to a much larger, much longer lasting, invisible to radar field called something like "Dispersed debris cloud". Ideally I'll do a range check and add any decaying debris from multiple fields to just the one large dispersed field.
It can sit there for a month or so, but only be found by coming across it.
Later on (though this will take quite a lot more work) interacting with these dispersed fields should be more complicated, perhaps an interaction dialog and/or some industry skill checks, with variable loot returned and taking a considerable amount of campaign time to trawl through them, perhaps about a week of searching before you get a loot screen. All that will need to wait for the future mind you, and I hope to implement a basic version of mining (in the sense of: drop off mining crawler, return later) before doing that.
-------------------------- BUG DIAGNOSIS FOLLOWS ---------------------------
Sorry to say Hiigaran, but Tradewinds II is entirely
incompatible with Starsector+. (I updated the initial post to say so a while back, but it's easy not to notice.)
The error you're getting is because Starsector+ has overwritten Tradewinds' plugins and implementation code - and it needs to, because otherwise most of Starsector+'s campaign level features wouldn't be working instead.
Before I do anything else in terms of features, I'm going to put in some work to have TWII's code be a library and then have the mod call that library. Then it should at least be
plausible for Dark.Revenant and other authors of large modpacks to support Tradewinds. It's never going to be trivial though, so I'm not going to actually push for its inclusion or even permission to release my own inclusion patch until I have a 100% guaranteed step by step method for getting it to work together myself that I can put in front of authors. If it's at all a pain, I wouldn't expect most people to want to put in the effort integrating it (there aren't enough cool features yet) but I'm hoping if I do all of the work and make it nice and easy, D.R and others will be okay about conditionally including it or letting me release an inclusion version.
Unfortunately I've been ill lately, which is why you're getting this post about what I plan to do instead of me having actually
done anything about it