he moves to that and stops.... I use the Move To attribute, but he doesn't continually keep moving after the main actor?

For collision shapes, we are updating the collision shapes for resize just as in the native engine, but the system isn't registering the change. The code is almost exactly the same as in the native en

COLLISIONS

the resizing bug! (if you're curious, for custom collisions, in HTML5, if you put the Collision behavior on one of the actors, then collisions don't work. But if you put it on the other actor you wan

Most of the HTML5 output system is working pretty great, but without the SOUND, COLLISIONS and TEXT working properly, there are some major limitations with what can be done with it.

I have an actor that using keyboard controls can go up and down... i don't want it to be able to go outside of the top or bottom of the given screen. How do I do this? Thanks.

Constrain X position to A*sin(game.time*B )+C

But yes, sadly, my big magnum opus, I cannot export to HTML5, as the issues with that output format prevent that from being viable. My game procedurally generates levels, and therefore the collisions

Fig3: You can see the .game level attributes (game.Count #) and (game.MaxCount)

Change Attribute is a behavior.

wow excellent breakdown! i was initially wondering about doing this with this physics editor https://www.codeandweb.com/physicseditor that program does allow to create multiple collisions within a sin

INDEX and MAX#, and my actors have an ID attribute, but I don't see how/where to "change attribute" in order to assign ID = INDEX. Do you do it inside one of the drop down bars that

What I do is set 2 game level 'integer' attributes: and 1 self attribute in the actor to be spawned;

spawn actors (about 200), each with some unique attributes.

(Quote)

(Quote)

Also, regarding collisions, great to hear you have a lead, and I would really like you to follow up on that, as I believe I reported it one or two years ago (I lose track), and nothing has been done.

I'll poke in here for a minute. As you know, we're busy at work with the online tool and it's really coming along. I know that personally, I'd love to see actor/image/attribute folders in the new tool

on that since we also discovered an issue where collisions are a bit weird and depend on which actor you add them too. I have a feeling both issues are related.

self.Position.Y of the enemy). You would constrain heroX and heroY to the hero actor's position attributes and then have the enemy or spawner actor check.