What do I edit to make experiment data transmittable again?

[Tassyr]

Yes, I know that Squad wanted to prevent "Data Spamming." Which is actually admirable. The problem is, say I'm in orbit around, oh, the sun.

Sending six probes up there to take that dang thing's temperature doesn't make a lot of sense to me- just glancing at a thermometer doesn't seem like it should cut me off from all data the -second- time, should it?

Or perhaps, as I was considering, I could make 'advanced' parts that can double or triple transmit before they 'fry.'

But I can't seem to find the 'once and done' variable. Anyone got any advice?

MODULE

{

name = ModuleScienceExperiment

experimentID = gravityScan

experimentActionName = Log Gravity Data

resetActionName = Delete Data

useStaging = False

useActionGroups = True

hideUIwhenUnavailable = False

xmitDataScalar = 0.4

dataIsCollectable = True

collectActionName = Take Data

interactionRange = 1.2

rerunnable = True

}

This is all I can seem to find about sensors- in lieu of finding an actual solution, would kludging together multiple of these modules into advanced sensors work, perhaps?

Edited May 7, 2014 by Tassyr
Apparently there's no "Spoiler" Tag I can use to hide a ton of code. Sorry. :(

[Seret]

You can spam sensors like the thermometer, you'll just get reducing returns. It's only the goo pods and the materials bay that are one-shot.

The example you posted says:

rerunnable = True

[Tassyr]

You can spam sensors like the thermometer, you'll just get reducing returns. It's only the goo pods and the materials bay that are one-shot.

The example you posted says:

rerunnable = True

I swear I got "no" return on temp sensors. I think I have to check again. Man do I feel like an idiot...

[Zeroignite]

My solution was to give reusable experiments (like the thermometer) 100% transmission.