unfortunately that's a blender thing - out of our reach
The 1.0.0 release does contain a wizard that sets the bounds on all selected objects activated and to static triangle mesh though. its under Scripts->Wizards->PyPRP->Assign default bounds to selected objects
One day I ran through the cleft for the fiftieth time, and found that uru held no peace for me anymore.
Currently in the 1.0 plugin, the only way to specify that an object can block the camera is by creating an AlcScript for the object and adding the line physical.campassthrough: false
Could you also support a logic property of type boolean (named "campass") that does the same thing? That way, it will be even easier than it was to specify via the col_flags5 property.
The alcscript property is for explicitly disabling camera blocking.
And, btw, the internal alcscript system for physical meshes is probably going to change a little, and current alcscript properties, and potential future logic properties will be easily processed by a quickscript. Thanks for the tip
One day I ran through the cleft for the fiftieth time, and found that uru held no peace for me anymore.