Sorry for the slow response, I have been thinking about it since you tagged me but barely had any time to actually sit down and mess with it (getting married in 4 weeks + work etc etc). I managed 30 minutes last night but spent that writing a logging function.
For the sake of discussion, I'll just think out loud.
The tunables are just loaded in to variables. So an individual mod could update that variable with new values it loads from it's own XML file (or be hardcoded in the PYO).
But one issue is that you'd need to know where in the Python code you'd want to apply that change - and it may vary, so it wouldn't be a case of quickly editing a template.py as such.
The other thing I'm not certain on, is if the variables which hold the tunable are static or not. If they're static, then you apply the change once and it would affect every instance (provided it does not reload the tunable). Otherwise you'd need to do it at startup, and everytime an object/sim was introduced - which could be quite annoying and you'd be reliant on callbacks for those events.
I'm also not sure if every piece of code defines it's tunables when setup (class definition)- if it was called inside a function you might not be able to update it in time without overwriting that function - and you'd want to avoid doing that as it'll cause just as much of a conflict issue.
