Thanks for the messages! Various things...
(1) I think it would be more usable with [version control, any text editor, diff programs, unix utilities, etc.] if it were multiple files e.g. one per script. one per material, one per node possibly even -- by default. Having to even know about "the option" is to me backwards usability, for me and my personal preferences anyway. The files can be in a directory structure like "bundles", down one level in the project, if that makes it look any cleaner (ie. replace the file *.tscn with a folder of the same name, and the individual files inside it)
(2) The "\n\t" etc. inside the *.tscn file on linux show up at literal "\n\n" rather than as any sort of actual newline (example below). I know cross-platform line endings are a nightmare. Git supports doing it automagically across platforms for whatever it is worth for example.
Nothing is a show stopper, it is more about solid end to end usability for software project management.
[subresource type="GDScript" id=9]
script/source = "extends Spatial\n\nonready var kplayer = getnode( \"/root/Spatial/player\" )\nonready var kground = getnode( \"/root/Spatial/grou
nd\" )\nonready var theta = PI # 0 radians is north/up.\n# todo: kinematics to get it on the ground for real\?\nonready var radius = kground.getscal
e().y + getscale().y\nonready var z = kplayer.gettranslation().z\nonready var origin_transform = Transform( Vector3(1,0,0), \\n\tVector3(0,1,0), ...