Made everything a bit more loose rather than pin-point timing. (:
|
![]() Sep 18 2011, 6:48 am
|
|
:P nice, movement looks soo smooth.
|
Are you using Forum_account's Sidescroller? If not, you might be wasting your time.
|
Nope, made my own. (:
I don't like to depend on other people's libraries unless they work exactly how I think they should. |
Well, it looks exactly like the Sidescroller "3.0" demo (with low gravity and "slow" movement) mixed with a slightly modified "shooter" demo. I'm sure you can modify it to also handle your transitions and edge wraparounds as well.
|
Welp. It's already done and I know exactly how it works and programming it didn't take long at all (this was just a modification on the original movement with less traction).
|
Kaiochao wrote:
Well, it looks exactly like the Sidescroller "3.0" demo (with low gravity and "slow" movement) mixed with a slightly modified "shooter" demo. I'm sure you can modify it to also handle your transitions and edge wraparounds as well. I like to wait for people to finish things so I can then re-create their creation using a simple combination of demos from my libraries. I hardly ever get the chance to do this because people don't finish things or even make enough progress to make it worth my time. Chris Gayle used to blog about a project of his quite often and all the progress he ever showed could have been accomplished in a few minutes using a library. Aside from making you able to accomplish more in less time, using a common library means that you can more easily share your work. If someone says "hey, this effect is neat, how'd you do it?" there's no guarantee that your implementation of a feature will play nicely with that person's existing project if you implemented it completely from scratch. If both developers are using the same library as a basis it's much easier. |