There is only one script file allowed, but within that script file you can have as many functions (what you're probably referring to as "scripts") as you like.
That said, the more functions included, the more get loaded and you can bloat a module pretty fast. It's generally a good idea to start breaking down huge files into smaller components. Then you create an animation script for your models that imports only the files that are needed for that model to work. This methodology allows you to reuse code without wasting memory by making every single model load up a bunch of script functions it probably isn't using. Incidentally, this applies to all the script events, not just animation.
Pro tip: When you first start out it's tempting to move every single function into its own file, but as I discovered that will quickly become an organizational and maintenance nightmare. A good middle ground is to create files that contain a few closely related functions in a group. Ex: One file for your grappling functions, another for graphic effects, and so on.
DC
