> Whenever possible, can you please make sure to make your changes backwards<br>> <br>> compatible, so the scripts don't break?<br><br>One of our goals has been to keep backwards compatibility (at least for a while).<br>
<br>Right now the new API does not break any scripts (at least it shouldn't). All the functions that have been replaced have been left in, but show a deprecation warning when used.<br><br>As for returning the object reference as opposed to the name shouldn't break scripts (at least not much). Most (if not all) the methods and properties that use the name of the object can also use object references. So, in cases where someone uses something like<br>
<br>ob = act.getObject()<br>act2.setObject(ob)<br><br>This would still work. Also, it would be properties that would be changed (well, mostly added as most of these properties don't exist). This means that the old methods would work the same way (save the deprecation warning), and it would be the property that would now be an object reference instead of a name. There are going to be a few methods left that return objects (I'm not sure if it's by name or reference) which will not have properties.<br>
<br>Also, the deprecation warnings can be turned off via an option in the Game menu (this is already there) and through blenderplayer with -g ignore_deprecation_warnings = 1 (also already added).<br><br>--Mitchell "Moguri" Stokes<br>