Scripting Caveats should be listed and accounted for in the documentation

[two-one-five]

Caveats with modeling and development burn countless days from development time for anyone uninitiated, and when a person moves on that mindshare is lost. Every new person has to start over and learn simple solutions to very wasteful problems.

Therefore, for more common caveats and gotchas... those should be listed in the APIDocs and/or in these docs if possible. This will help new users catch a problem before it becomes a time sink.

[digisomni]

e.g. userData won't get applied if you put too many bytes into it.