Pathfinding breaks the layout into a grid. Outside of the layout is out of range, otherwise there'd need to be an infinite grid, which would be unmanageable. I wrote a plugin extension to deal with the case where you want to allow a range beyond the "normal" layout bounds.
http://www.blackhornettechnologies.com/ ... oPLUS.aspx
Variable1 = left(Variable1, len(Variable1)-1)
On the image at the bottom there is some small text. One is "Mark forums read".
Pathfinding can take more than a tick, so you can not use 'Every tick'. Use a longer time interval.
You can't set the UID. Just add your own instance variable and assign a number/text. Then you can pick by that number/text.
Just use the 'ctr' value you already have. 'On start of layout', create your car and set the frame=ctr.
(Your Waits are doing absolutely nothing here).
Add the timer behaviour (type=once) and set a random value for the next period when the timer expires.
Sample:
Develop games in your browser. Powerful, performant & highly capable.
Having a quick look at what a ".fon" is, I don't see the value in supporting a Windows 3.x font format, so I'll have to say, no. Sorry.
Computers have a maximum range for storing integers. Javascript is further limited. What are your minimum/maximum numbers? Unless you start at 1, you can probably use a scaling factor to get accurate values.
"Is scored" can never be true as you only set it if it is true! Just move the 'Set text to score' up to event 20.
What you have should work. You probably are safest using fixed GUIDs to sync between two clients.
Are you destroying any initial objects using the container before creating your player "on start of layout"? If the old one is still there, scroll-to will try to incorporate both.
Don't try to treat these as three separate events, they are not. Use sub-events and ELSE to break out the conditions:
On key pressed
(sub)->IsMoving
(sub)(sub)->isLeft -> event 3 stuff
(sub)(sub)Else -> event 2 stuff
(sub)Else ->event 1 stuff