Sure thing, please do so through paypal or send me an email with the same mail that you used to buy the asset. If you are looking for something that does have all of those things, I can also offer you a free code for platforming framework for Unity instead. Its a complete rewrite 5 years later.
Hello, that is correct. ALL moving objects should not move at speeds below a full integer. This is intentional (and could be considered a design flaw). I have a newer, more complete platforming framework for Unity available on my page that fixes this. If you wish to try it, I can give you a free key if you cannot reach your desired results with this older asset.
Update: I tried to recreate your issue with faster platforms and there was indeed an oversight which I fixed. See version 1.6 on the downloads page. Thanks for the tip!
There are several variables that you can use to set sprites accordingly, for example the flip variable indicates which direction (left/right) the player is looking. All the variables you need are commented in the create event of the player.
Touch controls are tricky, I suggest you look up a tutorial on how to implement them. Once you are wiser, you can simply replace the keyboard_check() functions in the movement script with your own controls.
That's really strange. Did you try in a new project? I don't have access to MacOS I am afraid, but can refund your money if you are unhappy and cannot get things working.
I just tried and the answer appears to be no. It seems that slopes are borked entirely with the latest version of GameMaker.... great. I'll put it on the todo list.
Thanks for reaching out. If you look in the script "motion" you will find all the states under the green comments (collapse all regions).
Instead of a classic switch statement, the script uses if statements and calls exit (exiting the code) after performing actions for a certain state.
If you want to use a classic switch statement, just add a switch statement and state variable, wrap the original code in another state that you call whatever you want and voila!
You can write a separate input handler and pass its state as booleans to the motion function. If you manually start overriding stuff things might break :(.
