thanks cresco
python currently ignores picking and just applies actions to the first object
so if you had a condition
on collision with Sprite2
----python : Sprite2.x =50
it wouldn't apply to the sprite2 in the collision, it would apply to the first instance of sprite2, no matter what
the upcoming (not yet released) version of S
allows you to loop your python actions through every picked instance of an object
thus fixing this problem of python
the only other python issue I know of is that you can't use system actions
this would be an easy fix, but more time consuming than I can manage at the moment
finishing s is on the backburner for me right now, because my dayjob is unstable, and I need to get my game far enough along that if something happens with my job it isn't impossible to work on in short bursts
however, due to all the python talk on the boards lately, I'm going to probably release the In Between Version I'm currently working with, that has the python fix, and just warn people about the other new (nonpython) features that aren't fully integrated