ATL vs Motion()
Posted: Wed Jul 05, 2017 5:50 pm
So i've been looking up ways to generate visual paths that are not pre-defined, but instead generated as needed. Unfortunately ATL blocks insist on being pre defined and do not support generator expressions. I was recommended this thread in the cookbook as an example of a method of generating custom paths.
viewtopic.php?f=51&t=3977
One of the things i picked up in there is a very useful looking function called Motion()
https://www.renpy.org/wiki/renpy/doc/re ... ons/Motion
However it looks like this is a long defunct and "it may interact poorly with ATL code"
Where possible i want to use the most efficient methods, so using something that may mess up ATL code that is alongside it is not ideal. However i can't deny that it has a flexibility that ATL does not.
Is this a flaw of ATL that makes it inferior to the old way of doing things or am i missing something obvious with ATL?
viewtopic.php?f=51&t=3977
One of the things i picked up in there is a very useful looking function called Motion()
https://www.renpy.org/wiki/renpy/doc/re ... ons/Motion
However it looks like this is a long defunct and "it may interact poorly with ATL code"
Where possible i want to use the most efficient methods, so using something that may mess up ATL code that is alongside it is not ideal. However i can't deny that it has a flexibility that ATL does not.
Is this a flaw of ATL that makes it inferior to the old way of doing things or am i missing something obvious with ATL?