World Wrapping

@danpost Thank you so much! Your 'guess' is proven by this image btw: http://answers.unity3d.com/storage/temp/984-wrapping+world.png

I saw your code now. Very nice solution. Maybe it would be easier to make a new method "whatIshouldDo" (only with a better name) in cutActor, which is used in the act method of cutActor. So the subclasses would use whatIShouldDo", by overwriting it, instead of using the act method. So you dont have to write super.act() everytime. Maybe it's easier, especially for larger scenarios. The subclasses can't use the act method if you make it private, but I am not sure if they would use the act method of Actor instead. It's only an idea, no problem if you don't like it.

Well, you will still have to call whatItShouldDo every act cycle, so it would just be another way of saying super.act(), but then with your own addition. This would not be very hard for someone to add himself/herself, so I don't think it's necessary in this demo (although, if many people want it, I'll of course implement it).

I didn't meant it that way. whatIShouldDo() is supposted to replace the act method. It should be placed in cutActor, but it should be empty. The act method in cutActor should call it. So the subclassses will never use act. They use whatIShouldDo(). So the act method of the sublclass will be used every act, but because they haven't any the act method of the subclass (cutActor) will be used, which calls whatIShouldDo().