Then, when this kind of collision happens, the 1st actor will refer to the Hero and the 2nd actor will refer to the Button. Regardless of which Event you pick, you’ll typically see a block similar to this.ġst actor always pertains to the first actor in the “sentence.” The same goes for the 2nd actor. We support the following collision events. For example, if a Fireball crashes into Mario, Mario will die. By "handling", we mean responding to collisions with logic. Just check this box in the right-hand pane of an Actor’s Collision Page to make a certain shape a Sensor.
Sensors are special kinds of shapes (a yes/no flag on any shape to be precise), in which an Actor does not physically collide with another Actor, but still detects the collision. What if you want to detect collisions, without the shapes actually colliding? For example, in Tower Defense games, the towers shoot at targets that come into range. In this example, we’ve made an “L” shape using 2 boxes. You can place an arbitrary number of these shapes, in order to form more complex ones. (For Polygons, only convex shapes are allowed!) Stencyl supports 3 kinds of collision shapes: Boxes, Circles and Polygons. For each Animation state, the Actor can have different collision bounds.įor example, if a character is standing, he may be taller. They may be useful if you want a quick way to designate an actor as "non-colliding" ShapesĪs we talked about in the Animations section, Actors can take on different Animation states. Default groups cannot be edited or removed.īy default, Doodads and Regions never get involved in collisions. You can set an Actor's collision properties, and specify the group it belongs to, in the Properties page of the Actor Editor.Įvery Stencyl game starts out with a default set of Groups to help you get started. Next, click the Groups button (shown below), and you'll see a dialog that shows the Collision Groups in your game, the green Create New button that lets you make a new Group, and other settings. Click the Settings button to open the dialog. You can set up Groups in the Settings dialog. Conversely, collisions are ignored between groups that are not set up to collide with each other. Groups tend to be named after certain classes of Actors, such as “Players” and “Enemies.”Ĭollisions happen between groups that are set up to collide with each other. Groups are arbitrary collections of Actors. However, what if you only want certain collisions to happen? For example, if any enemy shoots a bullet, the bullet should only collide with the player, not other enemies. More Collision Handling (Sides, Groups, Points)īecause Stencyl is powered by Box2D, collisions happen automatically, as if every object existed in “real-life.” For the default cases, no action is required on your part to make collisions happen.
I did not change the location of the files either, so that should not be the problem either. Currently, I have not found a solution to this extremely frustrating program, as I checked to see that the settings of my Tiles shared the same settings as the Tiles in the sample RPG game, so I really cannot figure out what the problem is. Instead, the screen was a blank white with red pixels scattered all over. Another more major problem was that when I was happy with my arrangement of the Tiles in a Scene, as soon as I tested the game in a Flash player, the Tiles were not visible. All I had to do was create a new layer, and the Tiles could be overlapped. I learned that the problem was that I was working on the same layer.
This caused me some trouble when I was arranging Tiles in a Scene, as when I wanted to layer certain Tiles over another, there would be some very distracting white spaces. One of my first problems was that when I imported a Tileset (with some Tiles that had transparent backgrounds, which when I double-checked on Photoshop, found to actually be transparent), some Tiles would not have a transparent background and instead had a white background. I found Stencyl to be quite confusing and not very beginner-friendly, so I honestly encountered quite a few problems.
0 kommentar(er)
