[SUGGESTION] A large number of minor suggestions

Hello, I have a number suggestion`s, to improve existing behavior`s. I apologize in advance for my English - I write through Google translator .

In topic summon Ashley or Tom)))

"Bullet behavior":

• Add "Bullet conditions" called "For each X distance traveled", where X - the number you specify. If you want to make some regular activities related to the distance traveled, this condition will be indispensable. Now for such action is necessary to establish a separate variable and perform a number of checks, which is not very convenient. In example, i need to reaction at 40, 80, 120 and 160 distance traveled - and "For each 40 distance traveled" save me))

"Car behavior":

• Add "Car conditions" called "For each X distance traveled", similar to analogous at "Bullet behavior". Accordingly, it is also necessary to add "Car properties" called "Odometer", which can have two positions - "Only forvard" or "all", and considers distance traveled. As well, similar to the "Bullet behavior" to add "Car conditions" called "Compare distance travelled".

"Drag & Drop":

• Add "Drag & Drop properties" called "Drag point", which can have two positions - "Origin" or "Touch". This will define how sprite pin to touch point - by Origin or with offset to touch point.

"Sine behavior":

• Add "Sine expressions" called "CycleCount", which will count the number of whole cycles have passed since the start of sine.

"Platform behavior":

• Add to "Platform conditions" called "Is moving" and to "Platform conditions" called "On moved" additional conditions "Right", "Left" or "Any", so that it was possible to separately respond to these actions.
• Add "Platform conditions" called "If simulate control" with additional terms "Right", "Left", "Jump" or "Any".

add to post

"path finding"

make it so you can not just set path costs but also one direction in the path finding

"real time"

pull clock time from computer

add to post

"real time"

pull clock time from computer

What about just using the excellent system date plugin to get the time?

Up request... Still I would like (if it is not difficult and does not distract from the important things) to hear a comment from Ashley or Tom - does it make sense to write on anything, or so clear but "no time" or "this is impossible"...

> add to post

> "real time"

> pull clock time from computer

What about just using the excellent system date plugin to get the time?IMHO, official plugin & behavior better then non-official...

IMHO, official plugin & behavior better then non-official...

Even better would be if the most used plugins would be included in official releases as-they-are... I had some boring time in switching my project from rexrainbow's function plugin and official function plugin :)

Another "up" post... Still no answer, still wait it... Or discuss for "need/not need" ))

> IMHO, official plugin & behavior better then non-official...

Even better would be if the most used plugins would be included in official releases as-they-are... I had some boring time in switching my project from rexrainbow's function plugin and official function plugin :)

Totally against that, I still use rex function, hash plugin and not the official one cause I made very many changes with the plugins so It would destroy much if you make it official and update it with every new release.

It?s perfect like it?s at the moment, they make new plugins so every one can decide which one he wants to use.

add:

different colours to different parts of a text object - nice suggestion, imho.

scirra.com/forum/suggestion-multiple-colours-One-text-Object_topic76475.html

"Bullet behavior":

- Add "Bullet conditions" called "For each X distance traveled", where X - the number you specify. If you want to make some regular activities related to the distance traveled, this condition will be indispensable. Now for such action is necessary to establish a separate variable and perform a number of checks, which is not very convenient. In example, i need to reaction at 40, 80, 120 and 160 distance traveled - and "For each 40 distance traveled" save me))

• if DistanceTraveled = floor(X)*
• trigger the condition once

~ Do the actions

*floor if you want it to trigger when the game starts and ceil if you want it to not trigger when the game starts

"Sine behavior":

- Add "Sine expressions" called "CycleCount", which will count the number of whole cycles have passed since the start of sine.

CycleCount = -1

• If ( CyclePosition = 0 )

~ Add 1 to CycleCount

It's just about workarounds ...

You could always set a condition, is on floor and right arrow pressed to grab the 'moving right' one but otherwise, would be nice to see some of these implemented!

condition/compare: distancetravelled % 40 = 0

Will give you "for each distance travelled", % means modulus.

I know that my desired result can be achieved through local / global variable and opportunities of the program. But I have to add to the proposed improvements will significantly optimize the code "for reading and writing." Although actually be the same, but the event will be smaller, and the code will look neater.

In the case of "for each distance travelled", where the condition must be fulfilled (for example) 100 or more times - to prescribe a range (a range that is necessary to write, as at 60 FPS and less distance will not always clear) - it's a hell of hemorrhoids.

Most of these can already be done with events :P

The thing I would like to see most with bullet behavior, or any of the movement behaviors, isa better conection between its movement and and angle, and more support for diangle movement. As it standsright now the system is great for either side scroller or ootherwise 4-direction. If you want diangle section for anything else you need some hefty formulas., and variables. Also determining AI movement and angle is even worse.