As you probably already know, Blender comes with an embedded Python interpreter, which allows it to run scripts written in that language. These scripts can use the Blender Python (bpython) API to access the program's internals and greatly expand Blender's functionalities.
There is a page here where users can read about and download many scripts. Besides that, script writers usually announce and discuss their creations at the scripting forums at blender.org (API development) and specially elysiun.com (for users).
There were a few important issues that had to be solved before we could properly ship some scripts with Blender itself. One was better integration with the interface. That was reached and 2.32 and 2.33 already came with a few import and export scripts, as a first test.
The next limitation was that bundled scripts couldn't use important Python modules (code libraries) like 'os' and 'math', because these and others required full Python installations in some or all supported platforms, depending on the module. The new release for Windows comes with the most important non-builtin modules as an extra compressed package ready to be used. Since for all other platforms Python can basically be considered a default system component already, there are many more modules available without the need for a full Python install now.
Thanks to that, Blender 2.34 comes with a much expanded set of scripts. And this is only a start, the real test. The bundle is a mix of old and new, complex and simple scripts. With time and feedback from users we can make updates, following some basic guidelines and using newer bpython functionalities, to better integrate them in the interface.
Even with well tested code, it's still possible that something does not work as you expected. It can be a bug, but can also happen because you need to know something that you don't about how to use the script or because it is still an early and incomplete version with limited capabilities. Whatever it is, the recommended path is this:
For 2.34 we have worked mostly with updates and additions offered to us at the bpython mailing list. This was a necessary step to get experience and come up with a widespread, more organized way to support and expand the bundled scripts set for future releases.
Better access to script documentation is one of the planned additions soon to be implemented.
File->Import and File->Export menus are the first example of how much we gain with scripts. The options here simply exploded when compared to the few "hard-coded" ones Blender supports internally. And if the one you are looking for is not here, note that there are many others available. Try the scripts downloads page, forums or an online search to find them.
The already available options are still there, like VRML2 export by Rick Kimball (with help from Ken Miller and Steve Matthews) and AC3D. Chris Want added STL import and export directly to the program, in C. Counting old and new convertors plus hard-coded ones, Blender 2.34 comes with 19 importers and 19 exporters.
Paths import was a last minute addition and will be improved after 2.34, so remember to check for updates on forums. They are already useful, but being early versions we will give more information here. Jms made some notes about implementation and the current limitations, which are described below:
The scripts first transform each path format to GEO/Videoscape .obj, then load it directly to Blender (using the new Blender.Load bpython function).
The first three are available from the Help menu.
The Mesh menu, available from the 3d View while in mesh edit mode has a Scripts submenu now, with very good tools. Python coders should look at the bpython reference doc for info about the Window.EditMode() function, necessary for scripts that modify the active mesh. The scripts below were updated (when necessary) to use it and one of the benefits is that their changes to an active mesh can be undone by the "u" shortcut just like hard-coded tool operations.
There is also a Scripts submenu at the 3d View Object menu, currently with tools to automate some repetitive tasks, one of the benefits brought by scripting.
Scripts in this group are directly in the UVs menu of the UV/Image Editor window. Good tools here, too.
This menu, only present in the Scripts window, is the place for the more complex bpython plugins, that might need more space for their guis or can't be defined by another single category.
For 2.34 the only Wizard shipped with Blender is Kloputils by Carlos López (klopez), a very useful set of objects copying, aligning and modifying tools. Carlos wrote help docs in English and Spanish that demonstrate what the script can do, they can be found in a thread at the elysiun.com Python and Plugins forum or with a simple online search.
elysiun.com scripting forums;Let's reiterate that the included scripts represent a very good but still small fraction of what is available online. There are many useful scripts out there, even some very impressive ones. As always, the scripts download page and the forums are the recommended places to find out about them.
Now go play with the scripts, hunt more online and maybe try your hand at a little bpython script writing! The new reference guide should be available from the Documentation section. But first ...
We want to thank all script writers for their contributions, hard work and support. Really, you have made Blender 2.34 a considerably better release.
If you find any mistake or omission in the credits or information above we will be grateful to know about it.